Manufacturing Shift Handover Best Practices: Excel vs MES vs Custom

The notebook gets passed. Half the notes are illegible. The incoming shift leader spends 20 minutes tracking down the previous lead on WhatsApp to ask what "check pump 3 issue" actually means.

At a 400-person automotive supplier in Baden-Württemberg, I watched this exact scene play out at 06:00 and again at 14:00 and again at 22:00. Three shifts, three information deaths per day. The plant's OEE numbers looked fine on paper until we traced 23% of unplanned downtime back to shift handover gaps.

This post compares four approaches to manufacturing shift handover best practices. Not to sell you on one of them, but to give you criteria for your plant, your systems, and your compliance requirements.

Who Faces This Decision

You're running a plant with 200 to 800 employees. You have SAP ERP for planning and financials. Your MES is either legacy (installed in 2009, vendor stopped updating it in 2018) or nonexistent. Your floor supervisors use WhatsApp because it works.

You've thought about fixing shift handovers at least twice. The first time, IT proposed a full MES rollout. Budget killed it. The second time, someone built an Excel template. It worked for three months until nobody updated it.

Now you're asking: what actually works for mid-market plants that can't spend 18 months on implementation?

Here's the decision space:

flowchart TD
    A[Current State: Paper/Notebook Handover] --> B{What's your constraint?}
    B -->|Budget under €15K| C[Excel + SharePoint]
    B -->|Need audit trail for ISO| D[MES Module or Dedicated Tool]
    B -->|Complex multi-line handover| E[Custom Platform]
    B -->|Just need structure| F[Paper with Standard Template]
    
    C --> G[Works for: Single line, stable process]
    D --> H[Works for: Regulated, multi-shift]
    E --> I[Works for: Multiple systems, specific workflows]
    F --> J[Works for: Low complexity, <50 operators]
    
    G --> K{Does it integrate with SAP?}
    H --> K
    E --> K
    K -->|No| L[Manual re-entry, data dies again]
    K -->|Yes| M[Single source of truth]

Option 1: Paper with Standardized Templates

What it costs: €500 to design and print. Near zero ongoing.

What it's good at: Forcing structure onto chaos. A well-designed paper template beats an unstructured notebook. If your shifts are stable and your products don't change, paper works. I've seen ISO 9001 plants pass audits with paper handover logs, provided the templates are controlled documents and stored properly.

Where it breaks: The moment you need to search historical data. When an auditor asks "show me all shifts where pump 3 had issues in Q2," someone spends three hours flipping through binders. Root cause analysis across shifts is effectively impossible.

Who it's for: Plants under 100 operators with single-product lines and low variability. If your process is stable enough that shift-to-shift variation is rare, paper handles the exception cases fine.

Compliance note: ISO 9001 accepts paper if retention and access are controlled. FDA 21 CFR Part 11 does not. If you're in medtech or pharma, paper handovers create audit exposure.

Option 2: Excel on SharePoint

What it costs: €0 if you have Microsoft 365. Maybe €5K for someone to build a structured template with data validation.

What it's good at: Searchable history. Filtering by date, line, issue type. Familiar interface that operators already know. One automotive supplier I worked with ran shift handovers on Excel for four years. It worked because they enforced discipline: one person owned the template, data validation prevented garbage entries, and supervisors reviewed entries at shift start.

Where it breaks: Concurrent editing. If two shift leads are entering data at 05:58 and 06:02 during handover, version conflicts happen. SharePoint auto-save helps but doesn't solve it. Also, Excel lacks the audit trail depth ISO 9001 auditors increasingly expect. You can see what the file contains now, but proving what it contained six months ago requires IT to dig through version history.

Who it's for: Plants with 100 to 300 operators, single shift handover point, and IT support willing to maintain the template. Works well as a bridge solution while you evaluate bigger investments.

Option 3: MES Shift Handover Module

What it costs: €50K to €200K depending on your MES vendor and integration scope. Implementation typically 6 to 12 months.

What it's good at: Full integration with production data. Your shift handover automatically includes OEE from the previous shift, open quality deviations, and maintenance tickets. No manual re-entry. Audit trail is built in. If you're already running Siemens Opcenter, MPDV Hydra, or similar, adding the shift handover module is the lowest-friction path.

Where it breaks: Cost and timeline. For a 400-person plant, you're looking at 9 months minimum from contract signature to floor deployment. If your MES is legacy or you don't have one, you're not adding a module; you're buying a platform you might not need. Also, MES shift handover modules are designed for MES-centric workflows. If your floor reality lives partly in SAP, partly in SCADA, and partly in WhatsApp, the MES module only captures what goes through MES.

Who it's for: Plants already running modern MES (installed within last 5 years, vendor actively updating it), with IT resources to manage the implementation, and budget allocated for manufacturing digitalization.

For context on how MES compares to other data sources, see our comparison of real-time manufacturing dashboards.

Option 4: Custom Shift Handover Platform

What it costs: €30K to €80K for initial build, depending on scope. 3 to 6 months implementation.

What it's good at: Connecting systems that don't talk to each other. If your reality is SAP for orders, a legacy MES for machine data, Excel for quality tracking, and WhatsApp for urgent issues, a custom platform can pull from all four and present one handover view. It matches your actual workflow rather than forcing you into a vendor's assumed workflow.

TIMPIA builds these for mid-market manufacturers. One recent project for a Tier 2 automotive supplier connected SAP production orders, Siemens PLC data, and a legacy quality database into a single shift handover screen. Incoming shift leads now see: open orders with status, machine alerts from last 8 hours, quality holds, and free-text notes from the previous lead. Implementation took 14 weeks.

Where it breaks: You need someone to maintain it. Unlike a SaaS MES module, a custom platform requires ongoing technical ownership. If your IT team is two people already stretched thin, this creates dependency risk. Also, custom means custom: if your requirements change significantly, the platform needs updating.

Who it's for: Plants with complex, multi-system environments where off-the-shelf tools don't fit. Companies that have tried MES implementations and found them too rigid. Teams that need manufacturing shift handover best practices tailored to their specific floor layout and process.

Current State vs Improved State

Here's what the information flow looks like for most plants today:

sequenceDiagram
    participant PrevShift as Previous Shift Lead
    participant Notebook as Paper Notebook
    participant WhatsApp as WhatsApp Group
    participant NextShift as Incoming Shift Lead
    participant SAP as SAP ERP
    participant MES as Legacy MES
    
    PrevShift->>Notebook: Write notes (5 min)
    PrevShift->>WhatsApp: Post urgent issues
    PrevShift->>SAP: Log production (separate system)
    
    NextShift->>Notebook: Read notes (10 min)
    NextShift->>WhatsApp: Scroll back for context (15 min)
    NextShift->>SAP: Check order status (5 min)
    NextShift->>MES: Check machine alerts (5 min)
    NextShift->>PrevShift: Call to clarify (10 min)
    
    Note over NextShift: Total handover: ~45 minutes
    Note over NextShift: Information gaps remain

With a connected handover system (whether MES module or custom):

sequenceDiagram
    participant PrevShift as Previous Shift Lead
    participant Platform as Shift Handover Platform
    participant SAP as SAP ERP
    participant MES as MES/SCADA
    participant NextShift as Incoming Shift Lead
    
    SAP-->>Platform: Auto-pull open orders
    MES-->>Platform: Auto-pull machine alerts
    PrevShift->>Platform: Add context notes (5 min)
    
    NextShift->>Platform: View unified handover screen (5 min)
    NextShift->>Platform: Acknowledge critical items
    
    Note over NextShift: Total handover: ~10 minutes
    Note over Platform: Full audit trail, searchable

We've written more about where production data dies in shift handoffs, if you want to quantify the cost of your current state.

Decision Framework: Which Path Fits Your Plant

Here's how to decide based on your situation:

Choose standardized paper if:

• You have under 100 operators
• Your process variability is low
• You're not in FDA-regulated production
• You need a solution this week, not this quarter

Choose Excel on SharePoint if:

• You have 100 to 300 operators
• Single shift handover point
• IT can maintain the template
• You need searchable history but not real-time integration
• Budget is under €10K

Choose MES shift handover module if:

• You're already running a modern MES (vendor actively supporting it)
• You have IT resources for 6 to 12 month implementation
• Budget is €50K or more
• You want one vendor for production operations

Choose custom platform if:

• You have multiple disconnected systems (SAP, legacy MES, Excel, paper)
• Off-the-shelf tools don't match your floor workflow
• You need manufacturing shift handover best practices specific to your process
• You have 200 to 800 operators across multiple lines
• Timeline matters more than minimizing upfront cost

What Most Plants Actually Do

In practice, most mid-market manufacturers I work with follow this path:

1. Start with standardized paper templates. Quick win, forces discipline.
2. Move to Excel on SharePoint when they need searchable history or an auditor asks for trend data.
3. Hit Excel's limits when concurrent editing becomes a problem or they need real-time machine data.
4. Evaluate MES module vs custom based on their existing system landscape.

The jump from step 2 to step 3 usually happens around the 300-operator mark or when they add a second production line with different handover timing.

Manufacturing Shift Handover Best Practices Across All Options

Regardless of which tool you choose, these practices separate plants with smooth handovers from plants where information dies:

• Structured categories: Open issues, quality holds, safety notes, machine status, upcoming orders. Same categories, every shift.
• Acknowledgment step: Incoming lead confirms they've reviewed and understood. Creates accountability and audit trail.
• Time-boxed handover: 15 minutes maximum. If it takes longer, the format isn't working.
• Escalation path: Clear rule for what goes into handover notes vs what requires a call to the previous lead.
• Weekly review: Plant Manager reviews handover logs once per week. What patterns emerge? What keeps recurring?

These practices matter more than the tool. A well-run paper system beats a poorly-adopted MES module.

---

Not sure which path fits your plant? Book a 20-minute walkthrough and we'll map your current systems, handover workflow, and compliance requirements. No pitch, just clarity on your options.