Playbooks
One playbook for each compliance job
Each playbook is a packaged recipe for an agent: what starts it, what it does, which Arakan tools it may use, and what stays with a person. Draft playbooks are being piloted with partners and may change.
Anti-money laundering
Know who the client's customers are, screen them, and keep the evidence.
Customer due diligence for real estate and precious-metals dealers
DraftWhen a deal is created or changes in the client's ERP or CRM, identify the customer and its owners, screen them, check the deal against the reporting thresholds, hand anything that needs judgement to the MLRO, and file the evidence for the retention period.
Uses Comply, Verify, Vault
Read the playbook
Ongoing re-screening of existing customers
DraftScreen the client's existing customers again on a schedule and when a customer's details change, compare each result with the last screening, and send only what changed to the MLRO.
Uses Verify, Vault
Read the playbook
Client onboarding (KYC) for corporate service providers and accounting firms
DraftWhen the firm wins a new client, add it to the firm's client list, collect and read its company documents, record its owners, screen the company and its owners, and hand the customer due diligence decision to the MLRO.
Uses Onboard, Verify, Vault, Shield
Read the playbook
Compliance programme
Keep the client's programme current: deadlines, evidence, policies, licences and scope.
Licence and renewal watch
DraftWatch the company's trade licence, regulatory licences and permits, and the renewals in its compliance calendar.
Uses Comply, Roster, Onboard, Vault
Read the playbook
Monthly compliance close
DraftAt month end, find what was due in the client's compliance programme, collect the evidence from the client's own systems and file it in Arakan, chase owners for what is missing, and give the compliance officer a one-page close report to sign off.
Uses Comply, Roster, Vault, Lexara
Read the playbook
Policy refresh after a law change
DraftWhen the regulatory feed shows a change, find the client's policy clauses it may affect, prepare what would need to change, and send it to the policy owner.
Uses Comply, Lexara
Read the playbook
Regulatory scope when the business changes
DraftWhen a client adds or drops an activity, moves zone, changes legal form or grows its team, bring the change into Arakan, re-run the company's regulatory scope and show the compliance officer what changed: regulators and obligations added, those that may no longer apply, and the questions that would settle the rest.
Uses Onboard, Scope
Read the playbook
Board and governance
Board and committee meetings, minutes and follow-ups.
Workforce
Employees, permits, WPS and Emiratisation.
Tax and bookkeeping
VAT periods and the documents behind them.
Company changes
Closing a company, or changing its ownership.
Closing a solvent company
DraftOnce the owners have decided to close a company that can pay its debts, keep its closure case moving: gather the facts from the company's records, prepare the case for a person to open, collect proof for each step and clearance, chase what is overdue, and report what still stops the closure.
Uses Dissolve, Comply, Govern, Lexara, Vault
Read the playbook
Restructuring a business so investors can come in
DraftOnce the owners and their adviser have decided to restructure (convert to an LLC, move the business into a new LLC, or swap shares into an ADGM or DIFC holding company), keep the Flip case moving: gather the facts, prepare the case and the asset register from the company's records, collect proof for each step, chase what is overdue, and report.
Uses Flip, Lexara, Vault
Read the playbook