Weekly operations digest for leadership review

Use one source pack and one fixed digest structure each week. This gives senior managers the exceptions, decisions and overdue work without making them read daily updates. It is for operations leads who need a defensible weekly view, not a longer status report.

1. Set the reporting boundary

Choose a fixed reporting period, such as Monday 09:00 to Friday 17:00. Put that period at the top of every source document and the final digest. This prevents a Friday incident appearing in two reports, or a late update being treated as current when it belongs to the following week.

Create a folder or workspace for the week with these four inputs:

• Daily updates: team notes, handover summaries and delivery updates.
• Incident notes: incident records, post-incident notes and unresolved risks.
• Service data: agreed service measures, volumes, backlogs, response times or quality checks.
• Open actions: actions carried from meetings, incident reviews and prior digests.

Use the same naming pattern every week, for example Operations digest 3–7 June and Source pack 3–7 June. Keep the raw documents unchanged. Your digest is a summary layer, not the only record.

2. Build a source register before asking for a draft

Make a short table called Source register. It forces you to see gaps before the model turns incomplete material into smooth prose.

Source	Coverage	What to extract	Gap to resolve
Daily updates	All operating days	Changes, blockers, completed work	Missing team update
Incident notes	All logged incidents	Impact, current status, follow-up	No closure confirmation
Service data	Reporting period	Measures against agreed target	Late or partial data
Open actions	Current action list	Owner, due date, status	Unnamed owner or date

Add the document name and the date received for each row. If a service-data extract covers a different period, record that plainly. Do not silently compare a monthly figure with a weekly one.

Resolve the gaps you can. For those you cannot resolve, add a line to the source register such as: Customer support update not received at time of review. This is better than implying the function had no issues.

3. Define the exceptions that belong in the digest

Before drafting, decide what counts as an exception. Use rules that reflect your operating commitments, not what happens to sound important in a particular week.

Include an item when it:

• missed an agreed target or service level;
• created customer, supplier, operational or control risk;
• requires a senior manager to choose between options;
• has an action overdue, blocked or without an owner;
• has a material change in volume, backlog, capacity or delivery date;
• repeats an issue reported in the prior digest.

Do not include routine work just because it was completed. A single line of normal-service context is enough when it helps explain an exception.

4. Draft from the source pack using a fixed instruction

Paste or attach the source pack to the tool you are using. Check the current document-handling and usage details in the xAI documentation overview, as these are version-dependent.

Use this instruction, replacing the bracketed text:

Create a weekly operations digest for senior managers.

Reporting period: [date and time boundary]
Audience: [leadership group]
Source documents: [list each document name]

Use only the supplied sources. Do not infer missing facts, targets, owners or dates.

Write these sections in this order:
1. Executive position: three to five bullets covering the overall operating position and the most important changes.
2. Exceptions and risks: a table with issue, evidence, operational impact, current status, owner and next due date.
3. Decisions needed: a table with decision, options if stated in the sources, consequence of delay, decision owner and requested date.
4. Open actions: only overdue, blocked, unowned or newly raised actions. Include action, owner, due date and blocker.
5. Data gaps: missing, late, conflicting or unverified information.

Use concise factual language. Preserve numbers, dates and named owners exactly as supplied. Mark a field as 'Not stated in source' when it is absent. Separate facts from suggested wording.

Ask for a first draft only. Do not ask it to make the document sound more positive, more strategic or more reassuring. Those requests often remove the detail that makes an exception actionable.

5. Check the draft against the sources

Read the digest with the source pack open. Check every number, date, named owner and claimed status. The most dangerous errors are plausible ones: a due date copied from an old action, an incident described as closed when the note says mitigated, or a service measure presented without its target.

Use this check for each exception:

If you see this	Check this	Correct it by
A number or percentage	Period, unit and target	Add the source value or remove it
An owner	Named person or accountable team	Mark as unassigned if absent
A due date	Whether it is committed or proposed	Label a proposed date clearly
A resolved issue	Closure evidence	Use current status from the incident note

Then perform a leadership scan. A senior manager should be able to answer these questions in under five minutes:

1. Is the operation on plan, and what proves it?
2. What is off plan or becoming risky?
3. Which decision is needed, from whom, and by when?
4. Which action is blocked, overdue or ownerless?

If the answer is buried in a paragraph, move it into a table or a bullet. If two items describe the same root problem, combine them and retain the strongest evidence.

6. Publish, carry forward and reset

Send the final digest in the same place and at the same time each week. Put the reporting period in the subject line or file name. Keep the source register with the final version so a reviewer can trace a claim later.

After the leadership review, update the Open actions list immediately. Record the decision made, the confirmed owner and the due date. At the start of the next week, carry forward only actions that remain open. Do not copy the previous digest wholesale.

When the process does not work

If the digest is too long, tighten the exception rules before shortening the prose. If it lacks decisions, ask leaders which choices they need surfaced and add that rule to the instruction. If owners or dates are repeatedly missing, return the action to the meeting chair or operational lead who created it, rather than inventing a placeholder.

If source material arrives late every week, publish the digest with a visible data-gap note and agree a submission deadline with the missing team. The habit is not producing a perfect document. It is producing a traceable weekly view, then fixing the input that stopped it being complete.