Stop 8 of 8 · Weekly
Hany's week
Three routines on a timer, the desktop working while he is on the floor, and one spec section carried from checklist to closeout.
Three routines on a timer
A scheduled routine runs on its own, on your files and connectors, whether or not the laptop is open. Three of them cover most of Hany's week.
Weekdays 6.30, the log digest
From the submittal register and RFI log exports in this Project and my Outlook mail from the last twenty four hours, give me: submittals over fourteen days with the architect, RFIs past their response date, any item where an answer is blocking a delivery or an activity in the three week look-ahead, and anything that arrived overnight needing a reply today. Status comes only from the register and log export columns, never inferred from an email. Twelve lines maximum, blocking items at the top.
Wednesday 16.00, coordination prep
Build Thursday's MEP coordination agenda from the current clash report and the three week look-ahead in this Project, grouped by area and level, with the blocked activity and its date on every clash. Carry forward every open action from last week's minutes with its owner and the date it was first raised. Leave it as a draft. Flag any action item that has now appeared three weeks running.
Friday 15.00, the owner update
Draft this week's owner update from the daily reports, coordination minutes and site photos of the last seven days. Four short paragraphs: work completed by area and level, next week, decisions we are waiting on with the date raised and who has them, and what the owner needs to action. No completion dates, no schedule impact, no cost. Anything that reads like one goes at the end under FOR THE PM. Leave it as a draft.
From the floor
Dispatch sends a task from your phone to your desktop, which does it with your files and messages you when it is done. Turn the desktop on before you leave the trailer.
From level nine
Open the tile data sheet in the hotel Project, build the spec against data sheet table for section 07 13 00, and draft the deviation memo to the architect for anything not stated. Leave it in my drafts. Do not send it and do not put any cost in it.
The capstone
Take one spec section you are live on and run it end to end this week.
- Part 1 into the numbered submittal checklist, with the paragraph beside each item.
- The sub's package against the checklist, with the exceptions listed and the missing items verified by you in the PDF.
- The review comments, the transmittal and the register line.
- Any field conflict the review turned up written as an RFI with the sheet, the section and a proposed resolution.
- Part 2 against the product data as a met, not met, not stated table, and a deviation memo for what is not stated.
- The closeout items from that section added to the tracker with the trade and the room.
If all six exist by Friday for one section, the pattern holds for thirty.
The cheat sheet
| You want to | Do this |
|---|---|
| A submittal checklist | Part 1 of the section, never the sub's cover letter |
| A review that survives | Checklist first, verify the missing items yourself |
| An RFI answered once | Sheet, section, field condition, proposed resolution |
| Minutes worth keeping | Every action with a name and a date, no money |
| A punch list that closes | Trade, then room in walking order, photo on every line |
| A code answer | Research mode to find it, then open the code yourself |