The Factory Is Not a Collection of Departments

The Factory Is Not a Collection of Departments

Why Manufacturing Problems Often Begin at the Handoffs

A production machine stops during a shift. The operator informs the supervisor. Maintenance is called to inspect the equipment. A replacement part may be needed, so stores requires the correct specification. Production needs to know when the machine can be released. Safety needs to understand the work scope and controls required before anyone intervenes.

Each department has a role. Each may complete its own task correctly. Yet the machine remains unavailable because information, decisions and responsibilities have not moved together.

The factory is organised into departments, but the work does not stay inside them.

Departments may own functions. Work moves across boundaries.

Many operational problems begin where one team passes information, responsibility or an unfinished task to another. Understanding these handoffs is essential to keeping work safe, coordinated and continuous.

1. Departments Are Separate. Factory Work Is Connected.

Production, maintenance, engineering, quality, stores and safety exist for good reasons. Each function develops specialist knowledge, procedures and responsibilities.

But a production issue may require maintenance support. Maintenance may need engineering information, a spare part and access approval. Quality may need to assess affected product. Safety may need to confirm controls for the intervention.

The work is connected even when the organisation chart is not.

A department can complete its own part while the overall task remains stuck. A maintenance request may be raised without the equipment details needed to act. Stores may receive a part request that needs clarification. Production may be ready to release the machine, but the work status has not been confirmed.

The gap is not necessarily inside any one department. It is in the transfer between them.

2. A Handoff Is an Operational Event

A handoff is more than sending an email, updating a spreadsheet or changing the name of the person responsible. It is the point at which another person or team receives enough information and authority to continue the work.

The UK Health and Safety Executive describes handover as important whenever a task and its responsibilities pass to another person or team, including between operations and maintenance. It identifies preparation by the outgoing team, direct information exchange and cross-checking by the incoming team as elements of an effective handover.

HSE guidance on shift handover.

A useful handoff should make clear:

• What has happened so far?
• What is the current condition?
• What remains to be done?
• Which information and controls apply?
• Who owns the next step?
• How will the receiving person confirm understanding?

If these questions remain unanswered, the handoff may be recorded without being complete.

A task is not transferred simply because a message has been sent. It is transferred when the next person can take it forward.

3. Where Handoffs Lose Continuity

Handoffs can weaken in several ways. Often, these are small gaps that accumulate across a task.

Information changes form. An operator explains a problem verbally, a supervisor enters a short description in a work order, maintenance interprets it, and stores receives a part request. Detail from the original observation can be lost at each transfer.

Ownership becomes unclear. One team assumes another will take the next action. The issue remains visible, but no one is clearly responsible for moving it forward.

Timing does not match. A change is communicated after the next team has started work, or an approval arrives after the production window has passed.

Priorities conflict. Production needs the asset back quickly. Maintenance needs time to inspect and repair it. Safety requires controls. Quality may need to assess affected material. Each concern is legitimate, but the sequence must be coordinated.

The operating condition changes. The machine, material or work scope changes after the plan is prepared. The next team receives an instruction that no longer reflects the current situation.

These gaps may appear to be communication problems. Sometimes they are. But the deeper question is whether the operating arrangement makes the right information, responsibility and decision available at the right point.

4. Handoffs Are Also Safety Boundaries

When work crosses teams, the information being transferred may include hazards, energy sources, permits, operating limits, access restrictions and emergency arrangements.

This becomes especially important when contractors or external service providers work inside a plant. The host organisation may understand its own hazards and controls, while a contractor may bring a different work method, equipment or team.

OSHA guidance on communication and coordination between host employers and contractors emphasises exchanging information about site hazards, control measures, responsibilities and emergency arrangements, and updating that information when conditions change.

OSHA communication and coordination guidance.

A form or permit alone does not guarantee safe coordination. The people involved need a shared understanding of the work, the hazards, the controls and who is responsible for each part.

