Functionality thresholds: passing overall isn't the same as passing

Seven issues in, and this is the one that surprises even experienced bidders, because it runs against normal intuition about scoring.

What a functionality threshold actually means

Many tenders — particularly those involving technical or professional services — are evaluated in stages. Functionality (sometimes called "technical" or "quality") is scored first, often across several separate criteria: experience, methodology, key personnel, equipment, and so on. Only bids that clear a minimum threshold on functionality proceed to have their price and preference points evaluated at all.

The part that catches people out: that threshold is frequently applied per criterion, not just to the overall functionality score. A bid can score comfortably above the minimum overall and still fail if it scores too low on a single sub-criterion — sometimes something as specific as "years of relevant experience" or "number of key personnel with a stated qualification."

Where contractors get caught

• Assuming a strong overall score covers a weak section. If the tender specifies a minimum score per criterion, a zero or near-zero on one line item can fail the whole bid regardless of how well the rest scored.
• Under-detailing the methodology section because "it's obvious how we'd do the work." Functionality scoring is typically based strictly on what's written in the submission — not on the evaluators' independent knowledge of your company or reputation.
• Key personnel CVs not matching the tender's stated experience requirements precisely. If the tender asks for "minimum 5 years' experience in X," a CV that shows 5 years of adjacent-but-different experience often scores lower than a literal, on-point match — wording matters here more than it should.
• Missing the functionality pass/fail cutoff entirely because it's stated in a separate annexure, not the main body of the tender document, and gets skimmed past during a fast read.

Before you commit time to a proposal

• Locate the functionality scoring table specifically and check whether minimum thresholds apply per criterion, not just overall — this changes how you should weight your effort while drafting.
• Match your methodology and CV content to the tender's exact stated requirements, using its language rather than your own shorthand for the same experience.
• If a specific sub-criterion is clearly a weak point for your business, decide before you start writing whether it's worth the bid-writing hours at all.

This is the first issue in the series where the fix isn't really "get a form signed" — it's "read the scoring table before you write a single sentence." Worth the ten minutes.