Product help

Labor Productivity & Staffing Planner: Setup and User Guide

Save a working copy, set your assumptions, plan by workload or headcount, enter actuals, and use the dashboard to spot staffing gaps before the shift.

This guide takes you from opening the file to your first staffing plan. The short version: save a working copy, set your assumptions once, add one plan row per date, shift, and area, enter actuals after each shift, and read the dashboard.

Want the thinking behind the math first? Read Warehouse Labor Planning: How to Calculate the Headcount You Actually Need.

Step 1: Save the sample as your master reference

The product is delivered as one fully functional sample-data workbook. Keep the original untouched as your reference. Then use Save As to create a working copy for your facility, for example Labor Planner - Main DC.xlsx.

In the working copy, clear the sample entries from the yellow and amber input cells before entering your own data. The sample values are examples, not industry benchmarks. One sample shift is intentionally overloaded so you can see the utilization and backlog alerts work.

Step 2: Set your assumptions in 02_SETTINGS

Yellow cells are yours to change. Every plan row uses these values unless you override them on that row.

SettingWhat it is
Facility nameShows on the dashboard
Workload unitOne unit for the whole workbook: orders, order lines, cases, units, or pallets
Shift names (up to 4)Fill in order, leave unused ones blank. These feed the dropdowns
Area / Team names (up to 8)Fill in order. A single-area site can use one name for everything
Expected attendance %Scheduled heads × attendance = expected present heads
Paid hours per person per shiftHours you pay for. An unpaid lunch is not part of paid hours
Paid breaks (hours/person)Break time inside paid hours. Deducted to get productive hours
Other nonproductive time (hours/person)Start-up, huddles, travel, cleanup
Expected rate per productive labor hourWorkload units one person completes in one productive hour
Max overtime hours per personAn availability limit per present person per shift, not a recommendation
Labor cost per paid hourOptional. Leave 0 to skip cost figures
Overtime pay multiplierOT hours cost this × the hourly cost
Conservative and stretch rate multipliersScenarios: rate × this number
Utilization alert levelRegular utilization above this turns amber

Pick your workload unit now and don’t change it later. Fill the shift and area lists in order with no gaps, because the dropdowns read them. Use your own history for rate and attendance.

Step 3: Build the plan in 03_STAFFING_PLAN

Add one row per date, shift, and area. The amber headers are the columns you type into:

  • Date, Shift, Area / Team
  • Forecast Workload
  • Scheduled Headcount
  • Notes (optional)

That’s all most rows need. The grey columns show the value each row is actually using, and the teal columns calculate automatically.

Overrides

Columns F through K let a single row differ from Settings: attendance, paid hours, nonproductive hours, rate, max OT, and cost. Leave an override blank to use the Settings value. Use them for a 10-hour shift, a slower area, or a new-hire-heavy crew. Type attendance as a percentage (95% or 0.95). The cell rejects a plain 95.

Two ways to plan from the same row

  • By workload: “I have 4,600 lines tomorrow, how many people?” Read Required Scheduled Heads and Head Gap.
  • By headcount: “I have 70 people, what can they clear?” Read Regular Capacity and Surplus / (Shortfall) before OT.

How the key columns are calculated

ColumnCalculation
Productive Hrs / PersonPaid hours − paid breaks − other nonproductive time
Expected Present HeadsScheduled headcount × attendance %
Regular CapacityPresent heads × productive hours × rate
Capacity incl. Max OTRegular capacity + present heads × max OT hours × rate
Required Scheduled HeadsForecast ÷ rate ÷ productive hours ÷ attendance %, rounded up
Surplus / (Shortfall) before OTRegular capacity − forecast. Negative means overtime or backlog
OT Hrs RequiredThe overtime needed to cover the shortfall, capped at the OT limit
Backlog after OTForecast − capacity incl. max OT, never below 0
Regular Utilization %Forecast ÷ regular capacity. Above 100% means overtime or backlog
Paid-Hour Productivity Eq.Rate × productive hours ÷ paid hours. Matches the KPI Tracker’s UPH definition
Est. Labor CostPresent heads × paid hours × cost + OT hours × cost × OT multiplier

