Savannah Discovery: Production Requests in 2026

The shattered taillight on Bay Street was a constant reminder for Michael. He was a veteran motorcyclist, but that collision left him with a fractured tibia, bad road rash, and a stack of medical bills. He’d been heading east on a clear Tuesday morning, nearing Abercorn Street, when a delivery van just turned left right in front of him. Months later, he still couldn’t go back to his job as a port crane operator. His lawyer, Sarah, knew Michael’s testimony wasn’t enough to prove the other driver was negligent. She needed hard evidence. That’s where a request for production becomes the workhorse of his Savannah motorcycle crash case, and it’s what separates a weak case from one built on solid proof.

The Foundation of Discovery: What is a Request for Production?

Before a personal injury case ever gets to trial, you go through a phase called discovery. This is where both sides have to show their cards, exchanging information to avoid trial ambushes and, ideally, push the case toward a fair settlement. A key tool we use here is the request for production. It’s a formal written demand sent to the other side asking for documents, electronically stored information (ESI), and even physical objects that are relevant to the case. It works like a subpoena, but it’s just between the parties in the lawsuit, not some outside witness. For Michael, Sarah had to get inside the delivery company’s operations. That meant demanding the driver’s logbooks, his employment file, the van’s maintenance reports, and any dashcam video. Without that paper trail, Michael’s case was just his word against the driver’s, supplemented by an expert’s opinion, and having the company’s own documents would make his claim far stronger.

Working through Georgia Law: O.C.G.A. § 9-11-34 and Relevance

In Georgia, the rules for requests for production are laid out in O.C.G.A. § 9-11-34. The statute is clear that you have to describe what you want “with reasonable particularity.” This isn’t a free-for-all where you can just ask for “all documents related to the accident.” The request has to be focused enough for the other side to know what to look for. The core rule is that whatever you ask for must be relevant to the subject matter involved in the pending action. The standard for relevance is broad, covering anything that “appears reasonably calculated to lead to the discovery of admissible evidence.” The document you’re requesting doesn’t have to be admissible in court itself, so long as it could lead you to evidence that *is*. For instance, the driver’s full employment history might not be admissible to show he was negligent in that one moment, but it could absolutely point to a pattern of bad driving, which is relevant to a claim that the company was negligent in keeping him on the road. Sarah wrote her requests with this in mind. She asked for:

• All maintenance records for the delivery van involved in the collision for the past two years.
• The driver’s employment application, driving record, and training certificates.
• Any internal company policies regarding driver safety, vehicle operation, and accident reporting.
• All communication (emails, texts, internal memos) between the driver and the company regarding the incident.
• Any dash camera footage or GPS data from the delivery van for the date of the accident.

Each request met that “reasonable particularity” standard, making it hard for the opposing counsel to object that they were too vague.

The Responding Party’s Obligations: Search, Produce, or Object

Once served, the other party gets 30 days to respond (or 45 if the requests came with the initial lawsuit, per O.C.G.A. § 9-11-33(a)(2)). Those 30 days aren’t just for deciding what to give up. They’re for running a diligent search, finding responsive docs, reviewing for privilege, and then either producing them or formally objecting. The delivery company in Michael’s case had its own lawyers, and they had a clear set of duties:

1. Conducting a thorough search: This meant they had to look everywhere a responsive document might live, physical file cabinets, computer hard drives, email servers, and even personal phones if they were used for work. A quick, half-hearted search is a great way to get sanctioned.
2. Producing documents as they are kept in the usual course of business: They have to organize the production so it either mirrors how they keep their files normally or corresponds directly to the categories in the request. You can’t just dump a disorganized box of papers on the other lawyer’s desk.
3. Stating objections: If they believe a document is privileged (like a memo to their lawyer) or not relevant, they must object in writing, explaining exactly why it’s being withheld.
4. Creating a privilege log: For every document withheld because of privilege, they have to create a privilege log. This is a list that describes each document, who sent it and who received it, and the specific privilege being claimed (attorney-client, work product, etc.). This gives the requesting party a chance to challenge a privilege claim they think is bogus.

