Six stages, front to back. We label what runs today and what's still coming — every line.
Where a sheet points at a section, SPECUP compares them — fire ratings, gauges, types, board thicknesses — and checks both directions of reference. Every item quotes the sheet and the paragraph, side by side, and drafts the RFI. It reads the written blocks on a sheet: schedules, general notes, keynotes. It does not read geometry.
The scope for each sub, generated from the contract documents instead of last job's copy-paste.
What each sub actually owes — by spec paragraph, by SD classification — issued to them as a request.
The sub opens SPECUP on their phone and the first thing on the screen is what they owe you — with the 7-day resubmittal clock running on anything you sent back. They drop every file in the package at once, each one shows its own progress, and the whole package is checked together — an item found in file 2 still counts when they add file 5. No email chain.
The moment they upload, SPECUP reads the package and tells them which required items it couldn't find — before it ever reaches your desk. It flags for review; it does not rule.
When a package lands you're told what actually arrived: complete, short by a named count, or not verified because nobody could read it. A scan that can't be read is never called complete.
