The short answer: A job order is ready to send once it answers four plain questions. What will the person actually do? What disqualifies a candidate outright? What is the timeline forcing you to compromise on? Who signs off? Nonexecutive hires average 44 days to fill; skipping any of the four is usually why that clock resets.
This guide is written for private-sector employers working with a staffing partner to fill light industrial, professional, or IT roles, not for candidates or for public-sector procurement teams running a different hiring cycle.
In this guide:
· Why Does "We Can't Find Anyone" Usually Start With the Job Order?
· How Do You Turn a Vague Request Into One a Recruiter Can Actually Work From?
· What Job Orders That Fill Fast Have in Common
· When to Lock a Job Order Before It Ever Reaches a Recruiter
· The Numbers That Tell You a Job Order Actually Worked
· Frequently Asked Questions
· The Job Order Is Where the Fill Gets Decided
· References
Nonexecutive cost per hire has actually fallen, to $1,200 in 2025, a 27 percent drop since 2017 (SHRM, 2025 Recruiting Benchmarking Report). That should be good news for anyone requesting a hire. It usually is not. The number that decides a fast, sticking placement versus a redo three weeks later rarely shows up in a cost report. It shows up in what the job order named before it reached a recruiter.
Across the employers we work with, the requests that fill clean and the ones that fall apart do not look that different on the surface. Both name a title, a headcount, and a start date. The difference sits in what most requests skip: the daily work, the real disqualifiers, and which requirements are genuinely fixed versus habit. Candidates notice the same gap. Only 10 percent say job postings always match the reality of the role once they start (Monster, 2026). Seventy-eight percent say they are at least somewhat likely to abandon an application after reading one that reads as vague.
This guide covers why a bad fill usually starts at the request stage and the four questions a job order has to answer. It also covers what the fastest fills have in common and the numbers worth tracking to know whether your own requests are working.
Why Does "We Can't Find Anyone" Usually Start With the Job Order?
A fill falls apart at the request stage far more often than at the interview stage. Nearly nine in ten job seekers say vague language in a posting makes them ask more follow-up questions before committing to an interview (Monster, 2026). That confusion moves downstream, into a longer screening process built to recover what the request should have carried.
Ask a hiring manager whether the last request they sent was clear. The answer is almost always yes. Ask them to list the four or five details a recruiter needs to rule out the wrong candidate, and the answer gets vaguer fast. That gap, between a request that looks complete and one that actually is, is where most avoidable redos live. It is invisible from the hiring manager's side, because nothing about a title, a headcount, and a start date looks wrong.
The debrief on a bad fill almost always talks about the candidate: what they misrepresented, why a schedule conflict never came up, why they left inside a month. The job order rarely comes up, even though it usually decided the mismatch. Workers who have already hit vague or overly positive language in a posting this year, 81 percent of them, are not screening the next role generously (Monster, 2026). Thirty percent say vague language makes them actively less inclined to apply at all.
Trust runs the other way too. Seventy-six percent of workers trust a realistic job description more than one that reads as highly positive but vague (Monster, 2026). The specificity a job order forces is not a filter working against the employer. It gets the right person to apply.
Before widening the search, look at what the search started with. Does the job order give a recruiter enough detail to rule the wrong candidate out and give the right one a reason to say yes? See what a stronger job order should include.
How Do You Turn a Vague Request into One a Recruiter Can Actually Work From?
A request becomes workable once it names the daily work, the disqualifiers, and the real constraints, in that order. Allied OneSource runs every search on a fixed sequence: Listen, then Search, then Connect. Requests that skip the Listen step are the ones that turn into a second search three weeks later. Three components carry the weight.
1. Name the work a stranger could staff from, not the work you'd describe to a peer
A title and a shift pattern tell a recruiter almost nothing about what the job asks a person to do for eight hours. The detail that gets skipped, consistently, is the physical or situational reality of the role. What a person lifts, stands near, is exposed to, or has to tolerate. That is the detail an otherwise-qualified candidate discovers on day one and walks off over. A recruiter cannot infer it from a job title.
2. Separate what disqualifies a candidate from what you'd merely prefer
Most job orders list everything as required, because nobody wants to be the one who let an unqualified candidate through. The result is a request with no real filter in it. Three or four hard disqualifiers, stated as disqualifiers, with everything else marked a preference, gives a recruiter something to screen against instead of a wish list to guess at.
3. Say out loud what the timeline is forcing you to give up
Every rushed timeline trades something away: pay flexibility, schedule flexibility, or a skills requirement that would otherwise be non-negotiable. Naming that tradeoff in the job order, rather than discovering it three interviews in, is what keeps a fast fill from becoming a fast, wrong fill. "We need this filled in two weeks, so we're flexible on the certification timeline" tells a recruiter where to move.
Pull your last three job orders and check whether a stranger could staff the role from them alone. If they could not, that is the gap that turns into a redo, not the resume pile it produces. Stuck on what to add? Let's compare notes.
What Job Orders That Fill Fast Have in Common
The job orders that fill fast and stay filled name the same three things before the search starts: the real work, the real disqualifiers, and the real constraint. A request missing one does not fail outright. It just takes longer and costs more to recover, because the gap surfaces mid-search instead of at intake.
| What the request names | Fast-filling request | Slow-filling request |
|---|---|---|
| The daily work | Physical and situational reality, plain language | Title and shift only |
| Disqualifiers | Three or four, explicit | Everything read as required |
| The real constraint | Named up front | Discovered mid-search |
| Sign-off | One named person, before the search starts | Assumed, surfaces late |
The lead-in above the table names what it decides: whether a request was built to be searched against, or built to look thorough. Candidates reward the difference. Eighty-five percent say they are more likely to apply when an employer clearly outlines a role's challenges and expectations, rather than smoothing them over (Monster, 2026). The fastest fills we see are rarely the ones with the biggest pay band. They are the ones where the hiring manager put the one non-negotiable in writing. That single clear line lets a recruiter stop second-guessing the rest of the request. The offensive play most employers miss: ask a current top performer what a posting for their own job leaves out. That five-minute answer usually surfaces the daily-work detail nobody wrote down.
When to Lock a Job Order Before It Ever Reaches a Recruiter
A job order should be locked, not just drafted, at three separate points between the manager's desk and the first candidate screen. Skipping any one of them is how a request quietly drifts from what the manager intended. Nobody notices the drift until the wrong resumes start arriving.
1. Before it leaves the requesting manager. The manager who knows the work checks the daily-work section against what the role requires this quarter, not what it required when the template was last updated.
2. Before it reaches a recruiter. A second reader, someone who was not in the room when it was written, reads it cold and flags anything that is a preference dressed up as a requirement.
3. Before the first candidate is screened. The disqualifiers and the named constraint get confirmed once more, because a fast-moving timeline is exactly when a written tradeoff quietly gets dropped.
Automate the timing, never the human moment. A reminder that a review is due, or that a request has sat unconfirmed for three days, is worth automating. Whether the daily-work section is accurate for this specific opening stays a judgment call, however fast the request needs to move.
A complete job order names the disqualifiers before the nice-to-haves. Pull the one you sent last: does it? Want a second read on it before it goes out again? Ask us what we'd flag.
The Numbers That Tell You a Job Order Actually Worked
Three numbers show whether a job order is doing its job. How long did the request sit before reaching a recruiter? How many candidates got screened out at the disqualifier stage instead of the interview stage? And how does the search compare to the 44-day nonexecutive benchmark (SHRM, 2025)? That benchmark alone only says whether a search was slow.
Read against where candidates got screened out, it says why.
If a search runs long but most candidates were screened out at the disqualifier stage, the job order is working; the market is simply tight. If most get screened out in interviews instead, the job order likely never named the real disqualifiers. The recruiter has been doing at intake what the request should have done. Extra-large organizations run longer still, a 61-day median for nonexecutive roles (SHRM, 2025), which makes the diagnostic more useful the bigger the org gets, not less.
Cost tells a second part of the story. Executive cost per hire now sits at $10,625 against $1,200 for nonexecutive roles, a gap that has widened every measured year since 2017 (SHRM, 2025). Track these three numbers before the next job order goes out, not after the current one closes. A hiring manager who reviews time-to-fill only after a bad search cannot separate the market, the request, and the interview process. By then the three have blurred together.
Frequently Asked Questions
What actually goes in a job order?
A job order names the daily work in plain language, the hard disqualifiers separate from preferences, the timeline and what it forces you to trade off, and who signs off before it reaches a recruiter. A title, a headcount, and a start date alone are a request, not a workable job order.
Is a job order the same thing as a job posting?
No. A job posting is the public, candidate-facing version, written to attract applicants. A job order is the internal request that tells a recruiter what to screen for, and it usually carries detail, like hard disqualifiers, that never appears in the posting.
Why do job orders that "look fine" still produce the wrong hire?
Looking complete and being searchable are different tests. A request naming a title, headcount, and start date reads as complete to whoever wrote it. It becomes searchable once it also names what disqualifies a candidate and what the timeline forces you to give up, and most requests never get that far.
How specific does a job order need to be to work?
Specific enough that someone unfamiliar with the role could screen a stranger against it without calling the hiring manager to ask what was meant. That is a higher bar than most requests clear, and it is the bar a recruiter works against whether it is written down or not.
Who should sign off on a job order before it goes out?
Someone other than the person who wrote it, ideally someone who was not in the room when it was drafted. A second, cold read catches a preference written as a requirement, and it is the checkpoint most requests skip because it feels like it slows things down.
The Job Order Is Where the Fill Gets Decided
The fastest, stickiest fills trace back to the same starting point: a job order that named the real work, the real disqualifiers, and the real constraint before a recruiter ever picked it up. Nonexecutive time-to-fill runs a median of 44 days against a cost per hire that has fallen to $1,200 (SHRM, 2025).
Neither number moves in the right direction when the request itself is doing the guessing.
Writing that kind of job order is yours. It takes the person who knows the work, a few extra minutes, and a willingness to write down the tradeoff a rushed timeline is already making anyway. Making it a fill is what we do: matching it against a candidate pool, screening against the disqualifiers you actually named, and telling you honestly when a timeline asks for something the market cannot deliver.
References
1. "The State of Recruiting 2025: Insights to Maximize Recruitment from SHRM's New Benchmarking Report." SHRM. Published 2025. Verified live 2026-09-18.
2. "Vague Job Descriptions Are Costing Employers Candidates." Monster (Pollfish survey of 1,060 U.S. employed workers, July 14 to 15, 2026). Published July 2026. Verified live 2026-09-18.
