Workforce and shift planning

When Excel is no longer enough for shift planning

How to recognize when Excel reaches its limits in shift planning, what a planning tool does differently and how a switch can work.

In brief

Excel is enough for shift planning as long as a manageable team plans in a stable shift system. The limit is reached when qualifications, certificates, rules, absences and several areas all have to fit together at once and errors can only be prevented by the diligence of individuals. At that point, rules and qualifications belong in a planning tool.

Excel is enough for shift planning as long as a manageable team works in a stable shift system and the rules fit in the head of one planner. The limit is reached when qualifications and certificates, absences, rules and several areas all have to fit together at once and errors in the plan can only be prevented by the diligence of individuals. At that point, rules and qualifications belong in a planning tool that matches them systematically.

Why Excel works for a long time

A spreadsheet is quick to set up, almost everyone in the company can read it, and small changes are entered immediately. For a team with fixed shifts, few qualifications and rare exceptions, that can be enough.

The limit rarely arrives on a specific day. With every new requirement, the spreadsheet gains more columns, colors, formulas and extra sheets. At some point, only one person still knows its complete structure, and every change to the plan above all requires time-consuming checks.

Signs of the complexity limit

The signs rarely appear on their own. The more of them apply to your planning, the more likely it is that an error will slip into the plan unnoticed.

  • Qualifications and certificates: Only employees with valid proof may be deployed for certain facilities, workstations or tasks. In the spreadsheet, whether a certificate is still valid on the day of deployment depends on formulas or on the attention of the planner.
  • Shift systems and 24/7 operation: Several shift models and rotations run side by side. In continuous operation, every shift has to be staffed, including at night, on weekends and on public holidays.
  • Absences: Vacation, illness, training and short-notice absences are kept in other lists or systems and transferred by hand.
  • Rules: Rest periods, maximum working hours, minimum staffing levels and company agreements are kept in mind during planning, but not checked systematically.
  • Several areas: Each department keeps its own spreadsheet. Who could help out across areas is not visible at a glance.
  • Traceability and versions: Several file versions are in circulation. When questions arise, it is hard to establish which plan applied when and who changed it.
  • Dependence on individuals: Only a few people fully understand the spreadsheet. If they are absent, planning stalls.

Recognizing several of these points does not mean you have planned badly. The task has grown, but the tool has not.

What a planning tool does differently

In a planning tool, rules and qualifications are part of the system. They are matched during planning instead of being searched for in the spreadsheet afterwards. This reflects an insight from our projects in production and shift planning: errors are cheapest to avoid when they arise early in planning. That is why qualifications and requirements should be taken into account from the earliest phase.

Hawk IVO Plan is the functional core for planning logic, rules, optimization and plan versions. It plans your team according to qualifications and in step with your customer orders, from annual planning to short-notice changes on the same day. The platform’s scope of services to date includes:

  • Qualification matching: a qualification matrix with qualification-based matching. The article on the qualification matrix in shift planning explains how such a matrix is structured.
  • Shifts and absences: shift requirements, shift system groups with automatic assignment, shift swaps, and absence planning with vacation requests, absence types and plant calendar.
  • Traceability: reporting, audit-proof documentation and a log system.
  • Time and approval: time tracking, time accounts, approval processes and allowances.
  • Communication with employees: They see their shift schedule, submit absence requests and swap shifts. The mobile app also offers a chat for this.
  • Connected systems: master data, orders and personnel movements from SAP and other ERP systems, production data and recorded times from MES and time tracking, data exchange via the Hawk API and login via single sign-on.

We will clarify the right scope for you in a conversation. The decision about the plan stays with the people responsible: Hawk IVO Plan proposes a staffing plan based on rules and qualifications, and the people responsible approve it. The article Shift planning with AI describes how AI supports this.

Practical example: shift planning in a chemical plant

The video case study “Die Komplexitätsgrenze: Warum die Großchemie Excel abschaffen musste” (in German), which Hawk published in March 2026, shows OXEA’s Werk Ruhrchemie site in Oberhausen. Hundreds of complex facilities stand there on 1.2 km², and the plant operates 24/7. Shift planning is the foundation of plant safety, because exact qualifications determine safe operation.

As complexity grew, isolated Excel spreadsheets at the plant became an incalculable risk. The plant switched to a professional planning tool that matches the requirements of the facilities with employees’ valid certificates and handles nested qualification matrices. In the video, the tool still bears its former name, HAWK AI Planning. Today it is called Hawk IVO Plan.

Hawk IVO Plan is used at the plant in several areas, including the plant fire department, the security service, logistics and the power plant. The topics range from attendance at the plant and qualification management with a safety pass to time tracking, shift accounts and planning. The solution is operated in a private cloud.

The example combines several signs of the complexity limit: valid certificates, continuous operation and several plant areas. Read more in the OXEA case study. You can find the video in the news item on the video case study.

How a switch can work

A switch does not have to change over all areas at once. A step-by-step approach makes sense:

  1. Start small: Begin with an area where the limits of the spreadsheet are most obvious, such as a team with many qualification requirements or in continuous operation. Together, we determine which information and systems are needed and how you will measure the benefit.
  2. Transfer data: Employees, qualifications, shift models and absences are entered or imported from existing systems, such as master data from SAP. Rules that previously existed only in the planners’ heads are written down in the process and, where possible, incorporated into the planning logic.
  3. Check in parallel: For a limited period, plans are created both in the spreadsheet and in the planning tool. Deviations show where rules or data are still missing. Only when the new plan is correct does it replace the spreadsheet.
  4. Expand: Additional teams, sites or tasks are added step by step. Employees are involved via the mobile app.

In the pilot with real users, we set up the use case and support you during the first weeks of operation. Get in touch if your shift planning is reaching this limit.

Sources and further reading

  1. Video case study on YouTube (in German): “Die Komplexitätsgrenze: Warum die Großchemie Excel abschaffen musste” (opens in a new tab)

Related products

Read on