The difference between a supplier who submits his documents in writing and another who answers everything verbally is not in intention, but in maturity. Whoever prepares his documents has gone through enough projects to know where the differences lie, and whoever is satisfied with meetings leaves everything open to interpretation later.
This list is not a regulatory requirement imposed on anyone, but rather a rational purchasing practice that protects both parties. Ask it from every supplier you compare, and rate how quickly they respond — that’s an indicator in itself.
What decision do you need to make?
You have to decide what is enough for you to make a decision accountable to your management or facility owner. Meetings build an impression, and documents build a file that can be reviewed and referred to in the event of disagreement — which is what you will need if you are asked a year later, “On what basis did we choose this resource?”
Criteria to help you choose
Documents have three categories, and each category has a different purpose:
- Functional: Describes what the system does in reviewable detail, not marketing headlines. This category reveals whether the product is mature and documented or based on word of mouth.
- Commercial: Specifies what you pay, for what, when, and what is not included in the offer. These are what the procurement team reviews and compares against.
- Operational: Describes how the service will be implemented and supported after launch. It is the most neglected category and the one that most affects your daily experience later.
List of questions and required evidence
Request these documents explicitly, and set a deadline for their delivery:
- System Functions Document: Description of what each part does, not a list of titles.
- Roles and Permissions Document: What each role sees and does not see, and how to control this.
- Trade offer with detailed terms: Three fee types, with second year value and explicit exceptions clause.
- Implementation plan: Stages, outputs, responsibilities and acceptance criteria for each stage.
- Description of controls: Hosting, data location, backup and restore, and access management.
- Determination of processing responsibilities: What the provider is responsible for and what your facility is responsible for.
- Service Level Agreement: Coverage times, channels, response times and exceptions.
- Export Terms and Termination: The format of your data, how long it will be delivered, how much it will cost, and when it will be deleted.
- Draft Contract: Order early, not after agreeing on the price.
And add a simple request that reveals a lot: a copy of a real report that the system produces – after anonymizing its data – instead of an image of a report in a presentation.
Do not request all documents from every supplier in the first stage. Ask for the functional category when qualifying, commercial when requesting a proposal, and operational and contract when final negotiating with the shortlisted. Gradual ordering respects both parties’ time and keeps comparison practical.
Mistakes to avoid before certification
- Postponement of draft contract: Most surprises occur in items that were not read until everything was agreed upon.
- Accepting presentations as documents: Slides Asset No Reference Document.
- No timeout specified: An order without deadline is postponed until your negotiating power weakens.
- Ignoring termination clause: Is usually read too late and is the most important clause protecting your data.
- Ignoring your facility’s responsibilities: The documents outline the obligations of both parties, and what falls to you is equally worth reading.
The next step is to request a quote
Send this listing with Procurement Requirements Checklist In one request, and state the required response time. Evaluate the suppliers on what you received and the speed of its arrival.
When you receive the documents, distribute them to those concerned: commercial for procurement, technical for information technology, and operational for whoever will manage the project. Distributed reading reveals what individual reading does not reveal.
Request a quote for your organization
You receive the proposal with what you need to review: a written scope, an implementation plan with deliverables, a description of controls, and terms of support and export — so you can decide on a file, not an impression.