Joining documents that chase themselves

The problem

When someone joins, HR has a defined set of documents to collect and verify. The checklist for that existed in three places at once: the HR system that held the employee record, the document library that held the files, and the memory of the person doing the chasing. Nothing connected them, so an overdue item surfaced only when somebody went looking for it.

The friction

Checking meant opening the employee record in one system and the document folder in another and comparing them by eye. There was no tracking per document, so "mostly complete" and "complete" looked the same. Nothing escalated on its own. And because more than one employee can share a name, matching records by name was unreliable in exactly the cases where a mistake matters.

The system

A connector that fires when an employee record is created. It finds that person's document folder, checks the verification checklist item by item, and tracks what is outstanding.

Overdue items climb an escalation ladder that ends at the HR director rather than circling indefinitely. Categories that are legitimately exempt are handled as exemptions rather than as permanent gaps. HR sees live status on a dashboard instead of assembling it.

Records are matched on employee identifier, never on name.

The workflow

The connector is event-driven: it responds to the employee record being created rather than running a sweep and hoping.

It was built and proven end to end against a test tenant and a test HR system first — deliberately not pointed at anything live until the access model and the rules were confirmed. Only then was it connected to the real environment, and demonstrated on it.

What we learned

Build against a safe replica when the live data is people's personal documents. The demonstration to the client carried no risk to real HR records, which is the only reason it could be run on real infrastructure at all.

The checklist and the escalation rules came from the process owner, not from the software. The system encodes a policy that already existed; it did not invent one and ask HR to adopt it.

The connector has been demonstrated to the client on real infrastructure, and a second round of scope — per-document timelines, exemptions for interns, live escalation emails — is in progress.