Preparing employment tribunal and labour claims with AI
By the ChamberOne team 5 minute read
An employment case is usually a story told through documents: emails, contracts, payslips, warning letters, meeting notes. The facts are often messy, the client is often distressed and the paperwork is often incomplete. AI tools are well suited to some of this untidy work. They are poorly suited to other parts, particularly anything that depends on which forum you are in and when a clock started.
Key points
- Identify the forum and calculate every time limit yourself, then diarise them with a second check.
- Use AI for a first-pass chronology, but trace every entry to a document.
- Do not ask a tool which heads of loss apply; check the rules and recalculate any figures.
- Keep witness evidence in the witness's own words.
- Be careful with third-party personal data in the documents you upload.
Begin with the part AI must not touch: forum and time
Employment and labour disputes go to different bodies in different countries, and sometimes to different bodies within one country depending on the claim. Each has its own procedure, forms and deadlines. Some deadlines are short and unforgiving. A tool that answers a question about limitation with a confident number is giving you a guess.
Treat the forum and every time limit as a human responsibility. Identify the correct forum from official sources and your own knowledge. Work out each date yourself, record it in the diary, and have a second person check it. Then use AI for what follows.
Building the chronology
A good chronology is the spine of an employment claim. It shows the sequence of events, links each to a document and exposes gaps. Tools can do a useful first pass if you give them the material in an organised way.
- Gather the documents and number them before you begin, so every entry can point to a reference.
- Ask the tool to list events with date, source document and a one-line description, and to mark anything uncertain.
- Check every entry against the source. Pay attention to dates written in different formats, which tools sometimes misread.
- Ask for a separate list of facts that appear in only one document, and a list of apparent inconsistencies, then investigate both yourself.
- Keep the chronology as a living document and add to it as evidence arrives.
- 1Gather and number the documents
- 2Ask for events with date, source and description
- 3Check every entry against its source
- 4Investigate single-source facts and inconsistencies
- 5Add new evidence as it arrives
- Then back to step 1.
Schedules of loss
A schedule of loss is arithmetic wrapped around legal rules about what can be claimed and how it is measured. AI is better at the first than the second. It can help you lay out a table, collect payslip figures, and set out the headings of loss that you have already identified.
Do not ask it which heads of loss are available or how they are capped or calculated in your jurisdiction. Those rules vary, change over time and are often expressed in statute or regulation that you should read directly. Use a spreadsheet for the calculations, check the formulas, and have the numbers reviewed by someone who did not build them.
Where a tool does produce figures, ask it to show its working, then repeat the sum independently. Small errors in a schedule can undermine the credibility of the whole claim.
Witness evidence
Witness statements should be in the witness's own words and reflect their own recollection. A tool can help you prepare, but it must not put words in anyone's mouth. Useful tasks include organising interview notes into topic order, producing a list of questions for a follow-up meeting, and pointing out where a draft statement departs from the documents.
Avoid using a tool to polish a statement into fluent prose that no longer sounds like the witness. A statement that reads like a lawyer wrote it invites cross-examination about who did. Check the rules of your forum on how statements are prepared, and keep the witness's own phrasing wherever it is clear enough.
- Organise interview notes into topic order
- List questions for a follow-up meeting
- Flag where a draft departs from the documents
- Keep the witness's own phrasing
- Put words in anyone's mouth
- Polish a statement until it no longer sounds like the witness
Reading the other side's documents
Respondent bundles can be large: policies, disciplinary records, emails between managers. AI summaries of long documents help you decide where to look. They are especially useful for finding the paragraph in a handbook that deals with a given procedure. Always read the passage itself before you rely on it, since a summary can miss an exception or a date.
If your client's documents contain personal data about colleagues, think carefully about where they go. A third party's medical or disciplinary details do not belong in a tool whose terms you have not checked.
Preparing the client
Clients in employment disputes are often anxious and unfamiliar with the process. A plain-language explanation of what happens next, written by you and edited with a tool if you wish, reduces calls and improves the quality of their instructions. Remember that clients may already have asked a chatbot about their case. Ask them what they were told, and correct it where it does not fit your forum.
Be honest about what you do not know. If the outcome depends on a point of law you have not yet researched, say so, and say how you will research it.
Settlement, mediation and conciliation preparation
Many employment disputes end before a hearing, and preparing for a settlement meeting is a good use of a tool. Ask it to turn your chronology into a one-page summary of the strengths and weak points of each side, drawn only from documents you have provided. Ask for a list of questions the other side is likely to raise. Use the output as a prompt for your own thinking, not as a view of the merits.
Settlement ranges depend on the law of the forum and on how the claim is valued locally. Do not rely on a tool for figures. Discuss them with the client on the basis of your own research and experience.
A short checklist before you rely on any output
Before an AI-assisted chronology, schedule or draft goes any further, run a brief check.
- Has the forum been confirmed from an official source, and every time limit calculated and diarised by a person?
- Has each fact in the chronology been traced to a document?
- Have the figures been recalculated independently?
- Is the witness evidence in the witness's own words?
- Have you checked what the tool does with the data you entered?
This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.
Read next
AI in Witness Bundle and Proof of Evidence Preparation: What to Automate and What Not To
A practical guide for litigators on which parts of witness bundle and proof of evidence preparation AI can handle, and which parts it must not touch.
6 minute readHallucinated citations: what court sanctions teach about checking AI output
The patterns behind fake authorities reaching courts, and the supervision and checking controls that would have caught them.
5 minute readE-discovery and technology-assisted review explained for non-specialists
How predictive coding and generative review differ, why validation matters and how to document the process.
5 minute read