Weekly report, written from the work itself
Weekly reports are honest exactly to the degree they are written from the work itself rather than from memory. I run this one myself: it fills my own section in a shared company tracker every week, append-only, with my colleagues' sections byte-verified untouched. So this one reads the work.
How it works
Four steps, and the collector is the one that matters. It carries no AI at all, so the raw material of the report cannot be invented.
Deterministic, and dumb on purpose
Commits, tickets and documents since the last filled week. No AI in the collector – it cannot hallucinate what happened.
Your house style
The AI synthesises the raw items into a section in your house style – the same tone as the entries you wrote by hand.
You read it first
You read the exact text before anything moves. Publish happens on your OK, not on a timer.
Append-only, byte-verified
Append-only into the shared document. Colleagues' content is byte-verified untouched. A Monday nudge fires if last week's section is missing.
What you gain
- Backfill is free: a missed week is collected from the same sources as a fresh one
- The report reflects shipped work, not remembered work
- Co-authors' sections cannot be damaged – by construction, not by promise
Honest limits
- It reports work that leaves traces in systems; off-system work still needs a human line
- Our own Monday nudge once sat silently dead for six weeks before an audit caught it. Monitoring the monitor is part of the deliverable now – that lesson is included in the price
indicative, not a quoted delivery date
Who writes your weekly report, and from what?
Tell me on a 30-minute call – if the work leaves traces, the report can read them.