1
Define the result
The project begins with the result the business needs, not a broad request to “fix HR.” A useful result is concrete: an approved handbook and acknowledgment workflow, a reorganized employee-file structure with an exception log, or a documented onboarding process with role-specific checklists.
The scope states what Steady will deliver, what source information the client will provide, who approves decisions, which systems are involved, and what requires outside review.
2
Inventory the current state
Steady reviews the materials and workflows relevant to the project. For a file cleanup, that means the existing folders, HRIS, payroll roster, naming conventions, and approved retention structure. For onboarding, it includes the offer handoff, forms, payroll, benefits, access, equipment, orientation, and manager tasks.
The inventory produces an exception list. Missing documents, contradictory policies, unresolved classifications, and legal questions are not silently filled with assumptions.
3
Build and review
Steady prepares the structure, draft, templates, or cleaned data included in scope. The client reviews operational decisions, and qualified specialists review legal, benefits, safety, tax, or regulated matters when needed.
For a handbook, see employee handbooks and HR policies ↗. For employee files, see employee records administration ↗. These focused pages explain the boundaries that also apply inside a project.
4
Implement and hand off
A finished document is not a finished process. The handoff can include manager instructions, a rollout checklist, employee acknowledgments, a maintenance calendar, permissions, file naming rules, and a list of open items outside the project.
If the client wants Steady to maintain the result, the project can transition into fractional HR support ↗ or a narrower recurring administrative service.