Current plan
- Design approved Monday; build Tuesday and Wednesday; review Thursday; launch Friday.
- Build requires two full working days after design approval. Review needs one full working day. Workdays are Monday to Friday.
The changed approval date reaches the actual delivery plan. The team sees the earliest feasible sequence and the client decision needed to proceed.
3 records.
4 automatic steps.
One human check.
What goes in
3 ordinary records, nothing prepared specially for AI. Every fact in the finished work traces back to one of them.
How the work runs
Set up once: the plan format, the durations and the rule that only the project lead confirms dates live in a saved project. After each meeting the transcript goes in and the revised plan, decision brief and team note come out.
A saved project is a folder inside your AI tool that keeps its instructions and reference files between conversations, so nothing is re-explained.
Only three things changed: approval date, review owner and the client’s wish to keep Friday. Everything else is preserved.
Two build days after Wednesday afternoon push review to Monday. No weekend or extra staff is assumed.
Keep scope and launch after review, or assess a smaller first release. Neither is decided for the client.
Sam and Jo get their dates; the Friday request is marked unresolved, not confirmed.
The project lead checks the dates, chooses how to put the options to the client and sends the team note.
What comes out
This is the full review copy. Read it the way the owner would, with the records above open beside it.
Prepared for review · fictional records
| Step | Owner | Earliest working time |
|---|---|---|
| Design approval | Client | Wednesday afternoon |
| Build day 1 | Sam | Thursday |
| Build day 2 | Sam | Friday |
| Review | Jo | Monday |
| Launch | Project lead to confirm | After review acceptance; timing to agree |
The original Friday launch no longer fits the agreed work. Option A: keep scope and the two-day build; review can occur on Monday, with launch scheduled after acceptance. Option B: ask the team to assess a smaller first release before proposing a new schedule. Option B is not yet a feasible or approved commitment.
Design approval has moved to Wednesday afternoon. Sam’s build now falls on Thursday and Friday; Jo’s earliest full review day is Monday. Keep the current scope and durations while the project lead resolves the launch decision with the client. Do not publish or work through the weekend on the assumption that Friday still stands.
Human review
Two full build days follow Wednesday afternoon approval; Monday is the earliest full review day. Do not promise a launch before review acceptance.
Try it
The complete fictional pack and the instruction are below. Paste both into an AI chat you are allowed to use, then compare what comes back with the brief above.
Copy the notes and instructions into an approved AI chat.
Two full build days follow Wednesday afternoon approval; Monday is the earliest full review day. Do not promise a launch before review acceptance.
Before trying this on your firm's real files, use a business AI account and make sure someone checks every result before it is used.
Try a completed meeting with its prior plan. Check whether the revised plan captures the changes and exposes the decisions someone had to make.