On Monday morning, a depot supervisor in Nakuru lends a dispatcher to the Nairobi branch for three weeks. In the staff register, the dispatcher still belongs to Nakuru. In the duty roster, she reports to Nairobi. In payroll, her cost still lands in the old branch. On Friday she asks for a day off. Both supervisors receive the request, and each assumes the other will answer. Every system contains a plausible piece of the truth. The employee still goes home without an answer.
A business evaluating HR management software in Kenya can learn more from that one transfer than from a demonstration of twenty menu items. Ask each supplier to take the dispatcher through her reassignment, leave request, return and eventual exit. Follow the records that change hands. Find out which manager gains authority, which person loses access and what finance receives at the end of the month. The software earns its place when the people involved can explain what happened without reconstructing a trail of messages.
Consider the following a buying guide for a Kenyan employer with several branches, mixed office and field teams, or people whose assignments change more often than their job titles. The depot is an illustrative example. Adapt the scenario to your workplace and use fictitious records during supplier demonstrations.
Decide what a staff record should answer
Start with three ordinary questions. Who works here today? Who can approve this person’s next request? What changed since the previous payroll handover? Many employers have a spreadsheet that answers the first question. The second and third expose why staff administration becomes difficult. A spreadsheet can hold a manager’s name, yet it rarely tells the branch supervisor when that assignment starts, which kinds of decisions it covers or when the former manager should lose access.
Give each employee a stable internal identifier. Names can have spelling variations, people may share names, and telephone numbers change. A branch code combined with a name looks convenient until someone transfers. A payroll number can also cause confusion if the payroll provider changes. Decide who allocates the internal identifier and what happens when a former employee returns. Reuse or create an employment period according to a documented policy, while preserving the connection needed to interpret earlier records.
Define the difference between the person, the employment relationship and the current assignment. One person may leave and later rejoin, hold an acting role or divide time across two branches. If all those facts occupy a single row, updating a current detail can erase history. Ask the supplier to display a staff member as of a past date. A useful answer shows which assignment applied then and which changes had already been approved at the time.
Keep a field because someone needs it for a named decision. An emergency contact belongs in a restricted area with a clear purpose. A uniform size might serve a practical purpose for field teams but have no place in an executive headcount report. A branch manager who needs a reliable telephone number for tomorrow’s shift does not thereby need access to identification documents. Build views for the job being done and inspect a sample export from each role.
Turn a transfer into a dated event
Write out the depot transfer before configuring it. The Nakuru supervisor proposes a temporary assignment. Nairobi confirms the arrival and the expected end date. HR checks the record and approves the change. Finance receives the agreed treatment of cost. The employee receives the reporting instructions. Agreement about those steps will do more for the project than arguing about where to put a transfer button.
Choose what should happen if the start date falls in the future. A change approved on Thursday for the following Monday should not remove the employee from Friday’s local roster. The Nairobi supervisor might need to prepare equipment before arrival without seeing the employee’s full personnel file. Separate preparation rights from ongoing management rights. Run the demonstration on both sides of the start date and ask the two supervisors to open their actual work lists.
Temporary arrangements need an ending. Decide whether a temporary assignment returns automatically on the scheduled date or requires confirmation. Automatic return makes planning easier but can silently send requests to the wrong office when a secondment is extended informally. Confirmation gives managers a chance to correct the plan but creates overdue tasks. A good design identifies the owner of that decision, shows upcoming end dates and makes overdue confirmations visible.
Test an extension agreed after the employee has already returned on paper. The record should let HR explain what was originally expected, what actually happened and who authorised the correction. An invisible edit to the date is cheap today and expensive during a later dispute. Ask whether an amendment can preserve both the earlier value and the business reason. Check what downstream teams see once they have already acted on the first instruction.
Put the line manager in the right place
A reporting line can mean several different things. The Nairobi supervisor may direct daily work. The Nakuru manager may remain responsible for performance reviews. A regional manager may approve expenditure. Treat each authority as a business decision with a scope and a date. Giving the host supervisor every permission attached to the old manager’s job is convenient for setup and unnecessarily broad in use.
Draw a small decision table during discovery. For leave, identify who checks coverage and who approves the absence. For a timesheet, identify who can attest to the actual hours. For an expense, identify who owns the budget. Ask what happens if the person responsible is on leave. A deputy might approve requests from the same team for five days without gaining access to salaries, investigations or records from another branch.
Use a negative test during the demo. Sign in as the Nakuru supervisor after the temporary assignment starts. Try to approve a new Nairobi timesheet, search for a private document and open an old link saved before the transfer. A hidden menu alone proves little. The system should enforce the boundary when a user opens the record through another route or requests an export. Capture what the user sees and which attempt an administrator can investigate.
Managers also need an intelligible way to resolve mistakes. Suppose Nairobi receives a request for an absence that occurred before the transfer. The approval may belong to the original supervisor because the event happened under that person’s watch. Or your policy may assign outstanding requests to the current manager. Either can work when it is explicit. The costly outcome is a request that disappears between team lists because nobody defined ownership during a move.
Follow leave from a request to a balance
Ask the supplier to enter an opening leave balance for the dispatcher using a fictitious policy, then book a period that spans the transfer date. Record the balance before submission, while the request awaits approval and after it is approved. Your team should be able to tell whether the displayed balance is earned, available, reserved or already used. Ambiguous labels generate support requests even when the underlying calculation is correct.
Next cancel one day from an approved absence. Who is allowed to make the change? Does the manager receive notice? Does the returned day appear in the right period? If the employee has already submitted another request that relied on the old balance, make sure the recalculation gives a coherent result. A ledger of dated additions and deductions is often easier to explain to an employee than a single editable number.
Part days deserve their own trial if your workplace uses them. A person working different shift lengths may ask for an afternoon rather than a fixed number of hours. The business needs to specify how the request maps to the roster. Use a short shift followed by a longer one and inspect the balance, duty roster and report. Half of one type of day does not automatically mean the same number of hours as half of another.
Test cancellation close to payroll handover. An approved absence can affect an allowance or an attendance file even when it has no effect on base pay. HR should know whether finance has already received the relevant period. A corrected absence should appear in a change report with its previous value. Relying on someone to remember that the spreadsheet sent on Wednesday is stale makes the software less dependable than the paper process it replaced.
Handle the employee who shares a device
A staff portal that works on a manager’s laptop may fail on the shop floor. Ask a field employee to request leave on the device they normally use. Observe whether the page opens on a modest connection, whether the date picker fits the screen and whether the person can see a clear confirmation. A large desktop form compressed into a narrow window can be technically mobile compatible while being difficult to finish.
Shared devices add another problem. The next employee must not inherit a previous session or see the last person’s documents when the browser goes back. Ask the vendor to demonstrate sign out, session expiry and a return to the same page after another user signs in. If workers receive notifications on personal phones, decide which details can appear in a lock screen preview. A short instruction to open the portal may be enough.
Plan for people who cannot use self service during their shift. An authorised HR officer may need to enter a request on someone’s behalf. The record should distinguish the employee affected, the person who entered it and the person who approved it. Without those distinctions, a reviewer may wrongly conclude that an employee submitted a request they never saw. Provide a receipt the employee can review through an agreed channel.
Measure completion with a realistic task. Give a new starter the employee handbook and a test account, then ask them to update a contact detail and find the status of an absence. Observe without coaching. When the person hesitates, identify the label or step that caused the delay. The result is more informative than asking whether the portal feels intuitive immediately after the vendor has explained every screen.
Agree the handover to payroll
HR and finance can share a staff list yet disagree about which changes belong in a particular pay period. Set a cutoff and a record of what was handed over. For each change, include the stable employee identifier, effective date, field changed, old and new value where appropriate, and the approval reference. Restrict the file to what the receiving team needs. A payroll interface has no reason to expose every document HR holds.
Try an employee who transfers on the sixteenth, an acting allowance that begins on the twentieth and a correction approved after cutoff. Ask finance to explain the expected result before the supplier runs the export. The HR system may send dated instructions while payroll performs the calculation. Or an agreed allocation may originate in HR. Either model can work when one party owns each calculation and both parties can reconcile the result.
Run the export twice. An identical second file should not create duplicate changes when finance imports it. A replacement file containing an amendment should be distinguishable from the original. Find out whether finance can reject just one bad row, how HR learns about the rejection and whether an already accepted row is safe to resend. Errors caught during a trial cost less than a duplicated instruction discovered after bank files have been prepared.
Finish by reconciling people as well as values. Count joiners, exits, transfers and changes with financial effects. Match those counts to the receiving system and investigate exceptions by identifier. A file with the expected total number of rows can still contain the wrong person twice. Keep the reconciliation with the period record so another colleague can reproduce the decision while the usual payroll officer is away.
Separate headcount, positions and vacancies
A transfer exposes weaknesses in headcount reports. At the end of the month, should the dispatcher count in Nairobi, Nakuru or both? A national report that counts one person in each branch overstates the workforce. A branch report that shows only permanent assignments can understate the people available for today’s shift. Name the question next to the report and give readers the reporting date.
Position control answers a separate question. The company may have approved four dispatcher positions in Nakuru even though only three people are physically present. An employee on a temporary assignment can still occupy an approved position. If every movement creates a vacancy automatically, recruitment could open a permanent role that the business never authorised. Decide who approves changes to the position plan and how temporary cover appears.
Open a sample report for the past month before and after entering a backdated transfer. Does the report show the latest understanding of that month or the figures originally presented to management? Both views can be valuable. A saved monthly snapshot preserves what executives saw at the time. A restated view helps analysts understand what really happened. Give them distinct names and explain which one the board pack uses.
Consider time as well as people when analysing capacity. Two part time employees can be two people and one equivalent full time position under a suitable working hours convention. A relief worker covering an absence contributes hours without necessarily representing another permanent role. Agree definitions with finance and operations before requesting a dashboard. Otherwise a polished chart can turn a disagreement about definitions into an argument about data quality.
Migrate records without moving every old mistake
Treat migration as an editorial exercise. Identify what must support current work, what should remain available as restricted history and what should be retired under your approved retention policy. The temptation to upload every spreadsheet and scanned document is understandable. It also migrates contradictory names, stale contact details and obsolete permissions into a system employees will assume is authoritative.
Start with an inventory of sources. The main register may hold identifiers, branch files may hold current supervisors, and payroll may hold the best record of active employees. Choose an owner to resolve conflicts for each field. Finance should not silently overwrite a person’s current manager because an old cost centre still appears in payroll. Keep a record of which source won and which exceptions require a conversation with the employee.
Use a sample that contains difficult cases. Include someone on secondment, a recent leaver, a person with two historical assignments and two people with similar names. Compare their records field by field after a trial import. Check documents under the intended roles rather than under the administrator account used for upload. An import can preserve the right files while placing them in a folder visible to the wrong people.
Assign somebody to own the unresolved list. Each entry needs a specific question, a source likely to answer it and a date for resolution. If a missing item is unnecessary for launch, mark that explicitly. If the missing item controls access or determines whether an employee is active, keep the record out of the live workflow until the responsible person decides. A checklist marked ninety percent complete says little about the importance of the remaining ten percent.
Put privacy decisions into the design
Employee files include information whose exposure can affect a person’s safety, reputation or working relationships. Start with purpose and access. Which record does a supervisor need to plan a shift? Which records should only HR see? Who may export a file containing the entire workforce? Distinguish access needed to perform a duty from interest in the information. Consult the relevant Kenyan guidance when deciding how your organisation will handle employee data. Office of the Data Protection Commissioner guidance.
Test what happens when an employee corrects their emergency contact. The old contact should stop appearing in the operational directory, while authorised staff can explain when the update was made if your policy requires that history. Consider who may read the previous value, whether a change should be verified and what the employee can see about the update. Keeping an audit trail does not justify broad access to every historical detail.
External support access requires a practical boundary. If a technician must inspect a problem, decide who authorises access, how long it lasts and what evidence remains after the session ends. Prepare fictional examples for ordinary support requests. Screenshots can expose employee details long after the support ticket closes. A small support form that asks for the record reference, time and observed behaviour can reduce unnecessary copying.
Ask procurement to clarify where data is stored, which providers may process it, how backups are handled and what happens when the agreement ends. Obtain answers that the organisation can review against its own obligations. A general assurance about security is difficult to test. A defined export procedure, named approval route and demonstrated access review are concrete enough for HR and IT to rehearse together.
Walk the employee through an exit
End the demonstration by bringing the dispatcher back to Nakuru and then processing a later resignation. Separate the notice date, last working day and end of employment in your chosen policy. Dates may coincide in a simple case, but they answer different questions. A manager planning shifts needs the last day of attendance. A payroll officer needs the approved end of the employment period and any agreed follow up items.
List tasks by the person who can perform them. Operations confirms the final shift. Stores checks assigned equipment. IT closes access according to the approved timetable. HR confirms the personnel record. Finance receives the handover. Some tasks may finish after the employee leaves. Assigning every open item to the departing person’s account ensures that unfinished work disappears precisely when somebody needs to see it.
Question an automatic rule that blocks all exit steps until a uniform or device is returned. Equipment recovery and account closure can have different urgency. A missing charger should not leave an old account active. Record the outstanding item with its owner and continue the independent actions. Agree how disputes are referred to the responsible manager without exposing the details to everyone who handles the exit checklist.
Finally rehire the same fictitious person. The supplier should show how a new employment period begins, how old rights stay closed and which information is confirmed again. A convenient reactivation button can restore access that no longer matches the job. Ask the new supervisor to verify duties afresh. The test reveals whether your system recognises the person while treating the new relationship with the care it deserves.
Compare offers on the work they include
A supplier quoting a monthly price per employee may include only the core register. Another may include onboarding, employee self service and a basic payroll export but charge separately for complex approval rules. Ask for a written example using your projected workforce, branch count and support needs. Compare the cost of the first operating year with the recurring cost after implementation. Separate optional features so a low entry price cannot hide a costly dependency.
Include internal work in the comparison. Somebody must review the employee list, confirm manager relationships, validate leave balances and train supervisors. If a supplier expects your team to perform those tasks, reserve staff time. If the supplier will perform them, specify the inputs you will provide and the corrections included. Migration priced only by the number of rows can overlook the work involved in resolving contradictions between those rows.
Ask each supplier to show what a routine change costs after launch. Add a new branch, introduce a temporary approver, correct an earlier department name and create a new report. Some changes may be manageable by an authorised administrator. Others may require vendor work. Judge the offer against the frequency of real changes in your organisation. A rare specialist adjustment is different from a paid support request every time someone covers a manager.
Keep demonstration evidence alongside the price. Record whether the transfer, leave amendment, payroll resend and exit tests worked, required configuration or remain unproven. Use the same examples for each supplier. If a vendor promises a future change, ask for its scope, price and acceptance condition in writing. People attending different demonstrations can then compare observed results without relying on memory or presentation style.
Make the pilot small enough to learn from
Pilot the system across one originating branch and one receiving branch. A pilot limited to a single office can hide the very boundary problems that made the purchase necessary. Select representatives who actually approve shifts, answer leave questions and prepare payroll files. Give each one a scenario to complete without an administrator seated beside them. Record the task, time, outcome and any help required.
Take a baseline before implementation. Count unresolved leave requests older than your chosen service window, corrections sent to payroll after cutoff and staff whose recorded supervisor differs from their working supervisor. Record how you sampled the records. These figures will mean more to a branch manager than a long list of activated modules. Repeat the same checks after the pilot and explain significant changes, including any temporary rise caused by better visibility.
Plan the first support week around demand. Managers may need help finding delegated approvals. Employees may need assistance recovering accounts. HR may discover duplicate staff records overlooked in the trial. Assign owners for these different problems and tell employees where to raise them. A shared inbox can work when someone watches it and records decisions. An elaborate ticket system cannot compensate for uncertainty about who responds.
Use the final pilot meeting to make specific decisions. Which defects must be fixed before the next branch joins? Which are training issues? Which policies need clarification from management? Write down the evidence that would close each item. When a branch manager says the roster is wrong, identify a dated example and compare it to the agreed rule. This turns a broad objection into a decision the team can resolve.
Decide what the employee should receive
Write a sample transfer notice in the language your workforce uses. It should tell the dispatcher where to report, when the arrangement begins, who approves her requests and who can answer a question about the return date. A system email containing only a transaction number may satisfy a technical requirement while leaving her to telephone both branches. Read the sample aloud and see whether a person unfamiliar with HR terminology can act on it.
Give the employee a way to flag an error without granting permission to rewrite an approved assignment. Imagine that the notice says Nairobi for three months when the supervisors agreed on three weeks. A correction request should go to the named owner with the original instruction attached. The employee needs a visible acknowledgement and a way to find the outcome. Once amended, the notice should identify the changed date clearly enough that an earlier printed copy causes no confusion.
Treat accessibility as part of this exercise. Enlarge the text, navigate with a keyboard and check whether status is expressed in words as well as colour. Invite somebody who uses the interface differently from its designer to try the same tasks independently.
Take one case into the buying conversation
Before requesting a proposal, assemble a fictitious employee record, a temporary transfer instruction, a leave request spanning the change, a payroll cutoff date and a later exit. Ask HR, finance and operations to write their expected results independently. Disagreements between those answers are valuable. They reveal policy decisions the supplier cannot make on your behalf. Resolve them or explicitly price the work needed to do so.
Bring the person who receives the least attention in a typical sales meeting. It might be a depot clerk who enters requests for colleagues on a shared device. It might be the finance assistant who notices a missing allowance only after importing the monthly file. Give that person control of the demonstration for ten minutes. Watch where they need help and what evidence they would need to explain the result to someone else.
Keep the dated example available when the next branch manager joins the pilot team.
Your eventual purchase should make a small promise that the workforce can recognise. When a dispatcher changes branches, the appropriate supervisor sees the request, finance receives the correct dated change, and the employee knows what happened. Specify those outcomes in the brief and preserve the example for acceptance testing. For more Kenyan operations and software buying guides, visit the ZamaCore blog.