How to Win More Local Authority Quality Marks

Understand what a quality mark represents

A quality score is the evaluator’s documented judgement against the published criterion and scoring descriptor. It is not a general opinion of your company. Evaluators can only award marks for information submitted in the permitted response and supported by the procurement documents.

High scores normally require more than stating that a process exists. The response should explain the method, responsibilities, sequence, controls, evidence, reporting and outcomes. Where the scoring descriptor refers to confidence, detail, added value or risk, your answer must make those qualities visible.

Start with the published scoring model

Before drafting, record the weighting, word limit, minimum score, scoring scale and descriptor for every question. A 20% mobilisation question deserves more planning, evidence and senior review than a 2% supporting question.

Convert the question into a compliance map

Break every question into individual requirements. Look for command words such as describe, explain, demonstrate, evidence, identify and confirm. Then identify every topic, stakeholder, outcome and control mentioned.

For example, a question asking how you will mobilise staff, systems, vehicles and subcontractors while maintaining business continuity contains at least five separate response obligations. A polished answer that discusses only staff recruitment is still incomplete.

• Highlight every command word.
• Separate each requested topic.
• Identify the buyer’s desired outcome.
• Record mandatory references or documents.
• Allocate evidence and an answer owner.
• Check every element before sign-off.

Use a clear answer architecture

A consistent structure helps evaluators follow your method. One practical model is: commitment, method, responsibility, control, evidence and outcome.

1. Commitment: state exactly what you will deliver.
2. Method: explain the steps and sequence.
3. Responsibility: identify accountable roles.
4. Control: explain checks, escalation and reporting.
5. Evidence: prove the method has worked.
6. Outcome: connect activity to the buyer’s requirement.

This is not a rigid writing formula. It is a completeness test that stops answers becoming collections of unsupported promises.

Make the response contract-specific

Generic answers often describe a company process without showing how it will operate for the advertised contract. Tailoring should be practical rather than cosmetic. Repeating the authority’s name throughout the answer does not demonstrate understanding.

Reference the service environment, geography, users, properties, response categories, interfaces, reporting periods, mobilisation dates and contract outcomes where relevant. Explain how your established systems will be configured for this requirement.

Describe delivery, not aspiration

Statements such as “we will provide excellent customer service” or “we are committed to quality” describe intentions. Evaluators need the operating method behind them.

A deliverable method should show what happens, when it happens, who performs it, what system records it, how exceptions are handled and how the buyer receives assurance. For resident communication, this may include appointment confirmation, access needs, pre-arrival contact, identification, no-access recording, follow-up and complaint escalation.

Name accountable roles

Repeated use of “we” can hide responsibility. Identify the contract manager, mobilisation lead, supervisor, resident liaison officer, commercial lead, health and safety adviser or data owner where those roles are relevant.

Explain decision rights and escalation routes. Evaluators gain confidence when they can see who owns the activity, who checks it and who intervenes if performance falls below target. Avoid naming individuals unless permitted and genuinely available; role titles are often more resilient.

Use measurable controls

Quality responses become stronger when commitments can be monitored. Use accurate and supportable frequencies, targets, tolerances and response times.

Never invent targets merely to sound precise. Commitments may become contractual obligations.

Choose evidence that proves the point

Evidence should be relevant, recent, verifiable and connected directly to the claim. A case study is valuable when it explains the comparable context, your role, the method used, the measurable result and the lesson applied to the new contract.

Useful evidence may include KPI results, audit outcomes, satisfaction data, programme performance, response times, defect rates, accreditation, training records, corrective action, mobilisation outcomes and referenceable contracts. Policies alone rarely prove delivery.

Explain risk and contingency

Strong responses recognise delivery risk without undermining confidence. Identify credible risks, preventive controls, early warning indicators, contingency action and escalation.

For mobilisation, risks could include delayed recruitment, incomplete asset data, system integration, vehicle lead times or subcontractor approval. A useful answer explains how each risk is monitored and what action protects the commencement date.

Connect activity to outcomes

Do not stop at describing internal tasks. Explain why the method matters to the authority and service user. A scheduling system is not valuable because it is digital; it is valuable if it improves appointment reliability, reduces avoidable travel, provides auditable records and supports faster intervention.

Use the specification and evaluation criterion to identify the outcome. Typical outcomes include safety, statutory compliance, resident satisfaction, service continuity, first-time completion, programme certainty, accurate data, cost control and carbon reduction.

Show governance and reporting

