Turnover packages
Hand over the work with the proof already inside.
A construction turnover package is more than a PDF. RTI assembles checklists, photos, signatures and a tamper evident hash chain into one handoff.
- Approved inspections only
- PDF and CSV from one record
- Each approval hash-chained
Handed a verification package? Check its chain yourself, in your browser, nothing uploaded.
What goes wrong when closeout is rebuilt at the end
The week-before scramble
The binder is pieced together from photos, texts and memory just before the owner walks.
Proof apart from the decision
The approval lives in one place and the photos in another, so nobody can show which photo backed which sign-off.
Nothing to show it is unchanged
When a record is disputed later, there is no way to show it is the one that was signed.
With RTI
- Assembled as the work happens
- Each approval carries its proof
- Approved answers sealed and chained
RTI builds the record as the work happens, so the package is a snapshot of what is already proven.
Everything the handoff needs, already assembled.
- Cover sheetProject, scope, inspection point, date range, and the final approval status, all machine-stamped, not typed from memory.
- Checklist responsesEvery question, answer, and N/A reason captured exactly as the crew submitted it. No lost rows or manual copy-paste.
- Photo evidenceTimestamped photos tied to each checklist item, geotagged when geotag capture is on, so the proof matches the work, not the week after.
- Signatures & approvalsQA/QC signoff, owner acceptance, and any rework approvals, each linked to an authenticated user and a single record.
- Tamper evident audit statementEach inspection’s answers, status and review decision are sealed with SHA-256, and each approval is chained in the activity log, so a change after sign-off shows.
- PDF + CSV exportA branded PDF for the owner and a CSV for your own systems, both generated from the same underlying evidence.
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.
Gate
When the crew submits, the Photo Gate re-counts every required item and photo on the server. Short by one photo, the inspection stays a draft.
Review
Submissions land on the review board, where QA/QC managers approve them or send them back for rework. Each action becomes a record in the audit chain.
Chain
Each inspection’s answers, status and review decision are sealed with SHA-256, and each review decision is written to the company’s activity log, linked to the entry before it, so the chain can be checked at any time.
Hand off
The approved inspections are bound into one package, with the cover, the checklists, the photos, the signatures and the audit statement.
Why it holds up
- The proof is not stored separately from the decision. A checklist response without its photo cannot be submitted, so it cannot be approved.
- Each approval is written to the hash-chained activity log when it is made, and the package lists each inspection’s record hash.
- So a dispute comes 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
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 timestamped, geotagged when geotag capture is on and 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 geotag capture is on and the device grants permission
- Submissions blocked until photo requirements are met
- Each approval is sealed and chained in the activity log
Three handoffs it covers
Use case 1
One category, ahead of closeout
When every panel on the job is approved before the rest of the work, a package filtered to that category is built and handed over on its own.
Use case 2
The owner signs off
When the owner’s rep opens the project in the client portal, they review the approved inspections, download the package and sign off there.
Use case 3
A dispute after closeout
When a finished unit is questioned months later, the package shows the photo, the approval and the time behind each item.
From approved inspections to a handoff
Approve the inspections
QA/QC managers approve inspections on the review board. Only approved inspections go into a package.
Build the package
In Reports, choose Turnover package, the project and the dates. From the review board, the package follows the filters on screen.
Hand it over
Download the PDF and the CSV, or share the project in the client portal, where the owner can download it and sign off.
Keep the proof checkable
A manager can download the verification package from Activity at any time, and anyone handed it can check the chain on the verify page, in their own browser.
What it doesn’t do
- It does not certify the work. The package documents what was inspected and approved; the AHJ or the licensed professional on the job accepts it.
- It holds approved inspections only. Anything still in review, or sent back for rework, stays out until it is approved.
- It records where a photo was taken only when geotag capture is on and the device grants location.
Questions about turnover packages
4 answers
- What exactly is in a turnover package?
- A cover sheet, then every approved inspection in scope: its checklist answers, every required photo with its timestamp (and its location when geotag capture is on), and the electronic signatures that approved and accepted the work. It ends with an audit statement that lists each inspection’s record hash.
- Can I export a package before the whole job is done?
- Yes. A package can be built at any time from the approved inspections in a project, for a date range, or from the review board filtered to a category, a submitter or a search. You don’t have to wait until closeout to hand over a complete, signed record.
- What makes a package hold up in a dispute?
- Each required photo is attached to its checklist item and timestamped, with coordinates when geotag capture is on and the device grants location. Signatures are tied to an authenticated user and a specific record. Each inspection’s answers, status and review decision are sealed with SHA-256, and each approval is chained in the activity log, so a change to them after sign-off is detectable.
- Who can download or sign a package?
- Members with the export permission, admins and QA managers by default, build and download packages. Reviewers with approval rights sign approvals, and a client you grant a project downloads the package and signs off in the portal. Portal accounts are free and see only the projects you share.
Hand over a package that proves itself.
Run one walk, approve it, and export the turnover package with its hash chain and signatures in place.
30-day trial · No card required