Job order history: what years of client requisitions reveal

What does a job order record contain?#

A job order record contains a client's request for talent plus everything the firm learned while working it: the role, the requirements, the commercial terms, each status change and the outcome. In Bullhorn, JobDiva, Crelate and similar ATS platforms the core fields are structured, while the most revealing detail often sits in descriptions and activity notes.

Each field on its own is ordinary. Kept consistently over years, together they become a record of how a group of employers hired, what they asked for and what actually happened.

• 1Client company, department and hiring manager.
• 2Title, description, and required and preferred skills.
• 3Location, on-site or remote status, and shift.
• 4Employment type: contract, contract-to-hire or direct hire.
• 5Pay rate and bill rate for contract roles, or fee terms for direct hire.
• 6Number of openings, priority, and the recruiter and account manager assigned.
• 7Open, on-hold and closed dates, with a close reason.
• 8Channel: direct client, MSP program or VMS posting.

What can years of job orders tell a staffing firm?#

Years of job orders tell a staffing firm where its fills really come from, how demand shifts and which clients it serves well. Many firms stop at a fill ratio in a quarterly report, even though the history supports much sharper questions.

The analyses are only as good as the normalization behind them. Role families have to be mapped from many free-text titles, and rates typed as text or mixing hourly and annual units need cleaning before any trend means anything.

Why requirement text matters more than the job title#

Requirement text matters more than the job title because titles stay stable while the work underneath them changes. A role a client has always called business analyst can move over several years from spreadsheet reporting to SQL and then to a named BI platform, and only the description records that shift.

Edits to an open job order are even more telling. When a client drops a degree requirement after rejecting several submittals, or adds a certification midway, the job order captures a hiring decision in progress. Firms that overwrite descriptions instead of keeping versions lose that signal, so check whether your ATS stores edit history or only the latest text.

A practical way to read requirement text at scale is to tag each order with a controlled list of skills and tools, then compare the tags year over year by client and role family. The tags do not need to be perfect; consistent tagging across the whole history matters more than precision on any single order.

Which parts of a job order are client-confidential?#

The client-confidential parts of a job order are those that reveal a client's identity, economics or internal plans. Your firm holds them because the client trusted you with them, and MSAs and MSP program terms often say so in writing.

For internal analysis by your own staff, these fields are normally fine to use. The question changes when job order history leaves the firm, whether in a benchmark report, a sale-process data room or a data license, and each of those uses calls for its own review.

Where old job order data usually breaks#

Old job order data usually breaks at the seams: system migrations, inconsistent recruiter habits and statuses nobody closed. Spotting these problems early tells you which analyses you can trust and how much cleanup any outside use would require.

None of these flaws makes the history worthless. They do change which conclusions hold up, and they are cheaper to document now than to explain later to an acquirer or a data buyer.

• 1Duplicate orders created each time a client reposted the same role.
• 2Orders left open indefinitely because nobody set a closed status.
• 3Blank or catch-all close reasons such as other.
• 4Rates typed into description text instead of rate fields.
• 5History truncated or flattened during a past ATS migration.
• 6MSP orders imported in bulk with thin, templated descriptions.

Illustrative: an accounting and finance staffing firm reads its own history#

Illustrative: a fictional accounting and finance staffing firm has kept job orders in the same ATS since its founding, across direct clients and two MSP programs. Before a strategy offsite, the owner asks operations to normalize role families and close reasons across the full history.

The analysis shows that payroll and accounts payable orders fill quickly with direct clients but stall inside one MSP program, where requirement edits pile up and orders end as cancelled. It also shows audit roles steadily adding data analytics tools to their requirements. The owner moves recruiter time toward direct accounts, builds a bench of finance candidates with analytics skills, and makes the close reason a mandatory field on every order.

How SourceX looks at job order history#

SourceX looks at job order history as workflow data: a request, the work done against it and a dated outcome. Under the SourceX Enterprise Data Value Framework, long and consistent history supports scale and recency, recruiter-written requirement edits and close reasons add human-generated signal, and niche specialties add uniqueness.

The same framework counts preparation cost and privacy burden against net value, which is why client names, rates and confidential searches are generalized or removed before anything is shared. A first fit check needs only metadata: the ATS name, years of accessible history, record families and known client restrictions.