The award notice arrives. Your company won. There's coffee, there are hugs, there's a photo in the WhatsApp group. Celebrate — you earned it. But put an expiration date on the celebration: 24 hours. Because a tender is 10% winning and 90% execution, and the 90% starts tomorrow at 8:00 AM, whether it finds you ready or not.
This is the playbook we wish we'd had. Not procurement theory: what an operator actually does in the first weeks after the award so the contract doesn't become a loss with a letterhead.
1. Centralize the Truth Before It Scatters
Right now the documents live in six places: the award notice in someone's inbox, the item sheet in a spreadsheet on another person's desktop, the terms in a PDF that's "somewhere around." The first act of disciplined execution isn't producing anything: it's deciding where the truth lives.
One central register. The award with its evidence. The item sheet imported whole, not retyped by hand — every manual transcription is an error opportunity nobody will catch until it costs money. If your system can't import the sheet as it comes, you'll spend a week typing and a month discovering typos.
2. The Item Is the Unit of Truth
Tenders aren't executed "in general." They're executed item by item. Each line has its supplier, its quotation, its purchase order, its payment, its shipment and its technical approval. When you ask "how are we doing?", the honest answer is never a percentage: it's the state of every item.
Organize everything around that unit. If you can't answer the state of any item in ten seconds — with evidence, not from memory — you don't control the execution yet. You have optimism.
3. Adopt the Evidence Rule From Day One
This is where most bad executions die: the "state" of the operation becomes whatever the last message claimed. "The quotation was already sent." Who sent it? When? Did it arrive? Is it confirmed? A chat message answers none of that.
The doctrine is simple: recorded is not sent, sent is not delivered, approved is not paid. Every state must be backed by evidence — a document, a receipt, a confirmation — or it's not a state, it's a rumor. Install that rule in week one and you skip the arguments of month six.
4. Quote Suppliers with States, Not Goodwill
A supplier quotation has real states: requested, sent, failed, retried, received, confirmed. Treat them as states, not assumptions. If a send fails, it must show as failed and be retried explicitly — never silently rewritten.
And watch out for the classic: the duplicate email. A supplier who receives the same request twice with different prices doesn't quote twice; they lose trust once, which is worse. Sends must go through a single path that guarantees zero duplicates.
5. Payments: A Payment Without Evidence Is an Argument Waiting for a Date
Register every payment when it happens, with its proof and the validated exchange rate. Not at month-end. Not "when there's time." Cash planning for a multi-item execution is built on payments registered daily, or it isn't built at all.
Same for production and shipments: every update with its evidence attached — BL, container, ETA. From factory to port, if you know where everything is, surprises are logistical. If you don't, they're financial.
6. Technical Gates, per Item
Technical documentation and samples aren't a final formality: they're per-item gates that block deliveries and payments. Define them up front, give them a state, and review them as seriously as payments. An item without technical approval is money you can't collect, even if it's delivered.
7. What Not to Do
Don't buy an ERP for this. A two-year implementation doesn't solve an execution that starts Monday. Don't add the tenth spreadsheet either: sheets don't know the state of anything, they only know what someone typed last. And don't leave deadlines in one person's memory — people get sick, resign, and take vacations.
8. Install the Monday Cadence
Execution isn't reviewed "when there's time": it's reviewed on a fixed cadence. Every Monday at 8:00 AM, the same question: what needs action this week? Not an upward report — a ranked list of real urgencies: the quotation three days without an answer, the item whose technical gate expires, the payment waiting on approval, the container whose ETA moved.
If answering that question takes a morning of phone calls, your system isn't answering: you're interrogating people. Operational urgency should be ranked before you ask, with every number linked to its evidence. That sustained weekly cadence is what turns a reactive execution into an operation with command.
The Point
Winning the tender proves you can bid. Executing it proves you can operate. They're different skills, and the market only rewards the second one: margin is made or lost in the 90%.
Coraxis was built exactly for that 90%: items, quotations, purchase orders, payments and shipments, with evidence behind every state and everything on your own machine. See the full operation →