Setmark reads the set first and pins what your scope depends on, so the time before the bid goes to pricing, not to hunting.
A wall finish quantity is assembled, not looked up. The schedule says whether it is in scope, the elevation says which finish and how high, the reflected ceiling plan says where it stops, and the floor plan says how long, provided you trace the inside face where the finish stops. Four documents have to agree before the number is real, and they do not always agree.
An addendum usually arrives as a cover list plus a stack of reissued sheets. The list says which sheets changed, not which dimension moved, and the sheet binds you whether or not the list mentions it. Somebody has to lay the old sheet against the new one, and a change nobody catches turns straight into a number you are held to.
A drawing shows a finish, a detail, a transition. It does not say which trade carries it. Under the general conditions, how the drawings and specifications are organized does not decide how the contractor splits the work between trades. The contractor draws that line. You price your read of where it falls, and the narrowest read wins the job.
Setmark does not replace your estimator. AI can read a set quickly, but it cannot decide what a number is worth signing or what your crew will actually hit in the field, so every finding stays with the person who owns the bid. What changes is how much of the set gets read before the bid is due.
Setmark's rules are authored once and then run as ordinary software. The same set produces the same findings every time, and every finding points at the sheet it came from. Nothing is generated fresh on each run.
Your scope is not the next trade's scope, so we set up what you check before the call. Send a set you have already bid along with whatever your team checks before a number goes out. Then you see what Setmark pinned, what it missed, and what still needed your estimator to decide.
We will only use this to schedule your demo. No list, no spam.