← Files Rohas Legal AI: RegulatoryARCHIVED FILE

skills/licence-application-drafter/SKILL.md

3.53 KB · Oct 5, 2026 · 18:30 UTC

↓ Download file

---
name: licence-application-drafter
description: >-
  Prepare regulator-facing licence, permit, authorisation, approval, registration,
  renewal, variation, and change-of-control applications. Use to map eligibility,
  forms, ownership, fitness, capital, governance, systems, policies, evidence,
  fees, conditions, and post-approval obligations.
---

# Licence Application Drafter

Use the regulator's current official form, portal, instructions, eligibility rules,
and published criteria as of the submission date. Treat the application, business
plan, policies, financial model, ownership data, and supporting evidence as one
internally consistent representation.

## Intake

Obtain the jurisdiction, proposed regulated activity, products, customers, channels,
territories, applicant and group structure, controllers and beneficial owners,
management, finances, premises, systems, outsourcing, policies, prior licences,
regulatory history, desired launch date, and regulator correspondence.

## Preparation method

1. Confirm the correct regulator, permission category, territorial scope, applicant
   entity, application type, prerequisites, exclusions, transition, and whether any
   activity must stop until approval is granted.
2. Freeze the current requirements set: statute, rules, licence criteria, form and
   version, guidance, checklist, portal fields, fees, declarations, translations,
   notarisation, certifications, and processing timetable.
3. Build a requirement matrix for eligibility, legal form, ownership and control,
   fit and proper status, capital and liquidity, governance, key personnel, premises,
   insurance, systems, cybersecurity, outsourcing, complaints, reporting, and records.
4. Map every answer to evidence and an accountable owner. Verify identity, names,
   dates, percentages, group relationships, financial figures, forecasts, policies,
   incidents, litigation, enforcement, and other applications across all documents.
5. Write the business and operating model in concrete terms: activity, customer
   journey, revenue, money or data flows, controls, staffing, vendors, resilience,
   wind-down or continuity, and phased implementation.
6. Identify gaps against approval criteria. Classify each as pre-filing blocker,
   application commitment, proposed condition, regulator question, or post-approval
   obligation; use evidence-based dates and do not conceal material weaknesses.
7. Draft responses in the form's order and vocabulary while preserving material
   nuance. Explain exceptions, adverse matters, corrective action, dependencies,
   and assumptions instead of forcing inaccurate yes-or-no answers.
8. Run completeness, consistency, legal, financial, privacy, privilege, signature,
   payment, format, and portal checks. Prepare likely regulator follow-up and a
   controlled update process for facts changing before decision.
9. Build a conditions and obligations register for commencement, renewal, reporting,
   notifications, fees, capital, audits, records, public disclosures, and variations.

## Output

Provide the applicability and route note, current-requirements register, completed
application draft, evidence index, gap and commitment log, consistency exceptions,
approval checklist, submission plan, and post-approval obligations calendar.

## Guardrails

Do not claim authorisation before grant, use an obsolete form, omit adverse facts,
invent evidence, or submit without explicit authority. Flag protected terms such as
"licensed" or "regulated," pre-approval activity, and material-change duties for
qualified local regulatory counsel.

SHA-256: 73ef67736fd2d5943e2dc90d594a3aa344fece7cca4ecd935d606402ff29f831