SUPPORTED
The production state is supported by the governing evidence supplied.
ARCHITECTURAL MILLWORK / COMPLETED PROJECT REVIEW PILOT
Know what’s
approved before
you fabricate.
Before a package goes to production, can what you’re about to build be traced back to what was actually approved?
We’re developing an evidence-backed preflight check - and recruiting a small number of shops to test it on completed projects.
Apply for the Completed Project Review PilotResearch-stage system. Completed projects only.
PRODUCTION RELEASE REVIEWILLUSTRATIVE / SIMULATED
REVIEW ITEM / TOE KICK
CONFLICT3½″ in the package.
4″ in the approval.
Evidence linked. Decision stays with your shop.
ONE COMPLETED PROJECTPRIVATE FINDINGS & EVIDENCENO LIVE SYSTEM ACCESS
THE RESPONSIBILITY
The latest drawing
isn’t the whole story.
A returned submittal approves one detail. A later email changes another. Field measurements add a condition. The production package has to carry the right combination forward.
That history may live across drawings, revisions, review comments, RFIs, ASIs and correspondence. A newer document does not, by itself, establish approval.
Someone in your shop already owns the final review. We’re investigating whether a second, evidence-backed check can help that person see what agrees, what conflicts and what still needs an answer.
THE CHECK
From project history
to a traceable finding.
The question is deliberately narrow:
Does the package being considered for release agree with the approved drawings and documented changes that are supplied?
- 01 / INPUT
Project evidence
Drawings, comments, revisions, measurements and correspondence.
- 02 / RECONSTRUCT
Governing approval
Which approval applies to this detail, scope and point in the project?
- 03 / COMPARE
Production package
The recorded state your shop was considering for release.
- 04 / REVIEW
Preflight findings
A finding, its evidence chain and any unresolved question.
CONFLICT
The production state disagrees with the governing evidence.
INSUFFICIENT EVIDENCE
The supplied record does not establish whether the production state is valid.
HUMAN DECISION
The evidence exists, but the judgment or authority belongs to a person.
“Supported” describes the supplied record. It is not permission to fabricate.
AN EXAMPLE, NOT A CUSTOMER RESULT
A change discussed.
An approval missing.
This illustrative finding comes from a simulated project example used for capability testing. It shows the distinction we’re testing: a change can appear in a later drawing without becoming the approved requirement.
SIMULATED CAPABILITY EXAMPLEFINDING 002 / TOE KICK HEIGHTCONFLICT
PRODUCTION PACKAGE3½″
PR-01 · 22 Sep 2026
APPROVED SHOP DRAWING4″
A-601 Rev A · returned 12 Sep
- 01
Returned Rev A establishes 4″
The approved shop drawing specifies a 4″ toe kick.
- 02
Rev B proposes 3½″
The revised drawing changes the dimension. Correspondence discusses it, pending confirmation.
- 03
Later approval is limited to the filler
The 20 September email approves the left filler only and keeps the remaining work aligned with returned Rev A.
Unsupported change in the supplied record.
Human follow-up: confirm whether a separate toe-kick approval exists before making a release decision.
THE COMPLETED PROJECT REVIEW PILOT
Give us an old project.
Tell us what we missed.
We’ve been conducting controlled tests with simulated project examples. The next step is to see how the check handles a real, completed job—and let the people who know that job judge the results.
- 01
Share one completed project
Provide its document history and production/release package. Redact identifying or customer information where appropriate.
- 02
We run the experimental review
We work out was was approved - and what changed - and compare it with what the production package shows.
- 03
Receive a private evidence report
See what appears supported, potential conflicts, evidence gaps and human decisions, with the evidence behind each finding.
- 04
Review the results together
Tell us what was right, what was wrong and whether a finding would have mattered in your actual production review.
A small research pilot, not a commercially launched product.
Discuss a completed projectA USEFUL PROJECT
Real history.
It doesn’t need
to be tidy.
Perfectly organized records are not required. Messy histories, partial approvals and changes across documents are useful to this experiment.
The most useful starting point is a production/release package plus the records that explain what governed it. If something is missing, that becomes part of the review.
No uploads in the application. We’ll discuss fit and agree on the records and sharing process first.
Share what you have from one completed job
Design intent
Original architectural drawings and specifications
Shop history
Shop drawings, revisions and returned approvals or comments
Change history
RFIs, ASIs, change orders and relevant correspondence
Job conditions
Recorded field measurements and coordination notes
Production state
The package considered for fabrication/release
Final outcome, if available
What was ultimately fabricated, corrected or recorded as built
A CHECK. NOT A RELEASE AUTHORITY.
Your people
make the call.
This system compares records. It does not authorize fabrication, determine engineering adequacy, guarantee field fit, replace field verification or approve design changes.
It does not create CNC output or replace qualified shop personnel. During this phase, we review completed projects only. No live production-system access is required.
EXPRESS YOUR INTEREST
Curious what it
would find on
one of your jobs?
Tell us a little about your shop and how production release works today. We’re looking for operators willing to share a completed project record and give candid feedback.
01 completed historical projectPrivate review with evidenceYour feedback shapes the experiment
Submitting an application is not a guarantee of participation. We’ll discuss project fit with you first.