The right-to-sue letter starts a 90-day fuse. MatterOS lights it the moment it arrives.
Employment cases live and die on an administrative-exhaustion gauntlet before litigation even starts - and every claim type can be running its own clock in parallel. MatterOS tracks each one separately, for whichever side of the table you sit on.
What drives this practice: agency-deadline
What actually eats a employment attorney's week.
Multiple claim types mean multiple clocks, and they don't line up
Title VII, ADA, ADEA, FMLA, and FLSA all carry different limitations regimes, and a multi-claim matter is running several simultaneously. MatterOS's signature synthesis section tracks procedural posture per claim - exhausted? clock state? - because prose that blurs them together is malpractice-adjacent.
An arbitration clause reshapes the entire forward path
Whether the employment agreement contains an arbitration clause changes everything about where this case actually goes. MatterOS's extraction specifically hunts personnel documents for arbitration and class-waiver language on intake, not as an afterthought once litigation is already underway.
FLSA damages erode every week the case sits unfiled
The 2-year (3-year if willful) lookback window shrinks the available recovery continuously, not on a single deadline date. MatterOS displays this as a damages-erosion soft deadline - a genuinely different framing from a standard limitations date, because the exposure is shrinking in real time.
The stages MatterOS already knows this practice runs through.
Not a generic case-management pipeline - the actual shape of a matter in this discipline, branches and terminal stages included.
- Intake & assessment
- Internal / pre-charge
- Agency charge
- Investigation / position statement
- Right to sue / demand
- Litigation or arbitration
- Resolution
The right-to-sue 90-day suit deadline
Once an RTS letter is received, the 90-day suit deadline is fixed and federal - the pack's scariest number precisely because it doesn't vary by jurisdiction the way the charge-filing deadline does. MatterOS arms it the moment the RTS date is extracted, alongside the charge deadline itself (180 days federal-only, 300 in a deferral state) computed off the adverse-action date.
Termination/demotion/etc. - the master anchor.
Also used as the damages-module's salary_rate input.
e.g. Title VII, ADA, FMLA, wage & hour, retaliation - each arms different clocks.
Derived: 180d federal-only / 300d deferral-state (JV overlay decides which).
RTS + 90d (fixed federal) - the pack's scariest number. Critical once armed.
OWBPA 21/45-day windows when an ADEA release is involved. Critical once set.
Damages Model
Back pay accrued to date - salary rate times time since the adverse action, mitigation-adjustable - plus front-pay and liquidated-damages bands per claim type, ticking upward in real time. It's built to be dropped straight into a demand letter or a settlement conversation.
MatterOS already knows what this practice's paperwork looks like.
Drop a file into the matter and it gets filed to the right category on arrival - no manual sorting, no naming convention to remember.
Never the wrong word in front of a client - or a court.
Every draft and every synthesis MatterOS produces for this practice follows the same negative-vocabulary rules a careful associate would.
The checklist MatterOS opens before you've had coffee.
Six reasons employment attorneys choose MatterOS.
Serves both chairs: employee-side and employer-side postures reweight the checklist and prompt perspective from the same party question, without pretending the practice only runs one direction.
'Respondent' during the agency phase becomes 'defendant' once suit is filed - the pack switches the term by stage automatically, a small detail that makes synthesis read practitioner-authentic instead of generic.
A federal-employee client gets an entirely different, much shorter 45-day EEO counselor-contact regime instead of the standard 180/300-day charge deadline - gated by employer type, not left for someone to remember.
OWBPA's 21/45-day consideration windows plus the 7-day revocation period get tracked automatically the moment a severance release involves an ADEA claim.
The file-or-not decision memo is calendared within 30 days of receiving the right-to-sue letter specifically because drift against a 90-day fuse is lethal, and 30 days in still leaves room to act.
Never adopts an employer's characterization as fact on the employee side - 'poor performer' becomes 'characterized by employer as' - and the same discipline runs symmetrically on employer-side work.
What this looks like on a real file.
A termination intake starts with the adverse-action date, and MatterOS immediately calendars the charge-filing deadline off it - 180 or 300 days depending on whether the state is a deferral state, computed and shown, not assumed.
The employee's personnel file and handbook get read on arrival specifically for arbitration and class-waiver language, so the forum question - court or arbitration - is answered before strategy discussions start, not discovered mid-negotiation.
A right-to-sue letter lands four months later. MatterOS extracts the RTS date and arms the fixed 90-day suit deadline the same day, and the file-or-not decision memo gets calendared for 30 days out - well inside the fuse, with time to actually decide.
Questions employment attorneys actually ask.
Does MatterOS work for employer-side defense work too?
Yes - the party question asks whether you represent the employee or the employer, and the checklist, prompt perspective, and negative-vocabulary discipline reweight symmetrically for either side rather than assuming a plaintiff-side default.
How does it track the right-to-sue 90-day deadline?
The moment the RTS letter's date is extracted, MatterOS arms the fixed federal 90-day suit deadline - it doesn't vary by jurisdiction, and it's treated as the pack's highest-stakes number for exactly that reason.
What if a client has multiple claim types with different clocks?
The synthesis structure tracks procedural posture per claim individually - exhausted or not, clock state - because a multi-claim matter genuinely has different limitations regimes running in parallel, and blurring them together in one summary is the kind of error the pack is built to prevent.
Does it check for an arbitration clause automatically?
Yes - extraction specifically hunts employment agreements, handbooks, and policies for arbitration and class-waiver language on intake, because whether that clause exists reshapes the entire forward path of the matter.
See how MatterOS runs a employment & labor matter - on your own file.
Drop in the documents from a real matter and watch it assemble: parties, dates, deadlines, and a synthesis written the way employment attorneys actually talk. Free 7-day trial, no card required to start.