Case Study – Nancy Merreot

Name:  Nancy Merreot

Location: Washington, DC

What kind of work were you doing before litigation support found you?

Network Administration and Website Development

How did you get the opportunity to join the litigation support community?

I was hired to do software development and third-level support for all core applications at a law firm in Cleveland.

When did you realize that this career would be a good fit for you?

After taking on several large litigation matters, organizing the data, identifying efficiencies, and training the legal team on them, I was hooked and everyone was happy they could put their fingers on the information they wanted almost immediately. Prior to that preparing a legal team for a trial, setting up the databases, warroom, courtroom and being on the hotseat was crisis management and information management at its finest.

Do you prefer to be out in front and working with the clients or behind the scenes working with the technologies?

Both – If the audience is receptive 🙂 I prefer to be behind the scenes making it all flow.

Is there an area of litigation support that had a steep learning curve for you?

Yes, working with those resistance to change.

What do you consider to be one of the coolest things about working in litigation support?

Creating efficiencies and organizing everything.

Which types of employers have you had while working in litigation support?

  • Service Provider
  • Law Firm
  • In-House Legal Department

Litigation Support is a well-paying career. How much has your salary increased since joining the litigation support community?

$50,000 – $70,000

How many years have you been working in Litigation Support?


Care to share any words of encouragement or advice?

Give it a shot!! It's very rewarding and making the legal team look good is a great high. There will be tough times but all in all it has been worth every moment spent learning new things and working through the many bumps in the road.

Leave a Reply

Your email address will not be published.