The Procurement Copilot Prompt Library

22 min read
By Procurement Spectrum

10 tested, copy-paste-ready prompts for Microsoft 365 Copilot and other enterprise AI tools.
Works with: Microsoft 365 Copilot | Claude Enterprise | ChatGPT Enterprise | Gemini for Workspace


How to Use This Library

This library contains 10 tested prompts for Microsoft 365 Copilot and equivalent enterprise AI tools. Each prompt is designed for a specific procurement workflow and includes four components: when to use it, the exact prompt text with variable placeholders, what good output looks like, and a usage or governance note.

The prompts are organised across eight workflow categories. You do not need to use them in sequence — start with the workflow that represents your highest-value daily friction point. Each prompt is a starting template: replace the [PLACEHOLDER] fields with your specific context, and refine the prompt over time as you learn what produces the best output for your organisation.

Each prompt contains placeholders in [SQUARE BRACKETS]. Replace these with your specific context before running. The more specific your inputs, the more targeted and useful the AI output.

Governance Reminder
Prompts 05, 07, and 09 are marked with a governance note. These involve commercially sensitive data — supplier contracts, negotiation strategy, or invoice pricing. They must only be run using enterprise AI tools within your organisation’s governance boundary: Microsoft 365 Copilot within your M365 tenant, Claude Enterprise, ChatGPT Enterprise with data controls enabled, or Gemini for Workspace. Do not use these prompts with personal or consumer AI tools. All other prompts are suitable for any enterprise AI tool your organisation has approved.

The Prompt Index

#CategoryPrompt Title
01RFP & Scope Document Quality ReviewSpecification Completeness & Supplier Bias Check
02RFP & Scope Document Quality ReviewEvaluation Criteria Consistency & Weighting Review
03Bid & Proposal Compliance CheckingPre-Evaluation Supplier Submission Compliance Gate
04Bid & Proposal Compliance CheckingMulti-Supplier Response Comparison & Gap Analysis
05Contract Review & SummarisationIncoming Supplier Contract Key Terms Extraction
06Supplier Research & ProfilingPre-Sourcing Supplier Market Profile
07Negotiation PreparationSupplier Negotiation Brief & Leverage Analysis
08Supplier Risk AssessmentInternal Supplier Risk Signal Summary
09Spend Analysis & Variance ReviewOff-Contract Spend & Rate Card Variance Analysis
10Stakeholder Communication & ReportingSourcing Event Outcome Summary for Business Stakeholders

01 | RFP & SCOPE DOCUMENT QUALITY REVIEW

Specification Completeness & Supplier Bias Check

WHEN TO USE Before issuing any RFP, ITT, or RFI to the market. Run on the scope of work or requirements document prepared by the requesting business team — ideally 48–72 hours before planned issue, leaving time to resolve flagged items. Most valuable for complex services, IT, or consultancy categories where specifications are written by technical owners without commercial drafting experience.

THE PROMPT

Copy-Paste Prompt

You are a senior procurement professional reviewing a scope of work document before it is issued to suppliers as part of a competitive sourcing event.

Review the attached document and identify:

  1. SPECIFICATION GAPS: Any sections where requirements are too vague for a supplier to price accurately or submit a comparable response. Flag the specific section and explain what information is missing.

  2. SUPPLIER OR PRODUCT BIAS: Any language that describes requirements using a specific vendor’s proprietary terminology, product names, or capabilities that only one or very few suppliers could meet. Flag the exact language and suggest neutral alternatives.

  3. AMBIGUOUS EVALUATION CRITERIA: Any scoring or evaluation criteria too subjective for consistent application across evaluators. Flag and suggest more precise alternatives.

  4. INTERNAL INCONSISTENCIES: Any contradictions between sections — timelines, deliverables, or performance standards described differently in different parts of the document.

Present findings as a structured review with a section for each of the four areas above. Where no issues are found, state “No issues identified.” Conclude with the three highest-priority items requiring resolution before issue.

