Automate month-end variance commentary
Have an agent compare actuals to budget in Power BI and draft the narrative controllership normally writes by hand.
Combine a Copilot Studio agent with deterministic Power Automate steps to extract, classify, and validate contract terms across a batch of documents.
Contract intake that surfaces non-standard terms for legal review in hours instead of a manual read-through of every document.
The apps run in this order.
Write down the specific clauses and terms (termination notice period, liability cap, payment terms, auto-renewal) and the acceptable ranges for each, sourced from your legal team's playbook. This becomes the agent's grading rubric.
In Copilot Studio, build an agent that reads a contract and returns the key terms as structured fields, plus a flag for anything outside the approved ranges — not a free-text summary.
Prompt idea:
Extract the termination notice period, liability cap, payment terms, and auto-renewal clause from this contract. For each, state whether it falls within our standard range (see attached playbook) and flag any that don't, with the exact clause text quoted.
Use an "Apply to each" loop over the SharePoint contract library, calling the agent via the Execute Agent action for every document and writing the returned fields into a tracking list's columns, not a single free-text field — structured columns are what let you filter and report on flags later.
Add "Configure run after" on each step so one failed document (a corrupted file, a locked contract) logs an error and moves on instead of silently stopping the whole batch. Before pointing it at the full library, run it against a handful of contracts you already know the answer for — some clean, some with a deliberate non-standard clause — and confirm the flags land where expected.
Have the flow notify the legal team in Teams or Outlook for any contract with a flagged clause, including the quoted clause text so they don't have to re-open the document to see what tripped the flag.
A SharePoint list of every contract in the batch with extracted key terms, a flag for non-standard clauses, and a routing status.
This workflow already draws the line correctly: step 3 keeps routing and notifications in deterministic Power Automate, and only step 2's actual clause-reading and judgment against the playbook goes to the agent. That split is the model, not an afterthought.
Have an agent compare actuals to budget in Power BI and draft the narrative controllership normally writes by hand.
Use the Execute Agent action to route a reasoning-heavy step in a flow to a Copilot Studio agent instead of hard-coded logic.
It's end of quarter and the raw numbers just came in.
Workflows like this tend to raise real governance and licensing questions once more than one person is using them — that's exactly what we help with.