A multi-site IT rollout fails in the gaps between sites: a task done in one office and forgotten in another, an approval lost in a chat thread, a change nobody logged. Tracking the rollout as structured work, with one record per site, task and change, keeps every office on the same plan. This page shows the model we use in KPODATA.
The tracking model
Every rollout is broken into four record types:
- Sites: one record per location, with its contacts, access details and readiness status
- Tasks: each unit of work, assigned to an owner, with a due date and a site
- Approvals: sign-offs for access, downtime windows and go-live decisions
- Changes: anything that differs from the plan, with impact, risk and rollback noted
Nothing lives only in email or chat. If it matters to the rollout, it is a record with an owner and a status.
A sample week across three sites
| Site | Done this week | Blocked | Next |
|---|---|---|---|
| Singapore HQ | Network handover, 40 devices imaged | None | Server migration |
| Regional office | Line installed | Awaiting landlord access | Network build |
| Remote site | Survey complete | Hardware in transit | Device staging |
A view like this is a filter over the records, not a report someone writes. Anyone with access sees the same state at the same time.
Why structured tracking beats status meetings
Status meetings reconstruct the week from memory. Structured records show it directly: which tasks closed, which approvals are pending, which changes were accepted. Escalation is a filter for blocked items, not a special process.
Who runs it
KPODATA is built and operated by Global ITN. Rollouts like this are delivered by Global ITN’s system integration team across Singapore and the APAC region, using the same records the client sees.
Common questions
Do clients see the same records?
Yes. Clients get their own access to the same sites, tasks and approvals.
Does this replace our project manager?
No. It gives the project manager, on either side, one version of the truth to work from.
What happens after handover?
The same records move into ongoing support, so the managed service starts with full history.
