PRACTICAL WORK / TOLUWA STEPHEN ADEBAYO
Network rollout & handover pack
A conceptual topology, milestone plan, acceptance tests and operational handover checklist.
Demonstration sample • Synthetic scenario • Prepared with AI assistance for this portfolio; not a client deliverable or a record of a completed incident.
01 / WORK SAMPLE
Plan the delivery around acceptance
Scenario: a fictional three-building office needs a segmented wired/wireless network and voice service. This is an illustrative design, not Harvestfield’s production topology or configuration.
Conceptual design
Two internet providers → approved edge/firewall design → core switching → access switches by building → corporate devices, wireless access and voice endpoints. Separate corporate, guest, voice and management traffic according to approved requirements. Redundancy at one layer does not remove all single points of failure.
Illustrative delivery plan
| Stage | Deliverable | Acceptance gate |
|---|---|---|
| Discover | Survey, requirements, constraints, service dependencies | Business owner approves scope |
| Design | Topology, segmentation, bill of quantities, change plan | Technical review and purchasing approval |
| Prepare | Staging, labelled cabling, configuration backups | Readiness check; access and power confirmed |
| Implement | Agreed cutover and device configuration | Connectivity/security test set passes |
| Handover | Inventory, support guide, backups and training | Operations owner accepts; exceptions assigned |
Dependencies and risks
- Construction works can damage cabling: agree contractor sequencing, protected routes, inspection points and reporting ownership.
- Power or uplink failure can interrupt service: document the resilience boundary and test only the failover features included in the approved design.
- Late equipment can affect milestones: track delivery commitments and identify approved alternatives before changing the design.
- Voice and guest traffic need defined access rules: validate the required paths instead of assuming every VLAN should reach every other VLAN.
Change rule
Document scope, affected users, maintenance window, approvals, current backups, validation steps and rollback trigger before the cutover. Freeze unrelated changes during acceptance testing.
02 / WORK SAMPLE
Prove it works, then transfer ownership
All values and test states below are fictional. The table is an example acceptance register, not measured results from a client network.
Acceptance register
| Test | Expected result | Evidence to capture |
|---|---|---|
| Corporate connectivity | Approved resources reachable | Test device, location and result |
| Guest isolation | Guest cannot reach internal resources | Denied path and approved internet test |
| Voice | Calls complete across required routes | Call test and observed quality |
| Coverage | Agreed work areas meet requirements | Survey notes and measurements |
| Provider failover | Recovery meets agreed criteria | Failure/recovery timing and limitations |
| Recovery | Approved configuration can be restored | Controlled restore-test record |
Handover checklist
- Inventory: device roles, ownership, support entitlement, locations and labelling; keep management addresses restricted.
- Configuration: approved baseline, backup location, version/change history and recovery procedure.
- Operations: monitoring responsibilities, escalation contacts, support windows and maintenance ownership.
- Access: transfer privileged credentials through the approved secret-management system, not this document.
- Acceptance: signed test record, outstanding defects, agreed exceptions, warranty/support arrangements and operations-owner sign-off.
Rollback trigger
If a business-critical connectivity or security test fails and cannot be corrected within the agreed window, revert to the approved previous state where technically feasible. Notify the change owner, preserve the test evidence and agree the next attempt.
Handover summary
“The agreed test set has been reviewed with the operations owner. Any unresolved defects are recorded with an owner and due date. Support documentation and configuration backups have been transferred through approved channels.”