How to Write a Trades Staffing Order That Actually Gets Filled Fast

Why "Send Me an Electrician" Doesn't Work

Craft is not a job description. An electrician who's spent three years pulling low-voltage cable in commercial tenant buildouts is not the same worker as one who's been doing 480-volt motor control and PLC troubleshooting in a plant. Both will answer to "electrician." Only one of them should be sent to your panel swap.

When an order comes in as just a craft label, a dispatcher fills to the label, not to the job. That's not laziness — it's the only information they were given. The result is either a slow fill (because the coordinator has to call you back to ask what you actually meant, and that phone tag eats the hours you needed the crew on-site) or a fast but wrong fill, where someone shows up with the right ticket and the wrong experience, and you've burned a day figuring that out on your own dime.

The order also drives comp code assignment on the agency side. If the scope you describe doesn't match the duties the worker actually performs once they're on your site, that mismatch becomes a classification problem later, not a staffing problem now. A precise scope line protects you on both ends.

The Fields a Real Order Needs

A workable order has eight things in it, not two. First, craft and sub-specialty — not "pipefitter" but "pipefitter, Schedule 80 PVC and copper, no welding required." Second, license or certification requirements, stated as hard requirements versus preferred — a journeyman card is a hard requirement; OSHA 30 might be preferred but trainable in 24 hours. Third, the comp code and a one-line description of actual duties, so classification matches reality from day one. Fourth, tools and PPE — who's bringing what. A worker showing up without a tool belt they were never told to bring costs you an hour of downtime that isn't their fault.

Fifth, start date and shift, including whether it's a hard start (crane is booked, inspector is coming) or a soft start with flex. Sixth, expected duration and the honest likelihood of extension — agencies staff differently for a two-week punch list than a six-month rough-in, and telling them which one it is affects who they pull from their bench. Seventh, site orientation and badge logistics — some GC sites require a half-day safety orientation before a worker can touch tools, and if that's not flagged up front, day one becomes an orientation day instead of a production day. Eighth, a single decision-maker and escalation contact — one name the agency calls if something's wrong on-site, not "whoever's around."

None of this needs to be a formal document. It's five minutes on the phone or in a text thread. But it needs to happen before the order goes out, not after the wrong person shows up.

A Worked Example: Same Job, Two Orders

Say you need an electrician for a panel upgrade at a distribution facility, starting Monday. Order one: "Need an electrician Monday, 2-week job." That order gets filled — probably by end of day — with a licensed electrician who is perfectly competent and has never worked in an occupied industrial facility with lockout-tagout procedures specific to that site. You lose the first morning walking them through your LOTO program, and if the panel work turns out to need arc-flash-rated PPE they didn't bring, you lose more than a morning.

Order two: "Journeyman electrician, industrial panel and switchgear experience, comfortable with facility LOTO procedures, must arrive with Category 2 arc-flash PPE, 2-week job with likely extension to a related feeder run, start Monday 6 a.m., site safety orientation required day one — budget an extra 45 minutes, point of contact is [name/number] for anything on-site." That order takes the coordinator longer to fill because it's a narrower pool, but it's filled with someone who can be productive by 8 a.m. instead of noon, and the extension detail means the same worker might already be lined up for the feeder run instead of you starting the search over in two weeks.

Name Requests and Rehire History

The fastest fill of all is a name request — asking for a specific worker who's been on your site before. They already know your safety orientation, your foreman, your site rules, and in many cases your equipment. If you've had a good experience with someone, say so to your staffing coordinator and ask that it be flagged in their file. Most agencies track worker performance by client; a documented preference shortens the whole process the next time you place an order, because the coordinator isn't starting from zero.

Building this kind of history across a handful of projects is one of the most underused levers a GC or plant manager has. It converts staffing from a transactional "who's available today" exercise into something closer to a bench you're quietly building for yourself, without carrying the workers on your own payroll between jobs.

Where Over-Specifying Backfires

There's a failure mode on the other end too. An order that demands five certifications for a task that genuinely needs two, or specifies ten years of experience for work a solid three-year journeyman handles fine, isn't more careful — it's unicorn hunting. It shrinks the available pool to almost nobody and slows the fill down for no real safety or quality benefit.

The fix is separating must-haves from nice-to-haves explicitly in the order itself. A must-have is something that creates real risk or a hard site requirement if missing — a specific license, a confined-space cert, arc-flash PPE. A nice-to-have is preference — prior plant experience, a specific brand of equipment familiarity. Give the coordinator both lists, and let them make the tradeoff call on the nice-to-haves when speed matters more than a perfect match.