Turnover packages
Hand over the work with the proof already inside.
A construction turnover package is more than a PDF. RTI assembles the checklist, photos, signatures, timestamps and a tamper-evident hash chain into one signed handoff — ready for the owner, GC, or inspector of record.
What a package includes
Everything the handoff needs, already assembled.
Most closeout packages are rebuilt from photos, texts, and memory the week before the owner walks. RTI builds the record as work happens, so the package is just a snapshot of what's already proven.
Cover sheet
Project, scope, inspection point, date range, and the final approval status — all machine-stamped, not typed from memory.
Section 01 of 06
Checklist responses
Every question, answer, and N/A reason captured exactly as the crew submitted it. No lost rows or manual copy-paste.
Section 02 of 06
Photo evidence
Geotagged and time-stamped photos tied to each checklist item, so the proof matches the work, not the week after.
Section 03 of 06
Signatures & approvals
QA/QC sign-off, owner acceptance, and any rework approvals — each linked to an authenticated user and a single record.
Section 04 of 06
Tamper-evident audit statement
A SHA-256 hash chain binds every record to the one before it. If anything is altered after sign-off, the chain breaks.
Section 05 of 06
PDF + CSV export
A branded PDF for the owner and a CSV for your own systems, both generated from the same underlying evidence.
Section 06 of 06
How the evidence is assembled
Photo-gated in the field, chained in the backend, signed in the portal.
Capture
Crews scan the QR code on the inspection point and walk the checklist. Photos are required where the checklist says so, and submission is blocked until they are attached.
Gate
The Photo Gate checks every mandatory item and the minimum photo count on the device before it can leave. No photo, no submit — enforced server-side.
Review
Submissions land on the Kanban Review Board. QA managers approve, reject, or request rework. Each action becomes a record in the audit chain.
Chain
Approved records are hashed and linked to the previous record for that company. The result is a chain you can verify at any time.
Hand off
When the work is ready, the owner or client signs in the portal and the turnover package generates itself — PDF, CSV, signatures, and audit statement included.
The proof is not stored separately from the decision. A checklist response without its photo cannot be approved. An approval without its hash-linked record is not part of the package.
That means disputes come down to a signed, timestamped, photo-verified record instead of a hallway conversation.
Unit 305 — Kitchen Rough-In
RIV-A-F3-305
- StatusApproved
- Submitted25 Aug 2026 · 14:32 MDT
- Approved byM. Chen
- Photos4 attached
- Location40.233, -111.659
Evidence hash
a4f7c2…9c21 → b81d05…4e77
Photo-verified evidence
A photo is not extra paperwork. It is the proof.
In RTI, every required photo is attached to the exact checklist item it proves. It is time-stamped, geotagged when the device allows, and reviewed in context before anyone can approve the work.
That means a rejection comes with the missing photo attached, not a vague note. And an approval means the QA manager already saw the proof.
- Mandatory photo counts set per checklist item
- GPS coordinates captured when permission is granted
- Submissions blocked until photo requirements are met
- Approved photos become part of the tamper-evident chain