[ATTACH THE SCOPE DOCUMENT OR PASTE ITS CONTENT BELOW THIS PROMPT]

WHAT GOOD OUTPUT LOOKS LIKE A structured review with findings under each of the four headings, with specific section references and verbatim quotes of problematic language. If the AI returns only general observations without specific references, follow up with: ‘Identify the specific section number and quote the exact language for each finding.’ The most useful output also suggests concrete neutral alternatives for any biased specification language.

USAGE NOTE Works on Word documents attached directly in Copilot (Word or Copilot Chat with Work toggle on), or by pasting document text. For documents containing commercially sensitive pricing benchmarks or incumbent supplier information, use Copilot within your M365 tenant — do not paste into public LLM tools.


02 | RFP & SCOPE DOCUMENT QUALITY REVIEW

Evaluation Criteria Consistency & Weighting Review

WHEN TO USE After evaluation criteria and scoring matrix have been drafted, before the RFP is issued. Also useful after a sourcing event to review whether criteria produced consistent, defensible scores — particularly if a supplier has raised a challenge or the evaluation panel produced divergent scores.

THE PROMPT

Copy-Paste Prompt

You are a procurement specialist reviewing a set of evaluation criteria and a scoring matrix for a competitive RFP.

Review the attached evaluation framework and assess:

  1. CLARITY: Is each criterion and its scoring bands defined precisely enough that two different evaluators would score the same supplier response identically? Flag any criterion where subjective interpretation is likely.

  2. COMPLETENESS: Are there important dimensions of supplier performance relevant to [CATEGORY / TYPE OF PROCUREMENT] that are absent from the criteria? List any gaps.

  3. WEIGHTING LOGIC: Does the relative weighting of criteria reflect the actual business priorities for this procurement? Flag any criteria that appear over- or under-weighted given the stated objective of [BRIEF DESCRIPTION OF WHAT IS BEING PROCURED AND WHY].

  4. DEFENSIBILITY: Are there any criteria or scoring bands that could be challenged by an unsuccessful supplier as unfair, arbitrary, or inconsistently defined? Flag these specifically.

Present findings under each heading. Conclude with a recommended priority order for the top three items to resolve before the RFP is issued.

[ATTACH EVALUATION CRITERIA AND SCORING MATRIX]

WHAT GOOD OUTPUT LOOKS LIKE A criterion-by-criterion assessment with specific flags and improvement suggestions. Good output identifies which criteria are well-defined alongside which are not — not just flags everything. If the output is too generic, follow up with: ‘For each criterion you flagged, write a revised version of the scoring band description that would be clearer and more defensible.’ Particularly valuable for complex service procurements where criteria like ‘quality of methodology’ are common.

USAGE NOTE The AI’s assessment of defensibility is a starting point for judgment — final review by legal or compliance remains essential for regulated or high-value procurements. Also useful as a coaching tool: share the flagged criteria with the business team requesting the procurement to improve the quality of their requirements documentation over time.


03 | BID & PROPOSAL COMPLIANCE CHECKING

Pre-Evaluation Supplier Submission Compliance Gate

WHEN TO USE Immediately after bid submission closes and before technical evaluation is opened to evaluators. Run on each supplier’s submission individually. The output becomes the compliance record for the sourcing file and — where non-compliances are found — triggers the formal clarification or rejection process per the RFP rules.

THE PROMPT

Copy-Paste Prompt

You are a procurement officer conducting a compliance review of a supplier’s bid submission before opening it for technical evaluation.

Using the mandatory requirements listed below, review the attached supplier submission and for each requirement state:

  • COMPLIANT: The submission clearly addresses this requirement
  • NON-COMPLIANT: The requirement has not been addressed or is missing entirely
  • CONDITIONAL: The supplier has responded but with a caveat or qualification that requires a procurement ruling before evaluation can proceed
  • UNCLEAR: The submission may address this requirement but is ambiguous — clarification needed

