Does a reposted job ad mean a new vacancy?
The same employer and role appear again with a fresh date. Before adding a new vacancy to your recruitment-agency prospect list, compare the underlying request and the employer’s current statement.
A repost is evidence that an advertisement appeared again. It does not alone establish a new hiring request, another person to hire or difficulty filling the role. Compare employer and platform identifiers, dates, role details and current status. Record what remains unknown before treating the company as a recruitment opportunity.
Start with the employer’s current page.
This guide is for a recruitment agency researching potential employer clients. It helps you decide what to retain in the company record and what to verify next. It does not tell a candidate whether to reapply or classify an employer as dishonest.
Open the direct source.
Follow the advertisement to the employer’s current role page where available. Record the actual organization, role and location. Keep an unidentified employer unresolved.
Compare the earlier observation.
Use evidence you previously saved, not memory of a similar title. Check the employer’s request number, platform listing number and material wording.
Read the current status.
Look for an explicit current opening, closed role or future candidate pool. An active-looking page or apply button alone leaves hiring status uncertain.
Separate the conclusions.
Write what changed in the advertisement, what is known about the request and what is still unknown about headcount and agency support.
A new listing number can belong to the same request.
A requisition is the employer’s internal request to recruit. A posting is an advertisement for that request. The two identifiers can differ. One request may cover several hires, and one role may appear on several channels. Count visible records as visible records until the employer establishes what they represent.
Dayforce’s Recruiting Guide R2026.2.0, updated 12 August 2026, documents an evergreen refresh that creates a new posting identifier and current posting date within the existing requisition. This feature applies to its client career-site postings; external board postings made through eQuest are excluded. It is a concrete counterexample to equating a new posting ID with a new requisition, not an explanation for every repost.
| Field | What to save | What it cannot establish alone |
|---|---|---|
| Employer request / requisition ID | The employer-provided number and source. Mark unavailable if none is visible. | One hire, new headcount, an approved external agency brief or an unchanged request scope. |
| Platform listing ID | The identifier on each advertising channel, with its URL. | A different employer requisition or an additional vacancy. |
| Original publication date | A date explicitly identified as the employer’s original publication, with its source. | Today’s status or the date your team first discovered it. |
| Displayed date | The page’s date label and value, including “reposted” or “updated” wording. | The original opening date or why the advertisement changed. |
| Observed on | When you actually inspected this version. Keep separate observations. | The day recruitment began or a guaranteed continuous advertising period. |
| Current status / closing date | The current employer statement and any closing date, checked at a stated time. | A paid agency opportunity, budget, urgency or confirmation that all copies are current. |
Google’s JobPosting documentation defines datePosted as the employer’s original publication date and identifier as the hiring organization’s unique job identifier. These are publisher-supplied fields, not independent verification. A third-party “today” label need not describe the same event. An absent closing date does not establish that a role is still open.
Compare the work before calling it another role.
- Employer: distinguish the actual hiring company from a board, staffing agency or confidential advertiser.
- Request: compare the employer’s number and any explicit explanation of a replacement or additional request.
- Work: compare responsibilities, seniority, contract type, working pattern and location. Record material changes in the original wording.
- Status: compare the current direct source with each board copy. Preserve a contradiction instead of quietly choosing the newer date.
- Dates: keep original publication, displayed date and your observation date in separate fields.
Without an employer request number, matching title, location and description support a possible relationship. They do not prove one request or two. Retain both URLs and mark identity unresolved. A changed location could be a corrected advert, a multi-site role or a distinct request; record the change and seek the relevant explanation.
Do not restart “days open” from each new displayed date. If you only observed the advertisement on 9 October, write “first observed by us on 9 October.” Do not turn that into “first advertised on 9 October.” Gaps in your observations also prevent a claim that it stayed open continuously.
Four observations do not mean four vacancies.
Entirely fictional example: Poyraz Automation advertises a PLC commissioning engineer role in Ankara. The organization, pages, identifiers, dates and statements below are invented. PY-214 is the employer’s request number; B-701 and B-844 are identifiers on an unnamed fictional board. No headcount is stated. The example does not assert that the board uses Dayforce or its refresh schedule.
| Observed on | Source and displayed date | Identifiers and change | Conclusion available at that time |
|---|---|---|---|
| 2 October 2026 | Employer role page; explicitly says originally published 1 October. | PY-214; PLC commissioning engineer, Ankara. No number of hires stated. | One visible employer request. Current headcount and agency support remain unconfirmed. |
| 3 October 2026 | Board listing; displays 3 October. | B-701 links to PY-214 with the same role and location. | A board advertisement for the observed request. Do not add another vacancy from the extra channel. |
| 9 October 2026 | Another board listing; displays “today” on 9 October. | B-844 still links to PY-214; role and location unchanged. | A different board ID and date. They do not establish a new employer request, growth or a failed hire. |
| 10 October 2026 | Current employer page now explicitly says future opportunities / candidate pool. | PY-214 remains visible. The current statement does not specify a presently open position or a hiring count. | Update the record to an explicitly stated future pool. Do not present it as a confirmed current vacancy or an urgent agency brief. |
This is a teaching chronology, not a measured repost cycle or a real company check. The 10 October statement was not known at the earlier inspections; do not rewrite their evidence as though it was.
The record contains two distinct board listing IDs and one visible employer request family. The number of actual vacancies is unknown. The later pool statement changes the current classification; it does not prove that no hiring ever happened or that all similar advertisements are pools.
Write the next check without inventing the cause.
| Field | Recorded value |
|---|---|
| Employer / role / location | Poyraz Automation / PLC commissioning engineer / Ankara; all fictional. |
| Evidence history | Four inspections, 2–10 October. Two board IDs B-701 and B-844 link to visible employer request PY-214. |
| Dates | Employer states original publication 1 October. Board display dates are 3 and 9 October. Our first observation is 2 October. |
| Latest direct-source statement | Future opportunities / candidate pool, observed 10 October. No current hiring count stated. |
| New requisition / actual vacancies | A new requisition is not established by the board change. Actual vacancy count is unknown. |
| Growth / difficulty / agency acceptance | Not established. No claim of new headcount, failed hiring, urgency, budget or acceptance of agency proposals. |
| Research decision | Keep the history in the employer record; hold the claim of a current recruitment opportunity for this role. |
| Next evidence and review trigger | Recheck when the employer publishes a specific current request or supplies a relevant clarification. Record its date and the source. |
If there is an appropriate existing conversation, ask the unresolved question: “Does PY-214 describe a current opening or a pool for future roles?” Do not open with “Your repeated adverts show you cannot fill this role.” Respect a stated no-agencies instruction and the employer’s designated process; an advert is not an invitation to submit candidates or a confirmed service order.
Use the evidence to choose the next action.
| Observed facts | Bounded conclusion | Next action |
|---|---|---|
| New board date or ID; same visible employer request and unchanged work. | Another advertisement or version; a new request is unconfirmed. | Keep the history together for review. Check the direct source and avoid increasing the vacancy count. |
| Employer number missing; similar title and text. | Possibly related advertisements; identity unresolved. | Keep both sources and dates. Compare the work and request employer clarification where appropriate. |
| Responsibilities, contract or location change materially. | A material change is observed; its cause and request identity remain uncertain. | Save both versions and identify whether this is an edit, multi-site role or distinct request. |
| Employer explicitly confirms a separate current request. | A distinct request is confirmed within the statement’s scope. | Verify hiring count, replacement versus growth and the route for any external support separately. |
| Current employer page explicitly describes a future candidate pool. | Future pool; a currently open position is not established. | Hold the current-vacancy claim. Review if a specific opening is later announced. |
| Employer explicitly says the role is closed; board still appears active. | Direct-source closure conflicts with a visible copy. | Record the closure and check date. Hold reliance on the board copy; do not infer the reason for closure. |
| Current opening confirmed; agency acceptance not addressed. | Hiring need is supported; an agency brief is unconfirmed. | Review the designated process and external-support position before treating it as a sales opportunity. |
These are practical interpretations of the supplied facts, not an automated fraud model or universal ATS rules.
A long-running advert does not alone prove failure, turnover or deception. A new employer request can replace a departing employee rather than expand headcount. Several people can be recruited under one request. None of these interpretations can be selected from a refreshed date alone.
Online advertisements are imperfect evidence of vacancies.
Cedefop’s 2019 report explains advertisement-versus-vacancy distinctions and duplicate notices across portals in an early European data system. We inspected the full-text concepts, preprocessing and quality-limit sections. Its seven-country setting is not a measurement of Turkey’s job market in 2026.
Arthur (2021) analysed Reed.co.uk advertisements from January 2019 to January 2021 during the UK COVID-19 crisis. We read the published methods, relevant results and discussion. Multiple positions and agency copies complicate identification of unsuccessful-hiring reposts. This observational study does not identify a particular employer’s cause or test agency conversion.
Onur Emre’s 2025 article examines ghost advertisements conceptually through organizational theories. We inspected the relevant theory, evidence and conclusion sections in the publisher’s full issue PDF. It is not the author’s own Turkish vacancy sample. Referenced commercial surveys do not establish a current Turkish ghost-ad rate.
The chronology and decisions here are our practical synthesis. They have not been validated as an automatic classifier or an Anivo outcome. Official platform instructions show specific mechanisms and definitions; they cannot tell you which mechanism explains an unidentified employer’s advert. Preserve the unresolved result until suitable evidence arrives.
Keep the history usable in the next review.
Download the fictional chronology, completed decision and blank manual review form. The TXT works without Anivo or signup.
- Keep one row for each actual inspection, with the URL and original wording.
- Separate employer request and board identifiers, displayed dates and observation dates.
- Record current status, unknown headcount and agency support as separate conclusions.
- Assign the next evidence check and update the record when relevant facts change.
Example employer-research brief: “Research automation employers in [market] where PLC commissioning is relevant to our recruitment specialism. Review their stated work and hiring channels. Treat repeated job adverts as items for manual verification, without inferring urgent hiring or acceptance of agency support.” Adapt the market and specialism to your actual service.
In Anivo, describe the companies you want to research and review the proposed plan before approving it. For a relevant employer, manually add the inspected sources, dates and unresolved question to a CRM note, then add a task for the next check. A note’s creation date does not replace the advertisement’s publication or your observation date. The observation history is your review work. This guide does not describe an Anivo job-ad tracking, ATS verification or TXT import feature.
Use the recruitment-agency workflow for employer research and the lead qualification guide for the next sales decision. The company scores guide explains fit and data quality. A confirmed opening and a confirmed service opportunity require different evidence.
Questions about reposted job advertisements
Keep advertisement history, actual hiring need and external-support decisions separate.
Does a fresh date mean a new job opening?
Not by itself. It can describe a refreshed or newly distributed advertisement. Save the date label and source, then compare the employer’s request and current statement. Your discovery date is also separate from publication.
Does a new platform listing ID mean a new requisition?
Not alone. Posting and employer request identifiers can differ. Dayforce documents a specific refresh that creates a new posting ID under an existing requisition; its scope is not every external board. Check the actual employer identifier.
Does the same requisition mean exactly one person will be hired?
No. One request can cover more than one hire. Preserve a separately stated hiring count; when it is absent, record unknown. A new request also does not alone establish headcount growth rather than replacement.
What if no employer request number is visible?
Compare the organization, responsibilities, location, contract and source links. Similarity supports a possible relationship, not a confirmed match. Keep the records and mark identity unresolved rather than silently counting another vacancy.
Is a future candidate pool a current vacancy?
An explicit future-pool statement does not establish a currently open position. Record that statement and its check date. It does not prove that the company never hires or that every similar advertisement is a pool.
What if the employer says closed but the board still says active?
Save the employer’s explicit closure, source and observation date, and record the conflicting board copy. Hold reliance on that copy as a current vacancy. Do not infer why it closed or when every other copy will disappear.
Does repeated advertising mean the employer needs an agency?
No. It does not establish urgency, budget, failed hiring or willingness to use an agency. Review the employer’s designated process and any no-agencies statement. Acceptance of external support needs separate evidence.
Does Anivo automatically track reposts or import the form?
This article makes no such claim. The TXT is a standalone manual file. You can record your own checks in a CRM note and create a task in Anivo; source comparison and hiring confirmation remain your work.
Sources and access notes
Checked on 10 October 2026. Relevant primary text was inspected; platform scope, research dates and unresolved company facts remain separate.
- Dayforce · Create Evergreen Postings
Recruiting Guide R2026.2.0, updated 12 August 2026. Complete feature text reviewed. Client-site refresh under a requisition; eQuest external-board postings excluded. Not an Anivo capability or the mechanism of our fictional board.
- Google Search Central · JobPosting
Relevant datePosted, identifier, validThrough and expired-job instructions reviewed. Publisher fields and search policies, not independent employer confirmation.
- Cedefop · Online job vacancies and skills analysis (2019)
Full PDF accessed; printed pages 9–12, 21 and 24–25 inspected. Early seven-country European system; not Turkish 2026 prevalence or company-level hiring intent.
- Rudy Arthur · UK job market during COVID-19 (2021)
Published 27 May 2021. Full-text methods, relevant results and discussion reviewed. Reed.co.uk, 11 January 2019–11 January 2021; observational UK setting, not an agency or Anivo success test.
- Onur Emre · Ghost Ads (2025)
Çalışma ve Toplum 4(87), 1703–1730. Relevant theory, evidence and conclusion sections inspected in the full issue PDF; conceptual analysis, no original Turkish prevalence sample.