# Recipe: evidence gatherer

For anyone whose Build brief idea is still blank. Swap in your own systems and this is yours in ten minutes.

**The pain it copies:** a recurring review (an audit, a compliance check, a monthly report) needs evidence pulled from several systems by hand, then assembled into one document a human signs off on. Vivek's audit workflow is the reference case: two weeks of manual gathering down to 2 to 3 hours.

## The five blocks

- **Trigger:** the review's own schedule (monthly, quarterly), or on demand when someone asks for the evidence pack.
- **Input:** the systems the review checks: tickets, logs, config, transaction records, whatever the reviewer opens by hand today.
- **Work:** pull the relevant evidence from each system for the review period and assemble it into one document, organised the way the reviewer expects it.
- **Check:** every piece of evidence in the output traces back to where it came from: a link, a query, a filename. Nothing in the document is unsourced.
- **Output:** the assembled evidence pack, handed to the human who signs off. This recipe does not replace that sign-off.

## Swap in your own systems

- Two systems is enough to start. Add more once the first pass works.
- If you don't have a real recurring review, use any task where you open multiple tabs today to answer one question.
- To make the Trigger real: a [Claude Code routine](https://code.claude.com/docs/en/routines) on a weekly or monthly schedule matches how most reviews already run.

## Done when

It pulled evidence from at least two real systems into one document, every item is sourced, and the human reviewer only had to check the evidence, not go find it.