Write an action as a verb and an observable result. “Follow up on testing” leaves room for interpretation. “Rerun six payment tests and attach the results” gives the owner a clear finish line.
From commitment to evidence
Use one owner for each row, even when several people contribute. Agree a due date and a status vocabulary with the team. The evidence column can contain a file name or reference to the completed work; it should not contain a password or access token.
Fictional example
A-01: Rerun six payment tests and attach the results. Owner: Sam Lee. Due: 13 October 2026. Status: In progress. Evidence: Results pending.
The downloaded Excel file is a simple editable record. It does not send reminders, connect to calendars or update an external task system.
Read the columns as a workflow
Give every row a stable ID and one responsible owner. Keep the same ID when the record moves to another week; this lets a reviewer trace a change instead of treating it as new work.
- Action
- State one observable result. Split separate commitments when they have different owners.
- Due date
- Use an agreed date; do not create a deadline from a guess.
- Status
- Keep unfinished work separate from work complete with evidence.
- Completion evidence
- Record a result, document reference or confirmation. A status label alone is not evidence.
One filled row, with context
This fictional Northstar example is a starting point for your own wording. Replace every placeholder, confirm the owner and agree the next review date.
| ID | Action | Owner | Due date | Status | Completion evidence |
|---|---|---|---|---|---|
| A-01 | Confirm fallback environment access. | Sam Lee | 2026-10-12 | In progress | [Add request or test reference] |
Maintain the record after the first download
Keep one editable copy as the source. When an item changes, update the response, date and evidence together. If a record is closed, retain its ID and outcome instead of deleting the trail. These downloads do not sync, notify owners or validate acceptance.