Plaintiff Attorney Legal Information CenterRespondeat superior is one of those legal doctrines that sounds harder than it is. The basic idea is simple: if an employee hurts someone while doing the employer’s business, the employer may be legally responsible.
The Latin phrase means “let the superior answer.” In injury cases, that usually means the company, hospital, trucking company, store, restaurant, delivery business, or other employer may have to answer for what its employee did.
This matters because the employee who caused the injury often does not have enough money or insurance to fully compensate the victim. The employer usually does. So respondeat superior is not just a technical doctrine. It is often the difference between a case with limited insurance and a case with real compensation available.
What Is Respondeat Superior?
Under respondeat superior, an employer or principal can be held legally responsible for the wrongful acts of an employee or agent if those acts occur within the scope of the employment or agency.
So under the doctrine of respondeat superior, an employer is vicariously liable for the tortious conduct of an employee when the employee is acting within the scope of the employment relationship.
“Vicarious liability” means the employer is responsible even if the employer did not personally commit the negligent act. The employer may have hired a careful driver, trained the employee, and had all the right policies. But if the employee was doing the employer’s work when the crash happened, the employer may still be on the hook.
That is the point of the doctrine. The business gets the benefit of the employee’s work. The business also bears responsibility when that work injures someone.
The Old Master-Servant Language
Older cases use the words “master” and “servant.” That is a painfully archaic expression if there ever was one. But you still see it in the case law.
A “master” is liable for acts the “servant” commits with actual authority, apparent authority, or within the scope of employment. Actual authority means the employer really gave the employee authority to act. Apparent authority means reasonable people would think the employee had authority based on what the employer said or did.
The employer can also ratify the act later if it accepts or approves the conduct with knowledge of the material facts.
If you are looking for the Latin proverb — is there a lawyer who does not like Latin? — the phrase is qui facit per alium facit per se. It means the act of the servant, done within the scope and exercise of employment, is treated in law as the act of the master himself.
Why Respondeat Superior Is So Important in Many in Injury Cases
In personal injury cases, respondeat superior usually matters for one reason: money. The negligent employee may have little or no meaningful assets. The employer may have commercial insurance, corporate assets, and enough coverage to pay a serious settlement or verdict.
This comes up in many types of cases:
- truck accidents
- delivery driver crashes
- company vehicle accidents
- rideshare and transportation cases
- hospital malpractice cases
- nursing home negligence cases
- security negligence claims
- restaurant, store, and premises liability cases
- sexual abuse claims
In many cases, you would rather be fighting a giant, faceless trucking company or hospital than a nice individual truck driver, nurse, or doctor. That is not personal. It is practical. The company or hospital is the entity with the insurance and the ability to pay full compensation.
Respondeat Superior: Simple Breakdown
| Question | Why It Matters | Example |
|---|---|---|
| Was the person an employee or agent? | Respondeat superior requires an employment or agency relationship. | A delivery driver working for a company during a route. |
| Was the employee doing the employer’s business? | The act must usually be within the scope of employment. | A truck driver rear-ends someone while making a delivery. |
| Was the employee on a personal errand? | A purely personal errand may take the employee outside the scope of employment. | An employee leaves work to run a personal errand and causes a crash. |
| Was the employee commuting? | Maryland generally does not hold employers liable for ordinary commuting crashes. | An employee driving their own car to work in the morning. |
| Is there another theory if respondeat superior does not fit? | Plaintiffs may still have negligent hiring, supervision, retention, or entrustment claims. | A company hires an unsafe driver and puts him behind the wheel. |
Agency, Principal, and Agent
The doctrine of respondeat superior is alive in different forms in all 50 states. In Maryland, and in most states, the first step is determining whether an agency relationship exists.
The classic test comes from the Second Restatement of Agency, and Maryland courts have used that framework. The basic definitions are:
- Agency is the fiduciary relationship that results when one person agrees that another person will act on their behalf and subject to their control, and the other person consents to act that way.
- The person or entity for whom action is taken is the principal.
- The person who acts is the agent.
Translated into normal language: was the person acting for someone else and under that person’s or company’s control? If yes, you may have an agency relationship.
Scope of Employment
The hardest issue is often not whether the person was an employee. The harder issue is whether the employee was acting within the scope of employment when the injury happened.
Maryland courts look at whether the employee was advancing the employer’s interests at the time. That is the practical question. Was the employee doing the job, doing something reasonably connected to the job, or acting in a way that served the employer’s business?
Scope of employment does not always require perfect obedience. An employee can sometimes act within the scope of employment even if the employee was careless, violated a rule, or did the job badly. If every rule violation took the employee outside the scope of employment, respondeat superior would be almost meaningless.
But there are limits. If the employee completely steps away from the employer’s business and acts for purely personal reasons, the employer may not be vicariously liable.
The Release Trap: Releasing the Employee Can Release the Employer
Every year, there are legal malpractice cases that stem from lawyers missing one fundamental principle: releasing the servant can release the master from liability.
For example, you cannot settle with or release with prejudice a doctor and then expect to maintain a pure respondeat superior claim against the hospital for that doctor’s conduct. If the hospital’s only liability is derivative of the doctor’s negligence, releasing the doctor may destroy the claim against the hospital.
This is one of those issues that sounds technical until it wrecks a case. Lawyers must be very careful with releases, dismissals, stipulations, and settlement language when vicarious liability is involved.
Under the doctrine of respondeat superior, a tort plaintiff may recover damages from an employer without having a separate judgment against the employee. But that does not mean the employee’s legal status is irrelevant. If you release the wrong party the wrong way, you may give away the claim against the deep pocket.
Other Ways to Reach the Company or Employer
Respondeat superior is often the easy claim. Most lawyers quickly spot vicarious liability when an employee injures someone while doing the job. But if respondeat superior does not fit, there may be other options for finding a responsible defendant with insurance or assets.
- Negligent Entrustment
- Negligent Supervision
- Negligent Hiring
- Negligent retention
- Negligent training
Counsel must consider all of these theories when looking for additional insurance coverage or money to satisfy a settlement or verdict. Sometimes the employer is not vicariously liable for what the employee did. But the employer may still be directly liable for putting the wrong person in the wrong job, failing to supervise them, or ignoring warning signs.
Employer Liability Theories
| Theory | Basic Idea | Best Example |
|---|---|---|
| Respondeat Superior | Employer is liable because employee was acting within the scope of employment. | Delivery driver hits someone while making deliveries. |
| Negligent Hiring | Employer hired someone it knew or should have known was unsafe. | Company hires driver with a bad crash history. |
| Negligent Supervision | Employer failed to supervise an employee after warning signs appeared. | Company ignores repeated safety violations. |
| Negligent Entrustment | Employer gave a dangerous person access to a vehicle or equipment. | Company lets an unsafe driver keep using a truck. |
| Negligent Retention | Employer kept someone in the job after learning they were dangerous. | Employer keeps driver after repeated DUI or safety incidents. |
Car Accident Cases
Car accident cases are where respondeat superior comes up all the time.
If you are hit by someone who is on the job, vicarious liability may not be hard to establish. A delivery driver making deliveries, a truck driver hauling freight, a cable-company worker driving between appointments, or a salesperson driving from one work meeting to another may all be acting within the scope of employment.
But not every crash involving an employee creates employer liability.
In Maryland, an employer is generally not vicariously liable for damages from an employee’s car crash while the employee is traveling to or from work on their own time and in their own vehicle. This is the “going and coming” rule. The idea is that ordinary commuting is usually not part of the employer’s business. Maryland courts recognize this rule and apply it in motor tort cases. :contentReference[oaicite:1]{index=1}
There are exceptions. An employer may be liable if the employer expressly or impliedly authorized the employee to use their own vehicle in carrying out employment duties and the employee was actually engaged in those duties at the time of the crash. There may also be liability when the employee is on a special mission or errand for the employer.
So the key questions are:
- Was the driver on the clock?
- Was the driver doing something for the employer?
- Was the driver using a company vehicle?
- Was the driver going between job sites?
- Was the driver making deliveries or service calls?
- Did the employer require or encourage the use of the vehicle?
- Was the driver merely commuting?
These details can change the value of the case. A crash against an individual driver with a minimum insurance policy is one thing. A crash against an employer with commercial coverage is something else entirely.
Hospital Malpractice Cases
Can hospitals be liable for a doctor’s negligence when the doctor is not technically a hospital employee? The answer is maybe.
To establish that a hospital is vicariously liable for the acts of healthcare providers, the patient must show that the providers were acting as agents, servants, or employees of the hospital when they provided medical care.
The Maryland high court has said that a hospital, like any employer, may be liable under agency principles for the negligence of its servants or employees. But the harder issue is what happens when the negligent doctor is an independent contractor.
This comes up constantly in hospital cases. Patients go to the hospital. They do not choose the ER doctor, hospitalist, radiologist, anesthesiologist, or surgeon staffing the hospital that day. The hospital may later claim, “That doctor was not our employee.” From the patient’s perspective, that can feel ridiculous. You went to the hospital. The hospital gave you the doctor. The hospital should not be able to avoid responsibility by pointing to a contractor agreement you never saw.
Apparent Agency in Maryland Hospital Cases
Maryland recognizes apparent agency in hospital malpractice cases. This doctrine can allow a hospital to be held liable for the negligence of a doctor or healthcare provider who was not technically employed by the hospital.
The apparent agency doctrine holds that a hospital may be liable as a principal for the acts of another party when the hospital, by words or conduct, caused the patient to reasonably believe the provider was acting on the hospital’s behalf.
It is not enough that the patient simply assumed the doctor worked for the hospital. The belief must be connected to something the hospital did or failed to do. Did the hospital hold the doctor out as part of its emergency department? Did the patient seek care from the hospital rather than from a particular doctor? Did the hospital control the setting, the forms, the branding, the staff, and the process? Did the patient have any realistic reason to know the doctor was an independent contractor?
The most important recent Maryland case is Williams v. Dimensions Health Corp. In 2022, the Supreme Court of Maryland held there was enough evidence for a jury to find that an emergency-room surgeon was the hospital’s apparent agent, even though the hospital argued the doctor was an independent contractor. The court emphasized that hospitals can be vicariously liable for emergency-room providers under apparent agency, depending on the facts. :contentReference[oaicite:2]{index=2}
This case is a big deal for Maryland malpractice lawyers. It strengthens the argument that hospitals cannot always avoid liability by saying the doctor was not technically on the payroll.
What Evidence Helps Prove Apparent Agency?
In hospital cases, the apparent agency fight often turns on what the patient saw, understood, and relied on at the time of care.
Important evidence may include:
- hospital admission forms
- consent forms
- emergency department paperwork
- hospital branding on signs, wristbands, forms, and uniforms
- whether the patient chose the hospital or chose the individual doctor
- whether the doctor was presented as part of the hospital team
- whether the patient had any meaningful notice that the doctor was independent
- who controlled the schedule, location, staff, and care process
This is why hospital liability cases require careful discovery. The defense will point to contracts. Plaintiffs need to point to what the patient actually experienced.
Independent Contractors Are Not the End of the Case
Defense lawyers love the phrase “independent contractor.” They use it as if it ends the discussion. It does not.
In trucking cases, delivery cases, hospital cases, nursing home cases, and corporate negligence cases, the independent contractor label may matter. But it is not always controlling. Courts look at control, agency, apparent authority, and the reality of the relationship.
If a company controls how the work is done, presents the worker as part of the company, or uses the worker to perform its own business, there may still be a path to liability. The label in the contract is evidence. It is not the whole case.
Bottom Line
Respondeat superior is simple in theory: if an employee injures someone while doing the employer’s work, the employer may be responsible.
In real cases, the details matter. Was the person an employee or agent? Was the person acting within the scope of employment? Was the person commuting? Was the person on a special errand? Did the hospital hold the doctor out as its agent? Did the company create the appearance of authority?
These questions matter because they often determine whether the plaintiff can reach the real insurance coverage. That is why good personal injury lawyers look beyond the person who directly caused the injury and ask a bigger question: who had the right to control this person, who benefited from the work, and who should answer for the harm?
More Information
- Do parents have liability when their children cause a car accident?
- Looking at car accident claims in Maryland generally