How To Write A Multi-Site Tender Response With A Worked Rollout Example
Four branches are about to open. Preston can’t take bookings. York rings a minute later. Now imagine you’re the operations director about to award that contract. You like the smaller supplier. Their price works. But if you put your name to this, who picks up the second call?
To write a tender response for a multi-site rollout, answer the buyer’s scored question with the dates, people and cover you can commit to. Show how each site becomes ready, who decides whether it opens, and what happens when two sites need help at once. Then give evidence from a customer who has seen your team handle a comparable situation.

This guide follows a fictional four-branch booking system rollout. You can use the same approach for a service change, an installation or a contract moving from one supplier to another. The starting point is the hour your buyer is worried about.
How to structure a multi-site tender response
Open the invitation to tender (ITT), the specification, the pricing schedule and the marking scheme side by side. Find the exact question about mobilisation or implementation. “Describe your experience” asks for work you have done. “Explain how you will maintain service at all sites” asks for a commitment to this buyer. Give each its own answer if the panel scores them separately.
Write down what earns marks. List each part of the question, its weighting, any pass mark, the word limit and the evidence the buyer accepts. Assign an owner to each part. If local attendance is mandatory, establish that you can supply it before writing about remote support.
Check every site and date. Confirm opening hours, access, travel, training, the outgoing supplier’s handover and any dates the buyer cannot move. Put unknowns through the stated clarification channel before its deadline. Record the answer against the affected sites.
Put real people against the busiest hour. Reserve cover for work you already owe other customers. Identify the rollout lead, deputy, site contacts and the person keeping branches informed. Confirm any subcontractor’s availability, travel and cost on those dates.
Explain who can stop or restart the rollout. Give each site a readiness check, a person authorised to proceed, a fallback and a handover test. Show what happens to the other sites if one fails. Match response and restoration promises to your priced support hours.
Match the evidence to the claim. Use the forward rota for availability, a completed project for delivery history and an authorised customer account for what the branches experienced. Put each in the answer box or attachment the buyer has asked the panel to assess.
For public contracts under the Procurement Act 2023, the Cabinet Office guidance on assessing tenders explains how award criteria, relative importance and the assessment method fit together. Follow the documents issued for your competition. A private buyer may ask for a proposal in your own format. There, “Launch-day support” is a clearer heading than “Our national capability”.
Build a mobilisation plan the branch managers can use
Mobilisation covers the work between award and the point where the buyer can accept the service. In our example the buyer wants four branches live on Monday at 09:00. Preston and York have different opening teams, but the same booking system. On paper it looks like one change. In practice, four people need to be able to open their doors.
When | Owner, action and evidence |
|---|---|
At award | The rollout lead and buyer agree the site list, local contacts, access, opening times and who can authorise a delay. Record unresolved dependencies with an owner and due date. |
Five working days before | Each branch manager confirms staff and access. The outgoing provider supplies the agreed data. The rollout lead checks a test booking and confirmation at every branch and logs the result. |
Friday before launch | The buyer’s operations lead reviews the four readiness records. A branch with a failed test keeps its agreed fallback. A shared booking fault puts all four starts back for a decision. |
Monday opening | One coordinator takes calls across the four branches. The technical lead and deputy cover overlapping faults. Each branch knows the contact route, temporary booking procedure and next update time. |
After opening | The local manager checks a booking, a confirmation and any entries made manually. Once these match and the buyer accepts outstanding issues and owners, the service desk takes over. |
The Crown Commercial Service implementation schedule (PDF, page 327) gives a real example. It asks the incoming supplier to work with the buyer and outgoing supplier on handover, and to agree a plan with the buyer that sets out the milestones and dependencies. Read your own schedule for who signs, what they must see and when responsibility transfers. “Handover complete” is a poor substitute for a branch manager successfully taking a booking.
Work out how many sites you can support at once
Four technicians appear on the rota. Two are already committed to existing customers. That leaves two for this launch. A separate coordinator can keep four managers informed, but that still gives you two people able to fix technical faults at the same time. If all four branches require a technician physically present at 09:00, this rota leaves two sites uncovered.

Count separately the people who can answer a call, diagnose the fault and reach a site within the required time. Allow for travel, access, breaks and the work of the deputy when they are called away. The government bid pack for smaller suppliers asks bidders to consider simultaneous deployments alongside their existing workload.
If the dates are fixed, secure and price the extra cover or make the decision to pass. If the buyer permits waves, explain what two branches on Monday and two on Tuesday would change. Set out the effect on training, travel and support fees in the requested pricing fields. A cheaper bid built on a different start date can leave the buyer with two prices for two different jobs.
Worked tender response for a four-branch rollout
Example tender question. “How will you launch four branches on the agreed date, maintain bookings during disruption and keep local managers informed?” Assume the brief allows remote support, the buyer has approved a manual booking procedure and each site has a trained local contact. The people and commitments below are illustrative.
Example answer, ready for an evaluator to read. “By Friday at 15:00 our rollout lead will give your operations lead a readiness record for each branch, including staff cover and the result of a test booking and confirmation. Your operations lead will decide which sites may open on the new system. A shared fault goes to them for a decision covering all four.
“On Monday from 08:30 to 12:30 we will provide a coordinator and two technical staff dedicated to the launch. If Preston cannot take bookings while York can book but confirmations are late, the lead will take Preston. The coordinator will give York’s manager the agreed reference procedure. If York also loses bookings, the deputy will take York and the coordinator will alert your operations lead. Both managers will get an update within 15 minutes of logging their call, including the next update time.
“Before we hand each site to the service desk, its manager will test a booking and a confirmation and reconcile manual entries. We will give your operations lead the result, any open issues and their named owners. The service desk will acknowledge the handover. Our coordinator and technical lead will stay on any unaccepted site beyond 12:30 at the extended-cover rate in our pricing schedule, with the deputy remaining available for a second fault.”