A permit, isolation procedure or risk assessment should support coordination—not become a document passed around without a clear understanding of the conditions it covers.

5. What Makes a Handoff Work?

A reliable handoff does not require every detail to be repeated in every system. It requires the right information to travel with the task.

Clear status: The receiving team should know whether work is planned, in progress, waiting, stopped or complete.

Relevant context: Equipment identity, current condition, work scope, known hazards and recent changes should be available.

Named ownership: The person or team responsible for the next action should be clear.

Decision and confirmation: The receiving team should know what it can decide, what needs approval, and how to confirm understanding.

Closure and feedback: Completion should be communicated to affected teams. Relevant changes or findings should reach the people who need them.

A handoff is effective when it preserves continuity—not merely when a record is updated.

6. People, Machines and Processes Meet at the Handoffs

The relationship between People, Machines and Processes becomes especially visible when work moves between departments.

People carry observations, skills, decisions and responsibilities. Machines have conditions, configurations, constraints and hazards. Processes define how tasks are requested, approved, performed and returned to operation. Information connects these elements, but it can lose meaning when it moves between teams.

This is where the BRIGS solution areas have different roles.

Factory U/X helps make the workplace and its information easier to understand. Equipment identification, visual communication, wayfinding and point-of-work information can help people recognise what they are handling and what is expected.

Factory O/S supports the coordination of information and workflows. Digital SOPs and maintenance activities, permits, audits and action tracking can help keep relevant details and responsibilities connected to the task.

M/P Safety addresses machine and process risks through appropriate assessment and controls. Handoffs involving hazardous work must preserve the information needed to apply those controls correctly.

These areas support the operating conditions in which teams coordinate their work. They do not replace clear accountability or sound management.

7. Diagnose the Handoff Before Adding Another System

When a task repeatedly gets delayed between departments, the first response is often to add another meeting, form, approval or notification. But adding steps without understanding the handoff can make work slower while leaving the original gap untouched.

Start by following one recurring task from the first request to completion. Speak with the people who send and receive it. Compare the expected workflow with the way it is actually performed.

Ask:

1. What information is created at the start, and what does the next team need?
2. Where does responsibility change?
3. At which point does work wait, get repeated or require clarification?
4. What happens when equipment or operating conditions change?
5. How does the receiving team confirm the handoff is complete?
6. Who needs to know when the task is finished or the standard has changed?

The aim is to identify the break in continuity before deciding whether the answer is clearer visual information, a revised workflow, a defined responsibility, an engineering control or a digital tool.

8. The BRIGS Approach: Improve the Connections Around Work

BRIGS approaches handoff problems by understanding how people, machines, processes and information interact in the real workplace.

SEE how the task moves between teams.

CONNECT the functions involved and understand what each needs to receive and pass forward.

DIAGNOSE where continuity is lost—through information, ownership, timing, usability, equipment condition or safety control.

DESIGN an intervention that addresses the actual handoff.

IMPLEMENT it within the workplace and the teams that use it.

IMPROVE by checking whether the task now moves more clearly and whether the change has created a difficulty elsewhere.

The intervention may be visual, digital, procedural, engineering-based or a combination. The right choice depends on the conditions observed.

9. Keep the Work Connected

Departments are necessary. Specialisation and clear functional responsibility are necessary too. But none of these should prevent the factory from operating as one connected workplace.

A task should not lose its context when it moves from production to maintenance, from maintenance to stores, or from one shift to another. Safety information should reach everyone whose work may be affected. Decisions should have clear ownership. Completion should be communicated to the people who depend on it.

The real test is not whether every department has its own system.

It is whether the factory can carry work, information and responsibility across departmental boundaries without losing continuity.

At BRIGS, that is where the focus begins: understanding the handoffs, identifying what breaks down between teams and designing practical improvements around the way work actually moves.

A factory may be organised by departments.

Its work must operate as one connected system.