Root cause analysis: getting past the first plausible answer
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
Tendering rewards preparation and punishes enthusiasm. The most valuable decision in the whole process is the one about which tenders not to enter.
Tendering is competing for work through a formal, documented process — the buyer publishes what they need and the rules, suppliers submit written bids, and an evaluation follows criteria that were stated in advance. It is common in public sector work and in any large organisation buying something significant, and for a small supplier it is either a reliable route to substantial contracts or a quiet drain on the best people's time.
Which of those it is depends almost entirely on the decision made in the first hour: whether to bid at all.
Say no more often than feels comfortable. A supplier that bids for everything wins a low proportion, exhausts its team, and learns nothing; one that bids for a third as many, chosen deliberately, usually wins more in absolute terms because each bid gets the attention it needs. Track your win rate by category — it tells you where you are actually competitive, which is rarely where you assumed.
Ask for the feedback, whichever way it went. Public bodies usually must provide scores and often a comparison against the winning bid, and that document is the cheapest competitive intelligence available anywhere. Read it against your compliance matrix and record what actually lost the marks — price, a weak answer, a missing certification, an unconvincing reference. Do this for a year and your bid or no-bid decisions get sharply better, which is worth more than any single contract.
In Ettex, the bid itself lives in Ettex Docs: threaded comments with @mentions so a colleague can challenge an answer against the paragraph it concerns, version history so you can see what changed between drafts and recover the version submitted, and templates for the answers you reuse. The compliance matrix and the pipeline of open tenders — deadline, portal, status, owner — fit Ettex Sheets, where conditional formatting can flag a deadline approaching. Reusable answers to the standard questions belong in Ettex Notes with tags, the finished pack is assembled and page-numbered in Ettex PDF, and anything requiring signature goes through Ettex Signature.
Said plainly: Ettex has no bid or tender module. There is no portal integration, no automatic tender alerts, no answer library that suggests previous responses, no evaluation scoring, and no submission workflow. It gives you a document editor with real version history, a spreadsheet for the matrix, and a way to assemble the final pack. The reading of the pack and the discipline of the compliance matrix are the work, and neither is software.
A formal competitive process in which a buyer publishes requirements and evaluation rules, suppliers submit written bids, and the award follows criteria stated in advance.
Check the mandatory requirements and qualification thresholds first, then whether there is an incumbent, how the scoring is weighted, what bidding costs in your team's hours, and whether you could deliver if you won.
A table listing every requirement in the tender against where your response answers it. It is the simplest protection against the omission that disqualifies an otherwise strong bid.
Usually because they answered the question they wanted rather than the one asked, used adjectives where evidence was scored, or missed a mandatory requirement entirely.
Yes. Public buyers typically must provide scores and often a comparison with the winning bid — the most useful competitive information you can get, and it is free.
Hours early, not minutes. Portals are slow near deadlines and reject files for format reasons, and tender deadlines are almost never extended for a supplier's technical problem.
Tendering is won by preparation and lost by omission. Decide honestly whether to bid, build the compliance matrix, answer in the buyer's words with evidence, submit early — and read the feedback whichever way it goes.
Root cause analysis works out why something went wrong deeply enough that fixing it prevents a recurrence. Its main difficulty is stopping too early, at an answer that sounds satisfying.
A code of conduct says how people here are expected to behave and what happens when they do not. Its value is not aspiration — it is having decided the hard cases before one arrives.
A project charter names the objective, the boundaries, the sponsor and the person authorised to run the work. Its main use comes months later, when people disagree about what was agreed.