A usable assessment plan tells the Control Tester what to examine and gives the Independent Reviewer a clear basis for approval. Start with the business unit and risk, then define the control work and period. The approval must identify the scope revision that will guide testing.
Admin confirms the organization, business-unit code and team-member identities. AML Program Manager records the risk with its likelihood, impact and scale version, then links the relevant controls. Check that the assessment and business unit refer to the same organization.
AML Program Manager creates a Draft assessment with its subject, owner, planned testing and period. Write a scope statement that describes the intended examination. Set a positive revision and resolve the period before asking a colleague to review the package.
Independent Reviewer examines the scope and approves, rejects or returns the submitted revision with a reason. An approval supports moving the assessment from Draft to Planned. A rejection or return keeps it in Draft while the manager corrects the identified issue.
AML Program Manager gives the Control Tester the approved plan and evidence expectations. Reconcile the guarded operation receipt against the review decision. If the scope changes, bring the new revision back for review before relying on the previous approval.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.