Sidekick Orchestration
A worked example

From changed decisions to an updated project plan

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

Fictional project teamFictional recordsRevised plan and decision brief you can read in fullNo client claim
Records in · finished work out

3 records.
4 automatic steps.
One human check.

What goes in

The records the workflow reads

3 ordinary records, nothing prepared specially for AI. Every fact in the finished work traces back to one of them.

P1 · Project plan

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.
T1 · Meeting transcript

Decisions from today’s client meeting

  • 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.
D1 · Delivery notes

Who owns what

  • 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.

How the work runs

From records to a review-ready result

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.

  1. The transcript is compared with the plan

    Only three things changed: approval date, review owner and the client’s wish to keep Friday. Everything else is preserved.

  2. The sequence is recalculated with the same durations

    Two build days after Wednesday afternoon push review to Monday. No weekend or extra staff is assumed.

  3. The conflict becomes a decision with options

    Keep scope and launch after review, or assess a smaller first release. Neither is decided for the client.

  4. The team note and plan changes are written

    Sam and Jo get their dates; the Friday request is marked unresolved, not confirmed.

  5. A person reads, corrects and acts

    The project lead checks the dates, chooses how to put the options to the client and sends the team note.

What comes out

The finished artifact

This is the full review copy. Read it the way the owner would, with the records above open beside it.

Revised plan and decision briefFictional · prepared for review
Review copy

Prepared for review · fictional records

Design approval moved: earliest sequence and the client decision

Prepared for
Project lead
Built from
P1, T1, D1
Status
Review copy · launch unresolved
Changed
Approval date, review owner

Earliest sequence at the current scope

StepOwnerEarliest working time
Design approvalClientWednesday afternoon
Build day 1SamThursday
Build day 2SamFriday
ReviewJoMonday
LaunchProject lead to confirmAfter 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 · draft for approval

To
Sam, Jo
Subject
Revised dates after today’s client meeting

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.

Human review

What the owner checks before it goes out

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

Run the same records through your own AI tool

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 this fictional example

Copy the notes and instructions into an approved AI chat.

Fictional source material: P1 · 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. T1 · DECISIONS FROM TODAY’S CLIENT MEETING 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. D1 · WHO OWNS WHAT 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 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.