Make work updates useful to the people reading them.

An attendance record, a task update and a project review answer different questions. Treating them as one report can leave the reader with lots of information and little clarity. Start by asking what each person needs to know and what they will do with that information.

The useful reporting rhythm depends on the assignment. A daily operating task may need a different review cycle from a short campaign. Agree that rhythm with the people doing and managing the work.

Use a consistent set of fields so updates can be understood without a fresh explanation each time. Keep room for context when a task cannot be completed as planned.

• The assignment, location and reporting period
• Work completed against the agreed plan
• Open issues and the support needed
• The person responsible for the next action

A report is more useful when a concern receives a response. Record who will act on a blocker and when the team will review it again. Revisit the format after the first few reporting cycles: remove information nobody uses and clarify fields that different people interpret differently.