Loading…
Staff flag a session from /me (by badge) or the /cs page. A flag changes nothing on its own: put the time right in Manual Entry, then mark it fixed. What you write back is shown to them.
| Raised | Person | Session | What's wrong |
|---|
| Name | Short Code | Type | Nudge after (min) | Status | Actions |
|---|
Manage Customer Service task buttons shown on the CS tracker.
Manage Finance task buttons: Invoice Query, Invoicing, Courier Analysis, Pallet Analysis.
Manage Systems task buttons shown on the CS tracker.
Coming soon — will hold client onboarding workflow.
| Client | Mintsoft | Location | Activities | Actions |
|---|
| Name | Type | Times | Break | Warehouse | Members | Status | Actions |
|---|
| Name | Short Code | Clients | Mintsoft | Collections | Status | Actions |
|---|
A warehouse with no Mintsoft mapping is not offered in Burn-down and contributes no despatch figures to Time vs Dispatch. Both fail quietly, so map a new site here as soon as it goes live.
| Name | Short Code | Warehouse | Address | Status | Actions |
|---|
Back-fill a task someone forgot to log, or correct one that was recorded wrong — a forgotten log-out closed by the auto-timeout, say. Times are local (UK); overlapping an existing session is blocked. Pick a person and day, then edit any record in the list or add a missing one.
1 · Whose day?
Pick a person and day to see their timeline below.
Recent changes
| When | Change | Staff | Activity | Start | End | By | Reason |
|---|
Staff Badges
Printable QR badges for active staff
Task Cards
Print all or filter by category, client, warehouse, or group
Custom Sheet Builder
Hand-pick task cards for a tailored sheet — e.g. one person's clients and activities — and save it as a named preset for reprinting
0 selected
Loading task codes...
Reports
Flags clients that despatched orders on a day but had little or no time logged against them — the gap that distorts billing and productivity. Dispatch counts come from Mintsoft; hours from logged productive sessions.
One person's day: every clock and task scan, where each came from, and what needs correcting. A night shift shows whole on the day it started.
compared with
Excessive Break
Measured against each person's own shift-group break allowance, not a flat figure — allowances differ by group (Invoicing allows 120 minutes).
Long Shift (>9 hours)
Compares the hours each person actually keeps against the shift they are assigned to. Uses kiosk sign-in and sign-out where they exist, otherwise the day's first and last scan — several warehouse staff scan all day without signing in, and leaving them out would hide the sites that need this most. The Signal column says which was used. Today is excluded, because an unfinished day has no real finish time. Auto sign-outs and auto-closed sessions are also excluded — those are stamped with the shift's own end time, so counting them would make every shift look like a perfect fit.
Absence
From the Shift Planner. A full day counts 1.0, a morning or afternoon 0.5. Rate is absence as a share of known expected attendance (absence days ÷ absence days + days worked), because the rota is used in practice as an absence log rather than a full shift pattern.
Signed in after shift start
Earliest sign-in compared against that day's shift start (the rota override for the day, otherwise the person's default group). Days marked as absence are excluded.
System-wide values. Reporting thresholds only change how figures are presented. The operational ones change how time is recorded — they drive automatic sign-out and break tracking, so a wrong value here rewrites people's hours.
Reporting thresholds
Used as the default when a report is run without an explicit override.
| Setting | Value | What it does |
|---|---|---|
| Long shift threshold | min | A day on site longer than this counts as a long shift in HR Exceptions. Note: Early Shift is 08:00–17:00 = exactly 540 minutes, so 540 flags any day running even a minute over. 570 (9.5h) is a more useful figure. |
| Lateness grace | min | How late a sign-in can be before it counts in Absence & Lateness. |
Weekly manager digest
Sent every Monday around 07:30 with last week against the week before. Leave empty and no digest is sent. Recipients save as you add or remove them; the Save button below is for the other settings.
The group edition covers every warehouse. A per-warehouse edition covers only that site, and its links open the reports already filtered to it. Leave a site empty to send nothing for it — sites with only a handful of person-days a week are better left inside the group edition than given their own email.
| Edition | Recipients |
|---|
Send a test first
Sends last full week's digest to one address so you can see it before deciding who receives it. Real figures, marked as a test, and it doesn't affect Monday's send.
Operational
These affect how sessions are closed and how break time is measured. Change them deliberately, not casually.
| Setting | Value | What it does |
|---|---|---|
| Break allocation | min | Default paid break shown on the scanner break timer. |
| Session warning after | hours | A task running longer than this is flagged on the live dashboard. |
| Task auto-stop after | hours | A task left running longer than this is closed automatically. |
| Attendance auto-close after | hours | A sign-in left open longer than this is signed out automatically. |
| Shift-end grace | min | How long after a shift ends before the system treats the person as overdue. |
| Absence grace | min | How long after a shift starts before someone with no sign-in and no scan is called an unexplained absence on the dashboard. Separate from the lateness grace above, which only affects reports. |
| Absence alert emails | Emails each manager their unexplained absences on the morning it happens. While this is off the check still runs and records what it would have sent, so the thresholds can be reviewed before anyone is emailed. | |
| Over-break reminder at | min over | Emails the person once their break today runs this far past their allowance, asking them to scan back to a task if they're already working. Skipped for anyone with no email on file. |
| Over-break escalation at | min over | Emails their manager if they are still on break this far past their allowance. With no manager set it goes to the site's digest recipients, then the group list. |
| Over-break emails | At most one reminder and one escalation per person per day. While this is off the check still runs and records what it would have sent. | |
| Stale temp after | working days | An active temp with no sign-in and no scan for this many working days is emailed to whoever added them (or their manager, then the site's digest recipients, if that isn't recorded), asking them to deactivate the temp or set them on leave. Once, then each Monday until it's sorted. |
| Stale temp emails | On by default. While off, the check still runs and records who it would have emailed. |
By week
Unlogged gap is on-site time that fell between tasks without being recorded against anything. Logged % is task plus break time as a share of total time on site. Range is capped at 26 weeks.
Holiday, sick and other absence, with a reason. Approved leave is written into the Shift Planner automatically, so it flows through to Absence & Lateness, the roll-call and the Monday digest with no second entry. Weekends and bank holidays are skipped unless you tick to include them. Staff book their own holiday at Ops Tools → Leave, which reads and writes the same records as this page.
Days per person for the leave year. Changes save as you leave the box. Remaining is allowance + carried over + adjustment − taken − booked; pending requests are shown but not deducted, and only types that come off the allowance count at all — sick leave never does.
Review and approve pending overtime. Approved records are exported via Reports → Overtime Report.
Gross = total clocked time. Break = time logged against a Break activity (— if none). Net = Gross − Break. Use Mark Break Taken when lunch wasn't clocked but was taken; No Overtime for rounding cases where there's no real overtime to pay.
Pre-approved overtime plans auto-approve matching records when they are seeded.
| Time | Table | Action | Record | Changes |
|---|
Mintsoft usernames that picked or despatched orders today but don't match a Punched staff member. Pair each one to the right person so today's WMS counts appear on their dashboard card. Pairings are persistent and override the auto-match by name.
Unmatched WMS users — today
| Username | Picked | Despatched | Clients | Map to staff |
|---|
Existing pairings
| Username | Paired to | Created |
|---|
Loading...
| Name | Role | Status | Last Login | Warehouse |
|---|
Name
Email
Warehouse
Group
Status
All results shown · click row to edit · ⋯ for actions
Reporting lines
No manager set
Absence for these people escalates to the site mailing list rather than a person, and nobody can approve their leave by reporting line.
Currently on site
| Name | Company | Visiting | Site | Type | Signed in |
|---|
Sign-in log —
Personal details are GDPR-purged 24 hours after sign-out, so older entries show as purged. Auto sign-outs are assumed departures recorded at the run time, not observed exits.
| Name | Company | Site | Type | In | Out | Method |
|---|
A link for a screen on the floor that shows the live board for one site, and optionally one group, one area, one client or one activity, so people can be found. Nobody signs in on the screen. It shows who is on what, breaks and pick/despatch counts. It never shows absence, lateness, signed-out people or visitors. A link only works on the warehouse networks, and a link can be revoked at any time.
A goods-in board shows that site's Inbound calendar for today, hour by hour, and how far each delivery has got (due, arrived, unloaded, put away). No notes or charges. Preview opens any board from wherever you are.
Distance style is for a TV read from across the room. Its text grows to fill the screen. A people board becomes one line per person (first name and initial, status colour, time) and pages every 12 seconds if everyone won't fit; it shows exactly the same people as Standard. You can switch a board's style below without changing its link.
A client or activity board (e.g. Packing) shows only the people on that work right now. A break or a gap between tasks has neither, so those people drop off it until they scan again.
| Board | Shows | Link | Screen last seen | Created |
|---|
Notices
A strip along the bottom of the boards at a site, or one board, between the times you set. Boards pick it up within a minute and take it down on their own when it ends. Alerts come first; if everything won't fit on one line, it scrolls. A screen showing two boards side by side (a wall link, /wall?b=<token>&b=<token>) shows one strip across both. Don't put personal details in a notice: it is on a wall that temps and visitors walk past.
| Notice | On | When | Status | Put up by |
|---|
Live from Mintsoft, not the overnight sync. Shows open orders due today against courier cut-offs, with the pace needed to clear them. Team leaders see the same numbers on their handset.
By courier
Labour right now —
Team leader checks — last 14 days
Each is a deliberate look at the burn-down: opening it, pulling to refresh, or coming back to it. The background refresh is not counted.
Outstanding orders email
Orders by client and status (New through Awaiting replen) plus today's despatches, live from Mintsoft. Sent on weekdays, not bank holidays, at the times below, to each site's list.
Blind counting with batch and best-before capture, for clients where Mintsoft's own
blind count cannot break a bay down by batch. Counters work at
/stocktake on a handheld.
Didn't sign out — needs review
Staff who signed in but never signed out are auto-signed-out at the site's assumed end-of-day so the board and fire register stay correct. The leave time is a guess — Confirm to accept it, or Correct if you know when they actually left.
Loading…
Roll-call history
Email settings
Changes save as you make them.
Fire roll-call email
Sent when a roll-call is submitted. Global recipients get every warehouse's roll-call; a warehouse's own list is added on top.
| Scope | Recipients | Status |
|---|
Didn't-sign-out email & assumed end-of-day
A digest of the previous day's forgotten sign-outs goes to each site at about 07:00, with global recipients on every site's email. Assumed end-of-day is the leave time used when someone forgets to sign out (19:00 if a site has no row).
| Site | Assumed end | Recipients | Status |
|---|
Deliveries that have arrived and not been turned into money. A delivery nobody captured has no charge line at all; a receipt with a chargeable count left blank looks finished and invoices short. Both are invisible on the Charges tab, because what is missing is the row itself.
Today's uncaptured bookings are not listed: a vehicle booked for 15:00 has not failed to be captured at 10am. A receipt that has been saved is checked straight away. No-shows, cancellations and audited do-not-charge deliveries are decisions somebody recorded, so they are not gaps.
Every charge taken off a delivery: which line, worth how much, by whom, and why. The month's total on the Charges tab is already net of these, so this is the whole of the difference between what the rate card says the month was worth and what it will be invoiced at.
A waiver can be recorded against a line that never fired, or before the delivery has been captured. Those took nothing off and show a blank amount rather than £0.00. An audited do-not-charge on the whole delivery is a different decision and is not listed here — it is on the booking.
Inbound revenue for one ISO week, by client, under the names the weekly KPI pack uses. This is the figure the pack used to pull out of the goods-in tracker with a cross-workbook SUMIF. Punched does not charge a delivery that never arrived, so where this differs from the old number, the Booked but not charged list below is the whole of the difference.
Punched against the goods-in workbook. Upload the tracker as it stands and every delivery on it is matched to the booking Punched holds — by date, client and reference, never by its row number, because rows get inserted in the middle of the file. What is left over on either side is the answer: rows on the sheet nobody has entered, and bookings in Punched the sheet has never heard of.
Re-upload it whenever the warehouse has added to it. The file is stored, replacing the last one, so this tab has something to show without uploading again. Nothing on the sheet changes a booking on its own: Import writes a row Punched does not have, and Take sheet's version is per row. A closed month refuses both.
The Leamington tracker (Daily Delivery Tracker 2026.xlsx) — the
2026 tab, with its columns where they are today. A file whose columns
have moved is refused rather than read off by one.
Loading…
One placard per site, printed and fixed at the goods-in bay. Scanning it opens the bench app on a handheld; the operator then scans their own badge and picks the delivery off that day’s list. The QR carries a signature, so a photocopied or hand-typed code will not open anything.
Loading…
Each weekday at about 07:00 (not bank holidays), everyone on a site's list gets that site's Inbound calendar
for the day, hour by hour, in the body of the email. Each site has its own list. A site with nobody on it sends nothing.
Loading…
Engineer payroll register for on-call hours. Lists every payable on-call day with summed minutes ceiled to the nearest hour. Tick "Paid" once payroll has paid out for that day.
How much work each person got through for the time they spent on orders, per client.
How to read this
- Time on orders: time clocked in Punched on a client's Picking, Packing or Amazon task.
- Target time: how long the orders they picked and packed in Mintsoft should take at target speed. Each order's target depends on the client and its size (lines, units, parcels, pick locations, multi-tote or one at a time), set in Productivity Model.
- Productivity: target time ÷ time on orders. 100% = exactly at target speed; above 100% = faster than target; below = slower.
- Example: 7h 41m on Naturo, and the 47 picks and 73 packs done should take 5h 54m at target, so productivity = 5h 54m ÷ 7h 41m = 77%.
- Orders on a shared scanner login (lsscan, fullersea…) count for the person a TL signs off in Floor › Scanner logins. Until then they count only on Mintsoft's assigned picker or a single clear match in Punched, and are flagged.
- Time on a client where nobody could be credited with the orders (bulk B2B, for example), or with no target set, is shown but not scored.
Shared Mintsoft logins (lsscan, fullersea and the like) don't say who was holding the scanner. Each day, say who had each one and sign it off. Picks and packs on a signed-off login count towards that person's productivity. Until then they count only where Punched has clear evidence, and the rest count for nobody. Changing who had a login undoes its sign-off.
Each product's size, XS to L, so a 10kg bag of dog food can count for more than a 30ml serum in Productivity. Punched sets it every night from the size in the product's name or its Mintsoft weight, and leaves it unknown when they disagree or neither is there. For those, an AI assist suggests a size: it's used straight away only when it's sure, and otherwise waits here for you to accept or change. Set a size here when you know better: it sticks until you choose "Use the rules" again. Products are listed by how much was picked in the last 4 weeks.
Choose a client to see its products.
How long the work should take, by client, pick or pack. Each client and activity is counted per order (by number of lines), or per line, unit / case, parcel or pick location. Picks can be priced separately one at a time or multi-tote: a batch only counts as multi-tote where the same picker's orders were picked at once (overlapping); a batch picked one order after another counts as one at a time. Orders can be bracketed by size in lines, units / cases or parcels. A client's own bands replace the default entirely for that activity. Bands are dated: a client's newest set for an activity replaces its older set as a whole from that date, and never rescores earlier days. Adding one band on a new date carries the rest of that set forward. Delete a band to correct a mistake.
Edit the targets in Excel
Download the targets in force, with the last 8 weeks of orders beside them. Change the yellow columns, then upload the file. Nothing is saved until you've seen what changes and how a real day would have scored.
CS and floor time per client for the month, priced at the rough rates below. CS cost is set against the CS amount invoiced (type it as you check each invoice). Floor cost is set against pick/pack revenue and the admin fee: Mintsoft's charges for each order despatched this month, fetched automatically. You can type over the pick/pack figure. Green means the money covers the time, red means it doesn't.