Every entry must carry its proof.
That rule lives in the database itself: a machine-read conclusion cannot be stored as an established fact — the schema refuses the write. It is not a policy, a setting, or a promise. It is the structure.
The spec cites Section 15860. It isn’t in the book.
Every project carries errors like this — waiting in the pages nobody has time to read. ScopeForge is built to read them all: the drawings, the specifications, everything the project arrived as. So the job stands on what the documents say — not on the assumption that somebody read them.
Your judgment stays in charge. Nothing moves without your click.
Book the demo
Live, on a real project.
Every set has them. Nobody has time to find them.
A project’s truth is scattered across the drawing set, the spec book, the addenda — thousands of pages assembled by dozens of hands under deadline. Somewhere in there, a section is cited that doesn’t exist. A detail is referenced that was never drawn. A requirement sits in paragraph 1.02.A.3 that no one will meet, because no one will see it.
On one real mechanical job, our reading method found six. Each one costs nothing today — and collects later, with interest: the RFI argued from a weak position, the submittal returned, the change order fought against your own paper.
You have read documents at eleven at night looking for exactly these. The problem was never your reading. It was that no one can read everything.
Now something reads everything. And shows you where.
Give ScopeForge what the project arrived as — the drawing set, the specifications. It reads what they state, sheet by sheet, section by section, and builds the job’s working records out of the documents’ own words:
- The scope of work — a tree you can walk, every item placed by you or proposed to you. Nothing assumed.
- The submittal log — seeded from your own spec book. Every proposed entry arrives carrying its section, its article, its PDF page, and the specification’s exact words. “Show me where it says that” is one hover.
- The records the job runs on — daily reports, permits, contacts — in one place, on your machine, under your control.
- And everything the reading produces arrives the same way: as a proposal, showing its source, waiting for your confirmation. That last phrase is the whole design.
Built like a record. Because it is one.
When it cannot verify, it says so — on the record.
A spec book with no table of contents is reported as exactly that. A value it cannot confirm is marked unverified, with the search that came up empty logged beside it.
And the judgment it applies is not its own.
The reasoning it uses to read a specification was taken from a working construction PM — question by question, distinction by distinction — and frozen only after they confirmed it unchanged.
Your judgment, encoded — applied at a scale no person has time for.
Software whose every entry must carry its proof, working at that scale — we looked for it, and it did not exist. So we built it.
Watch it work. On a real project.
Ten minutes, live, no staging:
Tell Sage — the built-in assistant — to submit a submittal package. It proposes. You approve. The package renders, sends, and freezes permanently. The record is the record.
Open the log’s proposed lane: entries seeded from the project’s own spec book, the grounding cite on every row. Confirm one — it joins the log.
Export the log: every review cycle carrying its own rows and its own numbers, correct to the byte.
Early. And on the record about it.
ScopeForge runs today on real New York public-school construction — a full drawing set, a full spec book, a live job. It has been proven on one project manager’s real projects; the next could be yours. Acceptance here is adversarial: every flow is walked cold, every export verified to the byte, and a tester is paid to break what we build before you can.
No claim on this page runs ahead of the product. You are invited to check that sentence in person.
Start with one spec book.
Send it. We’ll show you what ScopeForge builds from your own document — a submittal log seeded from your spec’s exact words, every entry traceable to its page. One sitting, your paper, no preparation on your side.
It is the smallest test we can offer of a very large claim. The full read — drawings and specifications together — is what the demo is for.