He walks the job and talks. The punch items write themselves, name the trade, and go to the sub. The daily report assembles itself. Nobody types it twice.
Observations, inspections, punch — your project management software has all of it. A superintendent fills in every field.
A corridor shot is rarely one trade. SPECUP reads each one, writes a separate punch item for each with its own title, names the responsible sub, and says what in the photo it's based on. You tick the ones that are real.
Say "note to self," "punch," or "daily," and it goes where it belongs. Every entry comes back for approval before it lands on the signed report — nothing is filed on your behalf.
Every item is tied at creation to the activity, the sheet and the spec reference. Not tagged later. Which is why the daily report can assemble itself.
A superintendent doesn't think in deficiencies. He thinks in walks. So start one — everything you capture until you close it comes with you, and at the end you hand each trade their own list.
Start the walk and every photo, punch item, note and inspection attaches on its own. There is no "add to walk" button, because a step like that is a step nobody takes while holding a phone and a tape.
The walk report groups by the company that owns each item — not by the order you found them. It's a document you can send to one trade. Anything with nobody's name on it is called out at the end rather than buried.
An item raised on a walk is an ordinary punch item. It's on the punch list, routed to the sub, closing on its own clock. Closing the walk doesn't close it. Nothing ever lives only inside a walk and surfaces at closeout.
Nobody forgets to do the work. What gets forgotten is writing it down the day it happened — and three months later the only record is somebody's memory.
Standing in front of the condition, on a phone: what the contract documents say, what's actually there, a photo, a quantity, a date. Both directions — a sub raising it to you, or you raising it to the owner.
Work already installed that has to come back out is marked as rework on the face of the notice, because that is the number that gets argued about and the one nobody tracks.
Change numbers are issued by the system, in their own series per direction. Two people offline on the same morning don't both invent the same one.
From a photo, a pin on the sheet, or the form — assigned to the responsible sub with a severity and a due date.
The sub fixes it and attaches the after-photo from their own phone. No email, no spreadsheet round trip.
Your QC looks at the before and after side by side and verifies — or reopens it. That decision is the record.
Closed with evidence on both ends. The punch list publishes as a document when you want to send one.
The half that saves your week isn't reviewing faster. It's the package arriving complete.
The first thing on a sub's screen is what you're waiting on — with the clock running on anything you sent back, and a real due date rather than "seven days from receipt."
The moment they upload, SPECUP reads the package and tells them which required items it couldn't find. They fix it before it ever reaches your desk.
Complete, short by a named count, or not verified because nobody could read the file. A scan that can't be read is never called complete.
A sub with a question asks it in SPECUP instead of texting your super. Russell drafts an answer from the contract documents with the paragraph cited — and nothing reaches the sub until a person releases it, with their name on it.
If the documents don't answer it, the question converts into a real RFI in the RFI log and the sub is told to wait. Not a confident sentence in a chat thread that turns up in a claim.
A first-install inspection owed on a piece of work shows on the sub's screen and on your constraint log, and clears only when the inspection is actually recorded — nobody ticks it off. Catching one wrong first install is worth more than a year of the software.
Eleven years of a daily report your PM likes is not something software should argue with.
Mark the spots SPECUP should fill, upload your Word document, and confirm what each field is. It fills from the project record and comes back as your document, with your formatting untouched.
Fields it can't identify are left blank and flagged until you say what they are. A guessed field would print the wrong number on your letterhead.
Documents can be written to your own Microsoft 365 rather than ours. SPECUP is designed to hold the reference, not to become where your project lives.
The rigor came from where the paperwork gets audited — how the U.S. Army Corps of Engineers requires work to be reported, filed and logged. You don't get the federal forms unless you want them. You get the discipline underneath them.
Ask a question and the answer comes back with the document and the paragraph it came from. If it can't find it, it says so instead of guessing.
Offline-first, because jobsites don't have bars. Everything captured in a basement syncs when the phone comes back up.
Where a sheet points at a spec section, SPECUP compares them and drafts the RFI — quoting both sides so you read them before anything goes to the design team.
Two minutes, your own numbers, no email required. If Russell already handles something you're paying people to do, you'll see it on the same screen.
