What does the aml control testing planner produce?
Prepare an exact control-testing scope, selected population, test schedule, acceptance criteria and required evidence workpaper.
Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.
What do you need before you start?
- Define your scope and approved method.
- Retain actual original evidence and reviewed source references.
- Resolve input errors before preparing a complete result.
What information do you enter?
Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.
- Exact reference, organization, subject, responsible reviewer and preparation date.
- Your scope and policy reference, version, approver, approval date and actual supporting source IDs.
- Named task rows, relationships, rules and evidence annotations entered through the task-specific editor.
- Unchanged original files with exact filename, MIME type, byte count and SHA-256.
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.
How does the aml control testing planner work?
- 1Define the evidence basis
Exact reference, organization, subject, responsible reviewer and preparation date.
- 2Enter task-specific records
Compare declared and supplied control population counts. Bind each planned test to one control, exact selected item IDs, named tester, planned period, selection basis, expected evidence and exception threshold. Check full-population selection for all-items methods and retain omitted or orphan records. Mark all plans as unperformed.
- 3Inspect complete findings
Review exact calculations, source gaps and unresolved items.
- 4Keep recoverable work
Save drafts and exact original bytes in this browser. Restore a complete ZIP after validating tool identity, every original hash and full prepared results. Recovery clears payment and source authorization.
- 5Prepare finalized evidence
Prepare the complete pack, then download them free.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
Common questions
What information does the aml control testing planner need?
Enter exact reference, organization, subject, responsible reviewer and preparation date; your scope and policy reference, version, approver, approval date and actual supporting source IDs; named task rows, relationships, rules and evidence annotations entered through the task-specific editor; unchanged original files with exact filename, MIME type, byte count and SHA-256. Define your scope and approved method.
What does the aml control testing planner produce?
Prepare an exact control-testing scope, selected population, test schedule, acceptance criteria and required evidence workpaper. Complete named findings, exact calculations, original source references and unresolved evidence. Formal PDF and DOCX, complete Excel and findings CSV, source manifest, recoverable workspace, exact originals, instructions and delivered file hashes. Review unresolved findings and limitations before use.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the aml control testing planner for this task?
Prepare the testing scope and required evidence. Original evidence bytes, annotations and customer rules remain in this browser. Original files are not saved to the cloud. Customer verification and approval are declarations. Mechanical results do not authenticate source facts, decide legal applicability, clear screening hits, authorize transactions, classify exports, file reports or establish total wealth.
What still needs review?
Original evidence bytes, annotations and customer rules remain in this browser. Original files are not saved to the cloud. Customer verification and approval are declarations. Mechanical results do not authenticate source facts, decide legal applicability, clear screening hits, authorize transactions, classify exports, file reports or establish total wealth.
Selected-ID arrays support the full 100-item supplied population per planned test. No statistical representativeness, operating effectiveness or independence opinion is inferred.
At most 100 task rows, 100 KB input, 300 KB result and 500 KB workspace metadata. Original files support 20 files, 10 MB each and 25 MB total. Private cloud saving retains its separate 5 MiB file and 16 MiB total limits.