From site walk to client proof.
ContractProof is opinionated: a published checklist is frozen, a failing answer needs evidence, and a report revision cannot be rewritten after approval.
1. Configure once
Create customers and sites, then publish a checklist version. Required items, pass/fail/NA answers, critical flags and photo-on-fail rules are part of the template.
2. Inspect on site
Start an inspection against a site and the published version. Answers are saved as a draft; submitting validates required items and photo rules. The inspection freezes the site identity and checklist snapshot at submission.
3. Close the loop
Every failed item creates a corrective action. The assignee uploads correction evidence; an owner or QA manager verifies it. Reopening is owner-only and clears the closure record.
4. Approve and share
Approval creates a numbered report revision with a frozen snapshot. The PDF is generated server-side. A share link can be revoked and stops working on the next request.
5. Keep the history
Removing a member does not delete inspections or reports. Account deletion removes access and preserves the historical user identifier. Organization closure disables access and revokes links without purging records.
What it deliberately does not do
- No client portal, billing automation, AI extraction, payroll or CRM.
- No automatic evidence purge — closure and legal hold are separate from deletion.
- No offline sync guarantee. Draft buffering exists; field testing is pending.