Marapone SpecChecker
Two contract documents. One of them is wrong.
In partnership with Marapone. Built with the Marapone team, whose PMs supplied the manuals and drawing sets it was tested against and decided which conflicts were worth interrupting someone for.
Visit the product page- What we did
- Product design, cross-reference engine, hosted build — with Marapone
- Timeframe
- 2026
- Discipline
- App
- Status
- Released · 2026
The drawing says 1/2-inch drywall. Section 09 29 00 requires 5/8-inch Type X. One of those is what the inspector reads and the other is what arrives on the truck, and nobody finds out which until the wall is closed in.
The project manual and the drawing set are both contract documents. They are written by different people, revised on different cycles, and issued together as though they agree. Checking 400 pages against 90 sheets is a job nobody has time for, so it gets done in fragments — by the PM who happens to notice, or by the supplier who calls to ask which one to price. SpecChecker does it in one pass, before the material is ordered.
- 27
- Measurable properties compared
- 39
- Named assemblies, 25 CSI divisions
- 11
- Conflict types, including self-contradiction
01
Both sides, read into the same shape
A clause in a manual and a cell in a door schedule are the same fact wearing different clothes. So both are normalised into one structure — a single measurable property, of one named assembly, in one canonical unit, carrying the page or sheet it came from. Everything downstream operates on those, which is what makes the comparison possible at all.
Where both documents state a value for the same property and the values disagree, that is a finding: both statements, both citations, and the exact wording each document used. Fire-resistance ratings, gypsum thickness and core type, concrete strength, steel grades, R-values and U-values, SHGC, airflow, filter efficiency, sprinkler design density, interrupting ratings, glazing make-up, hardware grade, warranty terms.
02
The conflicts a document has with itself
The obvious check is manual against drawings. Two of the eleven conflict types are stranger and more common than anyone expects: a manual written by three people over two years that contradicts itself, and an old general note on one sheet that the revised note on another sheet was supposed to replace.
There is no precedence rule to fall back on inside a single document, which is exactly why those have to be asked rather than resolved. It also catches addenda that were never carried through — the two-page PDF that arrives by email during tender and changes one number while the manual and the drawings both keep saying the old thing — and cross-references to sections that were cut.
03
Silence looks exactly like agreement
The audit can only report a conflict where both documents say something about the same property. Where the drawings are silent there is nothing to disagree with, and on a findings list that is indistinguishable from the two documents matching. A tool that hid this would be quietly worse than no tool, because a short list reads as reassurance.
So coverage is a first-class screen, not a footnote: what was checked, what could not be read confidently, and where the silence is. Findings are then sorted by what stops a material order today rather than by how many there are, and one click drafts the RFI — one letter per spec section, quoting both documents and asking which governs, because deciding that is the consultant of record's job and not the software's.
In motion
The app, running
Inside the product
The tools
Built with
Python, MaraponeAI, Web app, Document OCR, Hosted
More applications from the lab
Taking one new project for Q4 2026
Have something worth building?
A game, an app, an AI model, or a problem that doesn't have a name yet — tell us about it and we'll build the prototype.