HR management template for people operations teams
Run employee records, PTO balances, and policy acknowledgments in one workspace your HR team owns in GitHub. This template models headcount lifecycle events—not a generic contact directory—so managers, HRBPs, and employees see the right fields and approvals from day one.
Centralize employee profiles, leave requests, and org changes with audit-friendly history.
- Maya Chen — PTOMar 12–16 · Manager Alex
- Jordan Lee — Sick leaveToday · Auto-approved
- Sam Ortiz — ParentalApr 1 start · HR review
What's included
Centralize employee profiles, leave requests, and org changes with audit-friendly history.
Intended users
- HR managers
- People ops
- Department leads
Suggested stack
- PostgreSQL
- Next.js
- Resend for HR emails
Core features
Employee directory with departments
PTO request and approval queues
Document acknowledgment tracking
Org chart and manager hierarchy
Role-scoped HR dashboards
Main workflows
Request time off
Submit dates, check balance, route to manager for approval.
Onboard new hire
Create employee record, assign manager, queue required docs.
Acknowledge policy
Notify affected employees and record signed versions.
Database model / entities
Distinct domain entities — not a renamed generic CRUD list.
User roles
- HR admin
- Manager
- Employee
- Payroll viewer
Possible integrations
Applications built from this template can connect to these services via their APIs.
- Slack
- Resend
- Google Calendar
- Okta
Example prompt
Copy this into Evonx to start from a production-shaped brief instead of a blank canvas.
How Evonx customizes this template
Start from the domain model above, describe the workflows your team needs, and Evonx generates a working preview you can refine. For teams with an existing codebase, the same agent can extend repositories instead of starting from a blank project.
Related resources
FAQ
Does this HR template handle PTO balances and approvals?
Yes. Leave requests check remaining balances, route to managers, and write an audit trail so payroll and people ops stay aligned.
Can we model contractors separately from full-time employees?
Describe contractor vs employee employment types in Evonx; the generated schema and permissions can keep fields and reports distinct without a rewrite.
How do policy acknowledgments work for handbook updates?
Each policy version can require re-acknowledgment. Employees see outstanding items; HR sees completion rates by department.
Will managers see salary fields for their whole company?
No by default. Sensitive compensation fields stay scoped to HR admin and payroll viewer roles unless you explicitly expand permissions.
Build production software with Evonx
Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.