Workspace
The audit documentation workspace, mapped
A plain-language model of how Intelligentwebapi thinks about folders, indexes, and sign-off before you step into a full course.
Three layers
Structure — a shallow tree that mirrors phases, not every workpaper title. Deep nesting is treated as a smell.
Trail — each significant conclusion points to a source pack ID and a residual note. Trails are written for the next reader, not the author.
Sign-off — review points live in one place with owner and disposition. Email is a channel, not the archive.
-
Index as a map, not a dump
The index should answer “where would a cold reviewer look?” rather than list every PDF. We teach pruning rules that keep the map short.
-
Source packs with boring IDs
Stable identifiers beat clever titles. When staff rotate, boring IDs are what keep trails intact.
-
Close-out artefacts
Final analytical review, subsequent events note, and representation checklist sit in a fixed close-out shelf so partners know where to land.