Post: 9 HRIS Configuration Defaults Every Small HR Team Should Change
Most HRIS platforms ship with conservative defaults that prioritize ease of implementation over data quality. Nine of those defaults are quietly producing the errors that small HR teams spend hours cleaning up later. Change them this week and the next quarter of cleanup work disappears.
This is the configuration companion to our pillar Drowning in Admin. The pillar explains why these defaults exist. This piece tells you which to change first.
How We Evaluated
Each default was scored on three criteria: frequency of error it prevents, time to configure, and risk of breaking an existing workflow. Defaults that prevent high-frequency errors with low configuration risk are the ones to change first. Names of specific settings vary by platform — the pattern is what matters.
Quick Reference Table
| Setting | Prevents | Configuration Time |
|---|---|---|
| Required fields on hire | Missing SSN, address, eligibility data | 1 hour |
| Effective-dated compensation | Salary drift between events | 2 hours |
| Date validation on hire/term | Future hires, retro terms | 30 minutes |
| I-9 expiration alerts | Re-verification gaps | 1 hour |
| Benefits eligibility logic | Wrong-plan enrollments | 4 hours |
| Audit log retention | Lost change history | 15 minutes |
| Manager approval routing | Unapproved changes | 2 hours |
| Document expiration tracking | Expired licenses, certs | 1 hour |
| Self-service field locks | Employees editing locked data | 1 hour |
1. Required Fields on Hire and Change Events
Most HRIS platforms ship with a handful of required fields and dozens of optional ones. The optional fields are where data quality drops. Make all data needed for I-9, benefits eligibility, payroll tax setup, and emergency contact mandatory at the hire event. The configuration is a one-hour task. The downstream cleanup it prevents is a quarter of work.
2. Effective-Dated Compensation History
Default behavior on many HRIS platforms is to overwrite the previous compensation value rather than preserve a dated history. Turn on effective-dated records for every compensation change. Without it, you cannot prove what someone was paid as of a specific date — which means you cannot defend against a back-pay claim or audit.
3. Date Validation on Hire and Termination Events
Without date validation, an HR coordinator can record a hire date six months in the future or a termination date six months in the past. Both create downstream errors in benefits eligibility, ACA reporting, and payroll. Turn on validation rules that prevent dates outside a sensible window without manager override.
4. I-9 and Document Expiration Alerts
Most HRIS platforms support alerts on document expiration — work authorization, professional licenses, training certifications. Default configuration is alerts off. Turn them on with a 90-day lookahead so re-verifications happen on time.
5. Benefits Eligibility Logic
Default eligibility rules are usually “wide open” — every plan is enrollable by every employee. Configure tight eligibility logic per plan: hourly versus salaried, full-time versus part-time, location, tenure. Wrong-plan enrollments are the source of most carrier feed errors, and they originate at this configuration layer.
6. Audit Log Retention
Audit logs are retained for a short default window in most platforms — sometimes as little as 30 days. Extend retention to the maximum the platform supports, ideally seven years to match HR records retention standards. The retention extension is usually a single setting and free.
7. Manager Approval Routing on Changes
Without approval routing, an HR coordinator can change anyone’s compensation or title without a check. Configure manager approval routing on the change types that matter — comp, title, manager assignment, classification. Slows things down by a day. Prevents a year of unauthorized changes.
8. Document Expiration Tracking on Compliance Documents
Beyond I-9 work authorization, this covers professional licenses, OSHA training certificates, harassment training renewals, and any document with a regulatory expiration. The system tracks expirations and alerts on lookahead. Default is off.
9. Self-Service Field Locks
Default self-service portals let employees update fields they should not — sometimes including bank routing numbers, addresses without verification, or even tax withholding without compliance checks. Lock the fields that require HR or payroll verification, and route changes through an approval workflow.
How We Evaluated, In Detail
The pattern across these nine settings is the same: the HRIS vendor ships with the lowest-friction default to make implementation easy. The defaults assume a fully staffed HR team will configure the platform during rollout. For inherited operations and HR-of-one environments, the defaults work against you. Spend a day changing them and the next quarter of error-correction work disappears.
For the broader framework on what to fix and in what order, return to the pillar. For specific tooling decisions, see our 2026 HR-of-one tools list.
