Your Tender Response was Beautiful. Shame it Didn't Answer the Bloody Question.
A love letter to beautifully written nonsense, meaningless corporate waffle and the poor bastards who have to evaluate it.

Picture the scene.
You've spent three weeks writing a tender. You've worked late. You've skipped lunch.
You've developed an intimate and deeply unhealthy relationship with Microsoft Word.
Your submission is magnificent. The formatting is immaculate. The headings are consistent.
The executive summary is so inspiring you briefly consider framing it.
You've used phrases like "strategic alignment," "operational excellence" and "customer-centric service delivery" with the confidence of someone who has absolutely no intention of explaining what they mean.
You press Submit.
You pour a celebratory drink.
You wait.
And then the email arrives.
Unfortunately, your submission was unsuccessful.
WHAT?!
But it was BEAUTIFUL!
It had a TABLE OF CONTENTS!
It had COLOURED HEADINGS!
It had an ORGANISATIONAL CHART!
How could they possibly reject such a masterpiece?
Well, here's one possibility.
You didn't answer the bloody question.
The Evaluator is not Judging a Creative Writing Competition
This may come as a surprise, but tender evaluation panels are generally not sitting around waiting to be dazzled by your adjectives.
They're trying to determine which supplier offers the strongest response to the published requirements.
And they've probably got several submissions to assess.
Possibly dozens.
They don't have time to admire your literary flair while trying to work out whether you've actually demonstrated relevant experience.
Let's imagine the tender asks:
Demonstrate your organisation's experience delivering comparable services.
You respond:
"Our organisation is a dynamic, innovative and customer-focused industry leader with an unwavering commitment to excellence, integrity and continuous improvement."
Lovely.
Absolutely lovely.
But what the hell does it mean?
Have you delivered comparable services?
Where?
For whom?
How big was the contract?
What did you achieve?
Did anything go wrong?
How did you deal with it?
The evaluator has asked for evidence.
You've given them a motivational poster.
The Difference Between Saying Something and Proving it
Here's another example.
The tender asks:
Explain how you will manage mobilisation and ensure services commence on the required date.
Your response:
"We are committed to delivering a seamless mobilisation experience through our proactive, collaborative and solutions-focused approach."
Wonderful.
So who's recruiting the staff?
Who's organising the equipment?
Who's checking licences?
Who's setting up the systems?
Who's training everyone?
And what happens when three people resign the week before commencement?
Silence.
Apparently, the proactive, collaborative and solutions-focused approach has gone out for coffee.
A proper mobilisation response would explain the activities, responsibilities, resources, timeframes and controls involved.
Not just promise that everything will be seamless.
"Seamless" is not a mobilisation plan.
It's an adjective.
The Magical Power of the Word "Demonstrate"
There's a word in tender documents that deserves considerably more attention than it gets.
Demonstrate.
Not "claim."
Not "suggest."
Not "tell us how marvellous you are."
Demonstrate.
It means the evaluator wants something that supports what you're saying.
Evidence.
Examples.
Results.
Relevant experience.
Actual arrangements.
You know. Stuff.
And yet some tender responses seem to treat "demonstrate" as an invitation to write a longer paragraph about the company's passion for excellence.
Passion is lovely.
But unless the contract involves interpretive dance, the evaluator probably wants something more concrete.
And Then There's the 20-Year Experience Trap
I hear this one regularly.
"We've been doing this for 20 years."
Excellent.
That may be very relevant.
But 20 years of doing something doesn't automatically tell an evaluator whether you've been doing it well.
Or whether you've delivered anything comparable to the contract they're offering.
Or whether the people who did the work are still with your business.
Or whether you have the capacity to do it again.
Experience is valuable.
But it needs context.
A specific project example with a clear explanation of scope, complexity, performance and outcomes can be far more persuasive than a sweeping claim about decades of industry leadership.
Even if the sweeping claim uses the word "synergy."
Especially if it uses the word "synergy."
Please Stop Making the Evaluator Solve a Mystery
Another favourite is the tender response that technically contains all the relevant information.
Somewhere.
There's a bit on page 14.
Another bit in Appendix C.
A performance figure buried in a table.
A methodology reference hidden behind a sentence about stakeholder engagement.
And a crucial explanation apparently living in the writer's head.
The evaluator is expected to assemble these fragments into a coherent demonstration of capability.
Like a procurement-themed escape room.
Except nobody's having fun.
If something matters, explain it.
If evidence supports your answer, identify it.
If a previous project is relevant, say why.
And if you're relying on an attachment, make sure the tender rules permit it and tell the evaluator exactly where to find the information.
Don't make them go treasure hunting.
They're evaluating your tender, not auditioning for Indiana Jones.
Beautifully Presented Bollocks is Still Bollocks
Now, don't misunderstand me.
Presentation matters. Clear writing matters. Structure matters.
Nobody wants to evaluate a 70-page submission written in eight-point font with paragraphs that resemble an uninterrupted stream of consciousness.
But presentation is there to help communicate substance.
It cannot replace it.
A beautifully formatted response that doesn't address the criterion is still a weak response.
A plain, clearly structured answer supported by relevant evidence may be much stronger.
And increasingly, with AI making it easier to produce polished prose, I suspect this distinction is becoming even more important.
Because generating a paragraph that sounds impressive is now ridiculously easy.
Generating a paragraph that accurately demonstrates a business's capability still requires understanding what that business actually does.
So What Should you do Instead?
Start by reading the evaluation criteria.
Properly.
Not just glancing at the headings before launching into your standard company spiel.
Work out what each criterion is actually assessing.
Then ask yourself:
What do we need to prove?
What evidence do we have?
What examples are relevant?
What practical arrangements will we put in place?
And what information would give the evaluator confidence that we can deliver?
I've put together a free Tender Evaluation Criteria Decoder through TenderWise to help businesses work through exactly those questions.
Because sometimes the biggest improvement you can make to a tender response isn't writing more.
It's understanding what you should have been writing in the first place.
One Last Thing Before You Press Submit
Imagine you're the evaluator.
You know nothing about the business beyond what's in front of you.
You have a published set of criteria and a stack of competing submissions.
Can you find the evidence?
Can you understand the proposed approach?
Can you see why this business is capable of delivering the contract?
Or are you staring at three paragraphs about unwavering commitment, world-class service and innovative excellence, wondering whether anybody actually read the question?
Because the evaluator can't award marks for the wonderful things you meant to say.
Only for the information you've actually provided, assessed against the published criteria.
So by all means, make your tender beautiful.
Give it lovely headings.
Use a sensible font.
Make the tables line up.
But before you press Submit, ask yourself one very important question.
Have we actually answered the bloody question?
Because if the answer is no, all that beautiful formatting is just putting lipstick on a very expensive pig.
About the Creator
Enjoyed the story? Support the Creator.
Subscribe for free to receive all their stories in your feed.
Comments
There are no comments for this story
Be the first to respond and start the conversation.