For calls logged at 09:10 that commitment means both managers hear back by 09:25. It promises an update. It gives no restoration deadline. If the tender specifies one, write down how you will meet it, what starts the clock and how service is counted as restored. If a third branch loses service while both technicians are busy, it still needs an owner. Explain who authorises the fallback, how the queue is prioritised and when the coordinator will update that manager. Check the commercial terms before offering a paid extension.
Put the right customer review beside the cover plan
Think about the difference between twelve branches opened on twelve Tuesdays and two branches that needed help on the same Tuesday. The first customer can speak about consistency. The second may be able to tell York what it felt like to be the branch waiting for a call. I’d want that second account beside the launch-day plan.

Fictional review shown above. Sam L., regional operations manager, four out of five stars. “Two branches rang me that morning. York still had to give references out by hand, but at quarter past nine their manager knew who was calling back. I didn’t have to chase it.”
The useful detail is that York still had a problem. Sam could see both branches, knew what the waiting team had to do and could tell the buyer who kept them informed. A ticket log can establish the response time. Sam’s account explains what that time felt like to the people at the counter.
Find the right witness. Ask a customer who saw the overlap what happened at each site, what the waiting branch heard and what remained unresolved. Check the dates and scope against the delivery record. If two managers each saw one branch, keep their accounts separate and get permission for the intended use.
Make that account easy to find. Bring authorised feedback into the EndorseHQ Toolkit and group it under the concern it answers, such as “Two branches need support together”. Keep the customer’s original wording and role. For a web proposal, hand-pick that account in a Singular widget immediately below your cover plan.
Give the panel evidence in the permitted format. If the portal accepts text only and allows quotations, insert the authorised words with attribution in the relevant response. If it asks for a case study or referee, provide the project details or the agreed contact separately. Check the final PDF or portal preview so the evidence survives submission.
When you have no comparable account, say which part of a previous job you can evidence and which part remains untested. Where the tender allows it, offer a rehearsal to test the overlap. If lost-bid feedback says only “preferred a larger supplier”, the EndorseHQ objection mapping guide can help you find out whether the sticking point was staffing, response time or a missing example.
Check the submission and use the buyer’s feedback
Give the answer and the scoring notes to somebody who was never on the sales calls. Ask them three things. Who covers York if Preston has the lead? Who can delay one opening? Where is the cost of the deputy? If they have to ring you, the evaluator may face the same problem.
The government’s guide to writing and checking a bid explains that different evaluators may read different questions. Read each answer on its own, check the word limits and permitted attachments, and allow time to review the submitted version and save the receipt. Scotland’s Supplier Journey also sets out how to raise clarification questions before the buyer’s deadline.
After the decision, keep the mobilisation score and the evaluator’s wording with the bid. Track wins as a share of decided, comparable tenders and record which losses concerned capacity. Keep open tenders separate. EndorseHQ can show views and clicks on a web proposal widget. The score, the debrief and the signed contract tell you more about whether that particular concern was answered.
Multi-site tender response FAQs
What is a tender response and how should I structure it?
A tender response is your formal offer against the buyer’s invitation. Use their question order and response format. For each delivery question, state your commitment, explain the method and responsible people, then give the evidence requested. For a multi-site job, spell out which parts apply everywhere and which change by location, shift or launch date.
What should be included in a contract mobilisation plan?
Include the period from award to acceptance, dates by site, dependencies, staff and deputies, training, customer responsibilities, tests, risks, fallback arrangements and who signs off. Give each milestone an owner and a completion test. Identify the service desk or operational team that will inherit each site and the issues it has agreed to take. Follow any template the buyer provides.
How do I show enough capacity for several sites at the same time?
Use a dated rota and check the busiest shared period. Subtract existing commitments, travel and unavailable staff. Separate on-site cover, technical support and communications. Work through two simultaneous faults, identify the owner for each and show who handles normal work. If you rely on a partner, confirm their dates and price before offering their capacity.
Should I propose a pilot or a phased rollout?
A pilot makes sense when a test site can expose a shared risk before the others start. Explain how you will choose that site, what must pass, who authorises the next wave and what happens if it fails. Check whether the buyer permits variants or alternative dates. If all sites must open together, meet that requirement or seek clarification before presenting a phased option.
How long should a tender response be?
Use the limit attached to the question and check whether the buyer counts headings, tables, diagrams and attachments. Spend the available words on the parts being scored. A short operational answer can be complete if it covers the sites, owners, timings and evidence requested. Where the rules are unclear, ask through the specified channel before the clarification deadline.
Can I use a customer testimonial instead of a case study or reference?
Use the evidence the buyer specifies. A case study sets out the project, your role, the scale and the outcome. A reference allows the buyer to check details directly with a customer who has agreed to take the call. A permitted testimonial can add the customer’s account of a particular incident. Quote it in context and obtain permission for its use in the bid.
How can a small supplier compete for a multi-site contract?
Start with the requirements you can meet on the buyer’s dates. Show the people who are available, how you will cover two problems at once and a comparable incident your customer can describe. If the specification allows lots or delivery partners, work out which arrangement you can staff and price. If a mandatory requirement remains beyond your team, a strong testimonial cannot close that gap.