The Missing "How": Why tenders that should win don't and the framework that changes that

I learned something early in this work that I've never forgotten ...

My first real failure as a tender writer taught me that. A genuinely strong solution well-considered, community-focused, technically sound came second to something that, frankly, shouldn't have won. The difference wasn't the quality of the idea, it was the quality of the explanation. The winning team could articulate exactly how their solution would work. Mine could only articulate that it would.

That lesson has followed me into every brief I've touched since because here's the uncomfortable truth sitting at the heart of tender writing:

Evaluators cannot fund what they cannot visualise.

Why the "How" is the whole game

Simon Sinek built a career on the Why. And he's right in leadership, in culture, in brand, the Why is everything.

But in tender writing, the why gets you to the table, but it is the How which wins the contract.

Most losing responses describe what will be delivered and why it matters. Winning responses show the exact steps, decisions, behaviours and safeguards that turn a solution into a reality. They answer the question every evaluator is silently asking as they read:

That question matters more in 2026 than it ever has. Government procurement panels are acutely aware of what gets quietly called "sharp practices"; organisations that win contracts on the strength of their pitch and then quietly underdeliver on the substance. The scrutiny on delivery has sharpened and so the How has become the evaluator's primary comfort mechanism.

Think about it from their side of the table ... Nobody wants to be the person who recommended awarding a million-dollar community infrastructure contract to an organisation that turned out to be all pitch and no process. That's a career-defining bad look. So evaluators read for the How not just to score your methodology but to reassure themselves that you will actually do what you say.

Here's the part most vendors miss: the How protects you too.

A detailed, honest How section is a risk mitigation exercise for your own organisation. It forces your team to confront delivery before the contract is signed. It surfaces the gaps between what your creative lead can sell and what your operations team can actually run. It also means that when you win, and you implement, you're working from a document that reflects reality, not aspiration.

The Creative vs The Operator - Finding the sweet spot

Every tender team has both.

The creative: the person who can see the vision, shape the narrative, make the silk purse gleam.

The operator: the person who knows exactly what happens on day one, who does what, what could go wrong, and how you'd recover.

The best tenders are written from the sweet spot between those two people.

But here's where it breaks down. The creative writes the What and the Why in beautiful, persuasive language and then hands the How section to the operator who fills it with process jargon and Gantt chart references that kill all the momentum.

Or worse, the creative writes the How too, and it sounds wonderful and means nothing.

The skill, the real craft in tender writing, is holding both. Making the How as compelling as the Why.

• Making the process as readable as the vision and sometimes that means the creative has to step into uncomfortable operational specificity

• And making the operator trust that a sentence can carry meaning without a dot-point beneath it.

That discomfort is where growth lives and the tenders that come from that place are the ones that win.

What weak "How" sections actually cost you

Before the framework, let's call out what's at stake. Vague How sections don't just score poorly on methodology criteria, they trigger evaluator anxiety. When an assessor reads "we will work collaboratively with all stakeholders to ensure optimal outcomes" they don't score it low because it's badly written. They score it low because it tells them nothing about what will actually happen and that gap feels like risk.

Strong technical solutions lose to slightly weaker ones with crystal-clear delivery plans. Every experienced tender writer has seen this. A pig's ear, explained in honest detail, will sometimes beat a silk purse wrapped in generalities.

The motherhood statement is the single most expensive habit in tender writing.

"We will leverage our proven methodology."
"Our team will engage proactively with community stakeholders."
"We are committed to delivering excellence."

Every evaluator has read these sentences ten thousand times. They land as noise. No worse, they land as a signal that the writer doesn't actually know what will happen next.

This is where we quote my Dad: "Son, there is an equation for every occasion"

The 4-Layer How Framework

Use this as the structural backbone of every major response section.

Layer 1: How you understand the problem

Before you tell them what you'll do, show them you understand what's actually happening. Reference specific community challenges, local data, site conditions, or brief details that demonstrate genuine reading of the context not just the document.

This is where HBDI thinking is useful at a team level. Your analytical thinkers have read the compliance data. Your relational thinkers have spent time understanding the lived experience of the community this project will affect. Show both. Show that your understanding is whole, not partial.

Layer 2: How you will deliver

This is the heart of the framework and the section most teams underwrite.

Break delivery into clear, sequenced steps with decision points, named responsibilities and realistic timing. Not Gantt chart references but actual narrative that walks the evaluator through what will happen and who will be in the room when it does.

The test is simple: could someone who has never met your team read this section and know exactly what will happen in the first thirty days?

If the answer is no, rewrite it.

Avoid: "We will implement best-practice community engagement strategies."

Use: "In weeks one and two, our community liaison lead will convene a reference group session using a co-design format. This shows here's what that looks like, here's who facilitates it and here's what changes based on what we hear."

That's the difference between a statement and a plan.

Layer 3: How we will manage risk and adapt

Evaluators fear failure more than they want innovation. Show your early warning systems. Name your escalation paths. Describe what happens when something doesn't go to plan because experienced evaluators know something always doesn't go to plan. At some point "You're gonna need a bigger boat"!

Real specificity here builds more confidence than any capability statement. "If community sentiment shifts significantly after the first engagement phase, here is the protocol we activate and here is who makes that call" is worth ten paragraphs about your organisation's commitment to quality outcomes.

Layer 4: How we will measure and prove success

Every claim needs a measure. Every measure needs a review cycle. Every review cycle needs to connect back to what the procurer actually cares about, not what's easy for you to report.

Tie your evidence framework to the procurer's language, their reporting requirements and the community outcomes they're accountable for. Show that you understand success from their side of the table, not just yours.

The 45-minute pre-draft exercise

Before AI touches the keyboard. Before anyone opens a template do this with your team in a room ... ideally at a whiteboard where anyone can pick up the pen and push back on what's written.

One: Read the evaluation criteria out loud. Underline every word that implies method: approach, methodology, deliver, implement, manage, demonstrate.

Two: Create a blank page for each major criterion headed simply: "How we will..."

Three: For every section, answer four questions:

• How exactly will we do this?

• Who specifically will do it and when?

• How will we know it's working and what happens if it's not?

• How does this connect directly to the community outcomes required?

Four: Replace every motherhood statement with a concrete process step or real example.

Five: Test it. Hand it to someone who has never seen the brief. Ask them: "Do you know exactly what will happen in the first month if we win this?"

Their confusion is your rewrite list.

The bigger picture

In 2026, AI can generate a perfect-sounding What section in seconds.

It cannot write an honest How. Not because it lacks the words, it has all the words. It is because the How requires your team to have actually thought through delivery. To have had the uncomfortable conversation between the creative and the operator. To have admitted where the gaps are and decided how to fill them.

That conversation happens at a whiteboard, not in a prompt window.

The tenders that win from here aren't the ones with the most impressive solution on paper. They're the ones where the evaluator can close the document and clearly see what happens next.

Show them that. In plain language, in honest sequence, with real people named and real processes described.

That's not just good tender writing.

That's a promise you can keep.

"A pig's ear, sold well, will beat a silk purse every time."

"If we give this to them how will it actually work on the ground and how do we know it won't fail?"