Owner
Access: weekly pack, issue register, decision register, evidence index and archive.
Limit:
no operational site control unless agreed.
Data, access and record governance
Different parties see different records.
Access should be narrow by default. Active deployments receive a project-specific gateway or access route.
Access by role
Adviser
Access: owner-approved records needed for reporting, decisions and review.
Limit:
access according to distribution scope.
Contractor / project team
Access: gateway, acknowledgements and record areas relevant to their role.
Limit:
no private owner records unless explicitly shared.
Visitor
Access: check-in and acknowledgement only where required.
Limit:
no project archive access.
LSS operator
Access: operational record setup, capture, classification, reporting and export.
Limit:
bound by defined access and retention rules.
Adaptable site notice wording
This project uses SiteWorks to record attendance, site acknowledgements, project notes, photographs, issues, decisions and reporting records for defined project-control purposes. Records are used to support owner-side visibility and project reporting. Records are not used for covert surveillance. Access is role-based and limited to relevant project stakeholders. For privacy or project-record questions, contact info@lsscoltd.com.
Purpose of collection
Records are collected for owner-side project control.
A live deployment should define why records are captured, who can access them, who receives weekly packs, how long records are retained and what archive/export is required.
| Data area | Purpose | Control position |
|---|---|---|
| Names, organisations and roles | Identify authorised project participants and attendance records. | Role-based access. |
| Check-in and check-out times | Maintain an attendance ledger for the project record. | Project-limited use. |
| Site-rule or risk acknowledgements | Record that a defined acknowledgement was presented and confirmed. | Not a substitute for competent health-and-safety management. |
| Photographs and documents | Evidence works, issues, completion items, access constraints or project status. | Captured for works evidence, not worker monitoring. |
| Issue and decision records | Track open items, required actions, outcomes and owner/adviser decisions. | Access limited to relevant project stakeholders. |
| Weekly reports and exports | Create a forwardable owner-side record and archive. | Distribution list agreed before deployment. |
Transparency
Contractors, consultants and visitors should be told what SiteWorks records before use.
Necessity
Only data required for the project-control record should be collected.
Proportionality
SiteWorks should not be used to create excessive or covert monitoring.
Role-based access
Owners, advisers, operators, contractors and visitors should only access records appropriate to their role.
Retention
Records should be retained for a defined project period and archived or deleted according to the agreed project position.
Professional boundary
SiteWorks supports record keeping. It does not replace statutory dutyholders, legal advice, building-control approval or competent professional advice.
Controller / processor position
Define this before deployment.
The engagement should confirm who determines the purpose and means of processing, who acts on instructions, who receives reports and who controls retention/export. This is project-specific and should not be inferred from the website alone.
Minimum deployment record
- Project purpose and record scope.
- Owner/adviser distribution list.
- Access roles for owner, adviser, contractor, visitor and operator.
- Retention and archive instruction.
- Escalation contact for privacy or project-record questions.
- Site notice wording approved before gateway use.