October 2, 2026
An evergreen requisition can help a business hire repeatedly for the same kind of work. It can also become a job-shaped inbox that nobody truly owns. Applications continue to arrive, an old hiring manager remains attached to the record, and recruiters cannot tell whether the business needs three people this month or merely wants a pool for later. Candidates see an open job, but the organization may not be ready to make a decision.
The answer is not to ban continuously open requisitions. It is to give each one an operating owner, a current demand signal, and an expiration rule. A useful evergreen requisition represents recurring, approved work. It should not conceal uncertain headcount, replace workforce planning, or keep applicants waiting without a genuine hiring path.
This guide explains how to review ownership of evergreen requisitions. Human-resources, finance, legal, privacy, and operational leaders should adapt the controls to the organization's systems, policies, and jurisdictions.
Decide whether the role is truly recurring
Start with hiring behavior, not the label in the applicant tracking system. A role may be suitable for an evergreen route when the work and minimum qualifications remain substantially stable, hiring occurs throughout the year, and the organization can identify a repeatable decision process. High volume alone is not enough.
Ask the operating team to show recent starts, approved near-term demand, typical locations or shifts, and the point at which a candidate can enter a real selection process. A distribution network hiring the same warehouse role every month may have a defensible recurring need. A business that might open a new site next quarter has a forecast, not necessarily an active vacancy.
Separate three states that are often mixed together:
- Hiring now: approved openings exist and qualified applicants can move promptly into selection.
- Building a disclosed future-interest pool: no immediate opening is promised, but candidates knowingly choose to be considered for later matching.
- Paused: neither active selection nor responsible pool engagement is occurring, so the public posting and associated campaigns should stop.
Those states need different candidate language and different measures. Calling all three "open" makes the recruiter appear slow when the underlying problem is that the business has not made a demand decision.
Name one business owner and one recruiting owner
Shared ownership often means unowned work. Assign a business owner who can confirm demand, staffing location, schedule, pay inputs, and selection capacity. Assign a recruiting owner who manages the applicant flow, service commitments, and candidate communication. Record backups for both roles.
The business owner should be a role with decision authority, not merely the person who originally asked for the requisition. If a regional operations leader owns hiring across several sites, the record can name that role and identify which local managers may request candidates. The recruiting owner should know where the boundary lies: recruiters can administer an approved process, but they should not infer headcount or invent a start date because an old requisition is still active.
Create an ownership card containing:
- accountable business role and backup;
- recruiting owner and backup;
- covered job family, locations, and shifts;
- approved demand source and its review date;
- current hiring state;
- selection-panel or hiring-manager capacity;
- candidate response commitment; and
- next renewal or closure date.
Keep the card close to the requisition rather than in a separate spreadsheet that recruiters may not see. Where sensitive planning data must remain restricted, link to the controlled source and show only the decision needed to operate the requisition.
Reconcile the requisition with actual demand
An evergreen record needs a regular demand reconciliation. Pick a cadence appropriate to the hiring cycle:weekly for fast-moving hourly hiring may be reasonable, while a lower-volume specialist role may use a longer interval. The important point is that renewal requires evidence, not silence.
At each review, compare four numbers: approved openings, accepted offers not yet started, candidates in active selection, and recruiting capacity available to handle additional applicants. These figures answer different questions. Ten approved openings do not mean ten new candidates are needed if eight accepted offers are preparing to start. Conversely, a large applicant pool does not prove that the employer has enough interview or onboarding capacity to move people fairly.
Consider a field-service company with an evergreen technician requisition covering three districts. District A needs two people immediately, District B has filled its opening, and District C may receive budget approval next month. One combined "open" status directs applicants into a queue without a clear destination. The review should activate District A, close or pause matching for District B, and describe District C only as future interest if the organization has approved that practice and can communicate it honestly.
Demand changes should be dated. Do not overwrite last week's figure without retaining who supplied the new figure and what approval it references. That history helps distinguish ordinary forecast movement from a requisition that has drifted for months without a decision.
Put capacity ahead of application volume
Evergreen postings can generate more applications than a team can responsibly review. Leaving the funnel unrestricted may improve a top-line applicant count while increasing delayed responses, inconsistent screening, and candidate abandonment.
Set an intake control tied to the actual selection path. If the team can review 80 applications and conduct 20 interviews in a week, it should not invite hundreds more people into an "active" process without a plan. Options include narrowing the posting to the locations and shifts with real demand, pausing paid promotion, setting a disclosed application window, or moving willing applicants into a separately governed future-interest pool.
Do not use an automated cutoff as a substitute for checking accessibility or accommodation routes. Make sure applicants can obtain help with the application process and that qualified owners review any exception. The EEOC's guidance for employers on recruitment and hiring is a useful federal starting point for reviewing hiring practices; local requirements and the facts of a particular process still need qualified review.
Capacity includes onboarding, not just interviewing. If trainers, equipment, background-processing support, or start-date slots are unavailable, continuing to accelerate candidates may only relocate the wait. Record the limiting step and the person responsible for resolving it.
Tell candidates which process they entered
Candidate messages should reflect the current state of the requisition. For active hiring, state the relevant location or schedule, the next selection step, and a realistic update date. For a future-interest pool, explain that there is no promise of an immediate opening, how matching may occur, how long information will be retained under the organization's rules, and how the person can update preferences or leave the pool.
Never allow an old automated message to announce that a recruiter will respond in two days when the requisition has moved to a pool state. Review acknowledgements, nurture sequences, interview scheduling, and disposition messages whenever the state changes.
Candidates also need an exit from ambiguity. If demand disappears after someone has begun interviewing, give the person a direct update rather than quietly moving the application back into an evergreen pool. Ask for permission before considering the person for a materially different location, shift, or role. Interest in one opening should not be treated as blanket consent for unrelated recruiting outreach.
The Federal Trade Commission's business guidance on protecting personal information recommends understanding what information a business holds, keeping only what it needs, protecting it, and disposing of it securely. Use those principles with the organization's privacy and records owners when setting retention and access rules for a recurring candidate pool.
Expire ownership instead of relying on memory
Every evergreen requisition should have a next-review date and a consequence for missed renewal. A practical rule is to suspend new intake or promotion when the business owner does not reconfirm demand by the deadline. The recruiter can then resolve people already in process and route the ownership decision to the named backup.
Suspension is not punishment. It prevents a public job from outliving the decision behind it. Reopening should require a current demand reference, refreshed posting details, confirmed selection capacity, and reviewed candidate messages. The system should retain the prior period so the team can see that the requisition was paused rather than pretending it remained continuously active.
When an owner changes roles or leaves, do not simply replace the name. Ask the incoming owner to accept the scope, demand assumptions, and response commitments. Until that acceptance occurs, the requisition is in an ownership-transfer state and should not continue accumulating applicants by default.
Audit outcomes by site and hiring period
Review whether the evergreen route helps candidates reach real jobs. Useful measures include time from application to first decision, share of applicants entering active selection, age of the oldest undecided application, offers and starts by location, accepted offers that did not start, periods spent paused, owner-renewal misses, and candidates contacted for roles outside their stated preferences.
Break results out by location, shift, recruiting source, and hiring state. An overall average can hide a district that continually accepts applications without scheduling interviews. Compare the requisition's stated demand with actual starts and closures, but do not pressure reviewers to lower standards merely to improve conversion.
Sample individual journeys as well. Choose candidates who were hired, declined, moved into a future-interest pool, and left without completing the process. Reconstruct what state the requisition was in when each message was sent. Check whether the owner had confirmed demand, whether the candidate received the promised update, and whether the final disposition describes what actually happened.
Use the findings to fix the operating model. Repeated pauses may mean the role is not truly evergreen. Large differences between sites may call for separate requisitions and owners. A healthy pool with few active openings may need a deliberate rediscovery process rather than constant acquisition. For that related control, see Check Consent Before Rediscovering Past Candidates.
Run the next ownership review
Choose one evergreen requisition and schedule a 30-minute review with its business owner and recruiting owner. Bring the current demand evidence, accepted offers, active candidates, selection capacity, posting copy, and automated messages. Decide its state for each covered location, identify any candidate whose promised update is overdue, and set the next renewal date.
End with named actions, not a general instruction to "keep hiring." One person updates demand, one adjusts intake, one contacts affected candidates, and one verifies the changes. If the team cannot name those owners, the requisition is not ready to operate as evergreen.
A well-owned evergreen requisition gives recurring hiring a reliable front door. It tells the business what demand it has confirmed, tells recruiters which work they can act on, and tells candidates whether an actual opportunity exists. That clarity supports a more dependable hiring experience and prevents a continuously open posting from becoming a continuously growing backlog.
For help improving the broader recruiting process, visit StopHighTurnover Services.