Two audiences need different routes from the homepage.
A recruitment agency needs to explain its services to employers and help candidates find relevant roles. ImbaHub can build the public structure, service presentations and routes to vacancies. Applications, candidate records and recruitment-platform connections require a separately confirmed solution.
The right route for each task
Employer
Explain the assignment and initial conversation.
Candidate
Show the current role and correct application route.
Editor
Keep approved details and status current.
Explain which assignments the agency accepts
Describe the roles and assignments you actually work with. Explain the route from an initial needs conversation to an agreed assignment without promising a particular candidate or hiring time. Distinguish recruitment, staffing and advisory work where several services are offered.
A fictional specialist agency might ask an employer for the role, context and desired timetable before an initial conversation. That inquiry need not collect candidate documents. It should help the recipient assess fit and identify what needs clarification.
Give candidates current roles and the correct next step
Present vacancies with understandable names, location and approved conditions. Distinguish applying for a particular role from a general expression of interest. Explain when a link opens another platform.
If roles come from a recruitment system, define update ownership and behavior. Test a new vacancy and what happens when it closes. A public vacancy page does not establish that a candidate account or application capability is integrated.
| Detail | Review question | Evidence |
|---|---|---|
| Duties | What does the person do each day? | Approved tasks |
| Requirements | Why is this needed from the start? | Reason linked to the work |
| Location | What attendance is expected? | Confirmed arrangement |
| Next step | What happens after the link? | Tested application route |
Build confidence through clear boundaries
Explain whom employers and candidates should contact and what happens next. Use only approved personal introductions and client references. Do not fill sections with invented logos or unsupported success figures.
Try two tasks: a candidate asks about the workplace while an employer wants to discuss a new role. Can each find the right recipient without providing the same information? That gives practical evidence about the structure.
Plan publication before moving vacancies
Start with a service page and a marked test vacancy in a safe environment. Review content, mobile use, links and closing the role. Assign ownership for approving role details and checking that the website reflects current status.
Distinguish the public design from application software, data storage, integrations and continuing support. Do not add CV uploading as a decorative form field. That journey needs its own requirements, owners and verified handling.
Questions, answered
Is recruitment software included?
Not automatically. A public website, a link and a custom integration are different deliveries.
Can one site serve employers and candidates?
Yes. Give each audience clear routes and recipients instead of one ambiguous shared form.