Your sourcing still lives in inboxes if an RFx needs email threads, copied files and private spreadsheets to hold together. Eleven signs give it away. Tick three or more and fairness, speed and the audit trail are already at risk. Score your own process in two minutes with the interactive RFx Health Check, no login needed.
None of these signs is a people problem. Each one is what happens when a sourcing process runs on tools that have no memory of who saw what, when. Here they are, grouped by where the damage lands, with the fix for each.
Where does the event actually live?
- One RFx lives in more than one email thread. A buyer, an engineer and a plant head each run their own chain with the same suppliers. Nobody has the whole picture, and the reply that matters sits in one person's inbox. The fix is one event record that every message goes out from and every reply lands back on.
- The invitation pack is copy-pasted from the last event. The cover letter still carries last quarter's dates, or worse, another supplier's name. The fix is a pack generated from the event itself, personalised per supplier and checked before anything is sent.
Who can see what?
- Suppliers have found out who else was invited. A CC instead of a BCC, a forwarded chain, a file name that lists the bidders. Once it happens, the event is no longer fair. The fix is supplier-blind sourcing: one message per supplier, and no participant names or counts on anything a supplier can see.
- Confidential specs go out before an NDA is in place. Drawings reach a new supplier's inbox before anyone checks for an NDA. The fix is an NDA gate: new suppliers see a teaser, and confidential documents unlock only once the NDA is accepted.
- Nobody can say, right now, which suppliers are cleared to see documents. The answer lives in legal's folder and a buyer's memory. The fix is NDA and access status shown on the event, for the whole team, supplier by supplier.
How is the evaluation run?
- Every evaluator scores their own copy of the spreadsheet. Versions fork, cells get overwritten, and one senior voice anchors everyone else. The fix is one evaluation model per event, independent scoring first, then an evaluation consensus that keeps every individual score on the record.
- The evaluation is framed commercial-first; price is seen before quality. Once a technical evaluator has seen the prices, the quality score is no longer independent. The fix is separate quality and price tracks, a split you set per event, and prices sealed until technical sign-off, as in two-envelope evaluation.
- New events start from a blank page or a stale file. Each buyer rebuilds the same questionnaire and price sheet from memory. The fix is a category starter kit that suggests questions and sheets, copied into the event and fully editable.
Can leaders see and decide?
- Senior leaders see nothing until someone shares a file. Who has evaluated, what is pending and with whom is found out by asking. The fix is a control room per event that answers those questions without a status meeting.
- Timelines are chased over email and reminders are manual. Slippage is discovered when a supplier asks why nobody replied. The fix is a timeline with owners and automatic reminders to suppliers and to the team.
- Approvals happen in chat, on a call, or in a forwarded email. A thumbs-up in a group chat is not an approval an auditor will accept. The fix is to bring the decision to the approver's inbox, with a signed link they tap on a phone, so the decision lands on the record. We wrote more on this in why leaders won't live in your procurement portal.
What does your score mean?
- 0 to 2: healthy. Your process lives in a system. Keep it there.
- 3 to 6: mixed. Half the process is in a system, half in inboxes. That seam is where fairness slips.
- 7 to 11: in inboxes. Fairness, speed and the audit trail are all exposed. Start with the evaluation file and approvals.
A high score is common, and it is not a sign of a weak team. Email and spreadsheets are the default tools, and they are very good at sending things. They are bad at remembering who was allowed to see what.
Which sign should you fix first?
Usually two: approvals (sign 11) and the evaluation file (sign 6). Moving approvals to a one-time link in the email leaders already read removes the biggest hole in the audit trail. Putting every evaluator on one model with independent scoring removes forked files, overwritten cells and anchoring in one step.
After that, look at signs 3 and 4. A supplier who learns who else is bidding, or who receives drawings before an NDA, is the kind of failure that ends up in front of legal.
What does iProcure change, and what is live today?
iProcure's eRFx module is built around these eleven signs. They are our scope test: a feature that removes none of them does not belong in it. We are pre-launch, so here is the honest status.
- Live: RFx creation with a quality and price split per event, supplier blindness enforced by the product, and approvals from a signed one-time email link.
- Demo on sample data: the evaluator workspace with sealed prices and consensus, and the event control room.
- Roadmap: the NDA gate, category starter kits, and a password-free supplier portal.
What should you do next?
Take the RFx Health Check with your last three events in mind. If you want the fix for each sign you ticked, leave your email there and we will send a one-page reply. Or see it live in 10 minutes and run one of your own categories through an RFx on sample data.