Row Check

Column M tells you OK, WARNING, or ERROR. It catches duplicates, shifts or areas not listed in Settings, a missing forecast, a date typed as text, and nonproductive time at or above paid hours. ERROR rows are left out of the dashboard until you fix them, so one bad row can’t distort the totals.

Capacity is 1,000 plan rows. Start a new working copy before you reach the limit.

Step 4: Enter actuals in 04_ACTUALS

After each shift, add one row: Date, Shift, Area / Team, Completed Workload, Backlog at End, Scheduled Headcount, Present Headcount, Regular Hours, OT Hours, and Notes.

The columns mirror the KPI Tracker’s daily log, so if you use both products you can copy values across.

Blank is not zero. If you don’t track backlog, leave Backlog at End blank. A blank shows No Data on the dashboard. A zero says you measured it and nothing was left over.

Each actuals row is matched to its plan row on date + shift + area, and the grey columns show the plan values next to what happened: completion vs. forecast, productivity vs. plan, and present heads vs. plan. If no plan row exists, the row still counts toward actuals totals, but the plan comparison stays empty.

ColumnCalculation
Paid HoursRegular hours + OT hours
Paid-Hour ProductivityCompleted workload ÷ paid hours
Attendance %Present headcount ÷ scheduled headcount
OT %OT hours ÷ paid hours

Step 5: Read 05_DASHBOARD

Use the yellow selectors in row 4:

  • Report date: the anchor date. Clear it and the dashboard jumps to the next plan date.
  • Period: Report day, Next 7 days, Last 7 days, Week of report date, Month of report date, or All data.
  • Shift: All shifts or one shift.
  • Area: All areas or one area.

The dashboard shows forecast workload, regular capacity, utilization, OT required, backlog after OT, labor cost, staffing gaps, scenarios, actual-vs-plan performance, and day-by-day tables/charts. Period figures come from summed numerators and denominators, never averaged percentages. Backlog is added row by row, so a surplus on one shift doesn’t cancel a shortfall on another.

Review it before each shift for shortfalls, and weekly for patterns. If your rate or attendance is consistently off, change the setting. That’s the point of tracking actuals.

Troubleshooting

SymptomCheck firstThen try
Row Check says ERRORThe Row Check messageFix the cell it names. Common causes: text date, invalid shift/area, duplicate date + shift + area.
Dashboard shows zerosReport date, Period, Shift, AreaChoose All data / All shifts / All areas. Clear report date to jump to the next plan date.
Shift or area missing02_SETTINGS listsFill the lists in order with no blank rows between names.
Attendance rejectedOverride cellType 95% or 0.95. A plain 95 means 9,500%.
Actuals say no matching planDate, shift and area on both tabsAdd the plan row, or correct the value on one tab.
Surplus looks positive but OT is requiredSurplus is before overtimeRead OT Hrs Required and Backlog after OT next to it.
Cost shows blank or zeroLabor cost settingEnter a cost, or leave it 0 to skip cost figures.

Things to avoid

  • Typing into grey or teal columns
  • Editing 07_CALC
  • Typing a shift or area name that isn’t in Settings
  • Treating Capacity incl. Max OT as normal capacity

What the planner assumes

  • One workload unit per workbook. A site that tracks both cases and pieces needs separate copies.
  • Overtime hours are treated as fully productive. If output drops late in a long shift, lower the rate on those rows.
  • The math is deterministic. It has no learning curve or random variation. Treat it as a planning baseline, and use the scenarios to see how much a bad day would hurt.
  • Attendance and rate are your inputs. The sample values are not benchmarks.

About the file

It’s a standard .xlsx with no macros, built for Excel 2010 or later on Windows or Mac. System sheets have red tabs and are protected without a password. The file recalculates when you first open it, so Excel may ask to save when you close. Keep the original sample workbook as your master reference and work from a saved copy.

Questions? hello@logisticsdeck.ai