Move Scenarios and Scope Definition

2.1 One-to-One Moves: Replicating the Current Operating Model

A one-to-one move is the simplest scenario to describe and often the easiest to underestimate. In this model, the company intends to move the current operation from one facility to another with limited changes to the operating model. The same products are made, the same services are provided, the same customers are served, and the same core processes continue. The new site is expected to become the functional replacement for the old site.

The central question in a one-to-one move is whether the organization is truly replicating the current operation or simply using that language to reduce perceived complexity. Leaders often say, “We are just moving,” but the project may include a new warehouse layout, updated office neighborhoods, different utility connections, revised shipping lanes, new security procedures, changed shift start times, reconfigured equipment, and new system master data. Those are not necessarily bad changes. But they must be named, planned, and tested.

The advantage of a one-to-one move is that the existing operation provides a strong baseline. Current process maps, staffing levels, equipment lists, production schedules, shipping volumes, quality procedures, maintenance routines, and customer requirements become the starting point. The team does not need to invent a new operating model from scratch. It needs to translate the current operating model into the new physical environment.

The risk is that current-state knowledge is incomplete. Many mature facilities operate through informal routines that are not fully documented. Operators know which machine warms up slowly, which dock is best for a carrier, which inventory needs separation, which customer requires special labeling, or which utility panel feeds a critical machine. A one-to-one move can fail when the team documents official processes but misses the practical knowledge that makes the site run.

For that reason, one-to-one moves require disciplined baseline capture. The team should walk the current site with supervisors, operators, maintenance technicians, material handlers, quality personnel, safety leads, IT support, and administrative staff. The objective is not only to list assets, but to understand how work actually moves through the facility, including material, people, information, waste, vehicle, visitor, and exception flows.

A one-to-one move also requires a clear standard for replication. Exact replication: the company intends to preserve current process sequence, staffing logic, equipment configuration, and service model as much as the new site allows. Functional replication: the company intends to produce the same outputs and service levels, but layout, workflows, and support routines may change. Improved replication: the company intends to use the move to fix known pain points while keeping the core operating model intact. Each version implies a different level of design, training, testing, and change management.

The move mandate should make the replication standard explicit. If the new site is treated as an opportunity to redesign the operation, the project needs time and resources for design decisions. If the business objective is speed and continuity, the team should resist unnecessary changes that create startup risk. The more the team changes during the move, the less it should describe the project as a simple relocation.

2.2 Consolidation Moves: Merging Two or More Facilities Into One

A consolidation move combines two or more existing facilities into one destination. It may involve manufacturing plants, warehouses, distribution centers, field offices, laboratories, repair centers, corporate locations, or shared service teams. The business case is often compelling: lower fixed cost, better utilization, simplified leadership, reduced inventory, improved service coverage, or a more scalable operating model. The execution risk is equally real, because consolidation is not only a physical move. It is an integration.

The defining feature of a consolidation is that different ways of working must become one way of working. Two warehouses may use different receiving practices, slotting rules, cycle-count routines, labor standards, carrier schedules, or packaging procedures. Two plants may have different maintenance philosophies, quality documentation, training methods, safety cultures, supplier relationships, and production sequencing habits. Two offices may have different decision cadences, reporting lines, employee expectations, and technology setups. The facility move exposes these differences and forces decisions that may have been avoidable when each site operated independently.

The first scope question in a consolidation is what operating model will govern the combined facility. The answer should not default to the largest site, the acquired site, the site with the loudest leader, or the process that happens to be easiest to move. Leaders should decide deliberately which practices become the future standard, which practices are retired, and which practices remain differentiated because the business has a real need for variation.

Consolidations also require careful volume and capacity modeling. Combining two sites does not mean simply adding their square footage, headcount, or equipment lists. Some processes may overlap. Some support functions may be shared. Some storage may be reduced if inventory pools are combined. Other requirements may increase because the new site must handle more peaks, more complexity, more inbound traffic, more outbound destinations, or more employee parking. A consolidation plan must convert current volumes into future operating requirements, not just copy each site’s footprint.

People’s risk is especially high in consolidation moves. Employees from different sites may compete for roles, question the fairness of decisions, resist new routines, or face longer commutes. Leaders may assume that “best practice” will be obvious, but employees often view legacy practices as part of their identity. The scope definition should therefore include which teams relocate, which roles remain, which leadership positions change, and which shift patterns and reporting relationships apply.

