HR Tech

Most agencies approach HR tech like it is a CRUD app with some PDF generation. They build a nice-looking onboarding flow, wire up e-signatures, and call it done. Then the client gets audited and discovers that the I-9 completion dates were not tracked correctly, the document retention policies do not match state requirements, and the system has no way to handle the fact that an employee transferred from Texas to New York mid-year and is now subject to completely different employment laws.

The other dimension most teams miss is integration complexity. HR does not exist in isolation -- it touches payroll, benefits, time tracking, background checks, tax withholding, and ATS systems. Each of these has its own data format, its own sync cadence, and its own failure modes. An onboarding system that cannot feed clean data into payroll is not saving HR time; it is creating a manual reconciliation step that someone has to do every pay period.

Compliance is not a feature -- it is the entire product.

Every form, workflow, and data field exists because a regulation requires it. Miss one, and your client faces fines, lawsuits, or failed audits. The compliance requirements change frequently and vary by jurisdiction.

Employee data is simultaneously the most sensitive and most shared data in an organization.

It flows to payroll, benefits, tax authorities, insurance carriers, and background check providers. Every integration point is a potential data leak or sync failure.

Multi-jurisdiction complexity is not optional.

A company with employees in three states needs three different sets of onboarding documents, three different leave policies, and three different tax withholding configurations. This multiplies with every new state.

Audit trails are not a nice-to-have -- they are a legal requirement.

Every document version, every signature timestamp, every policy acknowledgment needs to be stored immutably with the ability to reproduce the exact state of an employee's record at any point in time.

The end users range from tech-savvy HR professionals to new hires who have never used a digital onboarding system.

The UX needs to handle both without making either group feel lost or patronized.

Data retention and destruction policies are legally mandated and vary by document type.

Some records must be kept for 3 years after termination, some for 7, and some indefinitely. A system that cannot enforce these automatically is a compliance risk.

The I-9 form seems simple.

It is three pages. But ICE fines range from $252 to $2,507 per form for technical violations, and up to $25,076 per form for knowingly hiring unauthorized workers. The timing requirements are strict, the acceptable document combinations are specific, and the re-verification rules for expiring work authorization are where most systems break. We build I-9 workflows with deadline enforcement, document expiration tracking, and automated re-verification reminders.

The onboarding UI can be gorgeous, but if the data does not flow cleanly into ADP, Gusto, or Paychex, HR is still re-keying employee records into payroll manually.

Payroll integration is not just an API call -- it involves mapping job codes, handling mid-period starts, managing tax jurisdiction assignments, and dealing with the fact that every payroll provider has a different data format and a different API philosophy.

We have inherited three HR platforms built by agencies who treated compliance as a phase-two feature.

In every case, retrofitting compliance required restructuring the data model, because compliance is not a layer you add on top -- it determines how data is stored, versioned, and retained. You cannot add document retention policies to a system that overwrites records instead of versioning them.

Every HR platform promises to reduce admin burden through self-service.

What actually happens is that employees now contact HR about the self-service system instead of about the underlying HR question. The UX has to be so simple that a warehouse worker on their phone during a break can complete onboarding without calling anyone. If it requires a manual or a training session, you have failed.

Building a single onboarding flow and assuming it works everywhere is a guaranteed compliance failure. California, New York, Illinois, and Massachusetts each have unique requirements that affect forms, notices, and timelines. The system needs jurisdiction-aware workflows from the start.

When an employee signs a handbook acknowledgment and the handbook is updated six months later, you need both versions. When an employee is terminated, some documents must be retained for years while others must be destroyed. Flat file storage with no lifecycle management is a liability.

ESIGN Act and UETA compliance is not just about capturing a signature image -- it requires intent to sign, consent to do business electronically, record retention, and the ability to reproduce the signed document. Use DocuSign, HelloSign, or a similar compliant provider.

The admin uses the system daily and can learn its quirks. The new hire uses it once, is probably stressed about starting a new job, and is doing it on their phone. If the new hire experience is clunky, HR will spend their "saved" time answering onboarding support questions.

When an employee transfers from one state to another, their tax withholding, leave accruals, benefits eligibility, and required notices all change. Systems that model location as a static field instead of a history with effective dates cannot handle this without manual workarounds.