A litigation support specialist resume needs five things: a summary that names the support work you actually run, a skills block that pairs that work with the platforms and databases you run it on, experience bullets built around matters and deliverables, credentials written with their exact names, and education or training.
Precision is the through-line: every systems claim and credential claim on the page has to be one you can defend and spell out.
What law firms look for in a litigation support specialist resume
A resume gets read in one mode: as evidence.
Whoever screens a litigation support application is trying to predict whether you can run the support work the posting describes, and every line either supplies that evidence or takes up space.
Write the page around three kinds of proof:
- Named support work. The lane you have actually worked, stated in the posting's own vocabulary — its task names, its matter types. A resume that echoes the posting reads as a match; a resume that invents its own labels makes the reader do the translating.
- Software by name. "Familiar with legal software" is an empty phrase; the systems you have actually logged into are not. Put the platforms in your skills block and again in the bullets where you used them.
- Credential claims that survive a check. Claim only credentials you hold, named exactly as the issuing body writes them — the skills section below covers the names our research documents in this space.
Everything else — summary, bullets, education — exists to serve those three.
If you are still mapping the role itself rather than the paper it goes on, the litigation support specialist career guide covers the day-to-day work and the toolset; this page stays on the resume.
Resume summary examples
The summary is the short block at the top of the page, and it replaces the old objective statement entirely: an objective is about what you want, and the screen already knows what you want.
A litigation support summary names four things — your lane, your systems, a defensible proof point, and any credential — in that order.
Three shapes, adapted to where you actually are.
The bracketed slots are yours to fill with real figures you can defend in an interview — a number you can stand behind beats a string of adjectives:
- Experienced litigation support specialist: "Litigation support specialist with [X] years supporting [matter types] matters. Owns the document database and review-platform setup in [platform], and the hearing and trial support that runs on it."
- Moving over from e-discovery: "eDiscovery specialist widening into litigation support: [X] years of processing, loading and production work in [platform], now extending into hearing preparation and case-team support. [Credential name] certified."
- Career changer: "IT support specialist moving into litigation support: [X] years of hands-on systems and data work, now trained on [document review platform] and building matter-document experience through [course or project]."
Notice what the examples never do: they do not promise temperament ("hard-working team player"), and they do not claim platform expertise the bullets below cannot back.
The summary is a table of contents for the page under it.
Skills and software to list
Build the skills block in two groups, and put it near the top of the page: for a support role, the platform names are the quickest way to show your lane, and the skills block collects them in one place.
Support skills.
Use the vocabulary the postings use, and list only the items you can discuss in an interview:
- The work itself. Three to six phrases in the posting's own words — the documents-and-data tasks you have personally run, pulled from the posting rather than from a template.
- The platforms. Each system named as the product names itself, next to the task you did in it. If the posting writes an abbreviation, use the abbreviation; if it writes the full name, match that.
- Where your ownership ends. A phrase that draws the boundary of what you ran — what you owned end to end, and where you handed off to attorneys, case teams or vendors.
Credentials, named exactly.
Two names our research documents in this corner of the staff side.
ACEDS's Certified E-Discovery Specialist (CEDS) is the credential our research covers on the e-discovery side; ACEDS describes itself as vendor-neutral and states that it is owned and operated by BARBRI.
Relativity's certification program is tiered: Pro certifications (the entry point of the program, and they do not expire), Specialist certifications, and Advanced certifications such as the Relativity Certified Administrator (RCA).
Both facts matter for how you write the line: spell out "Certified E-Discovery Specialist (CEDS)" on first use, and name the tier for a Relativity certification rather than writing a bare "Relativity certified."
The CEDS exam itself is covered in the CEDS certification guide, and which Relativity exam to take in the Relativity certification guide; this page stays on how the line reads.
Whichever you list, keep it honest about currency.
ACEDS requires CEDS holders to recertify every two years with at least 40 continuing education credits; Relativity's Pro certifications do not expire.
A credential you have let lapse is a line you will have to caveat in an interview, so write the status you can defend.
Not sure whether your experience reads as litigation support or as e-discovery?
The litigation support vs eDiscovery comparison covers where the boundary sits — useful before you decide which lane your skills block claims.
Spell it out, then abbreviate
Experience bullets by level
An experience bullet has three moving parts: the matter work you supported, the deliverable you produced, and the system it ran on.
Duties alone ("assisted with the document database") read as nothing; a bullet that names the deliverable and the tool reads as evidence.
What changes by level is how much of the process you own:
First seat
You are showing you can keep the work moving under supervision, so name the pieces you personally ran.
"Maintained the document database for [matter type] matters in [platform] — loaded new documents, ran searches for the case team, and flagged problems to the lead before they reached the attorneys."
Mid-level
Own a process end to end.
"Administer the review platform for [number] active matters: user setup, project workflows, and the deadlines that depend on them; coordinate with [vendor] on processing and load turns."
Senior and lead
Show leverage — the people, systems and standards behind you.
"Built the firm's document-database templates and loading standards; trained case assistants on the review platform; acted as the standing point of contact between case teams and [vendor]."
Retitle nothing.
If you supervised, say what you actually reviewed and trained; if you did not, the "lead" framing collapses in the first interview question about it.
No-experience or career-change version
Coming in without litigation support titles, the page reorders: the skills block and any training move to the top, education sits high, and the work you do have gets framed by task rather than by title.
Frame adjacent work by what it actually was.
Help-desk and systems work, records and data management, vendor coordination, deadline-driven production of anything — describe the parts of the old job that match the posting's task vocabulary, and leave the rest described as what it was.
A retitled job reads as padding, and the interview will find the seam.
Use training lines you can defend.
A platform training line is the direct one for a newcomer: Relativity describes its Pro certifications as the entry point of its program, and those certifications do not expire.
On the e-discovery side, ACEDS's CEDS is the credential our research documents.
Career changers: keep your real title, retarget the summary, and let the task vocabulary do the work — "kept a [number]-user document database current and reported on its status weekly" reads the same to a hiring screen whether it happened in a law firm or a hospital system.
Check CEDS eligibility before you book
Common mistakes
- Bare abbreviations. "CEDS" without the issuer tells a screener nothing about who examined you — write "Certified E-Discovery Specialist (CEDS)" on first use. Same discipline for Relativity: name the certification and tier, not just the platform.
- A credential line with no currency behind it. ACEDS requires CEDS holders to recertify every two years with at least 40 continuing education credits, so a lapsed one is a claim the calendar contradicts — write the honest status. (Relativity's Pro certifications do not expire, so those carry no renewal asterisk.)
- Software with no evidence. A skills row that names a platform should be traceable to at least one bullet where you used it.
- Inflated metrics. Invent nothing: a number you can defend in an interview beats a stack you cannot.
- One resume for every posting. Retarget the summary and the skills block to each posting before you send, so the lane you are applying to sees its own evidence first. When it is tuned, measure it against live postings — browse litigation support specialist jobs to see how firms phrase what you have just written to match.