Signing a colocation contract feels like the end of the procurement exercise. It is closer to the middle. Between signature and a cabinet carrying production load sits a provisioning sequence with a dozen dependencies, several of which involve third parties, and most delays happen here rather than in the negotiation.
The sequence is not difficult. It is simply unfamiliar to teams whose previous deployments were in a building they already occupied. This guide covers what happens in those weeks and where the schedule usually slips.
What the provider does first
Once the contract is executed, the provider allocates your actual space. Until that point you have bought a quantity of cabinets or an area, not specific positions on the floor. Allocation determines your cabinet locations, your power feed routing and your distance from the meet-me room, all of which matter later.
In parallel they provision power. Circuits are run to your cabinets at the contracted capacity and configuration, which for most deployments means dual feeds from separate paths. This is physical electrical work and it has a lead time; it is not a switch somebody flips.
They also create your account in their systems: ticketing, access control, monitoring portal and billing. These are usually quick but they gate everything you do afterward, so chase them early.
Access: the step that delays more deployments than any other
You cannot rack equipment in a facility you cannot enter, and data center access control is deliberately slow.
Each individual who will enter needs to be registered, typically with government identification, and in many facilities with a background check. In the UAE this frequently involves documentation that takes time to assemble for staff who are not local residents. Biometric enrollment usually requires the person to attend in person, which cannot be done in advance remotely.
Then there is the authorization structure. Someone on your side must be designated as able to approve access for others, and that designation itself requires verification. Teams routinely discover at the loading dock that the engineer who flew in is not on the list and the person who can add them is asleep in another time zone.
The practical mitigations are simple and rarely done. Submit the access list the day the contract is signed rather than the week before deployment. Register more people than you think you need, including at least two who can authorize others. Confirm in writing what identification each person must physically carry on the day. And establish the escort policy for unregistered visitors, because contractors and vendors will need to attend at some point.
Getting equipment to the building
Hardware delivery is where schedules meet physical reality.
Most facilities require advance notice of deliveries, often with a specific window, and will refuse shipments that arrive unannounced. Many have loading dock constraints on vehicle size. Some have no dock at all and require ground-level delivery with a tail lift.
Receiving policy varies more than people expect. Some providers accept and store shipments for you, sometimes for a fee and usually for a limited period. Others will not sign for anything, meaning somebody from your team must be physically present when the truck arrives. That distinction changes your travel plans and is worth confirming in writing.
Staging space is the related question. Unpacking servers generates a surprising volume of cardboard and foam, and halls generally prohibit packaging material for fire-load reasons. If there is no staging room, you are unboxing on a loading dock, which is slower and weather-dependent.
For deployments importing hardware into the UAE, customs clearance sits upstream of all of this and is the longest pole. Our guide to importing mining and AI hardware into the UAE covers that process; the point to carry into onboarding planning is that the delivery date you give the facility should be the date goods clear, not the date they ship.
Connectivity
Cross connects link your cabinets to carriers, to other tenants or to the provider's own network. Each one is ordered individually, provisioned by the facility, and takes time.
Two details catch people out. First, a cross connect to a carrier requires the carrier to have a presence in that building and to accept the order, so you are dependent on a third party's lead time rather than the facility's. Second, you need to specify the physical media and connector type, and getting it wrong means a return visit.
Order connectivity before equipment arrives rather than after. A rack of servers with no path off the floor is an expensive paperweight, and the cross connect is frequently the longest lead item after customs.
If you are running your own structured cabling inside a cage or suite, that work also needs scheduling, and our guide to structured cabling standards covers the conventions worth following.
The installation window
With access granted, equipment on site and power live, the installation itself is usually the quickest phase. A few practices make it quicker still.
Produce a rack elevation before you arrive, showing which unit each device occupies. Deciding this on the floor wastes hours and produces layouts nobody can document afterward. Label everything as it is installed, because labeling retroactively never happens. Photograph the front and rear of each cabinet when complete; this documentation is worth more than it costs at the time of the first remote troubleshooting call.
Test both power feeds independently. Dual-fed equipment that is actually running on one path is a failure waiting for the next maintenance window, and it is invisible unless you deliberately check. Confirm every device is reachable on the management network before anyone leaves the building, as covered in our guide to rack and stack deployment.
Documentation nobody writes until they need it
A deployment generates a set of facts that exist only in the heads of the people who were there, and those people are frequently contractors or colleagues who change roles.
Four records repay the effort of writing them down during the installation rather than afterward. A rack elevation showing what sits in which unit, kept current as equipment changes. A cabling schedule recording every connection with both endpoints and the port identifiers. A power mapping showing which device draws from which feed and which circuit, which is the document you will want during an unplanned maintenance event. And an asset list with serial numbers tied to physical locations, which is what makes a warranty claim or an insurance claim tractable.
None of this is glamorous and all of it is faster to capture while the cabinet doors are open. The test of whether it is good enough is simple: could somebody who has never visited the site direct a remote hands technician to the correct device, on the correct feed, without guessing?
Who needs to be involved on your side
Onboarding stalls as often on internal gaps as on provider ones, because the work spans teams that do not usually coordinate.
Procurement owns the contract and is frequently the only party with the executed terms, including what was actually committed on power and space. Someone technical has to own the rack elevation and the connectivity design. Security or compliance may need to approve the access arrangements and review the provider's controls. Logistics owns shipping and customs. And somebody has to be designated as the authorized contact who can approve access and raise tickets, which is an administrative role people forget to assign until it blocks something.
Name those owners at contract signature. The most common failure is not that a step was hard but that nobody believed it was theirs.
Handover
The transition from project to steady state is the part most often skipped, and it is where operational problems originate.
Confirm the support path in practice rather than in the contract: how tickets are raised, what the response commitments are, and how an emergency is escalated outside business hours. Establish the remote hands arrangement, including what is included and what is billed, which our guide to remote hands and smart hands services covers in detail.
Verify your monitoring portal shows real data for your cabinets, including power draw per feed. Confirm the maintenance notification process and who on your side receives it. And check that billing reflects what was actually provisioned, because the first invoice is the easiest moment to correct a discrepancy.
A realistic schedule
The common error is planning backward from a go-live date on the assumption that provisioning is administrative. It is not; much of it is physical work and third-party dependency.
Treat access registration, customs clearance and cross connect provisioning as the three long poles, start all three the week the contract is signed, and sequence equipment delivery to arrive after access is confirmed rather than before. Teams that do this deploy in weeks. Teams that do not spend those same weeks waiting at a reception desk.
Rax Data and Energy handles onboarding for colocation and GPU hosting tenants across our UAE facilities, and we would rather walk through the sequence with you before the contract than troubleshoot it afterward. Get in touch to talk through a deployment timeline, or see our colocation buyer's checklist if you are still at the selection stage.
Frequently Asked Questions
How long does colocation onboarding usually take?
It varies with the deployment, but the schedule is set by three long-lead items rather than by the installation itself: access registration and background checks for your staff, customs clearance if hardware is being imported, and cross connect provisioning, which depends on the carrier rather than the facility. Starting all three the week the contract is signed is what separates a deployment measured in weeks from one measured in months.
What most commonly delays a colocation deployment?
Physical access. Each person entering must be registered, often with identification and a background check, and biometric enrollment usually requires attending in person. Teams regularly arrive to find an engineer is not on the access list and the person authorized to add them is unavailable. Submitting the access list at contract signature, and registering more people than you expect to need, avoids most of it.
Will the data center receive and store my equipment before I arrive?
It depends entirely on the provider. Some accept and store shipments, often for a fee and for a limited period. Others will not sign for anything, which means somebody from your team must be present when the truck arrives. Confirm this in writing before scheduling delivery, because it determines your travel plans and whether hardware can arrive ahead of your engineers.
Should I order cross connects before or after installing equipment?
Before. A cross connect requires the carrier to have a presence in the building and to accept the order, so the lead time belongs to a third party rather than to the facility. Equipment racked with no path off the floor cannot be commissioned. Order connectivity as early as the space allocation allows, and specify the physical media and connector type precisely to avoid a return visit.
A Real Energisation Date, Not a Brochure
Rax operates where transmission investment has run ahead of load, and we are direct about staged capacity and real dates. Talk to our team about sizing a deployment against a timeline.
Contact Rax Data & Energy