Skip to content

Rollout resource

Multi-site rollout location tracker

Keep each location’s readiness, visit and validation status distinct. This editable workbook helps project teams see where work stands and who owns the next action.

Free editable Excel trackers, printable guide PDF and full toolkit ZIP. No form required.

Download the working files

Use the blank workbook for your rollout, or inspect the separate fictional 50-site example. The toolkit includes both workbooks, the print guide, and blank and fictional CSV examples for site, visit and action records.

Keep site, visit and action references consistent. Record local dates and times with their time zone. The workbook summary uses the entered records; review the underlying records and checks before reporting the result.

Why a single green status can hide work

“Complete” can mean equipment delivered, installation finished, a test passed or the customer accepted the result. Those events are different. If locations use different definitions, the overall project summary becomes difficult to trust.

Use stable location references and agreed status definitions before the first wave. Keep the evidence behind each update available to the people who need to review it.

What to track for each location

  • Identity and plan: location ID and address, rollout wave and planned visit window.
  • Readiness: ready, blocked or not yet checked, with equipment and access dependencies, owners, due dates and evidence dates.
  • Visit and result: booking status, work carried out, incomplete tasks and the physical result.
  • Validation and review: agreed test status with a reference, plus the customer review or acceptance status required by the project.
  • Next action: remaining issue, responsible person, expected follow-up, completion record and last verified update.

The Excel workbook keeps site, visit and action records in separate sheets, with a summary calculated from your entries. It does not connect to a ticketing system. The PDF is a printable working guide.

Track partial completion within a location

A location may contain several rooms, network cabinets or work packages. When a visit finishes only part of that work, add child records under the site so the next visit can start from the actual result.

Illustrative site → sublocation → work-package records
Site / area / visitWork package and observed stageNext action
Site 014 / rooms A–E / visit 1Phone repairs finished; inbound and outbound checks recorded for these rooms.Reviewer checks the results for the listed rooms.
Site 014 / rooms F–H / visit 1Diagnosis recorded; corrective work remains.Technical owner approves the next work package.
Site 014 / rooms I–K / visit 1Not visited; no test result recorded.Coordinator arranges access and the next visit.
Site 014 / workstation area / visit 2Setup deferred because furniture is unavailable.Site contact confirms readiness before rebooking.

Keep these as illustrative entries, then adapt the structure to your own site list. Give each child record a stable reference, visit date, evidence link and action owner. Preserve the earlier result when another visit is added rather than overwriting the history.

Roll up a site only when the required child work packages meet the project’s definition. A repaired room, a connected cabinet and an unvisited area should not inherit one undifferentiated “complete” status.

Define what the project totals count

Choose the event behind every summary measure. “Locations with physical installation complete” and “locations accepted” can have different totals. Use a consistent denominator and explain how blocked or removed locations affect the planned count.

If a status is based on an assumption, label it and assign the check needed to confirm it. Review exceptions first in project meetings, then look at the trend across waves.

Illustrative record: Site 014 — visit complete; replacement connected; technical validation pending the customer engineer; action owner assigned. It may count as physically installed under the agreed definition. It should not count as validated or accepted.

This is a planning example, not a reported customer rollout.

Use the tracker through each wave

  1. Agree the field definitions, update owners and reporting cadence.
  2. Load the planned locations and check readiness before committing visits.
  3. Record the physical result separately from tests and customer review.
  4. Link evidence and assign each exception to a next action.
  5. Reconcile the summary to the underlying location records before reporting it.

Connect the supporting records

For carrier changes or room installations, define the child work packages using the ISP cutover checklist or conference-room acceptance checklist. Track the agreed checks for each room or site separately from the visit status.

Use the site readiness checklist before scheduling and the completion record for handover. Read the deployment-dashboard guide for how to connect project summaries to work at individual locations.

Browse all planning templates.