HIREBREW PEOPLE | PRODUCT PILOT BRIEF Everyday HR. A clearer way through. Connect employee context with the requests that need attention, giving people a clearer place to ask and HR a better starting point. CAPABILITIES TO EXPLORE Employee records and self-service Explore shared employee context, with record ownership and appropriate visibility considered during implementation. Leave and letters Give common employee needs a more consistent starting point and make the manager or HR review part of the journey. Requests and expenses Evaluate how requests and expenses reach their responsible reviewers, without implying automatic payment execution. Contracts, cases and people operations Explore the broader operational context around employees, while treating sensitive case information and contractual decisions with explicit handling requirements. PRACTICAL USE CASES An employee requesting leave Situation: An employee needs time off and their manager needs to consider team coverage. Workflow: Raise a sample request, review it from the manager perspective and clarify how the employee learns the next step. Intended improvement: A shared understanding of the request and its owner, instead of a decision buried in separate conversations. A letter that needs HR attention Situation: A colleague needs an employment letter and is unsure which member of HR to contact. Workflow: Start with a clear request, confirm the relevant employee details and assign review to the responsible people-team member. Intended improvement: A defined route from employee need to accountable review, with wording and release still controlled by HR. People operations across multiple sites Situation: A Nigerian business serves employees in head office, branches and operating locations. Workflow: Test a common request journey with a manager outside headquarters, including local policy questions and a cross-team handoff. Intended improvement: An evaluation that reflects real working locations rather than assuming all employees sit beside the HR team. WORKFLOW From an employee question to an owned next step. Find | Employee + people team Begin with the right context Locate the employee record and confirm relevant information. Identify which fields belong in Hirebrew and which remain authoritative in another system. Ask | Employee Make the request understandable Use the employee journey to raise a leave, letter or other people request. Include enough context for review without placing unnecessary sensitive information in the record. Review | Manager + HR Give the decision a clear owner Review the request against the appropriate company policy and working context. Agree who contributes and who is accountable when a question crosses department or location boundaries. Follow through | Responsible reviewer Keep the employee in the picture Clarify the outcome or next action and its owner. Check the employee view to ensure the journey does not end at submission. PILOT Test the request your team handles every week. Choose a leave or letter journey and use sample employee information. Ask an employee, a manager and HR to identify confusing steps and unclear responsibilities before expanding the scope. EVALUATION CHECKLIST [ ] The employee can identify where to begin [ ] Review and response responsibilities are explicit [ ] The employee perspective includes the next step SCOPE BOUNDARIES Validate production permissions, data handling, policy rules and record retention before live use. Payroll calculations, statutory filing, expense payments and automatic HRIS synchronisation are not demonstrated here. AI AND HUMAN REVIEW Brew illustrates how an HR colleague might draft a clearer explanation from an approved policy excerpt. Review accuracy and tone, exclude unnecessary personal information and keep case decisions with people. Example prompt: Draft a plain-language explanation of the next steps for a sample leave request, using only the policy text supplied. NEXT STEP Assign an owner, walk through the workflow with sample data and record the evidence required before a live rollout. This document is not a submitted enquiry, booking or confirmation of production readiness.