Who takes responsibility when the office is furnished but the internet handoff stops in the building equipment room? Appoint one business-side owner for the IT fit-out, then assign the work between the landlord, fit-out contractor, carrier and IT team. Use the matrix below to expose gaps between their contracts before move-in.
In Riyadh, make the plan specific to the building and premises you are taking. Confirm access arrangements, carrier delivery to the actual unit, installation windows and the people authorized to approve changes. A service available nearby does not establish that your office is ready to receive it.
Start with the occupancy requirements
List the workflows that must work before staff arrive: sign-in, business applications, internet access, calls, meeting rooms, printing and any local systems. Include reception, visiting staff and the people who will provide support.
Translate those workflows into locations on the current floor plan. Mark work areas, meeting rooms, equipment space and intended wireless use. Confirm which equipment uses fixed outlets and where cable pathways must coordinate with ceilings, furniture or other works.
Keep a revision number on the agreed plan. A relocated reception desk can change the outlet and device requirements. A new partition can affect the wireless design. Give the project a process for reviewing those changes before installation teams work from different drawings.
Assign the office IT fit-out responsibilities
The table below is a proposed coordination framework. Actual responsibilities depend on the lease, building arrangements and agreed supplier scopes; replace the suggested leads with the parties assigned to your project.
| Deliverable | Suggested coordination lead | Dependency to resolve | Acceptance evidence |
|---|---|---|---|
| Building access and pathways | Landlord or facilities | Permissions and access windows | Approved access and route plan |
| Equipment area | Facilities with IT input | Space, power and environmental requirements | Joint readiness inspection |
| Carrier handoff | Carrier with business owner | Building access and exact termination point | Working service at the agreed handoff |
| Cabling | Cabling contractor | Approved layout and accessible routes | Labels, test reports and as-built records |
| Switching and wireless | IT integrator | Cabling, equipment space and approved design | Connectivity and access tests |
| User accounts and devices | Internal or global IT | Staff list and approved configuration | Representative user workflow tests |
| Cameras and access systems | Assigned security team | Coverage, cabling and facilities coordination | Approved functional handover |
| Ongoing support | Business owner and support team | Inventory, access and documentation | Accepted support handover |
Example: the carrier is ready, but your office is not
In an illustrative fit-out, the carrier confirms delivery to an agreed building handoff. The office rack is elsewhere, and neither the carrier order nor the cabling proposal includes the remaining connection. “Internet delivered” has therefore left an unassigned task.
Put the exact handoff and rack location on the drawing. Have the carrier and cabling team confirm the interface and permitted route, with building access approved by facilities. Name the party supplying and testing the remaining link. Then test the required service from inside the office.
Sequence the dependency as access approval, route and equipment-area readiness, installation, then end-to-end testing. Put a required-by date beside each stage, based on confirmed supplier information. One move-in deadline copied onto every task will not reveal which delay blocks the next team.
What needs checking before cables are installed?
Agree the required applications, outlet locations, cable specification, termination method and test requirements with the designer and contractor. Include device power and uplink requirements in the network design rather than selecting equipment after the pathways are complete.
Clarify how each installed link will be identified and how its test result will be associated with that identifier. A basic connection check and a certification test answer different questions. Fluke Networks distinguishes verification, qualification and certification in its cable-testing guidance; specify the appropriate acceptance requirement in the contract. Fluke Networks cable-testing overview.
Have facilities and the relevant qualified contractors assess power, cooling and building-work requirements against the selected equipment. The IT team should communicate the equipment needs and confirm readiness, with the responsible trades owning their installation scope.
The network cabling service and IT infrastructure service describe connected parts of this work. In the project schedule, show when each can start and what evidence it must receive from the preceding task.
How should wireless readiness be accepted?
Plan wireless around the people, devices, applications and physical environment. Count simultaneous use in meeting rooms and shared areas as well as the number of desks. A single laptop obtaining a connection is only an initial check.
HPE Aruba's RF-design guidance discusses planning around the physical environment and using site surveys where appropriate. Use the selected design and actual client devices to define the test, rather than assuming a fixed number of access points will fit every office. HPE Aruba RF design guidance.
Test in representative areas after the relevant fit-out work is complete. Check intended staff and guest access separately, including whether restricted resources remain inaccessible to guests. For broader selection questions, see the business Wi-Fi guide.
What must happen before move-in?
Run a coordinated acceptance session with the people who will use and support the office. Test the carrier connection, representative accounts, application access, calls and meeting-room equipment. Include any agreed fallback connection using the workflows that actually matter to the business.
Test interactions between teams. If access to a business application fails, the support contact should know how to distinguish a local connection issue from an account or application fault. Record the escalation route while the implementation team is still available.
Review critical failures before accepting occupancy readiness. A nonessential display adjustment may be left on a completion list; a failure preventing staff from accessing their main application needs a business decision. Give every remaining issue an owner and a closure date. Use a short issue record: affected workflow, observed fault, business impact, approved temporary arrangement, responsible party and retest date. This lets the business owner see what accepting an exception actually means.
What should the handover contain?
Retain the approved drawings, outlet and equipment inventory, relevant test reports, configuration records, warranty details and support contacts. Transfer administrative and recovery access through the business's approved secure process. Verify that authorized staff can retrieve the records when needed.
Arrange a support handover that identifies which provider owns the live connection, network, devices and applications. Remove temporary installation access when it is no longer required, using an agreed sequence that preserves support continuity.
An office is ready when its required workflows work and its operators can support them. Request a Riyadh office IT survey from BustanTech with your latest floor plan, intended occupancy date and contractor responsibilities so the remaining dependencies can be scoped.