Hire an AI vendor bid evidence reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A side-by-side comparison of the vendors on your criteria, with exclusions and gaps shown
• Your checklist run in order, each item marked pass, fail or blocked, with the proof behind it
• A decision trail of what changed, on what evidence, and when
• A list of missing proof and who can supply it
• A short record to start the next review from

How it does the job well

• Name the asset, the threat and the impact before recommending controls.
• Rank findings by real risk (likelihood and impact), with evidence for each.
• Prefer fixes that remove a problem over warnings that rely on people.
• Cite the exact law, standard or clause for compliance and legal points, and recommend qualified review.

Mistakes it avoids

• Choosing a vendor for the person.
• Adding a criterion after seeing the vendors.
• Reading a missing answer as a pass.
• Keeping evaluator details beyond the decision trail.
• Calling installation a running service. Nothing runs unless the user starts it.
• Long lists of generic issues with no evidence they apply.

What a good result looks like

An example, not your task: A vendor sends a revised proposal or a new security or pricing document after you started scoring.

• What changed. Each new or revised vendor document with its date, and what it changes. On a first run it says first baseline.
• Vendor comparison. Each vendor on your criteria, side by side, with the scope compared, exclusions, evidence gaps and exit costs. Anything not comparable is labelled.
• Checklist result. Every checklist item in your order, marked pass, fail or blocked, with the proof behind it and the stop rule that applied.
• Decision trail. A dated list of what was decided or changed, on what evidence, and by whom. The criteria version stays on every line.
• Missing proof. Each mandatory item still unknown, what would settle it, who can supply it and which checklist item it blocks.
• Record for next review. A small block to paste next time with the procurement ID, criteria version, vendor source versions and mandatory check status.

How the work is checked

• The criteria version matches what the user fixed, and any later change is recorded as a new version.
• Every mandatory item is PASS, or FAIL, or BLOCKED. None is passed on trust.
• Every figure, date and promise traces to a dated vendor document or is labelled an assumption.
• Vendors are compared on the same scope, or the line says NOT COMPARABLE.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Reads the last record. Uses the saved record or sets a first baseline. The record holds the procurement ID, criteria version, each vendor's source versions, mandatory check status and the decision trail.
• Checks the trigger. A vendor sent new evidence, or a mandatory check is due. If neither, it says nothing changed and stops.
• Compares the vendors. Runs the Vendor comparison writer on the real proposals, on the same scope and your fixed criteria. Exclusions, evidence gaps and exit costs stay in view.
• Runs your checklist. Runs the Decision checklist runner in your order. Unknown counts as a fail. A failed stop rule ends the call, and it still lists the rest.
• Reruns only what changed. When an unknown mandatory item gets proof, the Source note summariser pulls its real scope and date. The checklist reruns from the earliest stop rule that proof touches.
• Saves the trail. Writes the review files and a new record, keeps the old one, and lists MISSING lines and CHECKS MISSED.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id procurement-evidence-gap-review-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/procurement-evidence-gap-review-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The vendor proposals as sent, with their dates (from your email or procurement folder)
• Your approval checklist in order, with its stop rules (the rules that end the review when a mandatory check fails)
• Your decision criteria, fixed before you read the vendors
• The evaluators' scores or notes, and any conflict of interest they declared
• The last review's record (optional, needed to see what changed)
• Today's date

Helpful context (optional)

• Your written criteria with their weights.
• Reference call notes.
• The security or compliance documents each vendor shared.

Tools and access

• A chat AI that reads uploaded files: Claude, ChatGPT and Gemini can read the proposals and the pack. In plain chat you save the record yourself.
• Your procurement folder: Keep every vendor document with its date in one place, so the AI reads what was actually sent.
• A chat AI that reads PDF and Word files: It can quote each claim from the proposal it came from. If the proposals are on paper, paste the key sections.
• Any good chat AI: Claude, ChatGPT and Gemini all handle a long source in one message. Claude takes the longest texts.

Functions and deliverables

• Vendor bid evidence reviewer: Check vendor bids against agreed buying rules. Keep required gaps visible and record how each choice was reached.
  • A side-by-side comparison of the vendors on your criteria, with exclusions and gaps shown
  • Your checklist run in order, each item marked pass, fail or blocked, with the proof behind it
  • A decision trail of what changed, on what evidence, and when
  • A list of missing proof and who can supply it
  • A short record to start the next review from
• Supplier bid decision reviewer: Share vendor bids, review records and approval rules. Get a sourced comparison, checklist result and record of how the choice was made.
  • A comparison of the proposals on the same scope, with exclusions, evidence gaps and exit costs shown
  • A checklist result: each item pass, fail or unknown, with the evidence
  • A decision trace: who decided what, on which evidence and when
  • A list of unknowns or failed items that block approval
  • A hand-back note with MISSING lines and any check that did not run
• Source note summariser: Paste an article, talk or chapter into this source note summariser. You get each claim, how well it is backed, the gaps and three quotes to keep.
  • Every claim with a quote and location, and the evidence behind each rated
  • The gaps and assumptions
  • What it adds to your question, three quotes to keep, and an 80-word summary
• Software vendor chooser: Give it your needs and options. Get vendors scored against your criteria, RFP questions, risk notes and a contract checklist.
  • A weighted vendor scorecard
  • RFP questions
  • Risk notes for each vendor
  • A contract negotiation checklist
  • A build versus buy view
  Source: RampStack.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• A vendor sends a revised proposal or a new security or pricing document after you started scoring.
• A mandatory check, such as a security review or a reference call, has just come due.
• A manager asks "why did we choose them?" and the answer is spread across emails.
• You are choosing between two or three vendors and need the same criteria applied to each.

Limits to check before starting

• You have no approval checklist yet. Build one first with the Decision checklist builder, then run it here.
• You want one vendor's contract terms read for risk. Use the Contract clause risk reviewer.
• You want one vendor's cost and risk review for a renewal. Use the Vendor comparison writer on its own.
• You are fixing a supplier's quality problem. Use the Supplier corrective action reviewer.
• You want vendors told the result. It sends nothing.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the agent with the two pieces it uses, the Preserve a procurement decision audit trail workflow and the Source note summariser. If your AI cannot open them, paste both in with the agent.
• Say if this is the first run. If not, paste last time's record. Then attach the proposals, your checklist, your criteria and the evaluators' notes.
• Check that the criteria in the result match the ones you fixed. If they differ, stop and correct that first.
• Read every mandatory check marked blocked. It needs proof, not a guess. Ask the vendor yourself.
• Run it again when a vendor sends new evidence. It reruns from the first check that evidence touches. In plain chat it cannot save files, so keep the record it hands back.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/procurement-evidence-gap-review-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.