An HRMS rollout checklist for a growing pharma team

1. Choose one workflow and its owner.

Pick a task that already consumes time: reconciling attendance, reviewing field visits or collecting travel claims. Identify the employee who submits the record, the manager who decides what happens next and the person who maintains the master data.

For a pharma team, a useful first journey is one rep, one territory, one doctor visit and one exception. Follow it through the system before deciding how much to roll out. Assign an internal rollout owner who can resolve conflicting records and confirm which process the company intends to use.

2. Prepare the employee foundation.

Check employee codes, names, joining dates, departments, designations, reporting managers and shift assignments. A single person appearing under different names in attendance, expenses and payroll creates work that software alone will not remove.

• Agree which existing record is authoritative.
• Resolve duplicate employee codes and inactive employees.
• Check who each employee reports to, including field reps.
• Decide who can correct a record and how the correction is reviewed.

Use sample or redacted records for the first demonstration. Arrange a secure handover for actual employee and payroll data during implementation; an enquiry form is not the place to send it.

3. Clean the territory and client records.

A territory structure and an approved client assignment answer different questions. The territory defines an area of responsibility. The client assignment identifies the doctors or trade clients a rep is expected to work with. Confirm both rather than assuming a map or hierarchy settles individual ownership.

Prepare doctor, chemist and stockist records with consistent names and territory links. For doctors with multiple chambers, check the location attached to each visit and the operating hours your team plans to use. A mistaken map pin can produce an exception even when a rep went to the expected place.

4. Test a rule by its effect.

List the attendance, leave, expense and field-visit rules that matter to your business. A configurable field is only useful when the daily workflow actually uses it. In a walkthrough, change a representative rule and verify the resulting calculation, status or approval path.

Test the exception as well as the normal path. What happens when a visit is outside the expected radius? Who sees the request? What explanation can the employee add? Can the manager’s decision be found later?

Repeat that exercise with the roles that will use the system: administrator, HR, manager and employee. Check access to another employee’s records, exports and approval controls. Agree access and data-handling responsibilities before introducing real records.

5. Confirm the modules and regional scope.

Separate the HR foundation from optional capabilities. Attendance, expenses, payroll, request approvals and coverage analysis may have different setup or entitlement requirements. Ask for the agreed modules and features in writing, together with setup, support, hosting and any integration work.

JASO HR’s payroll configuration currently focuses on India. If your team operates elsewhere, discuss country-specific payroll and statutory requirements before choosing a rollout. Currency or timezone settings alone do not establish a country’s payroll requirements.

6. Run a representative pilot.

Use a manageable group with a manager, an HR user and field reps. Include a routine visit, a location exception, a leave request, an expense and the report a manager needs. If payroll is in scope, compare a sample payroll result against an agreed calculation before adopting it for a live pay period.

For the field report, distinguish activity from coverage. Thirty visits to fifteen unique doctors across a territory of forty doctors gives 37.5% unique-client coverage. That is an illustrative calculation, not a customer result. The manager still needs the agreed visit cycle to decide whether an unvisited doctor is overdue.

Agree what the pilot must demonstrate, who signs it off and which issues must be resolved before expansion. Test the devices, connectivity and exception paths your team will actually encounter. A portal demonstration does not settle every mobile or offline requirement.

7. Agree the handover before expanding.

Name the people responsible for training, master-data changes, support requests, backups and access reviews. Confirm the escalation route and what ongoing support includes. Record the configuration you agreed, the decisions made during the pilot and any requirements left outside the scope.

The downloadable checklist gives each preparation task an owner, a readiness status and a place for questions. Use it to keep the rollout discussion concrete, then adapt it to your company.