Power Automate and AI Builder Checklist
Confidence policy, Approvals, limits, and retry keys. 0.65 is an example.
Download the Power Automate AI Builder checklist (ZIP)
Use this resource to define confidence handling, human approval, connector limits and failure behavior before a draft write. It is designed for Microsoft-stack teams designing document intake with Power Automate, AI Builder and Approvals.
Download the Power Automate and AI Builder Checklist
What is included
- a confidence-policy worksheet
- required-field and conflicting-total checks
- an Approvals ownership checklist
- connector and licensing questions
- normal, low-confidence, timeout and duplicate test cases
The files use fictional examples so you can inspect formulas, fields and expected results without exposing customer or financial data.
How to use the pack
- Choose one document family and record the fields that must be present.
- Set review rules per field; 0.65 is an example from Microsoft documentation, not a universal threshold.
- Name the Approvals owner and define what happens when that person is unavailable.
- Test missing fields, conflicting totals, duplicate files and approval timeouts.
- Allow a draft write only after the required checks and human decision pass.
Worked example
An invoice arrives with high confidence for the supplier and total but low confidence for the invoice number. The flow sends the original file, extracted values and confidence to the reviewer. No draft is created until the reviewer corrects the number and approves.
The useful evidence is the comparison between expected and actual behavior. Record corrections and rerun the same case after a change so the team can see whether the fix worked.
What to verify before launch
- The source file remains available beside any extracted or summarized values.
- Missing information stays missing until a person supplies or confirms it.
- Duplicate and retry rules prevent a second destination record.
- A named person owns exceptions and approval decisions.
- Failed runs remain visible and can be replayed safely.
- Access, retention and deletion rules match your organization’s requirements.
Limits
Confidence is a review signal, not proof that a field is correct. Licensing, Copilot Credits, connector limits and tenant interfaces change; confirm them in the Power Platform admin centre.
Read the paired implementation guide for the surrounding workflow. If the owners, rules or acceptance criteria are still unclear, start with an AI Success Audit. If the workflow is defined, book an AI Automation Systems conversation.