Warehouse investment: protecting value after board approval

Protecting a warehouse investment means challenging the decisions that become expensive to reverse, including those made after board approval. Agreeing a specification, approving a layout or accepting a testing plan can commit the business to years of operating consequences.

These decisions deserve attention while the team can still change them. Once construction, software development or installation advances, correcting an omission becomes more disruptive and expensive.

The board may have approved a sound response to a genuine business need. The warehouse needs more capacity, the network no longer fits, or operating costs are limiting growth.

But that approval cannot settle every detail needed to deliver the benefits. Some of the most expensive decisions follow afterwards, disguised as routine project tasks.

How project progress can hide operational risks

Project teams need to maintain momentum. Suppliers need answers, installation dates approach, and site operations managers still have a warehouse to run.

Under that pressure, signing off a document can feel like progress. Leaving a question open can feel like holding everyone up.

The difficulty is recognising which questions need resolving before work continues. A small omission can affect every order, every shift or the site’s ability to expand.

Responsibility also crosses departments. Property teams manage the warehouse agreement, IT manages systems, and suppliers manage their equipment.

The site team eventually has to make everything work together. That is where gaps between responsibilities become operational problems.

Challenge commitments while change remains practical

At Hatmill, our experience through design, implementation and recovery points to one conclusion. Scrutiny should follow the operational and financial consequences of a decision, rather than its apparent size.

That means asking what an approval commits the business to. It also means checking who has tested the proposal against the operation that will inherit it.

The right challenge can prevent rework, expose a capacity constraint or reveal costs missing from the business case. Three examples show how this works in practice.

Warehouse specification omissions

One retailer completed a network review and chose to develop a new warehouse. It then progressed the warehouse specification without specialist support.

Important requirements were missed. These included aspects of yard design, sprinkler systems, loading bay safety, insurer requirements and electrical and mechanical services.

Resolving the omissions through later changes cost more than £2 million. Those costs could have been avoided by including the requirements in the original specification.

The warehouse completion date also slipped by more than a month. That affected warehouse fit-out and the programme for bringing the site into operation.

An experienced operational review would connect the specification with how the warehouse needs to work. Does the yard provide enough space for vehicles to circulate, manoeuvre and access loading bays safely and efficiently?

Do the loading bays suit the trailers and handling equipment? Can fit-out teams access the site when they need to start work?

These questions need property, engineering and operational input before agreement. Otherwise, the business can find itself paying for requirements it needed from the outset.

Unresolved systems integration

Another programme combined automated vehicles, storage equipment and conveyors. Requirements were incomplete, and teams had not fully resolved how the different systems would work together.

The problems became clear during delivery. Significant rework followed, including more than 50 software development sprints to address technical issues.

Work on this scale can consume hundreds of hours of technical resource. Contractor and software vendor days add further costs.

Hatmill joined to help recover the programme, clarify requirements and responsibilities, and support implementation and testing. Several weaknesses contributed, so attributing everything to one missed decision would be misleading.

However, the practical challenge is straightforward. Someone needs to check how work passes between systems and what happens when that process fails.

An order might leave the warehouse management system but fail to reach the automation. A pallet movement might stop before the stock reaches its destination.

Who spots the problem? Who restarts the work and confirms where the stock actually is?

Without clear answers, warehouse colleagues inherit the gaps. They chase missing work, correct stock files and find ways to keep orders moving.

That can mean low productivity, overtime and more agency staff to clear backlogs. Customers experience late orders and unreliable service.

If those conditions persist, morale can fall and staff turnover can rise. Recruitment, training and the loss of experienced colleagues extend the cost beyond the original technical problem.

Autonomous mobile robot deployments

In one autonomous mobile robot implementation, pickers spent 36% of their time waiting for the next frame. Retail order picking achieved only 48% of the required peak volume.

The difficulties included an inadequate specification, poorly configured product flow and gaps in testing and project management. Additional support costs followed, while store replenishment and customer orders suffered delays.

Across other AMR deployments, we have seen products fall from shelving and block robots. Adding banding kept products in place but slowed replenishment.

Other problems have included floor joints damaging wheels, congestion blocking routes, and cages moving after set-down so robots could not collect them.

These examples show how equipment, automation, software and the warehouse’s physical infrastructure affect end-to-end material flow. A robot completing its journey does not prove that a picker receives stock quickly enough.

Nor does it prove that replenishment can keep pace or completed orders reach despatch on time. Performance depends on the slowest part of the complete process.

The practical response is to trial representative products, cages and workloads. Involve the colleagues who will pick, replenish and recover the operation when something stops.

Watch where people wait, where stock builds up and what needs manual intervention. Resolve those constraints before repeating the arrangement across the site.

What investment sponsors need to consider

Every review consumes time, and unnecessary delay has a cost. Leaders need proportionate challenge focused on decisions that could materially affect cost, capacity, service or future flexibility.

That requires explicit ownership. A supplier checking its equipment and IT checking its systems does not establish who checks the complete operation.

It also requires dedicated resource. Reviewing a major warehouse transformation alongside a full-time job can place impossible demands on the people involved.

If site managers need time for design reviews and testing, decide who covers their operational responsibilities. Otherwise, today’s service pressures will keep displacing tomorrow’s preparation.

Testing needs the same discipline. Equipment moving pallets at the specified rate does not prove the warehouse can receive, replenish, pick and despatch the required volume.

Agree what the complete operation must demonstrate, including busy periods and recovery from interruptions. That gives leaders evidence against the business case before accepting the solution.

Questions before the next approval

Before the next significant approval, ask:

• Which business requirement does this decision protect, and have we checked it against future demand as well as today?
• What becomes expensive to change after approval, and what would happen if our assumptions prove wrong?
• Who has checked the complete warehouse process, including the points where departmental and supplier responsibilities meet?
• What evidence proves the proposal works under representative workloads, and which failure or recovery scenarios remain untested?
• Who owns the decision, who will challenge it, and have we given them enough time and relevant expertise?

Examine three decisions approaching approval

At the next project review, identify three upcoming decisions that would be expensive to reverse. Name who will challenge each and what evidence they need before sign-off.

That expertise may sit within the business or come from an external practitioner. It needs to connect project detail with operating reality and stay involved as the team implements the answer.

A sound investment decision establishes the direction. Protecting its value requires the same care when the decisions appear mundane.

Planning a new warehouse or implementing automation? Hatmill can help review requirements, challenge operational assumptions and support implementation and testing. Talk to our team about the decisions approaching approval and the evidence needed to protect your investment.