Systems and data scope can also be larger than expected. Even when sites use the same enterprise systems, they may have different location codes, storage rules, item masters, routings, customer ship-from logic, tax settings, cost centers, permissions, label formats, EDI connections, reporting views, or inventory ownership rules. Consolidation creates a master data integration project. If this work is not scoped early, the move may be physically complete while the business still struggles to transact cleanly.

A strong consolidation scope statement should describe the future facility as a new operating entity, not merely as a larger version of one legacy site. It should name the sites included, the activities transferring from each, the practices being standardized, the volume assumptions, the workforce implications, the systems changes, and when each legacy site’s role will end or change.

2.3 Absorption Moves: Moving Operations Into an Existing Facility

An absorption move occurs when an existing facility takes on operations from another site. Unlike a consolidation into a new or largely empty destination, the receiving site already has an operating rhythm. It has daily production or service commitments, active employees, established space usage, current leadership routines, existing constraints, and its own performance targets. The move team is not only starting up new activity; it is modifying a live operation.

This makes absorption moves deceptively difficult. The receiving facility may appear to have enough space on a drawing, but practical capacity may be constrained by dock doors, staging lanes, aisle congestion, floor loading, electrical service, supervisor coverage, maintenance capacity, quality release timing, wastewater limits, parking, meeting rooms, training capacity, or fire-code restrictions. The facility may be able to absorb the work eventually, but not without enabling changes.

The scope definition for an absorption move must therefore begin with the receiving site’s true capacity. The team should assess not only square footage, but bottlenecks and operating constraints. A plant near capacity on the first shift may need a second shift before it can absorb transferred equipment. A distribution center with unused racking may still lack dock capacity for higher outbound volume. An office may have open desks but insufficient collaboration rooms, badge access, or neighborhood capacity for teams that need to work together.

The second question is whether the incoming operation will remain distinct or become integrated. Hosted operation: the receiving site provides space and support, but the incoming activity keeps its own procedures, leadership, metrics, and staffing model. Integrated operation: the incoming work becomes part of the receiving site’s operating system. Transitional operation: the incoming work remains distinct for a defined period before full integration. Each option has consequences for quality, supervision, training, systems, cost allocation, and performance management.

Absorption moves also create priority conflicts. The receiving site leadership may be judged on current performance while being asked to support project work, construction, equipment installation, training, and startup. Without explicit capacity relief, local leaders may protect today’s operation at the expense of move readiness. Conversely, the project team may push move milestones without respecting the receiving site’s live constraints. The mandate must define who arbitrates these conflicts and how decisions are escalated.

In many absorption moves, the old site depends on the receiving site before the move is complete. For example, the receiving site may need to train incoming employees, produce pilot batches, receive transferred inventory, host duplicate equipment, or support customer transition testing. These pre-cutover activities consume space and management attention before the receiving site has officially taken over the work. They should be part of the scope, not treated as informal support.

A well-scoped absorption move makes the receiving site whole. It identifies what work is coming in, what current work must be protected, what enabling changes are required, what temporary disruption is acceptable, what leadership capacity is needed, and how the incoming operation will be governed. The receiving site cannot be treated as a passive container. It is an active operating system that must be prepared for new complexity.

2.4 Split Moves: Transferring Some Activities While Shutting Down or Retaining Others

A split move occurs when only part of an existing facility’s activity moves to the new site. Some operations may transfer, while others remain, shut down, outsource, move to another facility, or continue temporarily before later exit. Split moves are common when a company is redesigning its network, exiting a product line, separating manufacturing from distribution, relocating corporate functions, transferring regulated work, or changing its make-versus-buy strategy.

Split moves are complex because the existing facility is not treated as one indivisible unit. Instead, the team must understand the internal dependencies among processes, assets, people, systems, certifications, records, suppliers, and customers. A process that appears separate on an organization chart may depend on shared utilities, shared quality staff, shared maintenance technicians, shared storage, shared cleaning procedures, shared IT infrastructure, shared permits, or shared customer service teams.

The most dangerous assumption in a split move is that activities can be separated because they have different names. A warehouse function may be moved while light assembly remains, but both may use the same inventory system, dock schedule, forklift fleet, supervisors, cycle counters, and hazardous materials storage. A production line may shut down while another line moves, but both may rely on common compressed air, wastewater treatment, spare parts, batch records, or environmental permits.

