In most software companies probation ends quietly. The offer letter said six months, nobody put the date in a calendar, and one day someone in finance asks whether the new backend engineer is permanent yet. The manager, a senior engineer with a sprint to run, writes three warm sentences in an email. Nobody can find them a year later, when the same person is up for promotion or, worse, on a performance plan.
A probation evaluation form fixes half of that. It makes the manager answer the same questions about every joiner, against the expectations that were set when they started. The other half is the process around the form: who gets it, when it arrives, what happens if they never fill it in, and where the answer ends up. This post covers both, with a form you can copy for engineering roles.
Why probation reviews slip in tech teams
Tech teams have a particular set of reasons for missing probation reviews, and none of them is laziness.
- The reviewer is not an HR person. An engineering manager or tech lead owns the judgement but may have no access to the HR system at all, so the request arrives by chat and gets buried.
- Reporting lines change. A joiner who started under one lead is moved to another team in month three. The old lead has the context; the new one has the form.
- Hiring is uneven. A startup hires five people in one quarter and none in the next, so there is no rhythm. Five probations end in the same fortnight.
- Nothing happens when the date passes. In most companies a missed review simply means the person drifts into being permanent, which is a decision nobody actually took.
Acas, the UK’s workplace advice service, puts the case for structure plainly: it suggests regular formal reviews during probation, a final review to discuss the outcome, records shared with the employee after each meeting, and an outcome that should not come as a surprise. The law on probation differs by country, so take the legal points from your own adviser. The management advice travels well.
What a probation evaluation form should ask
A good form is short enough to finish in fifteen minutes and specific enough that two managers would fill it in the same way for the same person. For engineering roles, five areas cover most of what matters. Each gets a rating on a short labelled scale and a comment that asks for evidence.
| Area | What the manager rates | Evidence to ask for |
|---|---|---|
| Delivery | Ships work of the agreed size on the agreed timeline | Two or three pieces of work, with how long each took against the estimate |
| Code quality | Code that passes review without repeated rework, with tests where the team expects them | Review comments that recurred, and whether they stopped |
| Collaboration | Asks for help early, reviews others’ work, communicates blockers | A specific moment, good or bad, and what happened next |
| Learning the system | Can work in the codebase and the team’s tools without hand-holding | What they can now do alone that they could not in month one |
| Ownership | Follows work through to production and deals with what breaks | An incident, a bug or a release they saw through |
Close the form with three things: an overall recommendation (confirm, extend or do not confirm), a required comment explaining it, and, if the recommendation is to extend, what the person needs to show in the extra time. Acas makes the same point about extensions: the conditions should be clear and agreed, not a vague “let’s see”.
Use a short scale with words, not numbers
A ten-point scale invites false precision: one manager’s 7 is another’s 9. Three or four labelled points, such as Good, Average and Poor, or Exceeds, Meets and Below, force a real choice. If you want a score for reporting, give each label a value behind the scenes and keep the words on the form.
Ask the joiner as well
A self-assessment with the same five areas, completed before the manager’s, does two jobs. It tells the manager how the joiner sees their own progress, and it surfaces problems the manager never heard about: an onboarding buddy who vanished, a laptop that took three weeks. The joiner should never decide their own outcome, but they should be heard before it is decided.
Run the review as a process, not a document
A Word template in a shared drive is still a form nobody is chasing. What makes probation reliable is the process around it:
- A due list worked out from start dates, so HR sees who is coming up weeks ahead instead of remembering.
- The review starts before the end date, with enough lead time for a real conversation. Three weeks is a sensible default for engineering roles.
- The form goes to the reporting manager automatically, and to someone else if there is no manager on record.
- HR makes the decision on the record: confirm from a date, or extend by a set period.
- The completed evaluation is kept with the person’s record, and they get their own copy.
How Orbiz HRMS runs probation reviews
In HRMS, probation is a workflow rather than a reminder. HR’s Probation reviews list is worked out from each member’s start date and your probation length, plus any extension, in four tabs: Due, Overdue, Upcoming and Needs attention. Needs attention collects members with no start date, reviews nobody could be assigned to, and decisions that failed to apply. A probation end that passes changes nothing by itself: the member stays on probation until someone decides.
The review starts ahead of the end date by a lead time you set, anywhere from 1 to 90 days, and reminders can be switched on so people are nudged as a step comes due. HR can also start a review early from the list. If anyone on probation has no reporting manager, a banner says how many and that their reviews will go to the department head or to HR instead, with a Set reporting managers link that opens the members list filtered to exactly those people.
The evaluation itself is a form built in the HRMS form builder, with sections and fields of these types: short text, long text, number, date, choose one, yes/no, rating and checklist. A rating field has its own labelled scale, Good, Average and Poor by default, and you can rename the labels and set the value behind each. A field’s key is fixed when it is first saved, so rewording a question later never orphans earlier answers, and a review already under way keeps the copy of the form it started with.
Each step of the process goes to the reporting manager, the department head, a role, anyone with a given permission, named people, or the person under review for a self-assessment, and they can never decide their own outcome. A decision can be made to require a note, which is kept with the review. Because anyone can be an assignee, every member has My Tasks, so a tech lead with no HR permission still sees the evaluation waiting for them, and HR can reassign a step when the manager has moved on. From the due list, HR confirms the member as permanent from an effective date, or extends probation by whole months, with extra leave days if the extension carries them.
When the review completes, the evaluation is kept as a PDF on the member’s profile, and if the process is set to share it, the employee can open their own copy. The same workflow engine runs the onboarding and offboarding checklists described on the onboarding and probation page. Managers who use an AI assistant can connect it to HRMS and ask it to open a probation review task and submit their answers; what an assistant can and cannot do there is on the HRMS assistant page.
Where HRMS is not the answer
HRMS runs probation evaluations and other HR-built review forms as workflow tasks. It does not run 360° review cycles, goal tracking or one-on-one agendas. If your performance process depends on those, a dedicated performance tool is the better fit, and HRMS can still own the probation step. HRMS also gives no legal advice: notice periods, the right to be accompanied and dismissal during probation are for your policy and your adviser.
A probation checklist for engineering managers
- Agree the five areas and what good looks like with the joiner in their first week.
- Hold at least one informal check-in a month and write two lines after each.
- Ask for the self-assessment before you fill in your own form.
- Rate on the labelled scale, and back every rating with a piece of work.
- If you recommend an extension, say what must change and by when.
- Make sure the joiner has seen the record before the decision is applied.
Sources, read 4 October 2026: Acas guidance on probation periods, probation reviews and extending probation (UK). For the step before probation, see a careers page on your own subdomain; for teams in Pakistan choosing a system, the best HR software in Pakistan. Software companies can see how the whole platform fits on the software and IT services page.
Built for your industry
