Only-we-do-this
Rev B lands.
We already know Rev A.
Every engineering deliverable goes through Rev A → Rev B → Rev C → IFC. At each turn, comments get closed out — or silently dropped. SpecSense remembers every finding from the last revision and produces a closeout matrix the moment the new one arrives. Chartered-engineer sign-off included. Audit-defensible, contract-defensible.
The one-liner
You can ChatGPT a single revision. You can't ChatGPT a revision-to-revision closeout audit with evidence and sign-off. That's what your client wants at IFC. That's what we sell.
20-40% of Rev-A comments silently disappear by IFC.
It happens because engineering reviews are governed by fragile institutional memory. Comments migrate across Excel comment registers, email threads and different reviewers over 6–12 weeks. Nobody hands over the full picture. Then at IFC, half the review is a re-check of Rev A comments no one can trace.
The silent-drop pattern.
Rev-A comment #7 was a MAJOR flange derating flag. Rev-B ships and comment #7 doesn't appear in the response sheet at all. Not marked open, not marked closed. Just gone. IFC review misses it because nobody's tracking against the original register.
The optimistic-EPC pattern.
EPC response sheet says 'addressed' but the evidence in the new revision doesn't support closure. A tired reviewer signs off. Six weeks later at construction hold, the same issue surfaces — now it's a change order and a schedule impact.
The reviewer-drift pattern.
Reviewer on Rev A leaves the project between revisions. Reviewer on Rev B doesn't know the history. Same discipline, different priorities, different severity calls. Register loses internal consistency, client can tell.
The response-sheet-mismatch pattern.
EPC response sheet uses P-001 numbering. Original review used comment-numbers C-001. Nobody maps between them systematically. Two reviews of the same package become two disconnected documents.
Every prior finding gets exactly one of these.
The AI does the classification. A Chartered Engineer signs the register. No neutral “probably closed” language allowed — a comment either closes with evidence, or it doesn't.
Evidence in Rev B fully closes the Rev A comment.
The AI cites specific evidence in the new revision that resolves the finding. Change is verifiable — new line class shown on P&ID + line list + iso. Stress engineer note added. Comment can be signed off.
Some evidence, some gap. Not ready to close.
The EPC has moved on the comment but not fully — one of three welds got the PWHT symbol, or one of two spans got the extra support, or the revision letter changed but the owner-review stamp is still blank. Residual action listed. Needs Rev C.
No evidence of closeout in the new revision.
The comment simply hasn't been addressed. Sometimes because it was missed, sometimes because it was deferred. Either way it doesn't close silently — it stays open and named on the closeout matrix until it's resolved.
EPC marks closed. AI disagrees, with evidence.
Highest-value verdict of the four. The EPC response sheet says 'addressed'; the AI reads the new revision and disagrees, citing specifically what's still missing. A Chartered Engineer reviews before this leaves — it's a client-facing call.
Four steps between Rev-B upload and signed closeout matrix.
Upload the new revision + EPC response sheet.
60 secondsDrop the new PDF and paste the EPC response sheet (or upload the Excel). SpecSense already has the prior review's findings — no re-upload needed. Metadata capture is one form; revision label auto-increments from prior document.
AI produces a per-comment verdict.
5-8 minutesFor every finding in the prior review, the AI reads the new revision, extracts textual and drawing-level evidence, and classifies the comment: CLOSED / PARTIALLY_ADDRESSED / OPEN / DISAGREE_WITH_EPC. Each verdict includes evidence quote and residual action.
Chartered Engineer triages the register.
45-90 minutesOn supervised tiers, a CEng reviews every verdict — accepting, editing or overriding as needed. False positives are removed. Severity is calibrated against project context. Nothing leaves without a named human signature.
Closeout matrix delivered — signed and traceable.
48 hours end-to-endYou get a comment register in your template (Excel), a marked-up PDF with hyperlinked findings, and a signed cover memo referencing SS-YYYY-NNNN. Every claim traces to a code clause and a drawing location. Contract-defensible.
One row from a real closeout matrix.
Anonymised excerpt from a real Rev 0D → 0E review. This is the shape of a single row. Every finding in the register gets the same treatment.
Original finding (Rev 0D)
MajorPWHT not annotated on P-No 5A material spool with wall thickness >19mm. ASME B31.3 §331.1.1 requires mandatory PWHT for this material group above the threshold.
EPC response
“PWHT added to weld map. Comment addressed.”
SpecSense verdict
Disagree with EPC
Evidence in Rev 0E
Weld map Rev 0E shows PWHT symbol at Weld W-024 only. The spool contains three P-No 5A welds above threshold: W-024, W-025 and W-027. EPC marked closed; two welds still lack the PWHT annotation.
Residual action
Add PWHT symbol to W-025 and W-027. Update weld map Rev 0F. Do not sign off closeout until confirmed.
Reviewed & signed by Kingsley Uzowulu, CEng MIMechE·SS-2026-0043 · M-007
Deliverables you can hand a client on the same call.
Closeout register (XLSX)
Per-comment verdicts in your team's Excel template. Sortable by discipline, severity, verdict. Every row has the original finding, EPC response, verdict, evidence and residual action.
Marked-up PDF (hyperlinked)
New-revision PDF with severity-coloured markers overlaid on the drawing zone or page. Each marker jumps to the closeout entry in the appendix. Findings appendix lists code clause and evidence per finding.
Signed cover memo
One-page cover memo issued under Chartered-engineer signature. References the review ID (SS-YYYY-NNNN), revision pair, and headline counts. What you present to the client.
Revision lineage
Every prior revision review is preserved and downloadable — Rev A → Rev B → Rev C, all linked to the same document number. Full audit trail across the project lifecycle.
EPC-disagreement flag
When we disagree with an EPC 'closed' claim, it lands as a dedicated section in the register with evidence and residual action. This is the section your client will read first.
Immutable review ID
Every review is tagged with a unique reference (SS-YYYY-NNNN). Referenced in the client email, the signed memo and the exported PDF metadata. Anyone can trace the review back to the exact register.
What technical buyers ask us.
“Can't a generalist LLM do this if I load Rev A findings into the context window?”
You can prompt it to try. What you can't get from a generalist LLM is (a) memory of accepted-finding severity calibrations from your prior reviews, (b) an audit-safe classification vocabulary — the four verdicts are contract-defined here, they're not just prose, (c) Chartered-engineer sign-off with named liability, or (d) a persistent review ID that references the exact register your client saw last time. The differentiator is the review-lineage system, not the reasoning step.
“What if the EPC uses different comment numbering than our original review?”
This is the norm, not the exception. The AI matches by content and severity across numbering schemes — 'C-001 revision-legibility' from the original review maps to whatever the EPC filed it as on the response sheet, or flags it as un-mapped if there's no clear correspondence. Un-mapped prior findings are called out explicitly so nothing hides in a numbering gap.
“What if there's no formal EPC response sheet — just a redlined PDF?”
Handled. Drop the redlined PDF and the AI reads the redlines as the response. Verdicts still classify against the four buckets. You get the same signed closeout matrix; the 'EPC response' column just quotes redline text instead of a response-sheet cell.
“Can we run this offline / on-prem for confidential deliverables?”
Yes. Enterprise-tier customers can deploy SpecSense on their own VPC (AWS/Azure/GCP) or on-prem VM, with the same closeout-matrix logic and Chartered-engineer sign-off performed by an appropriately-cleared reviewer. Data never leaves your environment.
“How far back can revision lineage go? Only Rev A → Rev B?”
Full lineage. If you have Rev A, Rev B, Rev C in the system, a Rev-D review compares against the accumulated live-comment list — not just Rev C. Long-lived comments (e.g. a MAJOR flag that has been open since Rev A) stay visible across the lineage until they either close with evidence or get formally deferred.
Bring your Rev-B. We'll compare it to Rev-A.
48-hour supervised pilot. Chartered-engineer sign-off. Full closeout matrix delivered as a signed comment register in your template.