In many organizations, probation lives in two places: a date in a spreadsheet and a reminder in someone’s calendar. When the reminder fires, the manager is busy, the date passes, and the employee carries on working — confirmed by default, without anyone having decided anything. Or the probation is extended in an email, and the original date is overwritten, along with the reason.
Probation is the last step of hiring. It deserves the same care as the offer that started it.
A record, not a reminder
The first change is to treat probation as a record with a life of its own. In DayOneFlow, a probation record starts on the employee’s first day, from the dates planned when they were hired. It keeps two end dates:
- the original end date, which never changes, so you can always see what was agreed at the start;
- the current end date, which can only move later, and only through a recorded extension.
Reminders, dashboards and reports read from that record. When the end date approaches, the people who need to act are told. When it has passed without an outcome, that is visible as “outcome due” rather than quietly forgotten.
Check-ins at the moments you choose
A good probation decision rests on conversations that happened along the way. It is tempting to fix these at 30, 60 and 90 days for everyone. But some roles need a check-in after two weeks; some need one before the end of probation and nothing in between. The rhythm should be yours.
In DayOneFlow, a check-in is a task in the onboarding plan, due relative to the start date or the end of probation, with the manager or a named colleague as reviewer. The new hire can add their own comments; they never see the reviewer’s notes or rating. When the final review is done, the decision has something to stand on.
One outcome, recorded once
Probation has three possible outcomes, and each should be a deliberate act:
- Confirm. Employment is confirmed and the onboarding journey is complete. The confirmation letter is created at that moment, with the details of that moment — later edits to the template or the record never change it.
- Extend. An extension needs a reason, what is expected to improve and a new end date. The reminders and the tasks tied to the end of probation follow the new date, and the history keeps every extension.
- End. Employment ends and the hiring record is closed. Whatever follows happens elsewhere; what matters here is that the decision is recorded clearly.
Confirm and end are final. Decisions are never edited or deleted, so the record still explains itself a year later — to HR, to the manager and, if it ever comes to that, to anyone reviewing how the decision was made.
Who decides is a choice
Some organizations want HR to record every probation outcome. Others trust managers to confirm their own people. Both are reasonable, so it should be a setting rather than a workaround: in DayOneFlow, HR decides by default, and an admin can let managers record the outcome for their own new hires — never for anyone else’s.
Make the end of hiring a decision
The hiring process doesn’t end when someone signs or starts. It ends when the organization decides, on the record, that this person is confirmed in their role. Treating probation as a lifecycle — with a start, check-ins, a deadline and one clear outcome — makes sure that decision is actually taken, and taken on time.
Read more in our documentation on probation and confirmation.