/ solutions / people operations
People operations stops being the answer desk and the file clerk
A people-operations team spends its day answering the same policy questions and hunting for the right version of a record. We build the systems that take both off the desk: a knowledge agent over the team's own policy and process, and document control for the records and sign-offs behind it.
The same policy question comes to a person over and over
How much leave is left, what the plan covers, how a transfer gets approved, what the expense policy allows: the answers already live in a handbook or a benefits summary, and the team reads them out by hand, one person at a time. People operations becomes the answer desk, and the questions never stop arriving.
A knowledge agent over the team's own policy and process material answers those in plain language and learns from how people use it, so the second person to ask gets the answer without someone finding the document again.
Records and sign-offs are scattered across folders and email
Policies live as files on a shared drive. Employee records sit in another folder. The acknowledgement that someone read the current policy sits in a forwarded email, if it was kept. Finding the current version, or proving who signed it, means knowing where each piece was filed.
Document control moves them into one database: versioned, access-controlled, and attributed, with the sign-off enforced. The current policy is the one you find, a personnel file is visible only to the people who should see it, and the acknowledgement behind a policy is a real record instead of a search of the inbox.
Onboarding runs by hand, one checklist at a time
A new hire arrives and the team runs the same sequence by hand: send the policies, collect the signed forms, answer the questions every new hire asks, chase the sign-offs that stall. It is the answer desk and the file clerk at once, repeated per person.
The two systems carry it. The knowledge agent fields the questions the new hire would otherwise bring to a person, and document control holds the forms and acknowledgements as a record that shows, at a glance, what is signed and what is still open. The team runs onboarding by exception instead of by hand.
/ use cases
What we build for People operations
The policy helpdesk runs on the handbook, not on a person
Explore ›Onboarding automationOnboarding runs as a controlled flow, not a checklist per hire
Explore ›Employee recordsA personnel file only the right people can open, with every change attributed
Explore ›Case managementEmployee requests become tracked cases, not an inbox nobody can see into
Explore ›/ start
Start with the work piling up on the people-ops desk
Tell us which questions repeat and where the records live, and we scope it. Or email hello@mcintoshsystems.com.