Checking compliance manually takes hours. Claude can identify gaps between your documents and your requirements.
Compliance checks — verifying that a policy, process or document meets a set of regulatory or internal requirements — involve reading two or more dense documents side by side and identifying what is missing, inconsistent or unclear. Done manually, this is slow, prone to oversight and often requires significant legal or compliance expertise just to know what to look for.
Claude can help with the gap analysis step. Provide the document you want to check and the requirements it needs to meet, and Claude can identify where the document is compliant, where it falls short, and what needs to be added or changed — giving your compliance team a structured starting point rather than a blank page.
Key insight: Claude checks compliance against the requirements you provide — it does not know current regulations autonomously, and its gap analysis must always be validated by a qualified compliance professional before any action is taken.
Policy gap analysis
Check whether an internal policy covers all the requirements of a regulation or standard you provide.
Document compliance review
Identify which clauses or sections of a document meet requirements and which need updating.
Requirements mapping
Map each requirement from a regulation to the relevant section of your policy or procedure.
Without Claude
Read two documents side by side for hours, manually cross-referencing requirements against policy language and hoping nothing is missed.
With Claude
Get a structured gap analysis in minutes — a clear view of what is covered, what is missing and what needs to change, ready for expert review.
A structured compliance check workflow keeps the analysis grounded in the documents you provide and produces findings a professional can act on.
1
Identify the document and the requirements
Decide which document you are checking (a policy, procedure or contract) and which requirements it needs to meet (a regulation, standard or internal framework).
2
Prepare clean versions of both texts
Copy the document under review and the requirements into plain text — removing formatting that could confuse the analysis.
3
Ask Claude to run the gap analysis
Paste both texts and ask Claude to identify which requirements are met, which are partially met and which are missing from the document.
4
Review the findings with a compliance expert
Have a qualified professional validate the gap analysis — Claude may have missed nuances or misread how a requirement applies to your context.
5
Update the document and re-check
Make the changes identified in the gap analysis and run a second check to confirm the gaps have been closed.
Note: Claude checks the document against the requirements you provide — if the requirements text you paste is outdated or incomplete, the gap analysis will reflect that. Always use the current, in-force version of the regulation or standard.
These prompts help run a gap analysis between a document and a set of requirements, with clear limits on what Claude should conclude.
Prompt 1 — Run a compliance gap analysis
Check the following document against the requirements listed below and identify any gaps.
Document to check: [Insert Document Text]
Requirements to check against: [Insert Regulation / Standard / Internal Policy Requirements]
For each requirement, state whether the document: (a) fully meets it, (b) partially meets it, or (c) does not address it. For gaps, note which section of the document is affected.
Crucial instruction: Base your analysis solely on the two texts provided. Do not add requirements from external regulations not included in the requirements text, and do not interpret ambiguous language as compliant.
Prompt 2 — Map requirements to document sections
Map each of the following requirements to the relevant section of the document provided, and note any requirements that are not addressed.
Requirements: [Insert Requirements List]
Document: [Insert Document Text]
Present the output as a table with columns: Requirement, Document Section, Status (Met / Partial / Gap).
Crucial instruction: Only reference sections that exist in the document provided. Do not suggest that a requirement is met if the document language is vague or ambiguous.
Before acting on a Claude compliance gap analysis
Requirements current: are you using the in-force version of the regulation or standard, not an outdated draft?
Expert validation: has a qualified compliance professional reviewed the gap analysis findings?
No invented requirements: has Claude not added regulatory obligations not present in the requirements text you provided?
Context applied: has the expert considered how requirements apply to your specific organisation and context?
Re-check planned: is there a plan to re-run the check after the document has been updated?
Important: A Claude gap analysis is a starting point, not a compliance sign-off. Regulations are interpreted differently across jurisdictions and contexts — only a qualified compliance professional can determine whether your organisation is actually compliant, and Claude's output must never be used as evidence of compliance.