Project records and responsibilities
Create projects and tasks, assign the people responsible and review work by project. Access checks keep authorised teams within their company and project scope.
SiteFlow Features
Keep project records, daily reports, materials and approvals connected. Give each next action an owner and the context to review it.
From the field.
To the next decision.
Record what happened, give the next action an owner and keep the project context available for review.
Daily reports from the field
Choose the work date and project, record site notes and manpower, and track the report review status. Reports describe the recorded day; they do not verify progress automatically.
Materials with a movement history
Record receipts, issues, returns and transfers against projects and storage locations. Review the quantities and decisions with their original movement records.
Snags, inspections and approvals
Give a defect or inspection a responsible person and follow its status. Record review decisions with the supporting evidence before treating work as complete.
Files and client reporting
Keep project files private and prepare authorised exports for the intended audience. File scanning and supported report formats depend on the configured workspace.
Connections with a defined scope
Approved API access and signed webhooks support agreed connections. A listed capability is not a claim that an external provider is connected.
Daily site report
A clear record of the working day.
- Project
- Demonstration site · Block A
- Reporting date
- Recorded by
- Example field engineer
Today’s site notes
Level 2 preparation completed. Delivery access needs coordination before the next concrete pour.
- Manpower
- 12 people recorded
- Site issue
- Confirm delivery access
Next step
Review and update the draft with your project team. Saving a draft does not mean it has been approved.
Questions about this workflow
Which features need deployment setup?
Private storage, malware scanning, mail, payment processing, queues, monitoring, backups, and a supported PDF renderer require deployment configuration before live use.