Give the week a result people can recognize.
The team can plan around a clear result and a named recipient. Copy this brief, set the scope together, and use it to review progress and decisions during the week.
Use it when several people contribute to one result.
A consultancy might need a delivery summary for the project lead. The first goal guide and goals-and-tasks workflow define the result; approvals identify the decisions it leads to.
Copy the brief and replace the project details.
The company setup guide helps choose a first process. Check the information guidance as you select material for the people involved.
WEEKLY GOAL: DELIVERY SUMMARY FOR PROJECT REVIEW Owner: project lead. Preparer: named coordinator. Recipient: manager reviewing the delivery. Result: a summary of the agreed deliverables, supporting source references, current version, and questions requiring a decision. Scope: the project phase and material selected by the lead. Sources: applicable scope note, delivery records, and confirmed changes. Source owners explain status and meaning. The coordinator organizes the summary; contributors check their sections; the manager reviews its intended use. Acceptance: material statements can be traced, the applicable scope is visible, and open questions have owners. Commercial promises and additional scope follow the authorized decision maker. When inputs change, identify the affected section and agree the next action. At the weekly review, record accepted sections, remaining corrections, decisions, and the next responsible person.
Describe the deliverable the recipient actually needs.
The Operations Agent can help assemble a professional-services summary. Give that assignment its own Agent brief with the relevant sources and review.
Each task should hand something useful to the next person.
AI Chief connects the tasks, the handoff template states acceptance, and the dashboard shows the current result and questions.
A reviewable week
Use the midweek check to revisit the plan.
If a source or request changes, identify the affected section and the person deciding its next step. The exception-review article helps keep that discussion focused.
- 01
A request changes
The coordinator records the new condition and its source.
- 02
The owner checks the effect
Identify the result, tasks and decisions affected.
- 03
The team updates the plan
Agree the revised scope, reviewers and next handoff.
Close the week through the result and its use.
Ask the recipient which sections are accepted and which need another answer. The source-context article and approval packet help distinguish a source question from a decision.
| Review question | A useful answer identifies | A weak substitute |
|---|---|---|
| Is the preparation acceptable? | The relevant source and result version | A confident completion label |
| What remains open? | A question and its decision owner | An unexplained warning |
| What happens next? | An action within someone's authority | An automatic commitment |
Keep the next version tied to its own work.
Use an exception note for a changed condition. Small-business and growing-company examples help choose scope. Review integration requirements, compare plans, or describe your team through the company form.
Questions, answered.
What should I write first?
The result and recipient, followed by sources and the work needed to produce it.
Who sets the review conditions?
The intended recipient and the people responsible for the work agree them together.
What belongs in the midweek check?
Changed inputs, affected tasks, open questions, and decisions about the plan.
How should the week close?
Record accepted results, corrections, decisions, and the next responsible person.