Weekly rhythm
One status. Same day each week unless the site forces a shift. Blockers at the top. Decisions that are still open stay on a single list. If nothing moved, the status says that — we do not pad a quiet week.
Method
Four stages. One owner on our side of the file. Exceptions do not travel through a chain of forwards.
| 01 · Brief |
What must be true when we leave. Where the work sits. Budget band — even a rough one. Who signs. We will not invent a scope to fill a silence. If the first note is thin, we ask three questions and stop. We do not write a proposal to discover the job. |
|---|---|
| 02 · Concept |
A plan you can walk: sequence, vendors, and the dates that actually bind. Drawings or a site note if the job needs them. No slide theatre. You get a written concept before we mobilize. Changes after that go on the file as changes — not as “alignment.” |
| 03 · Field |
We stay on the work. Weekly status names what moved, what is blocked, and who must act. The field gets a number that answers. If a vendor fails, we say so in the same week. We do not wait for a steering pack to make the failure polite. |
| 04 · Handover |
Snag list, documents, keys, and a close-out note a finance desk can file. The file stays reachable after we leave the site. Warranty or snag windows, when they exist, are written. We do not disappear behind a completed invoice. |
One status. Same day each week unless the site forces a shift. Blockers at the top. Decisions that are still open stay on a single list. If nothing moved, the status says that — we do not pad a quiet week.
Safety, stop-work, and a change that moves cost or date. Those go to one mailbox and one number on the file. Not a group chat that nobody owns.
Access, a signer, and honest dates. If approvals sit with a committee, name the committee. We will not run a job against a calendar you cannot keep.
Write
info@dellamondconcepts.com — site, date, budget band, who signs.