Build a weekly team digest from local notes

A digest should make the week’s changes easy to scan without repeating the entire activity log. Define the reporting window and include unresolved decisions.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: Dated team notes and a prior digest.

Work through the task

1. Group updates by outcome rather than author.
2. Separate completed results from plans.

A brief you can adapt

Create weekly-digest.md with wins, blockers, decisions needed and next-period plans. Cite the source note for each result and preserve unknown dates.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Check the date window and remove items already reported unless their status changed.

Where this approach can fail

Do not infer completion from an optimistic progress note.

For the related desktop setup, see review results.