AI Intake for Employment Law Firms: Charge Deadlines and Document Lists
AI intake for employment law firms: an intake form, a document checklist and deadline tracking an agent can run, with attorneys approving every legal date.

AI for an employment law firm is most useful at intake, where an agent gathers the facts, sorts the documents a matter needs and prepares a deadline log that an attorney reviews. The agent does not decide whether a claim is viable, whether a filing is required or which date controls. Those judgments stay with licensed attorneys, supported by a written intake form, a document checklist and a deadline process the firm owns and can audit.
Key takeaways
- Intake is the best first place to add an agent, because missing facts and missing documents create most of the rework early in a matter.
- The agent can run the intake form, the document checklist and the deadline log, but no legal date reaches a confirmed calendar without an attorney's sign-off.
- Write the firm's rules in plain language: which facts trigger which questions, which documents to request and which dates are only candidates.
- Limit permissions to reading the file, drafting summaries and tracking requests. Filing, advice and edits to confirmed dates stay out of scope.
- Judge success with observable checks, such as whether every intake reaches an attorney with a complete, reviewed document list and a logged decision for each date.
Why intake is where employment matters stall
Most prospective clients describe their situation as a story. They mention a meeting with a manager, a text message, a termination on a Friday and a complaint sent weeks earlier, but they rarely give the facts in the order an attorney needs them. The first call often leaves gaps: the employer's exact name as it appears on pay records, the date of each adverse action, whether an internal complaint was made in writing, whether an agency has already been contacted and what the client signed on the way out. Each gap delays the matter, and some of them change the analysis entirely.
Deadlines add pressure. The periods that apply to an employment matter depend on the type of claim, the agency or court involved, the jurisdiction and the date of the triggering event. A calculation that starts from the wrong event or the wrong rule can be wrong without anyone noticing, which is why a rule sheet written and reviewed by attorneys has to sit behind every calculation an agent makes. Firms that handle adjacent matters can compare the intake pattern in family law intake and court dates.
Building an intake form the agent can follow
A good intake form is organized around decisions, not around database fields. The agent should begin with the client's account in their own words, then ask structured questions that fill the gaps. A practical form groups questions into six blocks:
- Parties and representation: the client's contact details, any representative and any prior counsel.
- Employer details: the legal name as it appears on pay records, work locations and the client's understanding of company size.
- The events: a short narrative, then each adverse action with its date, the people involved and the client's own description.
- Prior steps: internal complaints, written responses, agency contact, and any charge or filing already made, with dates.
- Separation details: notices received, severance offered, and any agreement signed, with the date it was signed.
- Preservation: whether the client still has messages, schedules, calendars and records, and whether anything is at risk of deletion.
The agent's job within this form is to record answers accurately and to flag contradictions rather than resolve them. If the client says a complaint was sent in one month but the attached email is dated in another, the agent should record both facts, mark the conflict and route it to an attorney. It should not choose the version it prefers.
The document checklist and how it gets built
Each matter type should have a standard checklist that the agent adapts from the intake answers. The checklist is a working tool, so each line should name the document and say, in plain words, why it is requested:
- Offer letter and later notices of pay, role or schedule changes
- Pay stubs and payroll records covering the period in question
- Performance reviews, written warnings and any improvement plans, with dates
- Termination notice, resignation message or other separation communication
- Separation or release agreement, including any drafts the client received
- Messages and emails describing the events, saved in their original form rather than retyped
- Internal complaints and any responses received
- Any agency notice, charge or correspondence the client has received
- Medical or leave paperwork, requested only when an attorney has asked for it for this matter
The agent maps what the client has provided against this list, marks missing items, drafts request letters from approved templates and tracks responses. It labels each document neutrally, for example by type and date, and does not characterize its legal weight. Employment files contain sensitive personal data, so the checklist should ask only for what the matter needs, and the agent's access should match that scope. Document handling follows a similar logic in process server service logs.
Deadline tracking: candidates, not conclusions
An agent can keep a deadline log with clear fields: the triggering event, its date and source, the rule the attorney has assigned, the jurisdiction, the responsible attorney, the status and the confirmation record. When a rule is supplied, the agent can compute a candidate date from it. Every candidate stays labeled as a candidate until an attorney confirms it, adjusts it or rejects it.
A simple process keeps this honest:
- Attorneys write and date the deadline rule sheet for each claim type and agency, and set a review date for it.
- The agent logs events from intake and computes candidate dates only from rules on that sheet.
- Each candidate enters an attorney review queue with the source facts attached.
- An attorney confirms, adjusts or rejects the candidate, and the approver and time are recorded.
- Confirmed dates move to the firm's calendar with reminders that name an owner.
- A paralegal reviews the open queue on a fixed schedule, and any item without an owner escalates to the responsible attorney.
Illustrative scenario: A caller says she was let go a few weeks ago and that she sent a complaint to human resources before that. She is not sure of the exact dates. The agent records both events, marks the dates as unconfirmed, attaches the messages she uploads and places the matter in the attorney queue with the candidate windows that the firm's rule sheet associates with those events. The attorney checks the pay records, corrects one date, decides which window governs and signs off before the calendar entry is marked confirmed. At no point does the agent tell the caller a deadline, estimate a filing date or decide whether the complaint has legal significance.
An agent can calculate a candidate date. Only an attorney can turn it into a deadline the firm acts on.
Permissions, audit trails and measuring the results
Authorization is where the design either holds or fails. The agent should have scoped, revocable access to the matter folders it needs and to the intake and checklist tools, and nothing else. Reading the file and drafting summaries is a reasonable default. Sending advice, filing with an agency, deleting records and changing a confirmed date are outside its permissions, and the system should enforce those limits rather than rely on instructions in a prompt. The OWASP authorization guidance is a useful reference for checking whether each action is allowed for a specific role and matter, not merely for any logged-in user.
Documents from clients, employers and other parties also deserve caution. A file can contain text that tries to steer an assistant, such as an instruction to ignore the firm's rules, so the agent should treat document contents as data to summarize, not as commands. The OWASP prompt injection guidance describes this risk and the controls around it. Every action should land in an audit trail that shows what the agent read, what it drafted, who approved it and when, so an attorney can reconstruct how any date or document was reached.
Measure the process rather than the impression. Useful checks include how often attorneys correct the agent's intake summaries, how long an intake takes to reach the review queue, whether any confirmed deadline lacks a source fact or a named approver, and whether the agent has ever produced content outside its scope. The NIST AI Risk Management Framework offers a sound structure for deciding who owns these risks and how they are reviewed. Each finding should lead to a specific change in the form, the checklist or the permissions.
How Be Human runs this as a managed service
Be Human starts with one useful role. For an employment practice, that is usually intake and deadline support for one matter type, with the memory and tools the role needs, written approval boundaries and a success criterion the firm can observe in its logs. Managed operations then cover monitoring of the review queue, recurring evaluations of intake summaries against attorney corrections, permission reviews when staff or practice areas change, and controlled updates when the rule sheet changes. The work is delivered remotely, in English or Portuguese, and attorney judgment and sign-off remain with the firm.
Where to start
For most firms, the best first task is the one with the most repeated facts, the clearest owner and the least legal discretion, which is usually the intake form and document request cycle rather than deadline calculation. Start there, write the rules down, and expand only after attorneys have reviewed several matters from intake to confirmed calendar entry. If you want to find the first intake task worth handing to an agent, take the free Be Human AI diagnostic.
Frequently asked questions
Can an AI agent tell a client when a deadline expires? No. The agent can compute a candidate date from a rule an attorney has written and approved for the firm, but it should not state deadlines to clients or to anyone outside the firm. An attorney reviews each candidate, confirms or corrects it and records the decision before it appears as a confirmed entry.
Does the agent need access to our case management system? It usually needs read and draft access to the matter records it works on, plus write access to the intake and checklist tools, and nothing more. Access should be scoped to each matter, revocable and logged. Permissions should be reviewed whenever staff or practice areas change.
How do we protect confidential client documents? Limit collection to what the matter requires, keep data in systems the firm approves, restrict access by role, and avoid sending documents to any tool without contractual terms covering confidentiality and retention. Treat text inside uploaded files as data to be summarized rather than instructions, since documents can contain misleading or manipulative content.
What should we ask a vendor before starting? Ask who writes and approves the rule sheet, how the agent is kept from giving advice or confirming dates, what the audit trail records, how permissions are reviewed and who responds when something goes wrong. Ask to see sample logs and the escalation path rather than accepting a general promise. Ask where the work is performed and how long data is retained.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


