LearnGrokYou need a short chain of work, not one broad request. These prompts take you from the agreed service schedule to an escalation brief that shows the target, the result and the evidence behind it. They suit operations leads managing outsourced services or key suppliers.
Start with the signed documents and the reporting period. Keep the source files available while you work. The model can organise evidence, but it cannot resolve a missing definition or decide which conflicting report is authoritative.
1. Build the agreed measure register
Use Extract agreed service levels before looking at performance. Paste the relevant contract clauses, service schedule, approved change controls and formally agreed clarifications. Do not paste a sales proposal as though it were agreed wording.
The output gives you a measure register. Check that every row has a target, unit, period and calculation basis. A target such as respond promptly is not testable. A target such as 95% of priority 2 tickets responded to within 30 minutes each calendar month is testable, provided the ticket source and exclusions are known.
Key point
Test the definition before the result
A reported miss is only useful if the agreed measure, reporting period and calculation method match the data you are using.
If the agreement contains several documents, clause references matter. They let the supplier and your internal colleagues find the same wording quickly. Keep conflicting wording visible rather than selecting the version that best supports escalation.
2. Compare like with like
Use Compare monthly performance with targets once you have the confirmed measures and the relevant supplier report. Include internal records where you have them, plus incident logs, approved downtime and agreed exceptions.
The prompt produces three useful outputs: tested measures, measures that cannot be tested, and any trend across periods. The cannot determine section is not a failure. It is evidence that the reporting process needs a decision or an additional record before you make a stronger claim.
Check the reporting period in every source. A monthly service-level target cannot be compared cleanly with a rolling-quarter figure unless the agreement permits that calculation. Also check the direction of the target. A maximum incident resolution time and a minimum availability percentage need opposite variance calculations.
Check
Match four fields on each row
The target, unit, period and data source should match between the agreement and the reported result. If one does not match, retain the row but mark it unclear.
3. Audit the evidence, not just the narrative
Use Check evidence before escalation when you have a draft comparison or a supplier report containing explanations. This is where you catch statements that sound plausible but cannot be traced to a clause, report row, ticket or dated correspondence.
Give the prompt the draft brief as well as the underlying records. It will identify unsupported claims and recalculate figures. Review its Claims to remove or qualify section carefully. In particular, distinguish these statements:
The reported result was below the stated target.The supplier caused the operational impact.The agreement entitles us to a particular remedy.
The first may be supported by a report and service schedule. The other two usually need more evidence or internal confirmation. Keep the escalation brief factual until that work is complete.
Watch out
Do not let a root-cause explanation become a fact
Record the supplier's explanation as their explanation unless an independent record supports it.
4. Prepare the escalation brief
Use Draft the supplier escalation brief after the evidence audit. It gives you a meeting-ready structure rather than a long summary of every issue. Paste the validated comparison table, not an earlier draft with unverified results.
The requested actions should be practical. Ask for a named owner, a specific deliverable, a due date and evidence that shows completion. For example, a request for a corrective plan should state which missed measure it addresses and what reporting will demonstrate improvement.
Only include service credits, remedies or formal escalation routes where the supplied wording supports them. Where the wording is unclear, the prompt labels it for internal confirmation. That prevents the brief from presenting an interpretation as an agreed entitlement.
5. Keep commitments from disappearing
Use Set actions and remedy follow-through immediately after the escalation meeting. Paste the meeting notes while actions, owners and disputed points are still clear. The tracker separates an agreed action from a suggestion, and a submitted item from an accepted one.
Use the tracker at the next governance meeting. Review overdue actions first, then recurring misses, then unresolved evidence gaps. Do not close an action because the supplier says it is complete. Close it when the agreed acceptance evidence is present.
| If you see this | Do this | Keep it out of the brief until |
|---|---|---|
| Supplier and internal figures differ | Show both figures and request reconciliation | A common calculation and source are agreed |
| A target has no stated unit or period | Mark the measure untestable | The definition is confirmed in writing |
| An exception is claimed | Request its approval and scope | It is shown to apply to that measure and period |
| A remedy is mentioned without clause wording | Record it as a decision pending | The relevant wording is checked internally |
Note
Preserve the audit trail
Save the source report, clause reference and calculation used for each missed measure. The brief may be short, but the evidence file should let someone reproduce every line.
The available input handling and other operational limits depend on the version you are using. Check the xAI documentation overview before pasting large contracts or long reporting histories.
When the output does not work
Do not ask for a more forceful draft when the evidence is weak. Go back to the first missing input: the clause, report row, calculation method, approved exception or incident record. Run the evidence audit again after you add it.
If the output mixes periods, changes a target or supplies an unreferenced conclusion, discard that row and rebuild it from the source material. If the supplier challenges a result, keep the disputed figure in the tracker, request the underlying data and record the issue for the next governance review.
