Job Requisition Data Hygiene: Standardizing IDs, Statuses, and Ownership

Clean Requisition Data Keeps Recruiting Moving

A job requisition connects hiring approval, job advertising, candidate sourcing, and reporting. When its ID changes between systems, its status is unclear, or its owner is missing, routine recruiting work becomes harder to coordinate.

For employers managing multiple locations, advertising channels, or recruitment partners, data hygiene is an operational discipline. Consistent requisition records help teams avoid duplicate postings, route questions quickly, and understand which openings still need attention.

Start with three foundations: stable IDs, clearly defined statuses, and explicit ownership.

Give Every Requisition a Stable Identity

Separate the identifier from the job description

Assign each requisition a unique ID that remains unchanged throughout its lifecycle. Avoid relying on job titles, hiring manager names, or locations as identifiers. Those details can change, and different openings may share them.

Keep the internal requisition ID distinct from job board posting IDs. A single requisition may generate several advertisements, each with its own external reference. Recording that relationship makes it easier to update or remove the correct listings.

When reopening a position, establish a rule for whether to reuse the existing requisition or create a new one. Apply that rule consistently and preserve the history rather than overwriting it.

Define a minimum record

Before a requisition reaches a posting or sourcing team, require a small set of reliable fields:

• Unique requisition ID and approved job title
• Department, location, and work arrangement
• Current status and date of the latest status change
• Accountable requisition owner and assigned recruiter
• Approval reference and target posting channels
• External posting IDs, links, and relevant activity dates

Keep required fields practical. A shorter, consistently maintained record is more useful than a detailed form that teams routinely bypass.

Preserve IDs during transfers

Treat requisition IDs as text when exporting spreadsheets or moving records between systems. Otherwise, leading zeros may disappear. Establish one format and validate incoming files against it before posting begins.

For example, requisition REQ-004218 might connect to three advertisements. Maintain a separate row for each advertisement, including its channel, external ID, publication date, and removal date. This lets a coordinator retire one listing without mistakenly closing the underlying opening.

Make Statuses Describe Real Decisions

Use a controlled vocabulary

Choose a limited set of statuses, such as Draft, Pending Approval, Open, On Hold, Filled, and Canceled. Document what each means, who can apply it, and what action follows.

For example, Open might mean the requisition is approved for recruiting activity. On Hold should trigger a review of active advertising and sourcing instructions. Filled and Canceled should prompt posting cleanup and record retention according to applicable requirements and organizational policy.

Keep requisition status separate from advertisement status. An opening can remain active while one advertisement expires. Mixing those concepts can produce misleading reports and unnecessary reposting.

Record the reason and next action

Pair status changes with a brief reason, effective date, and action owner. If a warehouse opening moves to On Hold, specify whether sourcing should pause, paid advertising should stop, and existing listings should be removed or reviewed. Do not leave partners to infer instructions from the status label alone.

Where systems use different labels, document a mapping. A partner's “Active” should translate to your “Open” only when both represent the same approved recruiting activity.

Assign Ownership Across Every Handoff

Name an accountable person

Each requisition needs one accountable owner, even when several people perform the work. Clarify who approves changes, who updates the system of record, and who communicates those changes to recruiting partners.

This matters across recruitment process outsourcing, Craigslist job posting, resume search, manual job posting, and recruitment media buying. Teams need the same reference point to prevent stale instructions from spreading across channels.

For OFCCP-related posting workflows, consistent records can support documentation and review. Data hygiene alone does not establish compliance; applicable obligations, posting procedures, and retention practices still require appropriate evaluation.

Make handoffs verifiable

Designate a backup when the owner is unavailable. For each posting request or change, include the requisition ID, approved instructions, requested completion date, and recipient. Ask the receiving team to confirm completion and return the relevant posting references.

A manual posting assignment, for instance, is not fully reconciled when someone says “posted.” The record should identify where the advertisement appeared and which approved version was used. Resume search assignments should likewise reference the requisition and current location, schedule, and qualification requirements.

Build a Lightweight Review Routine

Review active requisitions regularly for missing owners, duplicate IDs, outdated statuses, and advertisements that no longer match hiring needs. Assign exceptions to a named person and track their resolution.

Use the findings to improve intake rules and handoffs—not simply to clean up the same errors repeatedly.

Use a practical exception checklist

During each review, ask:

• Does every active advertisement map to an approved requisition?
• Do closed requisitions still have live listings or advertising spend?
• Are channel references and completion confirmations recorded?
• Have ownership changes reached all recruiting partners?
• Are unresolved exceptions assigned a due date?

Choose a review frequency that reflects hiring volume and posting activity. Track recurring error types rather than just total corrections. If missing posting IDs repeatedly cause cleanup delays, make those IDs part of the completion checklist. If status updates arrive late, clarify who sends the notification and when.

Contact Redwood Technology Solutions to discuss how clearer requisition data can support your recruitment operations, job posting workflows, and advertising coordination.