HomeSolutions · By role
For compliance officers

When the auditor says "show me", the answer is a click.

You own dozens of policies across several regulators and you have to justify every purchase internally. Blueprint+ gives you the one thing a shared drive never will: proof. Which policy, which version, who approved it, who read it, which rule it satisfies.

Evidence pack · AML and Sanctions Policy
Current version
v2.4, published 12 May
Locked
Approved by
Head of Compliance, Board Risk Committee
Signed
Regulatory basis
CBUAE AML Circular 2023 (12 of 14 clauses), FATF R.10
Linked
Acknowledged
770 of 1,032 staff · reminders running
75%
Previous versions
v2.3, v2.2, v2.1 archived with history
Kept
What you can hand an auditor for any document, on demand (illustrative)
Your week, before and after
Before
  • Mon
    Chase three approvers by email

    Two reply. One is on leave; the policy misses its review date.

  • Tue
    A new circular arrives

    Read every policy that might be affected. Find four. Miss the procedure.

  • Wed
    HR asks who has read the new code of conduct

    Export the LMS, match names in a spreadsheet, estimate.

  • Thu
    Audit request: evidence for 12 controls

    Open the mapping workbook. It is six months old.

  • Fri
    Build the quarterly governance deck

    Collect status by email. Paste. Chart. Repeat next quarter.

After
  • Mon
    Open the approvals inbox

    One overdue approval, already escalated to the CCO by the workflow.

  • Tue
    The circular is logged in the Regulations Library

    The five documents citing the amended clause are listed; re-review workflows have started.

  • Wed
    Acknowledgement dashboard, by department

    71% acknowledged, reminders scheduled. Send HR the link.

  • Thu
    Filter the Linkages view by the 12 controls

    Export. Done before lunch.

  • Fri
    Open the saved board report

    It ran this morning.

Proof
What you get

Audit-ready history on demand

Every version, approval and acknowledgement is recorded as it happens. The evidence pack is the system itself. Policy management →

Acknowledgement you can prove

Who has read and signed, who has not, by department, with reminders that run themselves and MCQ scores where you need comprehension.

Regulatory gaps found first

The Consistency Check reports clauses with no regulatory basis and regulations with no policy, before the inspection does. Regulatory tracking →

A board view that is always current

Dashboards and scheduled reports built from live data, not a deck assembled by hand. Reporting →

Security you can defend internally

Role-based access, SSO, audit logs on every action, and a Trust page you can forward to IT security. Trust & Security →

Procedures staff can follow

Flows with screen recordings on the step that needs them, and assessments that show it was understood.

Making the case internally

What to tell procurement, IT and the board.

You will be asked three questions. Here are the pages that answer them.

  • "Is it secure enough for our risk data?"
    Certifications, hosting regions, encryption, SSO, audit logs and the DPA, on one page you can forward. Trust & Security →
  • "What does it cost and how do we buy it?"
    Three tiers, a comparison table and the procurement FAQ: data export, contract terms, SSO by tier. Pricing →
  • "Does it actually handle our lifecycle?"
    Start a trial with sample policies loaded and run one of yours through review, approval and acknowledgement. Start free trial →

Walk one of your own policies through it this week.

Work email, no card. Sample policies loaded so day one shows the product doing something.