An Applicant Tracking System that lets desks close a vacancy after placement without a confirmed start date leaves no-shows, fee timing and client handoff in chat. Require a confirmed start date on the placement before the vacancy may close, without vanity metrics or promising that artificial intelligence replaces recruiters.
This matters for recruitment agencies, staffing, secondment, executive search and in-house recruitment. A confirmed start date is distinct from an offer acceptance deadline (when the candidate must reply to the offer), from a next-action date (the chase clock on open work), from a single role owner (who owns the vacancy), from a stage-change actor (who moved the candidate), from a structured vacancy brief (what the role needs) and from a client-submission response deadline (when the client must reply to a shortlist). Placement start date answers when the hire actually starts — and when the vacancy may close in the Applicant Tracking System.
Why closing vacancies without a confirmed start date breaks post-placement control
Marking a role filled and closing it on “they accepted” looks finished and still poisons later work. Typical failure modes:
- Vacancies close while the real start is still verbal, so no-shows and delayed starts have no dated anchor on the placement
- Fee, guarantee and payroll timing cannot be reconciled because the desk never logged when work actually begins
- Client and candidate handoffs assume a start that only lives in chat or calendar invites outside the Applicant Tracking System
- Desk coaching cannot see which placements closed without a confirmed start versus which had an explicit date and owner
An offer acceptance deadline proves the candidate replied to the offer; it does not prove a start was agreed. Closing the vacancy without that start date turns “placed” into storytelling.
What a confirmed start date before vacancy close means
Define it clearly in the Applicant Tracking System:
- Confirmed start date — the agreed calendar date when the placement begins (first day on site or remote), logged on the placement or candidate–vacancy before close is allowed
- Named desk owner — the signed-in user who confirmed the date with candidate and client; not “desk”, not a shared mailbox
- Before vacancy close — the start date is required before the vacancy may move to closed/filled (or before a close action commits), not as an optional note afterward
- What it is not — an offer acceptance deadline, a next-action chase date, a single role owner, a stage-change actor log, a structured brief or a client-submission reply clock
If the start date stays optional, desks close roles under volume and patch dates later. The habit only works when the Applicant Tracking System blocks vacancy close until a confirmed start date is present — or an explicit deferral with reason and owner is recorded for desk review.
How to require a confirmed start date before vacancy close in the Applicant Tracking System
Process beats goodwill. In the Applicant Tracking System:
- On vacancy close (or filled status), require a confirmed start date on the winning placement — or an explicit “close without start / deferred start” path that stays reviewable
- Block the close save until the date (or deferral) is present; do not allow drag-and-drop to closed to complete silently
- Keep start date as a real date field, not free text in notes; optional short note for conditions (visa, notice period, relocation)
- For multi-placement or retained roles, require a start date per placement before that line closes; do not invent one shared fake date for the vacancy
Pair this with an offer acceptance deadline earlier and with a next-action date to chase outstanding start confirmations — without confusing those clocks with the start-date gate itself.
Alerts and desk review without vanity metrics
Alert on closed or filled vacancies whose placements lack a confirmed start date (or lack an approved deferral). Do not invent “start confirmation scores” or leaderboards of who closed the most roles. In the next desk meeting, review how many recent closes lacked a usable start date, which deferral reasons dominate and whether no-shows or delayed starts matched blank start fields. That review is quieter than a full post-placement rebuild and more honest than vanity charts.
Where artificial intelligence may help — and where it must not
Artificial intelligence may suggest a start date extracted from an offer email, contract draft or client confirmation for a human to confirm. It must stay secondary. Artificial intelligence does not replace recruiters, does not invent a start the parties never agreed and does not clear a vacancy-close gate without a recorded human confirmation. Humans own placement truth. The Applicant Tracking System stores the start date, the owner and when it was logged before close.
How this sits next to offers, next actions, owners, stage moves, briefs and client submissions
Confirmed start dates complement other Applicant Tracking System habits:
- An offer acceptance deadline clocks the candidate reply after the offer; it does not prove when work starts
- A next-action date can chase start confirmation without becoming a vanity metric
- A single role owner owns the vacancy; the start date still needs an explicit confirmation before close
- Stage-change actor and reason records who moved into placed; the start date records when the hire begins
- A structured vacancy brief defines the role; it is not a start calendar
- A client-submission response deadline clocks client reply on a shortlist; it is not the placement start
Without a required confirmed start date before vacancy close, post-placement truth stays political. With it, every close has a dated start — or an explicit deferral — before the Applicant Tracking System shows the vacancy as closed.
A practical week to introduce confirmed start dates before vacancy close
One week in the Applicant Tracking System:
- List recent closed vacancies with blank or chat-only start notes and correct the process (not by inventing history)
- Turn on requiring a confirmed start date (or reviewable deferral) before vacancy close commits
- Agree who may confirm the date (desk owner vs account lead) and keep free-text conditions short
- Close silent paths into closed/filled or route them through a desk queue with start date or deferral reason
- In the next desk meeting, review deferrals, no-shows and remaining blank-start exceptions
That habit is quieter than a full post-placement project. It is also how vacancies stop closing on hope while the real start lives only in chat.
Confirm the start date — then close the vacancy with intent
If your Applicant Tracking System allows a vacancy to close after placement without a confirmed start date, post-placement control will stay on guesswork. Require the start date — or an explicit deferral with owner — before close commits. Keep artificial intelligence as a suggester only. Then explore the product or book a demo — we walk through BoldATS placement start-date discipline in your segment.