The prompt
Score 10 of 10, Excellent
Use it when You have walked a nearly finished job and need the notes turned into a punch list each trade can act on without asking what an item means.
- {{project}}
- {{audience}}
- {{walkthrough_notes}}
- {{trades}}
- {{key_dates}}
- {{location_scheme}}
Full prompt and why it works
Prompt
Turn the notes from the final walkthrough of {{project}} into a punch list, for {{audience}} to issue to the trades and track to completion, so that every item is specific enough for the right trade to find, fix and close it without a second walkthrough to explain it. Walkthrough notes, voice notes or marked-up plans, as captured: """ {{walkthrough_notes}} """ Trades and subcontractors on the job, with their scopes: {{trades}} Dates that matter (substantial completion, inspections, owner move-in): {{key_dates}} How we name locations (building, floor, room or grid): {{location_scheme}} Produce: 1. A punch list table with the columns #, Location, Trade, Item, Done when, Priority, Responsible, Due, Photo ref. Sort it by location in walking order, so it can be carried on the next walkthrough. 2. A count of items by trade, so each subcontractor sees their total. 3. Items to resolve before assigning: work where the responsible party is unclear, items that look like missing scope rather than defects, and damage that may have been caused by another trade. Write each item as what is wrong, exactly where, and what done looks like, for example "Room [number], east wall, left of the door: touch up paint around the patched outlet; done when the patch cannot be seen from the doorway". That example shows the form only. Use these priorities: Life safety or code; Needed for occupancy or inspection; Finish and cosmetic. Set due dates from the key dates, life safety items first. A good punch list is one a trade can close in a single visit. Do not combine separate defects into one item, do not assign a trade where the notes and scopes do not make it clear, and do not add items that were not noted. Keep each item under 30 words. If a location or description is too vague to act on, keep the item and write [CHECK: location or detail] in it rather than dropping it or guessing. If no key dates are given, leave Due blank for {{audience}} to fill in.
Variables
- {{project}}
- The project, or the part of it walked, for example "floors 3 and 4 of the clinic build-out".
- {{audience}}
- Who issues and tracks the list, for example "the superintendent".
- {{walkthrough_notes}}
- Everything noted on the walkthrough, with locations and photo references where you have them.
- {{trades}}
- The trades and subcontractors on the job and what each one's scope covers.
- {{key_dates}}
- Substantial completion, inspection and move-in dates, or "none set".
- {{location_scheme}}
- How locations are named on this job, for example "floor, then room number from the plans".
Why it works
- What good looks like. Each item names the defect and its exact place and says what done looks like, so a trade can close it in one visit.
- If unsure. Vague items are kept with a [CHECK] note instead of being dropped, and unclear responsibility goes to a separate list before anything is assigned.
- What to avoid. No combined defects and no guessed trades, which are the two things that make punch lists bounce between subcontractors.