MANDATORY REQUIREMENTS FOR THIS RFP: [LIST EACH MANDATORY REQUIREMENT ON A SEPARATE LINE, for example:

  • Completed pricing schedule in the format provided (Annex B)
  • Signed and dated supplier declaration (Annex C)
  • Evidence of ISO 9001 certification valid within 12 months
  • Response to all sections of the technical questionnaire (Sections 3.1 to 3.8)
  • Minimum three client references from comparable engagements in the past five years]

SUPPLIER NAME: [SUPPLIER NAME]

Present findings as a compliance table with one row per requirement. Conclude with an overall compliance status: COMPLIANT (proceed to evaluation), NON-COMPLIANT (reject or seek clarification per RFP rules), or CONDITIONAL (procurement ruling required before proceeding).

[ATTACH SUPPLIER SUBMISSION OR PASTE CONTENT BELOW]

WHAT GOOD OUTPUT LOOKS LIKE A compliance table with a clear status for each mandatory requirement and an overall compliance verdict. Good output includes a brief explanation for any Non-Compliant or Conditional finding, quoting the relevant part of the submission. If reasoning is missing, follow up with: ‘For each Non-Compliant or Conditional finding, quote the specific part of the submission that led to that status, or confirm the section was absent.’ Save each output as a dated record — it forms part of the procurement audit trail.

USAGE NOTE Run this prompt on each submission individually before any evaluator opens a document. AI compliance output supports the procurement officer’s formal compliance ruling — it does not replace it. Where RFP rules specify a formal clarification process for minor non-compliances, this output triggers that process. This single workflow change eliminates the mid-evaluation discovery problem that can add two to four weeks to complex sourcing cycles.


04 | BID & PROPOSAL COMPLIANCE CHECKING

Multi-Supplier Response Comparison & Gap Analysis

WHEN TO USE After compliance checking is complete and technical evaluation has been conducted. Use to rapidly surface where suppliers have responded differently to the same requirements — particularly valuable for complex proposals where evaluators may have scored submissions inconsistently, or where the evaluation panel needs a structured comparison to inform its deliberations.

THE PROMPT

Copy-Paste Prompt

You are a senior procurement analyst comparing responses from [NUMBER] suppliers to the same RFP. The suppliers are: [LIST SUPPLIER NAMES].

Compare the supplier responses across the following specific dimensions: [LIST THE KEY REQUIREMENTS OR QUESTIONS YOU WANT COMPARED, for example:

  • Proposed implementation timeline and phasing approach
  • Pricing structure, assumptions, and any stated exclusions
  • Account management and escalation model
  • Relevant prior experience cited
  • Any proposed deviations from the standard terms and conditions]

For each dimension, show:

  1. What each supplier proposed (brief, factual terms — do not editorially favour any supplier)
  2. Any material differences between suppliers on this dimension
  3. Any supplier that did not address this dimension or addressed it incompletely

Present as a structured comparison table where possible, with a brief narrative summary of the key differentiators at the end. Do not make an award recommendation — that judgment belongs with the evaluation panel.

[PASTE OR ATTACH THE RELEVANT SECTIONS FROM EACH SUPPLIER’S SUBMISSION]

WHAT GOOD OUTPUT LOOKS LIKE A structured comparison table and short narrative identifying material differences between submissions. Good output is factual and neutral — it surfaces differences rather than drawing conclusions. If the AI begins making evaluative judgments or award recommendations, redirect it: ‘Please present only factual comparisons — do not assess which supplier is stronger or make any recommendation.’ Paste only the relevant sections from each submission rather than entire documents for the most precise output.

USAGE NOTE This prompt turns a multi-hour manual exercise into a structured input for panel discussion. It is particularly effective for proposals where different evaluators have read different sections — the comparison surfaces gaps in evaluation coverage as well as gaps in supplier responses. For very large proposals, run the comparison one dimension at a time and ask the AI to consolidate at the end.


