Writing a Project-Specific Methodology (Not a Generic One)

Methodology is usually the most heavily weighted non-price criterion in a government tender. It also produces the widest spread of scores in the moderation meeting — which means it is where tenders are most often decided, and where an hour of your time is worth more than anywhere else in the document.

It is also, reliably, the most polished section in most submissions and one of the lowest scoring. Those two facts are connected.

The problem with your best-written section

Your methodology has been refined across dozens of tenders. The prose is clean, the structure is logical, the diagrams are professional. It has survived years of internal review.

And that is exactly why it scores in the middle. Content refined across dozens of tenders contains, by definition, nothing that belongs to any one of them.

Meanwhile an assessor has just read a competitor who wrote three paragraphs about the level crossing at the north access, the school term dates constraining the noisy works, and the sequencing problem created by the existing services running under the proposed slab. That competitor's prose may be worse than yours. Their score will be higher, because the panel can see they read the documents and you cannot prove that you did.

Decision Signal 2 of circa 150 — Project-Specific Methodology. Generic methodology is the single most common cause of a mid-band score on the highest-weighted criterion. Panels distinguish between a contractor describing their standard process and a contractor describing how they will deliver this scope, on this site, under these constraints.

What "project-specific" actually means

It is not sprinkling the project name through your standard text. Assessors see that constantly and it fools nobody.

It means the methodology could not be lifted and submitted for a different job without substantial rewriting. Test it: delete the project name and read it. If it would work unchanged for the last three tenders you submitted, it is generic.

Specificity comes from four sources, all of which are in the tender documents you were issued.

The site. Access points, adjacent land uses, existing structures, ground conditions, services, environmental constraints, working hours, tidal or seasonal windows, heritage fabric.

The operational context. Who keeps using the asset during the works. Which stakeholders must be notified, consulted or coordinated with. What cannot be shut down and what can, and when.

The scope's own difficulties. Every scope has two or three genuinely hard parts. Name them. A methodology that treats a difficult tie-in as routine tells the panel you have not thought about it.

The program's dependencies. What has to happen before what, where the float is, and what the critical path actually runs through.

The structure that scores

Start with your understanding of the project. Not a restatement of the scope — a short section demonstrating you have identified the constraints that make this job different. This is the single highest-value paragraph in the section, because it establishes credibility for everything after it.

Then the delivery sequence. Stage by stage, with the reasoning. Panels are reading for logic, not activity lists. Why this order? What does each stage depend on? What is the trigger to move from one to the next?

Then the specific challenges and your response to each. Take the two or three hard parts you named and set out the approach, the resources and the fallback. This is where the highest-scoring submissions separate themselves.

Then the interfaces. Client, stakeholders, authorities, subcontractors, existing operations. Who talks to whom, how often, and who decides.

Then the program. And make sure it agrees with everything above it.

The program mismatch that costs two scores at once

If your narrative describes a staged approach and your program shows a single continuous sequence, or your narrative promises night works your program prices as day works, the panel does not simply score the weaker of the two.

They begin to doubt the plan itself. A mismatch says one of these two documents was not written by someone who understood the job — and the assessor cannot tell which, so both scores fall and the credibility damage spreads into the criteria either side.

Have one person read the methodology and the program side by side, specifically hunting for disagreement, before lodgement. It takes an hour.

Risks: specific or worthless

A risk register with "adverse weather — monitor forecasts" and "delays to approvals — engage early" contributes nothing. Every submission has those.

What scores is a risk that could only be identified by someone who read this tender: the tie-in window constrained by the authority's outage calendar, the lay-down area that disappears when the adjacent contract mobilises, the material with a lead time longer than the period allowed before it is needed. Each with a control that is actually a control — a named action, an owner, a trigger — rather than a verb like "monitor" or "manage".

Three specific risks beat thirty generic ones.

How much time this deserves

Disproportionately more than the other criteria. If methodology carries the highest weighting and produces the widest scoring spread, then the marginal hour spent there returns more than the same hour spent polishing organisational capability, where every tenderer scores similarly anyway.

In practice that means starting the methodology early — while there is still time to ask questions during the clarification period — rather than treating it as the section you write once the schedules are done.

Where a structure helps and where it does not

Nothing above can be outsourced. The site-specific reasoning has to come from people who have looked at the drawings, and probably at the site.

What can be handled for you is knowing what the section needs to contain — which sub-sections a panel expects under a methodology criterion for this type of work, what evidence belongs in each, and what the common failures are.

That is what the Smart Submission Blueprint provides: the section architecture for this specific tender, built from the criteria extracted from your own documents, with what each section requires and what a panel expects to find there. It does not write the methodology. It makes sure you are not guessing at the shape of it while the clock runs.

And once written, the Digital Evaluation Committee scores it against the published criteria and tells you where a panel would mark it down — before you lodge, while it can still change.

Your first tender is free, one per organisation.

---

Frequently asked questions

How long should a tender methodology be? Long enough to cover the sequence, the specific challenges, the interfaces and the risks with real detail — and within any page limit the tender sets. Padding a methodology out with standard process description actively lowers the score by diluting the specific content.

Should I include diagrams in the methodology? Yes, where they explain something the text cannot — staging plans, site setup, traffic management, sequencing. Every diagram should be referenced from the narrative and captioned with what it demonstrates.

Can I reuse methodology content between tenders? Reuse the structure and the descriptions of your standard systems. Rewrite everything that touches the site, the sequence, the stakeholders and the risks. If more than about a third survives unchanged, the section is probably too generic.

What if the tender doesn't give enough detail to be specific? Use the clarification period to ask. Questions asked during tender are normal, they are usually answered to all tenderers, and they demonstrate engagement. Where information genuinely is not available, state the assumption you have made — a stated assumption is far stronger than a silent one.