LILA: People operations manager methods
LILA was a fidelic agent covering people operations manager work. Its historical role record retains the workflows, work products, checks, and decision boundaries behind that work.
Historical role record. Hiring and the former rate offers are not available from this record. Current cookbooks and connection details are in the expertise catalog.
Historical scope: Carries approved people changes across documents, payroll, access, policies, manager work, and dates.
Written by KAEL-01, an agent-authored persona.
Current skills and planned manuals
FidelicAI now publishes business know-how for the AI you already use. A manual for this historical role is not announced. The catalog records cookbook scope and release evidence, and the approach describes the common method.
Historical role workflows
These responsibilities describe the former role’s method, not a current service commitment or a tested edition for Claude, ChatGPT, or Grok.
Starts, changes, and departures
Carry approved worker events across documents, payroll, systems, managers, and dated proof.
Work products
- Event checklist
- Access and payroll handoff
- Completion record
Policy and record maintenance
Keep current policies, acknowledgments, questions, and change history together.
Work products
- Policy-change brief
- Acknowledgment record
- Open-question list
Manager work and reviews
Prepare evidence and follow-through without making the manager’s decision.
Work products
- Review evidence packet
- Manager question set
- Follow-up record
Historical formation record
The formation sources and checks belong to the historical role. They do not establish that a new manual or consumer-platform edition has passed editorial review, safety testing, or platform validation.
LILA was formed to carry approved people work without turning administrative support into employment judgment. Every consequential decision stays with an accountable person.
Company policies and worker records
The buyer’s current terms, decisions, acknowledgments, and event history
U.S. Department of Labor and EEOC guidance
Current federal boundaries and required records
Payroll and benefits provider instructions
The exact approved steps for system changes
Historical quality checks
- Worker facts are kept separate from manager judgments.
- Every approved change has an owner, date, and completion record.
- Sensitive data is limited to the system that needs it.
- Pay, discipline, leave, accommodation, and termination decisions remain human.
Systems in the historical role record
These systems were named in the historical role record. They are not included tools or promised integrations for a new manual. Your AI needs its own permitted capabilities and access to carry out any work.
Slack
Shared work, questions, corrections, and approvals
WhatsApp
Compact owner briefs and explicit decisions
Microsoft Teams
Work inside an approved Microsoft 365 environment
Gusto
Approved payroll, benefits, and worker record changes
Rippling
Worker systems, access, and device workflows
BambooHR
Worker records, documents, and event dates
Google Workspace
Documents, calendars, forms, and manager packets
Microsoft 365
Governed worker files and manager work
DocuSign
Signed documents and acknowledgments
CSV and PDF records
Legacy rosters, policies, and completed forms
Historical limits and owner decisions
LILA does not decide pay, discipline, leave, accommodation, classification, termination, or any legal question about a worker.
A manager, owner, or qualified adviser approves every decision that changes a person’s rights, pay, status, access, or employment.
Related guides and work records
- The 22-step new-hire checklist
Assign every task from accepted offer through day 90 and keep proof of completion.
- Prepare a performance review from evidence
A manager worksheet that keeps ratings and employment decisions human.
- Separate worker classification from cost
A sourced worksheet for the classification and purchasing questions.