HR for a growing company: from first hire to fifty

Somewhere between the first hire and the fiftieth, HR stops being something the founder does from memory and becomes something that needs a record. The transition rarely happens on purpose. It happens because someone asks what another employee's start date was, or a probation decision gets second-guessed months later with no notes to check, and the gap in the paperwork suddenly costs real time. None of what follows requires legal expertise to set up — it requires deciding, once, what you will ask and when, and then asking it the same way for everyone. Entitlements and requirements vary by jurisdiction, so treat anything here as a starting structure, not a legal answer.

Comparing candidates fairly

An application form exists to let you compare people against the same criteria, not to collect an interesting story from each one. If your current process is "email me your resume," you end up comparing whoever wrote the best email, not whoever is best for the role.

A structured employment application should ask every candidate for a role the same set of questions:

• Relevant experience, mapped to what the role actually requires.
• Availability and any constraints on start date.
• Direct questions tied to the job, not generic ones — a support role and an engineering role should not get the same form.
• Consistent fields for resume and portfolio links, so nothing gets lost in an inbox.

The value shows up at the comparison stage, when you can put five completed forms side by side instead of five differently-formatted emails.

Scoring interviews instead of trusting your gut

An interview without a scoring structure tends to reward whoever interviewed last, or whoever happened to click personally with the interviewer, rather than whoever is actually best suited to the role. A structured scorecard fixes this without turning the interview into a rigid script.

Set up scoring before the first candidate walks in, not after:

• Define three to five criteria tied to the role, agreed on in advance by everyone who will interview — things like relevant experience, a specific skill the role needs, and how the candidate approaches a realistic problem you put in front of them.
• Have each interviewer score independently right after their interview, before comparing notes with anyone else. Discussing first and scoring second tends to produce scores that just agree with whoever spoke most confidently in the debrief.
• Require a short written note next to each score — a sentence on why, not just a number — so a score can be checked against something concrete later, and so the reasoning survives even if the interviewer forgets the specifics of the conversation.
• Bring the scores together in one place before making a decision, so the choice is visibly based on the criteria you set, not on a single interviewer's impression carrying more weight than it should.

This does not remove judgment from hiring. It gives the judgment a consistent shape, which matters most when two candidates are close and the deciding factor needs to be something you can explain later, including to the candidate who didn't get the role.

Recording offer acceptance in writing

A verbal yes on a phone call is not a record. Get the offer terms — role, start date, compensation, reporting line — into a document the candidate signs or explicitly confirms, before you tell anyone else the hire is final. A job offer acceptance form does this without needing a lawyer to draft a formal contract for every hire; it creates a dated, written confirmation of what was offered and accepted, which is the piece most often missing when a disagreement about terms comes up later.

Collecting onboarding data once

New hires are usually asked for the same information multiple times: once for payroll, once for IT, once for benefits, once by whoever manages the building badge. Each repetition is a chance for something to be entered wrong or forgotten entirely.

A single new employee onboarding form collects it once and routes it to whoever needs it:

• Legal name, address, and tax details for payroll.
• Emergency contact.
• Equipment and access needs for IT.
• Bank details for salary payment.
• Any information relevant to benefits enrollment.

The goal is one submission that every downstream team pulls from, not one form per team.

Paperwork on day one is necessary but it is not the same thing as a first week that actually helps someone become productive. A workable sequence: equipment and access working before they arrive rather than set up while they wait, with introductions and a walkthrough of what the week will contain; days two and three spent on role-specific setup plus a first small piece of real work rather than a disconnected training exercise; a short check-in on day four that asks what's unclear rather than "how's it going," which tends to get a polite answer regardless of the truth; and a slightly longer check-in at the end of week one that sets expectations for week two and confirms payroll, benefits, and equipment actually went through correctly. Write this sequence down once as a checklist tied to the onboarding form, so it runs the same way for the fifth hire as the fiftieth.

Probation reviews as decisions, not paperwork

A probation review that exists only to be filed is a waste of the meeting it documents. The point of the review is to force an actual decision at a set point: confirm, extend, or end the employment, based on specific observations rather than a general feeling.

A probation review form should ask the manager to record:

• Specific examples of work against the expectations set at hire.
• Whether the employee met, missed, or exceeded them.
• A clear recommendation — not "let's see how it goes," but confirm, extend with named conditions, or end.

If a manager cannot fill in specific examples, that is itself useful information: it usually means the expectations were never made clear at the start, which is worth fixing for the next hire regardless of what happens with this one.

Leave requests, including parental leave

Leave requests need a simple form and a clear route to approval, but parental leave in particular should not be handled the same way as a request for a few vacation days. Entitlements — length of leave, pay during leave, job protection — depend entirely on the country and sometimes the state or region you operate in, and they change. Do not encode specific entitlement numbers into your process as if they are fixed; build the form to collect what you need to make a decision, and confirm the actual entitlement with current local guidance or a professional each time, rather than assuming last year's answer still applies.

A parental leave request form should capture:

• Expected leave start date and anticipated duration.
• Any documentation your jurisdiction requires to be submitted.
• Who covers the role while the employee is away.

Keep general leave requests (vacation, sick leave) on a simpler, faster form — most of them do not need this level of detail and slowing them down just creates friction for routine time off.

As headcount grows, route every leave request — vacation, sick leave, parental leave, any other kind — through the same system even if the forms differ in detail, since an approval given over chat with no record elsewhere creates a gap the moment that manager is unavailable to confirm it happened. Keep a running balance per employee that both the employee and their manager can see, record the approval itself (who approved it and when) rather than just the request, and review the records periodically the same way you would review payroll — checking that leave taken matches what was approved and that balances are correct — since small mismatches are cheap to fix immediately and expensive to unwind after they compound across a year.

Exit interviews and what to do with what you hear

An exit interview only has value if something happens with the answers. Collecting them and never reading them again teaches departing employees — and the ones still watching — that the process is a formality.

An exit interview form should ask specific, answerable questions: what would have kept them, what they'd change about the role or the team, whether they'd recommend the company to a friend. Then someone needs to actually read the pattern across multiple exits, not just the individual answers. One person leaving because of a bad manager is a personnel issue. Three people leaving with the same complaint is a pattern worth acting on before it costs you a fourth.

Building it in the right order

If you are setting this up for the first time, start with the application and offer forms — they affect every hire from day one. Add onboarding once you have more than a couple of new hires a quarter. Probation reviews and leave request forms matter once your first cohort of hires reaches those milestones. Exit interviews become useful once you have enough departures to see a pattern rather than a single data point. None of it needs to exist on day one of the company, but each piece should exist before you need it, not after the gap in your records causes a problem.

The value of any of these forms compounds only if they are used the same way for employee one and employee fifty. A probation review skipped for a founder's friend, or an onboarding form filled in from memory because "we already know each other," creates a gap that shows up later as an inconsistency someone else has to explain. Revisit the forms themselves periodically — as the company changes, the questions that mattered at five people are not always the ones that matter at fifty, and it is easier to adjust a form once a year than to reconstruct a missing record after the fact.