This guide walks you through the tracker from first open to your first morning meeting. The workflow is simple: set it up once, enter one row per shift, review the dashboard, act on the misses, and check the trend.
Want the thinking behind the KPIs first? Read Warehouse KPIs to Track Daily.
Step 1: Save a master copy
Before you type anything, save the original file somewhere safe. Then make a copy for your facility and work from that, for example Warehouse KPI Tracker - Main DC.xlsx. If someone accidentally breaks something, a clean master is much faster than repairing formulas.
Step 2: Fill in 02_SETTINGS
This tab tells the workbook how your facility runs. Enter:
- Facility name
- Primary volume unit (orders, order lines, cases, units, or pallets)
- Shift names (up to four; leave unused ones blank)
- Targets: UPH, output per employee, completion %, on-time shipping %, order accuracy %, attendance %, maximum overtime %
- Backlog alert level
Choose the volume unit that matches how you manage workload, and don't change it later. Set the shift names before supervisors start entering data, since the Daily Log uses them. Sample targets ship with the file. Replace them with your own (see the targets section of the guide for how).
Step 3: Enter one row per shift in 03_DAILY_LOG
At the end of each shift, the supervisor or lead adds one row. The input columns (amber headers) are:
Date, Shift, Area / Team, Planned Workload, Completed Workload, Backlog at End, Orders Due, Orders Shipped On Time, Orders Shipped, Order Errors, Scheduled Headcount, Present Headcount, Regular Hours, OT Hours, Inbound Loads, Outbound Loads, Safety Incidents, Near Misses, Notes, Supervisor.
Once the numbers are in hand it takes a few minutes per shift. Gathering them from your system is the part that varies.
Blank is not zero. If you don't track a field, leave it blank. A blank means "not tracked." A zero means "we measured it and it was zero." If you didn't measure order errors and you enter 0, you've told the workbook every order shipped clean. A blank makes the related KPI show No Data instead of a number nobody measured.
Step 4: Let the workbook do the math
The teal columns calculate automatically:
| KPI | Calculation |
|---|---|
| Total labor hours | Regular hours + OT hours |
| UPH | Completed workload ÷ total labor hours |
| Output per employee | Completed workload ÷ present headcount |
| Completion % | Completed ÷ planned |
| On-time shipping % | Orders shipped on time ÷ orders due |
| Order accuracy % | 1 − (order errors ÷ orders shipped) |
| Attendance % | Present headcount ÷ scheduled headcount |
| Overtime % | OT hours ÷ total labor hours |
Supervisors don't calculate anything. They enter the data.
Step 5: Review 05_DASHBOARD
Use the selectors at the top to choose:
- Period: Report day, Last 7 days, Last 30 days, Month to date, Year to date, or All data
- Shift: all shifts together, or one shift
- Report date
The dashboard compares results to the targets in Settings. Each KPI shows On Target, Below Target, Over Limit (for overtime), or No Data.
Period results come from summed numerators and denominators, not an average of daily percentages, so a 500-order day carries more weight than a 20-order day.
In the morning meeting, look for exceptions. What changed? What missed? What's getting worse? What needs an action? If a metric is on target and nothing odd is behind it, move on.
Filtering by shift is useful when the facility number looks fine but one shift keeps missing.
Step 6: Read backlog and safety as context
Besides the KPIs, the dashboard shows completed workload, labor hours, latest backlog, inbound and outbound loads, safety incidents, and days since the last incident. These explain the KPIs. UPH can drop on a heavy inbound day. Backlog can rise while completion stays close to target. Overtime can climb because attendance fell. Read them together.
Backlog turns red when it goes above the alert level you set in Settings.
Step 7: Turn misses into actions in 04_ISSUES_ACTIONS
A red KPI isn't a corrective action. Log the issue here with an area, priority, owner, due date, root cause, action, and status. Open items show up on the dashboard so they don't vanish after the meeting.
The loop is: KPI miss → investigate → root cause → action → owner → due date → follow-up.
Step 8: Check the trend in 06_WEEKLY_SUMMARY
This tab shows the last 12 weeks: planned and completed workload, completion %, labor hours, UPH, output per employee, on-time shipping, order accuracy, attendance, overtime, and safety incidents. One bad Tuesday may mean nothing. Four weeks of falling UPH deserves attention. A steadily rising overtime percentage usually means staffing or workload planning no longer matches the work.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| A KPI shows No Data | The inputs it needs are blank | On-time needs Orders Due and Orders Shipped On Time. Enter them, or leave it if you don't track them. |
| A number looks wrong | A zero entered where the field wasn't tracked | Clear the cell. Blank means not tracked. |
| Dashboard is empty | Report date or period doesn't cover your data | Check the selectors, or choose All data. |
| Shift missing from the list | Shift name not entered in Settings | Add it in 02_SETTINGS. |
| Can't edit a cell | Calculation and reporting areas are protected | Only the amber input cells are meant to be edited. |
Common mistakes
- Changing the workload unit partway through
- Entering zero when you mean "not tracked"
- Supervisors counting labor or backlog differently
- Looking at productivity without quality, or service without labor
- Reading a percentage without the volume behind it
- Treating the KPI as the root cause
Notes on the file
It's a standard .xlsx with no macros. It holds up to 3,000 shift rows. Calculation and reporting sheets are protected without a password so normal users can enter data and read results without breaking formulas. Keep your master copy.
Questions? hello@logisticsdeck.ai