Compliance · 5 min

What an auditor actually asks about your software

Not “is it clever.” They ask what it touched, what changed, and what you reviewed. If you can't answer in writing, you don't have a clever-software problem — you have an evidence problem.

An auditor doesn't care that your system is clever. They care about three plain questions: what did it touch, what changed, and what did a human review before it shipped?

Most fast-built software can't answer any of the three in writing. Something made a decision, no one recorded why, and the trail stops. That's not a gap you paper over later — it's an architecture decision you made on day one without noticing.

The fix is boring and it works: record activity like a black box, keep the evidence, and make the answer a document, not a scramble.

This is the part we do — the crossing from a demo to a system that survives production.