Picture Friday at noon. Every client has this week’s update: confirmed dates and the decisions you need from them. Each project manager spent ten minutes reviewing a prepared draft, where the update used to take most of an afternoon. On Monday the operations lead reports one number, and it is green. Same team, same process document, 10X what it can do.
A company that runs on EOS has already done the hard part: its core processes are documented and each has an owner. This piece takes one of them the rest of the way into weekly use.
Your documented process is the head start.
A core process is written at a high level on purpose: it tells an experienced person what happens, in order. This one is from an invented 60-person commercial fit-out contractor.
Illustrative example with invented data. The process as the company has it documented.
Weekly client update
- Collect project status from the site leads.
- Compare progress with the schedule.
- Write the client update.
- The project manager reviews it.
- Send it by Friday.
Those five steps stay. A workflow adds what your best project manager carries in their head: what they read, what they decide and what they check before anything leaves the building.
Add inputs, decisions and checks to every step.
Sit down with the process owner and the person who runs it best. For each step, ask what they need in front of them, what they decide and what they check before it moves on.
Illustrative example with invented data. The same steps after an hour with the operations lead and one project manager.
| Step | Inputs | Who decides what | Check before it moves on |
|---|---|---|---|
| 1. Collect status | Each site lead’s Thursday note; open client requests. | Site lead: the note is current as of Thursday. | Every active project has a note dated this week. A missing note is named, never filled in. |
| 2. Compare with the schedule | The approved schedule; the approved change-order log. | Project manager: whether a slipped date needs a change order. | A date is “confirmed” only if the approved schedule shows it. Every other date is labelled an estimate. |
| 3. Draft the update | Steps 1 and 2; last week’s update; the update template. | AI prepares the draft. Project manager: what the client must decide this week. | Every statement names its source. Open questions sit at the top of the draft. |
| 4. Review | The draft with its sources. | Project manager: approve, edit or hold. | The four-line review in the job aid. Anything about cost or contract terms goes to the operations lead. |
| 5. Send | The approved update. | Project manager sends it. | Sent by Friday noon and filed with the project. A late or held update is logged. |
Read the third column: AI prepares, and every commitment to a client stays with a named person. The awkward cases get their own rules: Your SOP describes the happy path shows how to capture them. To write this method in a form an AI assistant follows, read From SOP to AI workflow. The client-status update preparation capability template gives you a starting version of this exact job.
Put the job aid where the work happens.
The table is for the owner. The person running the workflow needs one page.
Illustrative example with invented data. The job aid each project manager keeps open.
Job aid: weekly client update
- Have ready. This week’s site notes, the approved schedule, the change-order log and last week’s update for each project.
- Run. Open the client update workflow in the company’s AI workspace, attach the four inputs and name the project.
- Review, four lines. Every confirmed date matches the approved schedule. Every estimate is labelled. The client’s decisions are listed first. Nothing mentions cost or contract terms without the operations lead’s approval.
- Stop and ask. A missing site note: the site lead. A date that slipped more than five working days, or any disputed change order: the operations lead, before sending.
- Done when. The update is sent by Friday noon, filed with the project, and any hold or correction is in the exception log.
Review it in the meetings you already hold.
A workflow stays good when someone looks at it on a schedule, and you already have one. Add one line to the weekly meeting and one item to the quarterly session.
Illustrative example with invented data. The agenda item the operations lead added. The layout is ours.
Agenda item: weekly client update workflow
- Weekly, one minute
- The operations lead reports one number with the others: updates sent by Friday noon. Goal: 15 of 15 active projects.
- Raise as an issue when
- The number misses two weeks running, a client corrects a date we called confirmed, or the same exception appears three times in the log.
- Quarterly, fifteen minutes
- The operations lead brings the exception log, the reviewers’ edits and what the project managers want changed.
- The quarter decides
- What changes in the process document and the job aid, which repeated exceptions become rules and test cases, and whether the next core process gets the same treatment as a priority for the quarter.
The process document stays the authority. A change to the workflow is a change to the process, approved by its owner and retested before the team uses it.
EOS, Rocks and the Accountability Chart are EOS Worldwide’s terms. This agenda item is Fully Powered AI’s own working layout for teams that run on EOS, and it is independent of EOS Worldwide.
Start with one process this quarter.
Choose the core process that runs most often and already has a clear owner. Prove it on real cases, then follow the rollout checklist. To make it the quarter’s priority, read Make an AI pilot your next 90-day Rock. To show it beside the seat that owns the result, add it to your Accountability Chart.
The workflow runs in the ChatGPT, Claude, Copilot or Gemini your team already uses. You set the pace, and your organization keeps control of how the work gets done.
A workflow sprint fits exactly this: one documented process with a named owner, turned into one working workflow. Bring the process document and the name of the person who runs it best.