An internal-control walkthrough asks a simple question: how is this control actually performed, and how do we know? The answer usually lives in one person’s head. Claros captures it while that person does the work, and exports it as a walkthrough workpaper.

​
Export it

On a rule set, open Export → Audit walkthrough (PDF). The page at /map/{workflow_id}/walkthrough is a printable workpaper; Export PDF prints it. A Changes tab compares two versions of the map, for a year-over-year walkthrough. The same record is available as JSON from GET /api/workflows/{workflow_id}/walkthrough and GET /api/workflows/{workflow_id}/walkthrough/diff. The record is built deterministically from the stored map, its capture session and the request inbox. No model is called to write it.

​
What it contains

​
What it leaves to the auditor

Anything the owner did not say is marked to confirm or ask, with the question to ask, never filled in: control objective, risk, assertion, frequency. Preventive/detective, manual/automated, key/non-key, inspection, re-performance, sample selection and the reviewer sign-off are outside a capture and stay with the auditor.
Claros does not replace the auditor’s judgment. A walkthrough combines inquiry, observation, inspection and re-performance; a capture gives you strong inquiry and observation evidence, not the other two.
For evidence that the control ran on every action, add the check log.