Vendor due diligence pack
Onboarding a supplier means collecting the same evidence every time, then noticing that a certificate expired last spring. This agent matches what the vendor has sent against your own onboarding checklist, flags what is missing or out of date, and assembles a cited pack. Procurement decides whether the vendor is progressed.
Step by step
Load the onboarding checklist
The agent takes your own list of required evidence, whatever it covers: insurance, security, policies, ownership, accreditations.
Collect what the vendor sent
Attachments from the vendor mailbox and the shared folder are gathered against the vendor record.
Match evidence to each requirement
Every requirement is marked with the document that answers it, showing the date and the issuer.
Flag gaps and expired documents
Requirements with nothing attached, or with a document past its date, are listed separately with the vendor contact named.
Draft the chase for missing items
A short request for the outstanding items is drafted for procurement to send, quoting exactly what is still needed.
The procurement lead approves
The reviewer approves the pack and decides whether the vendor proceeds. The agent takes no view on that.
Exactly what this agent can see, touch and change
The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelProcurement and vendor management teams onboarding suppliers against a fixed evidence list, particularly where security, insurance and policy documents trickle in by email over weeks.
Escalation
When it asks a personThe procurement lead approves the pack before a vendor is progressed
Applications & Rights
Which tools it uses, and what it may do in eachVerification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Procurement and vendor management teams onboarding suppliers against a fixed evidence list, particularly where security, insurance and policy documents trickle in by email over weeks.
What you’ll need
- Your vendor onboarding checklist
- A mailbox or folder where evidence arrives
- Agreed expiry rules per document type
- A procurement lead to approve
What you get
- A cited evidence pack
- A missing and expired list
- A drafted chase to the vendor
What it doesn’t do
It checks documents against your list. It does not assess a vendor's risk, approve or reject a supplier, or judge whether a certificate is adequate for what you are buying.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Does it score vendor risk?
No. It reports presence, absence and dates against the list you gave it. Turning that into a risk view is a judgement your team makes, usually with security and legal in the room.
What if a vendor sends everything in one document?
It reads the document and maps the parts to the requirements they answer, citing the page. Where a requirement is only partly covered, it marks it as partial rather than complete.
Can it start the chase automatically?
It drafts the chase and names what is outstanding. Sending is a person's decision, because the tone of a supplier chase depends on the relationship and where you are in the negotiation.
Will it work for renewals as well as onboarding?
Yes. The same check runs against an existing vendor's file, which is usually where expired evidence turns up. Teams often run it across the supplier base before an audit or a security review.