Data and access governance
Define purpose and visibility before capturing live records.
Each SiteWorks deployment requires a project-specific decision on data purpose, roles, photographs, distribution, retention, exports and deletion.
| Area | Required project decision | Boundary |
|---|---|---|
| Purpose | State why each record category is required. | No speculative or covert collection. |
| Access | Define owner, adviser, contractor, visitor and operator permissions. | Users see only what their role requires. |
| Photographs | Set locations, categories, exclusions and approval route. | Avoid unnecessary personal or occupant data. |
| Distribution | Name report recipients and export routes. | No uncontrolled forwarding list. |
| Retention | Agree active period, archive and deletion approach. | Retain only for the agreed purpose. |
| Professional use | State how records support the contracted workflow. | Not statutory certification or professional advice. |
Initial enquiries should contain minimal data.
Do not send access credentials, worker lists, client files or live project evidence until a secure route and data purpose are agreed.
