Tender management for oil & gas

One tender. Two sides. No black box.

Tenderflow runs the whole thing — pre-qualifying vendors, reading the requirements out of your own RFQ, judging every bid against them, and handing you a decision you can defend line by line.

Category-matched invitationsCited findingsHash-chained audit trailReproducible scoring

What the buyer sees

Evaluation board · TND-2026-0114
Brightpath Engineering
5 documents · 4 Aug
Qualified87.5%
Bureau Nordic Inspection
4 documents · 4 Aug
Qualified87.5%
Alliance Weld Fabricators
H-01 · not evidenced
Excluded — flagged62.5%
Tied on 87.5% — Brightpath ranks first on HSE 100% against 50%.
Same tender

What that vendor sees

Your bid · TND-2026-0114
Bid received
4 Aug 2026 · 5 documents
Done
Checked against the criteria
Evaluated — decision pending
In progress
Award decision
Published with the buyer's decision
Pending
No score, no verdict, and no other bidder's name — until the buyer publishes.
The journey

From an RFQ on your desktop to a decision on the record.

Eight steps, each one a screen somebody actually works in.

01

Create & attach

Start a tender, pick the service categories, attach the RFQ you already have. It is parsed and hashed on the way in.

02

Requirements read out

Grouped into Technical, Safety / HSE and Quality, each row carrying its clause, its page and the standards it names.

03

You confirm them

Row by row, mandatory flag included — no bulk approve. Publishing freezes the set as criteria v1.0.

04

Publish by match

Only vendors pre-qualified in your categories are invited, and the ones who missed out are listed with the reason.

05

Vendors bid

Verified vault documents attach in a click. A gap warns and never blocks — a lost certificate should not cost you a bidder.

06

Bids evaluated

Requirement by requirement, every finding citing a document and a page. Mandatory gaps are flagged for you.

07

You shortlist

Ranked by weighted score, ties broken by the higher HSE score. Your confirmation — with a note — is the decision of record.

08

Everyone hears

Shortlisted or not, each bidder is told, and the unsuccessful see the findings against their own bid.

What it does

Six things that change how a tender feels.

Requirements, not retyping

Your tender package is the source. Requirements come out of it with the clause and page attached, and you correct anything the reading got wrong before it counts.

The right vendors, automatically

A tender reaches the suppliers pre-qualified in its own categories — with their standing, their conditions and any at-risk flags shown before you invite them.

Scores you can reproduce

Fixed credit per verdict, averaged per dimension, weighted, rounded once. Nothing is a black-box number — you can check the total on paper.

Nothing leaks between bidders

Before you publish a decision, no vendor screen shows a score, a verdict, or another bidder's name. Afterwards, each one sees only their own.

An audit trail, not a log

Append-only and hash-chained: every edit, override reason, decision and AI attempt, each AI step naming the model and prompt behind it.

A registry that stays current

Vendors register once. Certificates are verified, watched for expiry, and carried straight into the next bid instead of being uploaded again.

Where the line is
The system flags.
A person decides.

That is not a slogan on a page — it is the rule the product is built to, and the three places it would be tempting to break are the three places it is enforced.

An exclusion is a flag, not a decision.A mandatory gap raises it for you. Override it with a written reason and the bid is judged again — which may reach the same answer. The override stays on the record either way.
A missing document warns; it never blocks.A vendor who cannot find a certificate at 16:55 can still submit. You see the gap next to what they did send.
Nothing is awarded automatically.Even at its most autonomous the machine only skips a review step. The shortlist becomes real when you confirm it, against your name.