How to generate a compliance checklist in Microsoft Copilot: step by step

João Barros 02 de November de 2026 4 min read

This guide shows how to create an assistant in Microsoft Copilot to generate compliance checklists from internal policies and regulatory requirements. An automated checklist helps standardize audits, reduce human errors and speed up reviews.

Prerequisites

Account with access to Microsoft Copilot (including Copilot Studio if available).
Files of internal policies or summaries of standards in Word/PDF or plain text.
Permissions to create and test agents/flows (if using Copilot Studio or Power Automate).
Simple text editor to create prompts and templates (e.g.: Notepad, VS Code).

Step 1: Define the checklist objective

Start by clarifying what the checklist should cover: applicable standards, periodicity (daily, monthly), owners and required evidence. Specify the final format (list, table, columns: item, criterion, evidence, status).

Step 2: Prepare policy examples

Gather 3–5 representative excerpts of your internal policies. These examples help Copilot understand the language and extract items. Include different levels of detail (procedures, requirements, metrics).

Step 3: Create a base prompt to extract items

Write a clear prompt that requests the extraction of checkpoints, format and priority. Test locally in the editor before sending to Copilot.

Extract compliance checklist items from the following policy excerpt. Output as a markdown table with columns: Item, Criterion (one sentence), Evidence required, Frequency (daily/weekly/monthly), Owner.

Policy excerpt:
"[cole aqui o texto da política]"

Only list concise items. If unclear, mark "Clarify" in Owner.

Step 4: Test the prompt in Microsoft Copilot

Paste the policy excerpt in the chat or agent and send the prompt. Check that the output follows the format and contains actionable items. Adjust the prompt to clarify format or levels of detail.

Step 5: Refine for source variation (Word/PDF)

If policies come in Word/PDF, convert or copy the text without noise. To automate, configure an input that accepts files and extracts text before passing it to Copilot.

// Exemplo conceptual para um flow que extrai texto de PDF (Power Automate pseudocódigo)
1. Trigger: Upload de ficheiro na pasta "Policies"
2. Action: Converter PDF para texto (OneDrive/SharePoint connector)
3. Action: Send extracted text to Copilot agent via API or Copilot Studio input
4. Action: Save checklist output como ficheiro Markdown/Excel

Step 6: Add validation rules and clarification questions

Instruct Copilot to automatically ask when a requirement is unclear or when there are gaps. Use conditional prompts to generate concise questions to the owner.

When an item has no clear owner or evidence, append:
"Question: Who is responsible for this item? Provide contact role."

Step 7: Generate versions for audit and operations

Create two formats: a detailed version for auditors (content, legal references, accepted evidence) and a simplified operational version (only checkboxes, owner, periodicity).

// Prompt para versão operativa
Generate a concise checklist table suitable for daily operations: columns = Task, Owner, Frequency, Checkbox. No legal references.

Verify the result

Confirm that the checklists have actionable items, assigned owners or marked as "Clarify", coherent periodicities and described evidence. Perform a manual review with an area owner and run a practical test: follow the checklist in a real task and record if items are missing or if there is ambiguity.

Conclusion

With a structured prompt and real examples, Microsoft Copilot can transform policies into useful checklists for audit and operations. Next steps: automate file ingestion, integrate with Power Automate for flows and link output to Excel/SharePoint. Tip: maintain a small set of refined prompts per domain to reduce common extraction errors.