05 | CONTRACT REVIEW & SUMMARISATION

Incoming Supplier Contract Key Terms Extraction

WHEN TO USE When a supplier submits their own standard terms, master service agreement, or any supplier-paper contract for review. Use before engaging legal to give procurement a commercial picture of the document and identify the clauses needing legal attention most urgently. Also effective for rapidly reviewing contract variations or amendments against the original agreement.

THE PROMPT

Copy-Paste Prompt

You are a procurement contract manager reviewing an incoming supplier contract. Extract and summarise the following commercial terms. For each item, quote the relevant clause reference and provide a brief summary of what it says. Where a term is absent, state “Not addressed.”

TERMS TO EXTRACT:

  1. Contract duration and renewal terms — including auto-renewal clauses and notice periods required to terminate or renegotiate
  2. Pricing — fixed, variable, indexed, or subject to annual uplift; any price review mechanisms
  3. Payment terms — payment period, early payment discounts, late payment penalties
  4. Liability cap — maximum financial liability of each party; any exclusions or carve-outs
  5. Indemnification — what each party indemnifies the other for
  6. Intellectual property ownership — who owns IP created under the contract
  7. Data protection and confidentiality — key obligations on each party
  8. Termination rights — grounds for termination for convenience and for cause, and consequences
  9. Governing law and dispute resolution mechanism
  10. Any non-standard or unusual clauses a procurement or legal reviewer should be aware of

After the extraction, provide a 3–5 sentence commercial summary of the contract’s overall risk profile from a buyer’s perspective — identifying the top two or three clauses that require legal review or negotiation before signature.

[ATTACH SUPPLIER CONTRACT OR PASTE CONTENT BELOW]

WHAT GOOD OUTPUT LOOKS LIKE A structured extraction table with clause references and summaries for each of the ten items, plus a commercial risk summary. Good output identifies the auto-renewal trap, liability cap relative to contract value, and any non-standard clauses departing from market norms. If clause references are missing, follow up with: ‘For each item, add the specific clause or section number from the document.’ Use the output to brief your legal team on priorities — it does not replace legal review.

Governance Reminder
Do not paste supplier contracts containing commercially sensitive pricing, trade secrets, or information subject to NDA into any public LLM tool. Use Copilot within your M365 tenant or an equivalent governed enterprise AI environment. This prompt produces a commercial overview to accelerate legal triage — all final contract decisions require qualified legal review.

06 | SUPPLIER RESEARCH & PROFILING

Pre-Sourcing Supplier Market Profile

WHEN TO USE In the early stages of a sourcing project — before issuing an RFI or RFP — to rapidly build a picture of the supply market and key players, particularly for categories where the procurement team has limited prior experience. Use Copilot Chat in Web mode (toggle to Web) to draw on current market information.

THE PROMPT

Copy-Paste Prompt

You are a category manager preparing for a competitive sourcing event in the following category: [CATEGORY — for example: IT managed services / industrial cleaning services / temporary staffing / logistics and freight forwarding].

Provide a structured market profile covering:

  1. MARKET OVERVIEW: Key characteristics of this supply market — approximate market size, level of supplier concentration, and whether this is currently a buyer’s or seller’s market.

  2. KEY SUPPLIERS: The main suppliers active in this category at [global / regional — specify] level. For each, note their approximate market position and any relevant differentiating characteristics.

  3. COST STRUCTURE: The primary cost drivers for suppliers in this category — what makes pricing increase or decrease, and what pricing models are typical.

  4. MARKET RISKS: Known supply risks, capacity constraints, regulatory developments, or market disruptions relevant to this category in 2026.

  5. TYPICAL CONTRACT TERMS: What contract duration, pricing structure, and commercial terms are standard in this market.

  6. KEY QUESTIONS FOR AN RFI: Five questions that would help differentiate supplier capability and commitment in an initial market engagement for this category.

Where you are uncertain about specific data points, say so clearly — I will verify key facts independently before using them in procurement decisions.

