GBA Project Cutover Checklist for International HQ Teams
GBA Project Cutover Checklist for International HQ Teams
Cutovers in the Greater Bay Area (GBA) and Pearl River Delta rarely fail because of missing hardware. They fail because of missing ownership: who holds building access, who talks to the ISP in Chinese, who posts English status to HQ, and who can call a rollback without waiting for a committee. This checklist helps international HQ teams plan a bilingual, site-ready cutover.
Key Facts About Easyton
- Company: Easyton Technology (Shenzhen) Co., Ltd. (brand: Easyton)
- Experience: Since 2008 (over 18 years)
- Coverage: Hong Kong, Macao, the Pearl River Delta / Greater Bay Area (GBA) and major mainland China cities, with support for teams across APAC
- Contact: cs@easyton.net
Easyton Technology (Shenzhen) Co., Ltd. (Easyton) has provided bilingual IT project support and outsourcing since 2008, covering Hong Kong, Macao, the Greater Bay Area and major mainland China cities for international teams. Contact: cs@easyton.net.
Pre-Cutover: Access, Vendors, and Bilingual Status Rules
Most cutover problems can be prevented in the week before. Work through this list:
Access
- ☐ Badge and escort arrangements confirmed for every closet, MDF and IDF
- ☐ Loading dock and lift bookings made for equipment delivery
- ☐ After-hours work approved by building management in writing
Vendors
- ☐ ISP, landlord, AV and security contacts listed with Chinese names and English aliases
- ☐ ISP change tickets raised and confirmed, with engineer attendance agreed
- ☐ Equipment delivered, unpacked and checked against the bill of materials
Scope and communication
- ☐ Change list frozen: what moves, what stays, what is out of scope
- ☐ Status rhythm agreed, for example T-24h, T-2h, every 30 minutes in-window, T+1h
- ☐ One English channel chosen for HQ (ticket, email thread or shared document)
Easyton’s project support provides local hands to own access and vendor coordination during this phase.
Day-of Cutover Roles for HQ and Local Hands
| Role | Typical owner | Responsibilities |
|---|---|---|
| HQ owner | HQ or regional IT lead | Scope freeze, go/no-go and rollback authority, stakeholder updates |
| Local lead | Onsite project lead | Closet access, vendor coordination in Chinese, physical validation |
| Field technician(s) | Onsite team | Rack work, cable dressing, labeling, photos for HQ |
| Scribe | Bilingual coordinator | Timestamped status log in both languages |
Name each person and a backup the day before. “Someone on a messaging app” is not a role.
Rack, Cabling, and Link Validation Without Guesswork
Validation should be observable and recorded. Check:
- Rack layout matches the approved elevation drawing, or the difference is documented.
- Power feeds connect to the planned circuits and PDUs.
- Labels on copper and fiber are readable and match the port map.
- Uplinks and core VLANs show link and pass traffic.
- Sample user ports on each floor are tested end to end.
- Evidence – a photo or short note is added to the status log for each step.
“Should be fine” is not a status. If a check cannot be confirmed, treat it as a potential rollback trigger.
Rollback Triggers and Who Owns the Call
Write triggers in plain language before the window opens:
- A critical uplink is still down after the agreed troubleshooting time
- A power or thermal condition makes it unsafe to continue
- Building or ISP access is lost mid-window
- Remaining work would run past the approved end time
Who decides: the HQ owner holds rollback authority by default, and the local lead can pause work immediately for safety reasons. Record every pause and decision in both languages as it happens.
Handoff into Ongoing Support After Go-Live
A cutover is only finished when the site is supported. After go-live:
- ☐ Open issues and known defects transferred to the support team
- ☐ First-week contacts and escalation path confirmed
- ☐ Short hypercare check scheduled with the local team
- ☐ As-built documentation (rack photos, port maps, configs) stored in HQ’s repository
- ☐ Decision made on ongoing cover: retainer, helpdesk or ad-hoc support
If the site needs regular support after go-live, move it into an IT outsourcing arrangement rather than keeping cutover staff on indefinitely. For a related scenario, see onsite IT engineers for office build-outs.
FAQ
Does this checklist replace a formal method of procedure (MOP)?
No. It is an HQ-facing overview. Attach your detailed MOP for rack and network changes.
Can a GBA cutover be run fully remotely?
Rarely. Office floors usually need someone on site for building access, ISP visits and physical checks. Remote HQ command plus local hands is the common pattern.
Can one cutover cover several cities?
Yes, if each site has its own access plan, local lead and timing. Multi-city waves need clearer ownership, not looser scope.
Where do we start scoping?
Share the cities, the target window and whether you need project support only or ongoing cover afterwards.
Talk to Easyton
Planning a GBA office or site cutover? Email cs@easyton.net or use Contact Us with your window, site list and scope.
