Board foot has been used for decades in component manufacturing, and it still serves its purpose for sales reporting, legacy KPIs, and corporate roll ups. There is no need to abandon it. But for scheduling, pricing, and determining how much work a plant can actually handle, board foot alone will always fall short. It cannot show the true labor content of the work. That is where engineered work minutes become essential. Board foot and work minutes can coexist—because each belongs in a different decision lane. This article shows a practical coexistence method: keep board foot for reporting, add engineered minutes for decisions, and prove minutes in parallel without disrupting current routines.
Work Minutes Reveal What Board Foot Cannot: the real setup, handling, and process time required at each work center under the conditions the job will run. They turn load into something measurable, predictable, and grounded in actual behavior, not assumptions. They also expose variation hidden inside similar looking BF jobs, such as automation availability, run length impacts, manual handling, and the “If conditions” that change how work is performed.
Let Board Foot Do What It Does Best: Board foot is still a useful measure of volume. It works for sales reporting, legacy KPIs, and corporate rollups because it’s consistent and widely understood.
Work minutes serve a different purpose. Minutes exist to run the plant: loading, scheduling, capacity planning, and protecting margins by aligning commitments to real labor content.
When leaders use board foot to make planning promises, the schedule becomes opinion. When they use engineered minutes for planning and keep board foot for reporting, both measures stay honest and both remain valuable.
The Coexistence Method: In practice, both metrics can coexist smoothly. Most wood truss software can be set up to run work minutes alongside existing board-foot practices, so you can test, compare, and validate minutes in real production without disrupting current reporting, KPIs, or quoting routines. That parallel run is often the fastest way to prove accuracy and build trust because the numbers are evaluated against actual performance, not theory. Board foot can stay in its traditional role, while work minutes guide the operational decisions that determine throughput, schedule stability, and margin protection. In most plants, trust builds quickly because minutes are judged against actual performance, not opinion.
Where Teams Go Wrong When They Try to Add Minutes:
- The most common failure is treating work minutes like a replacement project instead of a parallel run. That turns a practical improvement into a culture fight.
- Using broad averages is another failure. If minutes don’t reflect real methods and real “If conditions,” teams quickly learn they can’t trust the number.
- Skipping validation is next. If minutes are not tested against actual production, they remain theoretical and get dismissed the moment pressure hits.
- Using paid time as available time is another common miss. If the available-minutes number can’t be defended on the floor, the plan will never match reality.
The fix is not complicated: keep board foot in place, run minutes in parallel, and let real production validate what’s true.
Why Minutes Bring Clarity: When board foot stays in its reporting lane and minutes take the planning lane, “busy” becomes measurable and decisions become calmer.
Defined work minutes capture the effort at each work center for a defined method under defined conditions, with appropriate allowances. Capacity planning then compares required minutes to available minutes to confirm whether the system can actually carry the load.
Most plants struggle because work content is not stable—mix shifts, setups vary, and staffing fluctuates. Plans built on averages can look reasonable on paper while the floor experiences congestion and missed commitments. The issue is usually not performance; it’s overload that minutes can reveal. Board foot did not fail—it was never designed to carry planning responsibility.
When planning is anchored in defined minutes, you stop over-releasing work, you protect the true constraint, and you stabilize cadence while reducing overtime spikes, expediting, and quality drift.
How to Prove Minutes Without Disrupting Board Foot: Start with a planning window your team already lives in—daily or weekly—and run minutes as a parallel “truth test,” not as a replacement for existing reports.
Then calculate true available production time—not paid time—by subtracting breaks, startup losses, routine stoppages, and planned maintenance. If that number can’t be defended on the floor, it will undermine trust in minutes before minutes ever get a fair test.
Next, translate demand into required minutes using standards that reflect how the work is actually performed. This is where “If conditions” prevent standards from drifting into averages by selecting the correct time standard as reality changes. The goal is practical accuracy that holds under real “If conditions,” not a fragile average that collapses under pressure.
For example:
- If a setup change is required, the setup burden changes with run length.
- If automation is available, use the automated standard.
- If automation is not available, use the manual standard tied to those conditions.
With credible minutes, planning becomes straightforward: compare required minutes to available minutes at the constraint. This is where coexistence pays off—board foot continues to describe volume, while minutes tell you whether the constraint can actually carry that volume this window.
Building condition-based work minutes requires solid industrial engineering capability, especially in mixed automation where variation is uneven. That’s what TDC provides engineered standards with practical “If conditions” that hold up in real production so leaders can price, schedule, and load the plant with confidence.
A Simple Proof Loop That Builds Trust: Start with the constraint work center and one upstream step. Run engineered minutes in parallel while board foot reporting remains unchanged.
Each week, compare planned minutes to what actually happened and correct only what changed in the method, conditions, or allowances. Do not “force-fit” minutes to match a bad week.
When the team sees minutes reliably predict load and completion, expand minutes to the next work center. Trust comes from disciplined validation, not from asking people to believe.
When minutes guide planning decisions while board foot remains the reporting measure, profitability improves for practical reasons: better job selection, steadier schedules, fewer disruptions, less overtime and expediting, and more predictable throughput. Even modest margin protection adds up quickly because decisions are finally anchored to the true labor content of the work.
Scheduling as a Leadership Behavior: Board foot can’t enforce release discipline, but minutes can, because minutes show when you’ve already spent tomorrow’s capacity today. Once the constraint plan is honest, release must match it. Work must be released at the rate the constraint can complete it, not the rate that keeps upstream teams busy. When required minutes exceed available minutes, leaders must decide what to protect, what to delay, and what to adjust.
This is where Swap Not Stack becomes an essential habit. When a hot job appears, many operations simply stack it on top of the existing release, expecting the floor to complete tomorrow’s work in today’s minutes. That approach creates overtime, shortcuts, and missed commitments.
Swap Not Stack keeps the system stable: if a new priority enters, something of equal minutes must move out or move to the next window. This protects both the people doing the work and the commitments made to customers.
Swap Not Stack is from my pending new book, “Lean Manufacturing Made Obvious for Leaders,” being published this spring.
Bottom Line With Changing Markets: In changing markets, the margin for error shrinks fast. Demand shifts, mix shifts, staffing shifts, and the jobs that used to “average out” start punishing the schedule and the P&L. Board foot can still describe volume, but only engineered minutes can tell you what that volume will cost in time at the work centers that govern throughput. When leaders keep board foot for reporting and use validated minutes for planning, they protect the constraint, make tradeoffs earlier, and keep profit from leaking out through overload, overtime, and quiet drift.
If this article resonates, here’s the practical next step. At Todd Drummond Consulting (TDC), I help truss and component manufacturers replace “pretty good averages” with defensible, engineered work minutes that hold up when mix, run length, staffing, and automation availability change. My Truss Manufacturing Time Standards (Man-Minutes) have been tested and validated inside 100+ wood truss operations and are built using proper industrial engineering motion and time study methods, not vendor benchmarks or guesswork.
When your standards are grounded in real methods and “If conditions,” you can convert demand into required minutes, load the constraint honestly, and protect schedule stability without living in overtime and expediting. Client feedback is available on the Testimonials page, including measurable gains and clear operational direction from operators and owners.
Website: www.todd-drummond.com • Phone (USA): 603-748-1051
E-mail: todd@todd-drummond.com • Copyrights © 2026