WHAT GOOD OUTPUT LOOKS LIKE A structured market profile under six headings, with five RFI questions at the end. Good output names actual suppliers, cites typical pricing models, and identifies real market risks rather than speaking in generalities. If the output is too vague, follow up with: ‘Be more specific about [cost drivers / key suppliers / typical contract terms] for this category.’ Always verify supplier-specific claims independently — AI market profiles are a starting framework, not a definitive market assessment.

USAGE NOTE For highly specialist or niche categories, treat the output as a starting framework to validate through direct supplier conversations and available market intelligence. Pair with category-specific trade publications, analyst reports, or conversations with subject matter experts for high-value strategic categories. This prompt works best in Copilot Chat with the Web toggle enabled.


07 | NEGOTIATION PREPARATION

Supplier Negotiation Brief & Leverage Analysis

WHEN TO USE Before entering any significant supplier negotiation — renewal, post-tender award negotiation, mid-contract renegotiation, or dispute resolution. Use to structure thinking, identify leverage points, and prepare fallback positions before the negotiation opens. Most effective when run 3–5 days before the negotiation, leaving time to pressure-test the analysis with stakeholders.

THE PROMPT

Copy-Paste Prompt

You are a senior procurement negotiator preparing for a commercial negotiation.

SUPPLIER: [SUPPLIER NAME] CATEGORY: [CATEGORY OR PRODUCT/SERVICE BEING NEGOTIATED] CURRENT ANNUAL CONTRACT VALUE: [APPROXIMATE VALUE] NEGOTIATION OBJECTIVE: [PRIMARY OBJECTIVE — for example: renew at current pricing / achieve 10% cost reduction / extend payment terms from 30 to 60 days / add new scope without price increase] CONTEXT: [2–3 sentences describing the current relationship, any relevant history, what has prompted this negotiation, and any performance issues or leverage events]

Provide a structured negotiation brief covering:

  1. OUR LEVERAGE POINTS: What gives us commercial leverage? Consider: competitive alternatives, supplier dependency on our spend, market conditions, contract expiry timing, performance issues, or our ability to self-deliver or insource.

  2. SUPPLIER’S LIKELY POSITION: What outcome is the supplier likely seeking, and what pressures are they under that may influence their flexibility?

  3. OPENING POSITION: What should our opening ask be, and why?

  4. TARGET OUTCOME: What does a successful result look like for us?

  5. WALKAWAY POSITION: What is the minimum acceptable outcome below which we should escalate or explore alternatives?

  6. CONCESSIONS WE CAN OFFER: What could we offer in exchange for movement on our primary objective? For example: longer contract term, earlier payment, volume commitment, reference case, reduced scope of audit rights.

  7. KEY RISKS: What could go wrong, and how should we prepare?

Be direct and specific — this is an internal planning document, not a communication to the supplier.

WHAT GOOD OUTPUT LOOKS LIKE A structured seven-section negotiation brief with specific, actionable positions. Good output identifies non-obvious leverage points and realistic concession options rather than generic advice. If the output is too generic, add more context about the supplier relationship and specific market conditions — the more specific your inputs, the more targeted the analysis. Always review the leverage analysis against your own knowledge of the relationship before using it.

Governance Reminder
Do not include commercially sensitive pricing data, confidential supplier financial information, or information obtained under NDA in this prompt. Use Copilot within your M365 tenant. This brief is an input to your negotiation thinking — it does not replace the relationship knowledge and commercial judgment that only the category manager holds. Review and edit before sharing with any negotiation team member.

08 | SUPPLIER RISK ASSESSMENT

Internal Supplier Risk Signal Summary

WHEN TO USE Before a supplier review meeting, at the start of a new contract term, when a supplier’s performance triggers concern, or as part of a periodic category health check. Use to synthesise internal ERP and contract data into a structured risk picture. This is Layer 1 of an effective supplier risk monitoring model — run this before investing in external financial health feeds.

