These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- HRMS + PM for IT Companies
- Features
- Organization and employees
Organization and employees
Keep the employee register, reporting lines and position records aligned.
OverviewActive employees×
HRMS + PM for IT Companies · Organization and employees
New
Active employees
Employees
| Employee ID | Full name | Department | Position | Manager | Location | |
|---|---|---|---|---|---|---|
| EI-663 | Full 416 | DPR-130 | PST-2447 | LCT-150 | ||
| EI-876 | Full 659 | DPR-150 | PST-8239 | LCT-140 | ||
| EI-100 | Full 520 | DPR-110 | PST-8451 | LCT-110 | ||
| EI-825 | Full 972 | DPR-110 | PST-5120 | LCT-110 | ||
| EI-754 | Full 778 | DPR-110 | PST-5530 | LCT-120 |
6 of 6 records
EI-663Employees · EMP-84729
ActiveFull nameFull 416
DepartmentDPR-130
PositionPST-2447
LocationLCT-150
What you can do
Give each person a place in the organization
Departments and locations give the employee register its working structure. A position carries a job title, department, location, pay grade and reporting position. An employee links to a position, manager, payroll calendar and current status. The Employees feature page gives HR Business Partner a filtered register, a distribution by department and an individual detail. HR Business Partner should agree which department and position owns a worker before the first payroll cycle.
The HR Business Partner maintains the people and position records. The CHRO / VP People reviews the distribution and exceptions; Admin controls setup. A manager change belongs in employment history with its effective date and from and to manager. That dated event matters when an employee moves between engineering groups: the current register should show the new manager, while the earlier decision remains traceable.
How the work is organized
- Placement. HR Business Partner checks that each employee points to the right position, department, location and manager.
- Vacancy. A planned or open position keeps its headcount and pay grade separate from a filled employee record.
- History. A dated employment event explains a manager, position or salary change without hiding the prior assignment.
What to agree during setup
HR Business Partner and Admin agree the job title, position and pay grade list before importing employees. Check that each location has the right country and that each payroll calendar matches the employee’s entity and currency. Decide who records a manager or position change and who checks the effective date. The CHRO / VP People can inspect the records, while HR Business Partner maintains employee and position details. Review roles before loading salary data.
Check the handoff on an actual case
For example, a developer joins a remote engineering department as a contractor. HR records their country, entity, hire date, employment type, location and manager. The position points to the approved job title and pay grade. When the developer becomes full time, HR updates the employment type, records a dated employment event where the change affects position or compensation, and checks the employee record before payroll uses it. If the company has positions reserved for future hires, those remain separate from active employees.
At the end of the case, ask the person receiving the work to inspect the record, its owner and its status. If a date or reference is wrong, correct that source record before using a summary or report. Keep the original decision visible so the next person can tell why the change occurred.
What your team sees
- Active employees — The primary list for this work, with the owner and current status beside the record.
- Open positions board — A focused list for the next review or handoff.
Follow the work through
- Requisition to hire: Rehearse the decision and the record passed to the next owner.
- Implementation: Prepare the first operating cycle.
What it keeps track of
Data model- Departments
- Organizational departments with parent hierarchy and cost centers.
- Positions
- Seat-level org entries that an Employee fills.
- Job titles
- Canonical job titles with job family, level and exempt status.
- Locations
- Physical and remote locations where employees work.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Pay grades
- Salary bands tied to job titles and positions.
Who uses it
Permissions- HR Business Partner
- , CHRO / VP People, Admin.
- Each person should see only the records needed for their part of the cycle.
Set up HRMS + PM for IT Companies your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.