A split move requires dependency mapping before timeline planning. The team should identify what each activity needs in order to operate independently. This includes people, equipment, space, utilities, systems, data, quality approvals, documentation, suppliers, customers, records, licenses, and management routines. The team should then determine whether those dependencies will be duplicated, transferred, replaced, shared temporarily, or retired.

Shutdown scope is often underdefined. If some activities are ending, the move plan must include asset disposition, inventory runout, customer communication, supplier termination, employee transition, contract closeout, records retention, environmental cleanup, waste disposal, permit closure, security changes, and landlord handback obligations. Shutting down a process is not the absence of work. It is a workstream.

Retained scope is equally important. If part of the old facility remains operational, the team must define its future operating model after the move. Will it keep the same leadership? Will it still have enough maintenance, quality, IT, HR, safety, and administrative support? Will its cost structure change when shared overhead leaves? Will it retain required permits, storage areas, docks, utilities, and emergency systems? A facility that remains open after losing part of its operation may become more fragile unless it is redesigned for its smaller role.

Split moves also create sequencing risk. The project may need to move one process before another can be shut down, shut down one process before space becomes available, or retain a shared function until the new site is stabilized. These dependencies make a simple move calendar misleading. The plan should include decision gates tied to operational readiness, not just dates.

A strong split-move scope statement specifies the disposition of every major activity. Transfer: activity moves to the new site. Retain: activity stays at the current site. Shutdown: activity ends. Outsource: activity moves to a third party. Defer: activity continues temporarily and moves or ends later. Reassign: activity moves to another company facility. This logic should be applied to processes, products, assets, people, records, systems, and external relationships.

2.5 Scope Definition Checklist

The purpose of scope definition is to remove ambiguity before detailed planning begins. The move team does not need perfect answers to every question on day one, but it does need a structured way to identify what is known, what is assumed, and what remains undecided. The checklist below can be used during the charter phase, the first steering committee discussion, or the launch of the facility move PMO.

Facility Move Scope Definition Checklist

• Move scenario: Identify whether the move is one-to-one, consolidation, absorption, split, shutdown, expansion, or hybrid.
• Current sites: List every facility affected, including sites that will transfer work, receive work, retain work, or close.
• Destination site: Define the selected site’s intended role and whether it is new, existing, leased, owned, shared, or temporary.
• Business rationale: State why the move is happening and what business outcome it must deliver.
• In-scope processes: Identify production, storage, distribution, office, support, administrative, customer-facing, and compliance processes included.
• Out-of-scope processes: Identify processes that will remain, shut down, outsource, defer, or move elsewhere.
• Products and services: List product families, SKUs, programs, customers, services, or business units affected.
• Assets: Classify equipment, tools, racking, furniture, technology, inventory, records, fixtures, and vehicles as move, replace, retain, sell, scrap, or dispose.
• People: Define which roles transfer, which roles are hired, which roles remain, and which roles are eliminated or redesigned.
• Systems and data: Identify applications, master data, reporting, integrations, user access, labels, addresses, tax settings, and transaction rules requiring change.
• Suppliers and service providers: Identify vendors, carriers, contractors, utilities, outsourced partners, maintenance providers, and services affected.
• Customers and external users: Identify customers, distributors, visitors, drivers, auditors, regulators, and others that need communication or transition support.
• Permits and certifications: Identify licenses, inspections, quality approvals, environmental permits, regulatory registrations, insurance requirements, and landlord approvals.
• Operating changes: Document changes to layout, flows, shift patterns, procedures, staffing model, service model, governance, and performance routines.
• Transition state: Define how the business will operate during the move, including duplicate operations, inventory buffers, temporary storage, phased cutovers, and customer exceptions.
• Success measures: Identify the metrics that will determine whether the move has succeeded during transition and after stabilization.
• Open decisions: List unresolved scope questions, decision owners, required analysis, and decision deadlines.

The checklist should be converted into a live scope register. Each item should have an owner, current status, decision date, and impact on cost, timing, risk, and readiness. Scope definition is not a one-time workshop. It should continue as site assessments, layout design, utility reviews, workforce planning, and customer transition work reveal new facts.

The most useful scope register distinguishes facts from assumptions. A fact is verified: the equipment exists, the permit is required, the customer uses a specific pickup process, or the receiving site has a known dock constraint.