Pick Lists and Why Deduct-on-Start Beats End-of-Month Counts
If stock only comes off the books at month end, your counts are wrong for the other 29 days. Deducting each pick list when the job starts fixes that.
5 min read
Running out of a plate size in the middle of a batch stops a crew cold. Here's how to keep plate counts you can actually trust.
Metal connector plates are small, heavy, easy to miscount and absolutely essential. A truss plant can have plenty of lumber, a crew ready to go and a job due tomorrow, and still lose half a day because the one plate size the job needs is gone. Plate inventory is rarely the biggest number on the balance sheet, but it may be the one most likely to stop production without warning.
This guide covers practical habits that keep plate counts accurate, without turning your yard lead into a full-time counter.
Before fixing the problem, it helps to understand why counts go wrong in the first place. In most plants, the usual causes are:
Each of these is a small, ordinary mistake. Together, over a few months, they make the count meaningless.
Plates are typically identified by their dimensions and gauge, and plants often carry many combinations. Your inventory list should match how plates are stored and picked:
If your design software and your plate supplier use slightly different names for the same plate, pick one naming scheme and stick to it everywhere.
The single biggest improvement most plants can make is to deduct a job's plates when the job starts, not when someone gets around to it. Your truss design software already produces a pick list or material list with every plate the job needs. Use it.
When the yard pulls material for a job, upload or enter that pick list and take the plates off the count right then. Now your count reflects what's actually left for the next job, not what was there last month. If a pick list goes in twice or for the wrong job, undo it rather than adjusting counts by hand, so the history stays clean.
We go deeper into this in Pick lists and why deduct-on-start beats end-of-month counts.
Pick lists cover the plan. The floor covers reality. To keep the two close, make it easy to record the exceptions:
The goal isn't perfect paperwork. It's catching the big, repeated differences that make counts drift.
Full physical counts are slow and disruptive, and many plants only manage one or two a year. Cycle counting spreads the work out: count a few sizes every week, and the most important sizes more often.
A simple approach:
An accurate count is only useful if someone notices when it gets low. For each important size, set a low-stock level: the point at which you should order more. A reasonable starting point is the amount you typically use while waiting for a new delivery, plus a safety margin. (See Setting low-stock reorder points for plates and lumber for a worked approach.)
When a size drops below its level, the right person should see it without having to go looking. And once it's ordered, mark it on order, so nobody orders it a second time.
Receiving is where many errors start. When plates arrive:
It takes a few minutes, and it prevents the frustrating situation where the system says you have plates that never arrived.
Plates cost real money, and the cost changes over time. Recording a cost per piece for each size lets you see the value of the plate inventory on the floor at any time, and makes it much easier to spot when one size is tying up more cash than it should. It also helps when you estimate jobs, since plate costs are part of every truss.
Counts kept in one person's notebook are only as good as that person's memory and availability. Put the counts where the office, the yard lead and the plant manager can all see them, on a phone or a computer, and keep them current. When everyone can see that a size is low, someone usually does something about it.
Accurate plate inventory isn't about counting harder. It's about recording usage when it happens and checking the important sizes often enough that drift never gets far. Inventory & pick lists in Truss Plant Portal is built around exactly that routine.