A data center shell provides a defined building envelope and agreed base improvements. A fully fitted facility includes a much larger portion of the systems needed for operation. Neither description has a universal contractual scope, so an owner should compare responsibility schedules rather than relying on the label.
A shell agreement might include structure, roofing, site access, and certain utility provisions while leaving electrical distribution, cooling equipment, controls, and customer areas for later work. Another offer could include equipment yards or selected plant. The differences affect both the price and the time required before computing equipment can operate.
Create a handover matrix organized by system. For each item, state who designs it, purchases it, installs it, connects it, tests it, and maintains it. Include penetrations, supports, utility connections, control wiring, meters, and replacement access. Small items at package boundaries are easy to omit because each contractor assumes another party supplies them.
Then define the acceptance condition. Weather-tight completion, utility energization, successful equipment startup, and demonstrated operation under agreed test scenarios are separate milestones. A customer moving into a shell needs a clear understanding of the unfinished work and the restrictions that may affect fit-out.
For pricing, request a common scope basis with explicit exclusions. A cheaper shell can be the appropriate choice for an experienced operator with a specific technical standard, but it is not inherently cheaper after fit-out. Compare the total path to the intended operating condition, including coordination and temporary facilities.