Service model
Control map
A fixed sequence so internal control work ends with artefacts your team owns—not a deck that expires when fieldwork closes.
-
Scope — name the stuck cycle
We begin with one decision your team cannot settle: a disputed approval path, a reconciliation nobody trusts, or a walkthrough that reinvents itself each year. Breadth stays intentionally narrow.
-
Access — read-only by default
You grant temporary read access to ledgers, approval logs, policy packs, and relevant system reports. Write access to production finance systems is not required for review work.
-
Inventory — surface the contradictions
Design narratives, owners, sample evidence, and system paths are listed before recommendations. Synonyms, rubber-stamps, and silent gaps appear here—not as a Friday surprise.
-
Test — rank by reporting impact
Samples and walkthroughs are ordered by how much they change decisions this quarter. Cosmetic policy edits wait behind broken evidence paths and ownership without authority.
-
Handoff — artefacts stay with you
You leave with written narratives, sample schedules, and a remediation briefing. We do not keep operating your control environment unless you separately book Control Office Hours.
Ready to start?
Most teams begin with an Internal Control Review. If you already know which cycles look mature on paper but fail under sampling, tell us which ones and we will suggest a Control Maturity Assessment instead.