Ask in any company that executes tenders: "Was the quotation sent to the supplier?" The answer comes fast: "Yes, it was sent." Ask again, differently: "Where's the send?" Silence. Inbox archaeology. "Here it is, look, I sent it Tuesday." On Tuesday the supplier's mail server rejected the message. Nobody saw it. The quotation never arrived, the deadline expired Friday, and the item went out at a worse price with a backup supplier.
Nobody lied. Everyone was operating with one word that means five different things: "sent." That imprecision costs real money, every month, in every company executing complex awards. This is the doctrine that fixes it.
The Five States Everyone Conflates
Recorded means: someone wrote the intention into a system. The quotation exists as a record. It doesn't mean it left the company.
Sent means: the message went out the door. It doesn't mean it arrived.
Delivered means: the recipient got it — there's confirmation, not assumption. It doesn't mean they read it or accepted it.
Approved means: a human with authority said yes, explicitly. It doesn't mean it was paid.
Paid means: money moved and there's proof. Not before.
Five states. Five different pieces of evidence. The phrase "already sent" collapses all five into one, and inside that collapse the expensive errors hide: the quotation that never arrived, the payment believed made, the approval someone "took as understood."
Why the Collapse Is so Expensive
In post-award execution, every state confusion has a price. Confusing recorded with sent costs deadlines. Confusing sent with delivered costs suppliers. Confusing approved with paid costs cash — and arguments with accounting nobody wants to have.
The approved-versus-paid confusion deserves its own paragraph, because it's the one that hurts owners most. A supplier calls asking about "the payment that was already approved." Approved, yes — by the technical lead, in a meeting, verbally. Nothing was ever drafted for the finance team to execute. Three weeks pass. The supplier stops believing the calendar, starts adding a risk premium to the next quotation, and the relationship survives on apologies. The fix wasn't a faster payment. It was a sharper word: approved means a human with authority said yes explicitly, in the system, with a record. Paid means money moved and there's proof. Everything between those two states is work still owed.
The pattern is always the same: the operation's "state" is whatever the last message claimed, not what the evidence proves. And messages are optimistic by nature. Nobody writes "I think it was sent." They write "sent," and the system — if one exists — nods along.
Evidence-backed states reverse the direction of trust. Instead of people vouching for the system, the system vouches for the work. A new hire can ask any question — where is this quotation, who approved this payment, did this container actually ship — and get an answer that doesn't depend on who happens to be at their desk that day.
The Doctrine: Evidence or It's Not a State
The fix isn't asking people to be more careful. People are already as careful as they can be at 7 PM with three tenders open. The fix is structural: no state exists without its evidence.
A quotation should never lie about its state. If it was recorded, it says recorded. If the send failed, it says send failed — big, visible, impossible to ignore — and it gets retried explicitly. What must never happen: a record silently rewritten, a failed send appearing as sent, a sent record disappearing.
What to Demand From Any System — Including Your Current One
Even if you operate on spreadsheets and email today, you can demand the doctrine:
- Separate states. Recorded, sending, send failed, sent, received, confirmed. If your tool only has "sent," you have a rumor with a column.
- Failure is visible. A failed send must shout, not whisper in an outbox.
- Retry is explicit. Retrying is a human decision, not a side effect of reopening a file.
- Nothing is silently rewritten. A record's history is part of operational truth.
- Zero duplicates. Supplier sends go through a single path. A duplicate email with different prices doesn't produce two quotes; it produces one distrust.
- Explicit human approval. Payments, offers and purchase orders require a person with authority to say yes. Always.
The Question That Changes Everything
Next time someone says "it was already sent," ask: "Recorded, sent, delivered, approved or paid?" The first week, the question annoys. The second week, it organizes. Within a month, your operation speaks a language in which it's impossible to lie to itself.
That's the difference that saves tenders. It's not sophisticated technology: it's the discipline that every state proves what it claims.
Coraxis was born with this doctrine at its center: every state is evidence-backed and auditable, supplier sends go through a gateway with zero duplicates, and human approval is explicit for everything that moves money. See what delivery truth looks like →