Skip to content
Morning Meteor Haven
Illustration of a futuristic interface with face outlines and a finger touching a cloud icon

Records for people, decisions by people

This page sets out the thinking behind how the work is built, and where we choose to draw the line on what is assisted.

Back to home

Where this started

Recruitment work involves judgement calls that matter to real people on both sides of the process: the candidate applying, and the panel member deciding. A great deal of the time spent on hiring goes not into that judgement, but into formatting, transcribing, and reconciling information so that the judgement can be made at all.

The work here is built around that gap. It does not try to close the distance on the judgement itself.

Philosophy and vision

Assistance in hiring is something like a well-kept filing cabinet. It does not decide who is hired, but it makes the material easier to work through consistently. The vision is narrow on purpose: tools that handle the mechanical parts of a process, and stay out of the parts that need a person's discretion.

Core beliefs

Structure helps consistency

A shared layout reduces the chance that some applications get more careful reading just because they arrived in a tidier format. It does not, by itself, make a process fair or free of bias.

Records should be traceable

A summary is only useful when the reader can go back to the source and check it. Originals are kept next to every draft.

Judgement belongs to people

We do not set up tools that assess whether a candidate is suitable. That decision stays where it belongs.

Handover matters as much as setup

A step that only we can operate has not made your team more capable.

Principles in practice

Every summary is treated as a draft that a person reads against the source. Interview records are made only after the candidate has been told, and an interview can go ahead without one. Every engagement ends with a written procedure instead of a dependence on us, and applicant data is covered in the written scope before any real application is processed.

Working around what exists

Each hiring process has its own history, team, and constraints. We do not arrive with a template to impose. An intake step or an interview record is built around your existing evaluation forms and your own workflow, not the other way round.

Caution about capability

We are wary of adding capability for its own sake. A feature earns its place only if it answers something a hiring team has told us slows them down. That keeps each engagement narrow and the result easier to understand and maintain.

Being straightforward

Candidates are told when an interview record is being made. Reports on a process review are delivered in writing, including findings that point to simplifying a process rather than adding to it, even when that means less work for us. Where we do not know something, such as how well a summary will hold up on your documents, we say so and test it on your records instead of quoting a figure.

Working alongside your team

Setup is done together with your team rather than handed over afterward. Trial periods, such as five interviews for interview records, are part of the scope so changes can be made together before anything is called finished.

Long-term thinking

A setup that works only while we are involved has limited value. The aim is an arrangement that still works months later, kept up by your own team from the written procedure.

What this means for you

You can expect a narrow, specific scope, a written record of what was decided and why, and a step your team can run without us. We will not suggest more than the situation calls for, and we will say plainly if a review finds that a stage should be simplified rather than assisted.

If this approach fits how you think about hiring

We are glad to talk through how it might apply to your process, with no obligation either way.

Go to contact page