THE PROMPT

Copy-Paste Prompt

You are a procurement risk analyst preparing a supplier risk summary for an internal review meeting.

Using the data provided below, produce a structured risk assessment covering:

  1. PERFORMANCE SUMMARY: Overall assessment of delivery performance based on the data. Identify any trend — improving, stable, or deteriorating — and the most significant positive or negative data point.

  2. FINANCIAL EXPOSURE: Summary of our financial exposure to this supplier — contract value, payment terms, concentration risk if this is a sole or preferred supplier.

  3. RISK FLAGS: Specific data points that represent a risk requiring action or monitoring. Rate each flag HIGH, MEDIUM, or LOW based on potential business impact if it materialises.

  4. RECOMMENDED ACTIONS: Specific actions procurement should take based on this assessment. Be concrete — for example: issue a formal performance improvement notice / schedule a senior-level review within 30 days / request a financial health update / assess alternative suppliers in parallel / no action required at this time.

SUPPLIER DATA: Supplier name: [SUPPLIER NAME] Category: [CATEGORY] Annual contract value: [VALUE] Contract expiry: [DATE] Sole supplier or one of several: [SOLE / PREFERRED / ONE OF SEVERAL]

Delivery performance (last 12 months): [PASTE ERP DATA — for example: on-time delivery rate, quality rejection rate, lead time adherence, number of escalations]

Invoice and payment history: [PASTE DATA — for example: invoicing accuracy rate, number of disputed invoices, average days to resolve disputes]

Open issues or escalations: [LIST ANY CURRENT PERFORMANCE ISSUES, DISPUTES, OR ESCALATIONS]

Contract compliance notes: [NOTE ANY KNOWN DEVIATIONS FROM CONTRACTED TERMS — SLA breaches, pricing anomalies, unauthorised scope changes]

WHAT GOOD OUTPUT LOOKS LIKE A structured four-section risk summary with specific flags rated by severity and concrete recommended actions. Good output synthesises patterns across the data rather than restating it — for example, identifying that declining on-time delivery combined with increasing invoice disputes suggests a supplier under operational or financial stress. If the output is too descriptive, follow up with: ‘Based on these patterns, what is the most likely root cause and what should procurement do in the next 30 days?’

USAGE NOTE This prompt uses data you already have in your ERP — no external tool investment required. Once an internal risk summary process is working, Layer 2 of the supplier risk model (external financial health feeds from D&B or Creditsafe) adds early warning signals for financial distress that internal operational data alone cannot detect. See the Procurement Spectrum AI in Procurement report for the full four-layer implementation model.


09 | SPEND ANALYSIS & VARIANCE REVIEW

Off-Contract Spend & Rate Card Variance Analysis

WHEN TO USE During a category review, ahead of a contract renewal, or when the business suspects spend is drifting outside contracted terms. Most effective when you have invoice-level spend data that can be compared against a contracted rate card or price list. Also useful as a regular monthly check for high-value or high-volume supplier relationships.

THE PROMPT

Copy-Paste Prompt

You are a procurement spend analyst reviewing invoice data against contracted pricing to identify off-contract spend and rate card variances.

Using the data below, identify:

  1. RATE CARD VARIANCES: Any invoiced line items where the price charged differs from the contracted rate. For each variance, calculate the value difference and flag as OVERPAYMENT or UNDERPAYMENT.

  2. OFF-CONTRACT ITEMS: Any invoiced items that do not appear on the contracted rate card or approved scope — items being purchased outside the agreement.

  3. PATTERN ANALYSIS: Are variances concentrated in a particular time period, supplier location, product category, or business unit? Identify any pattern suggesting a systemic issue rather than a one-off error.

  4. FINANCIAL IMPACT: Total estimated annual financial impact of the variances identified.

  5. RECOMMENDED ACTIONS: For each category of variance, recommend a specific action — for example: issue a credit note request / update the rate card / escalate to the contract manager / implement a purchase order control / no action required.