Authorities need confidence that performance will remain controlled after mobilisation. Explain meeting structures, reporting cycles, action logs, dashboards, escalation, change control and continuous improvement.

A proportionate governance model may include operational reviews, monthly contract meetings, quarterly strategic reviews and defined exception reporting. State who attends, what information is reviewed and how decisions are recorded.

Demonstrate continuous improvement

Continuous improvement should be a repeatable process, not a closing sentence. Explain how data, audits, complaints, staff feedback, customer insight and lessons learned generate improvement actions.

A credible cycle is: identify variance, investigate root cause, agree action, assign ownership, implement, verify effectiveness and standardise the improvement. Include an example where a previous issue led to a measurable change.

Use added value carefully

Added value should support the criterion and be deliverable within the commercial offer. Relevant examples might include improved reporting, resident accessibility, local supply-chain development, practical innovation or additional assurance.

Do not fill answers with unrelated extras or uncosted promises. If an enhancement requires buyer participation, data, access or approval, state the dependency. Evaluators may discount offers that appear unrealistic or disconnected from the requirement.

Write for evaluators under time pressure

Use descriptive headings, short paragraphs, direct language and tables where permitted. Place the answer close to the relevant requirement rather than relying on the evaluator to assemble it from different sections.

• Use the buyer’s terminology accurately.
• Lead with the answer, then provide detail.
• Keep one main idea per paragraph.
• Define acronyms and technical terms.
• Use evidence beside the claim it supports.
• Remove marketing language that adds no assurance.

Worked example: resident communication

Low-confidence response

We have extensive experience and always communicate professionally with residents. Our friendly team will arrange appointments and resolve any concerns quickly.

This answer contains broad claims but no process, ownership, records, controls or evidence.

Higher-confidence response

The Resident Liaison Officer will issue appointment options through the agreed contact channel and record access needs in the contract system. The operative confirms attendance before arrival, presents identification and records the outcome immediately. Missed access, safeguarding concerns and complaints follow defined escalation routes. The Contract Manager reviews appointment kept rates, no-access trends and complaints monthly, with corrective actions tracked to closure.

The stronger version explains responsibility, sequence, systems, exceptions, measures and governance. Evidence should then be added where space permits.

Worked example: mobilisation

A weak mobilisation response lists activities without dates or dependencies. A stronger answer divides the period into controlled workstreams such as governance, people, systems, supply chain, assets, communications and operational readiness.

It identifies the critical path, milestone owners, buyer dependencies, readiness tests and contingency. It also explains what evidence will confirm readiness: approved plans, trained staff, tested interfaces, stocked materials, completed inductions and signed go-live assurance.

Align quality, price and programme

Evaluators may review different schedules, but contradictions can still damage credibility. Check that the quality response matches the price, mobilisation plan, staffing schedule, method statement, social value offer and contract departures.

Do not promise enhanced supervision, extended coverage or additional reporting if the price and resource model do not support it. Likewise, ensure programme durations reflect the method described.

Run three distinct reviews

A single final proofread is not enough. Use separate review gates:

1. Compliance review: every requirement, instruction and attachment is satisfied.
2. Evaluator review: the answer supports the highest achievable descriptor with clear evidence.
3. Red-team review: an independent reviewer challenges credibility, consistency, risk and differentiation.

Finish with document control and portal checks. Reviews should improve substance, not only grammar.

The WPP quality-mark scorecard

30-day improvement plan

Master quality-response checklist

• The scoring model and highest descriptor have been analysed.
• Every command word and sub-requirement is covered.
• The answer is tailored to the contract.
• The delivery method is explained step by step.
• Roles, responsibilities and escalation are clear.
• Controls, frequencies and targets are supportable.
• Relevant evidence is placed beside key claims.
• Risks and contingencies are credible.
• Buyer and service-user outcomes are explicit.
• Governance and reporting are defined.
• Continuous improvement is demonstrated.
• Added value is relevant and deliverable.
• Quality, price and programme are consistent.
• Compliance, evaluator and red-team reviews are complete.
• The final files meet all submission instructions.

Frequently asked questions

Worked SME example

Use the same principle with your own contract, evidence and delivery model. The example is not wording to copy into a tender; it demonstrates the level of specificity needed to make a response credible and assessable.

Failure points to remove

• Chasing word count rather than marks
• Using generic social-value content
• Failing to connect evidence to the proposed contract
• Leaving review to the original author

Each failure point should be converted into a control within your bid process. For example, a recurring document error should result in an amended checklist, named checker and earlier review date.