A few useful Tasks, one real-life Workflow
Keep a contractor project understandable from quote to closeout
Work hasn't started or the status is unclear? Start with the checkpoint Task for a factual status packet and next request. Use it for a punch list before signoff, or compare estimates if you're still choosing.
AI should organize the evidence and questions. The signed scope and qualified professionals still decide the things AI cannot.
Real output
What you can leave with
- A normalized estimate comparison that exposes missing scope, allowances, exclusions, and questions before selection.
- A source-grounded status packet for work that has not started or a project whose status is unclear: agreement, recorded payments, dated promises, permit records, observations, and unanswered questions.
- A neutral next request or closeout punch list that preserves unknowns and conflicting accounts without inventing technical, code, warranty, payment, or legal conclusions.
Your Workflow
Checking this browser…
Checking this request…
Use what you need
The Tasks inside this Workflow
Each Task works on its own. Follow the sequence when the whole problem has enough moving parts that one Task is not really the job.
Before you choose
Compare the estimates in the same language
Normalize scope, allowances, exclusions, materials, schedule, warranty, payment terms, and price before letting the cheapest total decide the job.
Before work starts or signoff
Build a status packet or a closeout punch list
If work has not started or permits, payments, or dates are unclear, organize the supplied records and questions first. Near signoff, reconcile the promised scope against observations and build a punch list. Keep technical judgments with qualified professionals.
Next written request
Turn the open items into a calm message you can send
Use the checked status packet or punch-list facts as rough notes. Ask for the missing records, confirmed dates, responsible people, or closeout follow-up in one concise message you review before sending.
Prefer one focused job?
You do not have to follow the whole Workflow.
These are useful connections, not a prescribed path. Explore individual Tasks whenever one specific job is all you need.