Progress Claim and Defect Tracker
Field photos attach to project, block, level, and unit records so claims and defect packs assemble from structured evidence.
The problem
Completion photos land in group chats without unit context. QS staff spend days matching images to locations and rebuilding evidence packs before a progress claim or defect report can go out.
Implementation
Structured capture: foreman selects project → block → level → unit before upload. Photos and defect notes sit on site_location and defect records; payment_claim outputs pull from that evidence.
Workflow steps
- Foreman picks the exact unit location before capturing completion or defect photos.
- Evidence stores against the site record — not a shared folder or chat thread.
- QS generates progress claim or defect report outputs from linked records instead of manual assembly.
Expected result
Earlier claim submission (shorter billing cycle), fewer re-keys between field and office, and defensible evidence packs when disputes arise.
Why this works in Norbital
Each step reads and updates the same records. Forms, approvals, automations, and reports do not need separate data copies.