See the work

From changed decisions to an updated project plan

A complete illustration with fictional source material. Explore the result, then try the same task.

Illustration · Fictional project team

The changed approval date reaches the actual delivery plan. The team sees the earliest feasible sequence and the client decision needed to proceed.

Earliest sequence at the current scope

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

Decision for the client

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.

Team follow-up: ready for approval

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.

Plan changes to record

Supersede the old Tuesday to Wednesday build dates.
Name Jo as review owner.
Mark the Friday launch request as unresolved, not confirmed.
Project lead confirms the selected option and launch acceptance before scheduling release.

See the source material and try it

This is a worked illustration with fictional inputs. The output was produced and edited for this example; your AI tool may produce a different version.

Copy this fictional example

Copy the notes and instructions into an approved AI chat.

Fictional source material: 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. MEETING DECISIONS Client moved design approval to Wednesday afternoon. Sam remains responsible for the build. Jo agreed to review. The client requested the original Friday launch but did not approve a scope change or extra staffing. DELIVERY NOTES The project lead owns the schedule and must confirm changes with the client. A reduced first release could be considered, but nobody has assessed its effort. The team needs a revised plan and a concise decision request, not just meeting minutes.

Your task: Reconcile the meeting with the current plan. Produce a feasible earliest sequence, a decision brief with options and a team follow-up. Preserve agreed scope and work durations. Do not assume weekend work or unapproved resources.

Check the result

Two full build days follow Wednesday afternoon approval; Monday is the earliest full review day. Do not promise a launch before review acceptance.

Apply it to your work

Before trying this with real work, confirm that the AI tool may use those records and that someone can check important mistakes. Otherwise, keep using fictional details.

Try a completed meeting with its prior plan. Check whether the revised plan captures the changes and exposes the decisions someone had to make.

Find where AI fits your work →