01 · DEPARTMENTSOrganization
Name, code, lead, and status identify the operating home.
Product model
Every dependency stays attached to the person and plan.
HRMS keeps organization, employment, onboarding, enablement, and acknowledgement records distinct while connecting them around the target start.
Eight records, one readiness context.
Each table represents work a team recognizes and can own.
02 · POSITIONSApproved role
Title, code, location, status, and department define the job.
03 · EMPLOYEESPerson context
Name, work email, start date, employment state, department, and position stay together.
04 · ONBOARDING PLANSReadiness owner
Employee, position, target date, plan owner, and status anchor the work.
05 · ONBOARDING TASKSSequenced preparation
Task, owner team, due date, state, and plan make responsibility visible.
06 · EQUIPMENT REQUESTSPhysical enablement
Equipment type, needed-by date, request state, asset tag, and plan stay linked.
07 · ACCESS REQUESTSSystem enablement
System, profile, needed-by date, request state, and plan preserve the approval boundary.
08 · POLICY ACKNOWLEDGEMENTSCompliance evidence
Policy, assignment date, acknowledgement date, state, and plan retain completion.
Roles match the teams doing the work.
HR, hiring managers, IT, and employee experience collaborate without receiving identical authority.
| Role | Primary responsibility | Control boundary |
|---|---|---|
| HR Administrator | People context, plans, tasks, and acknowledgement | Equipment and access remain read-only |
| Hiring Manager | Plan ownership and manager tasks | No system provisioning |
| IT Coordinator | Equipment, access, and assigned IT tasks | Employment records remain read-only |
| Employee Experience | Plan support and onboarding tasks | Policy evidence remains visible, not rewritten |