An employee does not experience your HR system. They experience the order it happens in.

Scout is named for the bees that do this job in a real hive. When a colony needs a new home, scout bees go out and assess each candidate site against several criteria at once, volume, entrance, height, how dry it stays, then come back and make the case for what they found. No single bee decides. The colony converges on the answer together, from evidence several scouts gathered independently. That is the whole design principle here: the portal gathers and reports, people decide.

It is an online recruitment portal reached through a browser, which means there is nothing for the client to host and nothing for a manager to install. It exists because recruitment in a business of this size almost always happens in someone's personal inbox, and an inbox is not a process. It is a place where records go to become unfindable.

For a hiring manager, end to end, it runs like this. A vacancy is raised against a role with a defined scope and an approver, so the first thing that exists is a decision rather than a rumour. Once approved, the advert is written once and published out to the channels the client uses, with a single application link rather than four addresses that collect four different piles of CVs. Applications land in one place, structured, with the documents attached to the candidate rather than to a covering email.

From there the manager works a pipeline instead of a folder. Candidates move through defined stages, each move is stamped with who made it and when, and the screening questions asked of one applicant are the questions asked of all of them. Interviews are scheduled from inside the portal, notes and scores are captured against the candidate at the time rather than reconstructed a fortnight later, and the shortlist that reaches a second decision maker arrives with its reasoning attached. The offer, and the regret letters, go out from the same place.

What you are left with at the end is the part most SMEs are missing. Not the hire, the file: the advert as published, every applicant, every stage change, every question asked and answered, the basis on which the appointment was made. That file is what you want in your hands the day someone asks you to justify a decision, and it is the same file the onboarding step reads from, so nothing is captured twice.

The standard SME induction is a single overwhelming day. Contract, policies, systems, safety, product, culture, all of it, to a person who has not yet worked out where the kettle is. Nobody retains that. What they retain is the impression that this business tells you everything once and then holds you to it.

The drip portal releases the same content in sequence over time. Day one carries what a person genuinely needs on day one. The rest arrives on a schedule tied to the role, over the first weeks and months, with each module unlocking when the previous one is complete. Completion is recorded per person per module, so a manager can see at a glance who is where, and the record of what an employee was trained on and when is built automatically rather than reconstructed the week a dispute starts.

It also keeps working long after induction. Refresher cycles, a new procedure, a policy change, an annual repeat on the things that must be repeated: all of it runs on the same rails, to existing staff, without anyone booking a room.