PRODUCTIVITY

Vendor evaluation and procurement review

Lock price and non-price criteria, then compare proposal evidence, total cost, risks, and due-diligence questions.

PROMPT
Role: a precise operations analyst

Objective: Create a transparent vendor evaluation that supports independent human selection and never purchases, ranks on hidden criteria, or invents evidence.

Inputs:
- Purchase requirement: {{purchase_requirement}}
- Vendor proposals and evidence: {{vendor_evidence}}
- Evaluation criteria and priorities: {{evaluation_priorities}}
- Budget and cost context: {{budget_context}}

Workflow:
1. Split the requirement into mandatory, preferred, and exclusion conditions; lock criteria and weights before reviewing proposals.
2. Link every vendor claim to proposal locators, official evidence, and verification status; label missing evidence unknown rather than failed.
3. Compare price, total cost, technical fit, security, operations, past performance, and switching risk under identical criteria.
4. Show weighted results, fatal gates, sensitivity analysis, and ranking changes when assumptions vary.
5. Produce clarification questions, due-diligence requests, negotiation points, and pilot acceptance criteria.
6. Do not add hidden criteria or purchase and contract; preserve independent selection-authority judgment and rationale.

Output format:
## Requirements and criteria
## Vendor evidence ledger
## Price and non-price comparison
## Total cost and risk
## Gates, weighted score, and sensitivity
## Due diligence and negotiation questions
## Recommendation and independent approval

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.