Stop 2 of 8 · Daily
Submittals
Part 1 of a spec section becomes the checklist, the sub's package gets held against it, and the exceptions are written before the transmittal goes out.
The checklist is written before the package is opened
Every spec section has a submittals paragraph, usually 1.4 or 1.5, and it is prose. Product data, samples in the full range of colours, shop drawings at a stated scale, certificates, test reports to a named standard, warranties, closeout data. Hany's job is to turn that prose into a list, then hold four hundred pages of subcontractor package against it.
The reading is the part that goes slowly and the part Claude is good at. The judgment about whether a deviation is acceptable is yours, and it stays yours.
Section to checklist
From the spec book in this Project, read section [09 30 00 Tiling] and give me every submittal the section requires as a numbered checklist. For each item: what is required, the paragraph it comes from, the standard or scale it names if any, and whether it is required before fabrication or at closeout. Do not add items the section does not call for. If a paragraph bundles several items in one sentence, split them and say which paragraph they came from.
Read the list once against the section yourself. It takes two minutes and it is the last cheap moment to catch a missed line.
Package against checklist
Here is the subcontractor submittal package for [section 09 30 00, tile]. Hold it against the checklist we built, item by item. For each checklist item say: found and where, found but partial and what is short, or not found. Then list the exceptions separately, meaning anything the package includes that departs from the specified product, standard or scale, with the spec paragraph beside each one. Ignore any pricing page and tell me if you see one. Do not judge whether a deviation is acceptable.
The last sentence matters. Claude marks what departs from the spec. Whether the departure is approved as noted, revised and resubmitted, or rejected is a decision with your name and twenty years behind it.
The transmittal and the log
From the review above, write the submittal review in our template in this Project: the action, the comments numbered to the checklist items, and the exceptions with their spec paragraphs. Keep each comment to one sentence and reference the sheet or page in the package where the issue is. Then give me the register line: submittal number, section, title, revision, date sent, ball in court, and the date a response is needed by. Leave the action blank for me to fill in.
From the submittal register export, list every submittal that has been with the architect for more than the review period stated in section [01 33 00], with the number, the title, the date sent and the days out. Draft one email to the architect covering all of them in a single table, neutral in tone, asking for a return date on each. No adjectives about their turnaround.