CONTRACTED RATE CARD: [PASTE RATE CARD — product or service description, unit, contracted unit price]

INVOICE DATA ([PERIOD — e.g., last 6 months]): [PASTE INVOICE LINE ITEMS — date, description, quantity, unit price, total]

SUPPLIER NAME: [SUPPLIER NAME] CONTRACT REFERENCE: [CONTRACT REFERENCE OR NUMBER]

WHAT GOOD OUTPUT LOOKS LIKE A structured variance analysis with specific line-item flags, a pattern assessment, a total financial impact figure, and recommended actions. Good output identifies both individual exceptions and the systemic pattern — for example, a consistent 3% uplift on a specific product line suggesting an unauthorised price increase. If the data volume is large, run the analysis by category or time period rather than all at once and ask the AI to consolidate findings at the end.

Governance Reminder
Invoice and pricing data should be processed in Copilot within your M365 tenant or equivalent governed environment — not in public LLM tools. This prompt works particularly well in Copilot in Excel: export rate card and invoice data into a spreadsheet, then use Copilot’s Excel agent mode to run the analysis directly on the data without needing to paste it into a chat interface.

10 | STAKEHOLDER COMMUNICATION & REPORTING

Sourcing Event Outcome Summary for Business Stakeholders

WHEN TO USE After completing a competitive sourcing event and before communicating the outcome to business stakeholders, senior management, or a governance committee. Use to produce a clear, consistent summary that explains the process, the result, and the rationale in plain language — without requiring the reader to have procurement knowledge.

THE PROMPT

Copy-Paste Prompt

You are a procurement manager preparing a sourcing event outcome summary for presentation to [AUDIENCE — for example: the budget owner and their leadership team / a governance or approvals committee / the project steering group].

Using the information below, write a clear, professional summary covering:

  1. PROCUREMENT OVERVIEW: What was procured, why a competitive process was conducted, and the timeline of the sourcing event.

  2. MARKET RESPONSE: How many suppliers were invited, how many responded, and the overall quality and competitiveness of responses.

  3. EVALUATION PROCESS: How submissions were assessed — the evaluation criteria used, their relative weightings, and who was involved in the evaluation panel.

  4. RECOMMENDED SUPPLIER AND RATIONALE: Which supplier is recommended for award and the key reasons — covering commercial, technical, and risk considerations. Reference the evaluation scores where appropriate.

  5. CONTRACT VALUE AND KEY TERMS: Recommended contract value, duration, and key commercial terms including any performance KPIs or milestone structure.

  6. VALUE ACHIEVED: Any cost savings, value improvements, or risk mitigations achieved through the competitive process compared to the previous arrangement or the original budget estimate.

  7. NEXT STEPS AND APPROVALS REQUIRED: What approvals are needed and the proposed timeline to contract execution.

Write in plain language appropriate for a non-procurement audience. Avoid jargon. Length: [BRIEF — approximately one page / STANDARD — approximately two pages / DETAILED — two to three pages with supporting data].

SOURCING EVENT DETAILS: [PROVIDE: category, number of suppliers invited and responded, evaluation scores summary, recommended supplier name, contract value, savings achieved, key contract terms, proposed next steps]

WHAT GOOD OUTPUT LOOKS LIKE A clear, structured sourcing outcome summary in plain language, sized for the specified audience. Good output tells a coherent story — why we ran the process, what the market told us, how we evaluated, and why this supplier is the right choice — without requiring the reader to have procurement knowledge. If the tone is too technical, follow up with: ‘Rewrite this for a non-procurement audience — remove jargon and explain any technical terms in plain language.’ Always verify all factual claims before submission to governance.

USAGE NOTE This prompt is most effective when you provide actual evaluation scores and commercial outcomes as inputs rather than asking the AI to infer them. The AI structures and communicates the story — the judgment and the data are yours. For formal governance submissions requiring sign-off, review all figures (savings, scores, supplier references) against source records before finalising.