Review the model, not the PDF

An approving authority's work is constrained by the form of what it receives. A ground investigation arrives as a report; a cost submission as a spreadsheet export; a design as a drawing set. Each is a snapshot, hand-assembled from richer data the submitter holds, and each question the reviewer asks costs a round trip: request, reassemble, resubmit.

The snapshot tax

Snapshots do not just slow reviewers down. They hide the very things review exists to catch. A PDF of cross-sections cannot be interrogated where the sections were not cut. A summary table cannot reveal the anomalous test result that was smoothed into an average. The reviewer sees what the submitter chose to show.

What read-only access changes

• The reviewer rotates the ground model, cuts their own sections, and inspects the borehole that concerns them — without a request letter.
• Analytics carry their methods: every correlation cited, every flag traceable to the data that raised it.
• The submission is the current state, not the state at printing. A revision does not mean a re-print; it means the same link shows the newer truth.

Control is preserved, not surrendered

Live access does not blur accountability. A share is read-only; the submitter controls what is shared and when; the decision remains the authority's. What changes is the quality of the evidence and the number of round trips it takes to reach a decision.

Strats3D projects can be shared this way today — a reviewer opens a link and sees the model, the sections and the analytics, not a stack of PDFs. We think every submission in the built environment is heading in this direction.