Procurement evidence pack gym operators need to win recompetes

Your contract renewal lands on a procurement officer's desk at the same time as two competing bids. One is a national operator with a recognisable brand. The other is a regional trust with lower overhead costs. You have run this leisure facility well for three years — but 'running it well' is not a submission. What sits inside your evidence pack is.

This article is for operators who are twelve to eighteen months out from a recompete and want to build the documentary foundation that turns a strong operational record into a credible, scoreable bid.

What procurement panels are buying at contract renewal

Procurement teams at leisure trusts, local authorities, and housing associations are not primarily buying enthusiasm or brand reputation. They are buying demonstrable risk reduction. The officers who score your bid need to be able to justify their recommendation to a committee — and committees ask difficult questions about what happens when things go wrong.

That means the scoring criteria — however the panel phrases them — typically reduce to three commercial questions:

1. Did the operator maintain safe, available facilities over the contract term?
2. Did the operator demonstrate financial and operational control?
3. Did the operator retain and grow the member base in line with agreed targets?

Your evidence pack is the document that answers those questions with data, not assertion.

The four categories of evidence that move the score

Most operators arrive at recompete with a narrative document and some headline membership numbers. Panels have seen enough of those to be sceptical. The operators who score consistently well in the 'quality of current service' section submit evidence across four distinct categories.

1. Asset availability records

This means a timestamped log of every equipment fault, every engineer callout, every resolution, and every period of unavailability — organised by asset, by site, and by month. If your treadmill bank ran at 94% availability over thirty-six months, that is a figure worth submitting. If one specific unit caused repeated problems, show what you did about it and when.

Panels are not looking for a perfect record. They are looking for evidence that you operated a controlled, documented process.

2. SLA performance data

Response time commitments and resolution time commitments are standard clauses in leisure management contracts. At renewal, the expectation is that you can demonstrate performance against those clauses — not estimate it from memory. Your SLA data should show, for each contract year:

• Average time from fault report to engineer attendance
• Average time from attendance to resolution
• Number of SLA breaches and documented remedial actions
• Trend direction (improving, stable, or deteriorating — and what you did about it)

If your SLA performance improved year-on-year, that trend is one of the most commercially persuasive things you can put in an appendix.

3. Member outcome data

Retention rates, active membership trends, peak-hour utilisation, and complaint volumes all belong in the evidence pack. Procurement panels increasingly include social value criteria, and member outcome data — particularly for specific cohorts such as older adults or referral scheme participants — feeds directly into those scores.

Link your member data to operational decisions wherever you can. For example: if you moved your free weights area to address congestion at peak hours, show the utilisation figures before and after. Operational changes with measurable member outcomes are far more persuasive than operational changes described in isolation.

4. Incident and compliance records

This category overlaps with compliance submissions but belongs in the evidence pack in its own right. A clean summary of reported incidents, RIDDOR submissions where applicable, and corrective actions taken — presented clearly and without gaps — signals professional management. Blank periods with no explanation raise questions. Gaps followed by a change in process demonstrate maturity.

Building the pack twelve months before submission

The most common reason an operator arrives at recompete with a thin evidence pack is not that they ran the contract poorly — it is that they did not record and retain the right data as they went. Reconstructing three years of asset history from engineer invoices and email chains in the final six weeks before submission is possible, but the result is always incomplete and always shows.

A practical twelve-month preparation timeline looks like this:

1. Month 12: Audit your current data sources. Identify what exists, what is missing, and what format the procurement authority requires for submissions.
2. Month 10: Close any gaps in asset records. This includes retrospective entry of callout data if your current system does not hold it.
3. Month 8: Run your first internal SLA review against contract commitments. Identify any periods where performance dipped and document the context and remedial action.
4. Month 6: Compile member outcome data and map it to operational decisions. Identify two or three specific examples where operational changes improved a member metric.
5. Month 4: Draft the evidence appendices. Get an internal sign-off from someone outside operations — ideally finance or a senior manager — to stress-test clarity and credibility.
6. Month 2: Final review against the scoring matrix. Map each appendix to a specific criterion and score band.
7. Month 1: Submit, with a cover index that makes navigation easy for the scoring panel.

How SLA performance becomes a commercial narrative

SLA data on its own is a table of numbers. The evidence pack that wins the recompete turns that table into a commercial story.

The structure that works is: baseline, event, response, outcome. For example: in year one, average equipment response time was 18 hours. A cluster of faults on the cardio floor in month nine — three treadmills and a cross-trainer within a fortnight — pushed that average up. You introduced a vetted engineer rota with pre-agreed response commitments. By year two, average response time was 11 hours. By year three, it was 9 hours, with no SLA breaches in the final six months of the contract.

That story demonstrates operational learning, commercial control, and a management team that responds to evidence rather than waiting for problems to escalate. It is also verifiable — the panel can ask for the underlying data and you can produce it.

Contrast that with a submission that says: 'We maintained high equipment availability throughout the contract period.' That sentence is unscoreable. The story above is not.

The engineer network dimension of your evidence pack

One of the questions a procurement panel will ask — sometimes explicitly in the specification, sometimes implicitly in the scoring criteria — is: how do you ensure consistent, qualified service delivery when things go wrong?

If your current answer is 'we have a list of engineers we call' or 'we use whoever is available', that is a vulnerability in your bid. Panels assessing risk want to see that your maintenance and repair capability is structured, not ad hoc.

A Partner Engineer network — a pool of vetted, credentialled field engineers with pre-agreed response commitments and documented qualifications — is an asset in this context. It means you can submit, alongside your SLA data, evidence of the qualification standards your engineers are required to meet, the vetting process they went through, and the contractual commitments they operate under. That converts 'we call engineers' into 'we operate a structured maintenance supply chain' — which reads very differently to a procurement panel.

Presenting the pack: format and framing

The evidence pack is not the bid narrative. The narrative tells the story. The evidence pack substantiates it. Treat them as separate documents with cross-references between them.

Format considerations that help your submission score well:

• Use a clear index with page references mapped to scoring criteria
• Keep data tables simple — one metric per table, clearly labelled axes and date ranges
• Include a one-paragraph plain-English summary at the top of each appendix explaining what the data shows and why it matters
• Avoid combining multiple metrics into a single chart unless the relationship between them is the point you are making
• Date-stamp everything, including the data extract date for any digital records

Procurement officers read multiple submissions under time pressure. A pack that is easy to navigate and clearly connected to the scoring matrix reduces friction and increases the chance that your evidence is actually absorbed, not just filed.

The recompete mindset starts at contract award

The operators who consistently win recompetes are not necessarily the ones who run the best facilities. They are the ones who treat every month of a contract as a month of evidence collection. The log they open the day after contract award is the same log they submit three years later.

If you are mid-contract right now, the question is not whether you have enough time to build a compelling evidence pack. The question is whether your current systems are capturing the data that will make the pack credible when the moment arrives.

GymAxis is built to give operators exactly that foundation — asset tracking, SLA monitoring, member lifecycle data, and a Partner Engineer network — all in one platform, all producing the structured records that a procurement evidence pack requires. You can find out more at https://gymaxisai.com.

Book a demo at https://gymaxisai.com/demo-request to see how GymAxis structures the data your next recompete will depend on.