In Michael’s case, the company first objected to producing the driver’s whole employment file, claiming it was a privacy violation. Sarah fired back, arguing the driver’s past safety record was directly relevant to a potential negligent entrustment claim against the company itself. This kind of back-and-forth is pretty standard in discovery. They eventually agreed to produce a redacted file, personal info was blacked out, but the important stuff like disciplinary actions and his driving record was included.

The Importance of Electronically Stored Information (ESI)

In 2026, the good stuff isn’t in a file cabinet. It’s digital. Electronically stored information (ESI) covers everything from emails and texts to GPS data, dashcam video, social media, and vehicle black box data. O.C.G.A. § 9-11-34 makes it clear that ESI is fair game in discovery. The rules for producing ESI can get complicated. Lawyers often have to negotiate the format for production (should they be produced as native files or as static images?) and how wide a net to cast when searching. The dashcam footage was the potential smoking gun for Michael. If it showed the van turning with no signal or cutting him off, that would be huge. The company’s first response was that no footage existed. Sarah didn’t just take their word for it. She pushed back, demanding IT logs to prove a camera wasn’t installed or, if it was, that the data had been overwritten as part of a normal business practice. This is where knowing a bit about digital forensics really pays off for an attorney. I’ve seen parties claim ESI is “gone” when really they just haven’t looked for it properly or failed to preserve it.

Consequences of Non-Compliance: What Happens When You Don’t Produce?

If a party stonewalls on a legitimate request for production, there are serious consequences. The first step is to file a motion to compel with the court. If the judge grants that motion and the party *still* doesn’t produce the documents, the court can bring down the hammer under O.C.G.A. § 9-11-37. Sanctions can be as simple as ordering the non-compliant party to pay the other side’s attorney fees for having to file the motion. Or, they can be much worse:

• Excluding evidence: The court can forbid the party from using any evidence at trial that they should have produced earlier.
• Striking pleadings: The judge could literally strike out parts of their complaint or their answer to the lawsuit.
• Default judgment: In the most extreme cases of willful refusal, the court can just enter a default judgment, meaning the party that hid the ball automatically loses the entire case.
• Adverse inference instruction: The jury can be told to assume that the evidence the party refused to produce would have been bad for them. This is an incredibly powerful instruction.

Sarah had to file a motion to compel when the delivery company slow-walked the production of the van’s GPS data. The judge ordered them to produce it within ten days and made them pay for Sarah’s time spent on the motion. The message is clear: discovery is mandatory. It’s part of the process to make sure both sides have access to the facts. I’ve seen cases where a defendant’s refusal to produce key documents resulted in an adverse inference instruction. You don’t want to be the party on the receiving end of that.

The Resolution of Michael’s Case and Lessons Learned

Once the company finally produced the GPS data, it showed the van was speeding right before it made the turn onto Abercorn Street. That evidence, combined with the redacted employment file showing a prior traffic violation and Michael’s own clear testimony, gave Sarah a very strong hand. While the dashcam footage didn’t capture the impact perfectly, it did confirm the van’s sudden turn. Armed with this collection of evidence, Sarah went into mediation with a compelling argument. The delivery company, looking at a trial where their driver’s negligence would be on full display (along with their own early reluctance to cooperate), agreed to a substantial settlement. It covered all of Michael’s medical bills, his lost income, and his pain and suffering. Michael’s case is a perfect example of how a request for production works in the real world. It was the tool that dug up the objective facts Sarah needed to back up his story. For anyone caught up in a personal injury case, getting a handle on this discovery tool is essential. It’s what separates a case built on he-said-she-said from one built on hard proof.

For anyone trying to pick up the pieces after an accident, especially something as messy as a Savannah motorcycle crash, understanding how legal discovery works is a big deal. A tool like the request for production isn’t just a piece of paper. It’s often the foundation you need to build a successful claim. Getting that evidence is how you fight for your rights and get to a fair outcome.