There is no single lumberyard org chart. A counter salesperson may answer a phone, check stock, build a quote, enter an order, coordinate will-call, and protect a long-standing account in the same hour. The labels vary. The operating responsibilities still have to be owned.
This guide maps the work as states and handoffs instead of treating a job title or software screen as the process. It is a candidate model based on public role context, trade reporting, and Second Counter’s discovery framework—not an official standard or a claim about how often each pattern occurs.
Keep the scope honest
Federal labor data can describe occupational categories in the broader building-materials dealer industry, but that industry includes businesses beyond lumberyards. Trade articles can show named operator examples, but they do not prove a universal staffing pattern. The only reliable map for a particular yard comes from tracing its own recent work.
The operating loop
- Request arrivesA phone call, voicemail, email, text, web form, PDF, image, or counter conversation creates work. Capture the customer, account, request, callback, urgency, and original source without promising an answer that the record cannot support.
- Request is triagedSeparate a stock question, order, simple quote, takeoff or complex quote, delivery issue, credit matter, technical question, or named-person request. Answering is not the same as resolving.
- Information is qualifiedCollect the item, species, grade, dimension, length, quantity, unit, branch, job, date, delivery or will-call choice, and any plan or configuration details that apply. Flag ambiguity instead of guessing.
- Price or quote is preparedSimple price, configured product, special order, and plan-based takeoff do not require the same work. Keep the source data, assumptions, revision, terms, tax, freight, availability, and validity visible.
- Authorized review releases a commitmentA draft becomes customer-facing only through the yard’s rules. Credit, margin, substitution, technical, and availability exceptions go to the appropriate role.
- Customer response changes stateThe quote may become an order, require revision, remain open, be postponed, be duplicated, be lost, or be suppressed from follow-up. The disposition and next action need a named owner.
- Order moves to fulfillmentConfirm the approved version, quantities, account, PO, tax, credit or payment state, inventory context, and delivery or will-call details before release.
- Physical work confirms realityPicking, loading, will-call readiness, route status, site conditions, unloading, returns, and claims depend on people closest to the material. A system state cannot replace required physical or safety confirmation.
Roles are ownership—not just titles
| Operating responsibility | Work it may own | Typical escalation |
|---|---|---|
| Counter / inside sales | Request intake, triage, stock and product questions, simple pricing, quote ownership, order entry, and customer updates. | Counter lead, branch manager, specialist, credit, or operations. |
| Estimator / product specialist | Plans, takeoffs, configured products, technical selection, assumptions, revisions, and specialist-reviewed quotes. | Supplier, qualified designer or engineer where applicable, sales manager, and customer approval. |
| Outside sales / account owner | Named-account context, relationship rules, open-quote decisions, next action, and protected communication. | Sales manager, credit, or owner/GM. |
| Inventory / purchasing | Availability qualification, shortages, open purchase orders, special orders, supplier confirmation, and candidate alternatives. | Product specialist, branch manager, supplier, or customer. |
| Credit / accounting | Terms, limits, holds, past-due status, deposits, approved payment path, refunds, and reconciliation. | Credit manager or owner/GM under yard policy. |
| Yard / operations / dispatch | Released pick and load work, physical status, will-call readiness, routes, driver communication, delivery changes, and operational exceptions. | Operations manager, driver, or safety authority. |
| Owner / GM / branch manager | Policy, workload, unowned work, aging, exceptions, role boundaries, approvals, and cross-functional decisions. | Named functional owner, system owner, legal/safety specialist, or outside authority as needed. |
One person may wear several of these hats. That makes the boundary more important, not less. The question is which role the person is acting in when they see private data, approve a commitment, change a record, or direct physical work.
Track states, not activity
“Called customer,” “sent email,” and “opened quote” describe activity. They do not prove that the request has a responsible owner or a safe next state. A useful operating view distinguishes:
- received, acknowledged, and triaged;
- waiting for customer, estimator, purchasing, supplier, credit, or approval;
- drafted, reviewed, released, sent, and revised;
- open, won, lost, postponed, duplicate, abandoned, or suppressed;
- order drafted, held, approved, released, picked, physically confirmed, delivered, returned, or under claim;
- blocked by stale data, unsupported access, conflict, safety condition, or missing authority.
Each state needs an owner, timestamp, source, and allowed next actions. Otherwise a dashboard can make work look visible without making it accountable.
The exceptions reveal the real operation
A clean order tells you less than an exception. The operating design appears when the quoted item is short, the account is past due, the customer wants a substitute, the quote version changed, the site is unsafe, the driver cannot unload, or the POS/ERP disagrees with physical reality.
Trace one recent exception
Start with the original request. Record every person, system, handoff, wait, decision, edit, customer message, and final state. Then ask where ownership became unclear, which data had to be checked manually, and which decision could not safely be delegated.
That trace provides the foundation for a process change, software evaluation, or carefully bounded automation. Without it, teams risk improving a diagram instead of the work.
Where software and AI fit
The software landscape guide separates the records held by POS, ERP, quoting, CRM, ecommerce, takeoff, dispatch, and workflow layers. The AI control guide separates observing, structuring, coordinating, preparing, and executing within explicit authority.
Across both maps, the same rule applies: technology should appear after the operating job is understood. It can help preserve context and carry repetitive work, but it should not invent a price, stock state, approval, relationship rule, route, or safety decision.
Workflow review questions
- What happened to the last five calls received while the counter was busy?
- Which request types exist here, and who owns each one?
- How does every acknowledged quote request receive an owner and next step?
- Where does takeoff end and pricing responsibility begin?
- Which quotes should be followed up, when, by whom, and which should not be touched?
- What confirmations and approvals are required before a quote becomes an order?
- What must be physically verified before a will-call customer is told to arrive?
- Which delivery changes require dispatcher or driver judgment?
- Who owns each failure class when data or system access is unavailable?
Sources and limitations
- U.S. Bureau of Labor Statistics, Building Material and Garden Equipment and Supplies Dealers: NAICS 444, 2025. This broad industry includes home centers, hardware, garden, and other retailers.
- U.S. Bureau of Labor Statistics, Building Material and Supplies Dealers — May 2023 OEWS, published 2024. Estimates are broader than lumberyards and subject to OEWS methods and sampling limits.
- U.S. Bureau of Labor Statistics, National Employment Matrix — Industry 444100, 2025. Projected values are not current headcount.
- OSHA, Lumber and Building Material Dealer Industry — Hazards and Solutions. Not a complete compliance program.
- LBM Journal, The Employee Balancing Act, March 14, 2025. A non-random operator panel; individual observations are not universal metrics.
- LBM Journal, Technology makes it easier to decipher data and manage business, November 15, 2024. Trade context; vendor examples require independent verification.