How to Write a SOAP Note as a Medical Student (With Real Examples)

Your first SOAP note will be brutal. The good news is everyone's first SOAP note is brutal. The bad news is that you have to write your second one tomorrow, and your tenth one next week, and you'll be presenting most of them in front of a team who has opinions. If you want to learn how to write a SOAP note as a medical student without getting that polite-but-deflating attending feedback ("good attempt — let's work on the assessment"), the trick is not the template. The template is everywhere. The trick is understanding what each section is actually for.

---

What a SOAP note actually is

A SOAP note is a structured progress note used to document a patient encounter in four sections: Subjective (what the patient reports), Objective (what you observe and measure), Assessment (what you think is going on), and Plan (what you're going to do about it). The format was introduced by Lawrence Weed in the 1960s as part of the problem-oriented medical record, and it's still the default format for inpatient progress notes, outpatient encounters, and most clerkship documentation in 2026.

It's not the only format you'll encounter. You'll see APSO (Assessment-Plan-first, then Subjective-Objective) on some inpatient services because it puts the clinical reasoning at the top where attending eyes actually go. You'll see narrative H&Ps for new admissions. You'll see SBAR for handoffs and I-PASS for sign-out. But SOAP is the workhorse, and it's the one you'll be graded on most often as a third-year.

The structure itself is easy. The hard part is that two students can write SOAP notes with identical structure and one gets praised while the other gets red ink. The difference isn't in the template — it's in what they chose to include, what they cut, and whether the assessment shows actual thinking.

---

The four sections, and what makes each one good

Subjective

This is the patient's voice, filtered through yours. The chief complaint, the history of the present illness, and the relevant updates since you last saw them. For a progress note, the subjective is mostly an interval update — what's changed since yesterday, how the patient feels today, anything new the patient is reporting.

The most common mistake here is over-quoting. You don't need three sentences of the patient describing their pain in their own words. You need the clinically relevant version: location, quality, timing, what makes it better or worse, associated symptoms. Quote the patient only when their exact phrasing matters ("worst headache of my life" is a quote worth keeping).

Objective

Vitals, physical exam, labs, imaging, intake/output, weights, telemetry findings. This is the section where students over-include, because it feels safer to put everything in. It isn't. A progress note that documents every system in full each day is a progress note your team won't read.

Include the vitals (always). Include the focused exam — relevant systems, plus anything that changed. Include the labs that matter for today's decision-making. Drop the "no acute distress, alert and oriented x3" boilerplate after the first note unless something changed. If the team starts skimming, your assessment never gets read.

Assessment

This is the section you'll be evaluated on. Everything before it is data. The assessment is where you show you understand the data.

A weak assessment restates the problem ("Patient is here for CHF exacerbation, doing better"). A strong assessment names the problem, summarizes the clinical course, identifies the likely contributor, and signals where you are in the workup or treatment trajectory. Same case, much more reasoning.

You can write the assessment by problem (#1 HFrEF exacerbation, #2 CKD-3, #3 T2DM) or by system, depending on the service. Medicine and family medicine usually prefer problem-based. ICU and surgery sometimes prefer system-based. Ask your senior on day one. The format matters less than the fact that each item has both an analysis (why this is happening, where you are in the course) and a plan (what you're doing next).

Plan

The plan section answers "what are you actually doing today?" — medications continued, started, or stopped, tests ordered, consults placed, discharge planning, dietary changes, code status discussions. For each problem in your assessment, the plan should follow logically.

Two common mistakes: writing a plan that's identical to yesterday's plan (if the patient is the same, fine — but say why), and writing a plan that doesn't match the assessment. If you said the patient is hypovolemic in the assessment, "continue maintenance fluids" doesn't follow. The team will notice.

---

A side-by-side example: okay vs stellar

Same patient. Same data. Two MS3 notes from two different students. Mr. K is a 68-year-old man with HFrEF (EF 30%), HTN, T2DM, and CKD-3, admitted yesterday for an acute-on-chronic systolic heart failure exacerbation. This is the day-2 progress note.

Version A (what most MS3s write on day one)

It's not wrong. It's just empty. There's no clinical course, no reasoning about why he came in, no acknowledgment of his other problems, no anticipation of what tomorrow looks like. If you stopped reading after the assessment, you'd have no idea where Mr. K is in his recovery or what the team is thinking.

Version B (what attendings remember)

The data is almost identical. Version B reads like a clinician thinking; Version A reads like a checklist someone filled out. Notice what Version B does that Version A doesn't:

• Quantifies the change (2.9 kg weight loss, JVP from 12 to 8) instead of saying "improving"
• Identifies the precipitant (medication non-adherence) and what was done about it
• Anticipates the next decision (when to switch to oral, when to restart GDMT)
• Addresses every chronic problem the patient brought with them, not just the headline diagnosis
• Mentions discharge planning by day two, because someone reading this note can see where this admission is going

You don't need to write Version B on your first day. You need to be moving toward it. Most students plateau at Version A because they never get specific feedback on the assessment. Asking your senior resident "can you look at my A&P and tell me what's missing" once a week is the single most useful thing you can do during clerkship.

---

Common mistakes that get you graded down

These are the patterns that show up over and over in clerkship evaluations. They're easy to fix once you know to look for them.

• Don't restate the chief complaint in the assessment. "Patient with chest pain, has chest pain, plan: work up chest pain" is a sentence that contains zero thinking. The assessment is your differential, your leading diagnosis, and your reasoning.
• Don't copy-paste yesterday's plan. If the plan is the same, say why it's the same — "continue current management as patient is clinically improving on diuresis with appropriate weight loss." That sentence shows reasoning. "Continue Lasix" doesn't.
• Don't include findings you didn't actually examine. Attendings catch this fast. If you didn't auscultate the lungs, don't write "lungs clear to auscultation." Document what you did, even if it's less.
• Don't use abbreviations the team doesn't use. Every service has its own shorthand. ICU SOAP notes look nothing like family medicine SOAP notes. Pick up the local conventions in the first week.
• Don't bury the assessment under data. If your objective section is 40 lines, nobody's reading your A&P. Be ruthless about what's relevant today.
• Don't forget pertinent negatives. "No chest pain, no SOB, no fevers, no chills" is sometimes the most important sentence in the note.

---

How Talimo helps you write better SOAP notes

Talimo's clinical note grading feature is built for exactly this gap — getting specific, structured feedback on the assessment and plan section without having to corner your senior resident at the end of a 14-hour shift. You write the SOAP note inside a case simulation, the AI grades it against a competency rubric (history-taking, clinical reasoning, diagnostic accuracy, documentation quality), and you get a breakdown of what's strong and what's weak, with specific suggestions.

It's not a replacement for real attending feedback. It's a way to get 20 reps in before you ever write a note that goes in a real chart. The students who get the best feedback on real rotations are usually the ones who've already done this practice and developed instincts for what belongs where.

---

FAQ

Should I include vitals every day in a progress note?

Yes — current vitals belong in every progress note, even if they're stable. They establish that you laid hands on the patient that morning. What you don't need to do is duplicate the trend; one set of current vitals is enough. If you want to highlight a change, mention it explicitly ("HR 92, up from 76 yesterday").

How do I write an assessment when I don't know the diagnosis?

Write what you do know. Name the syndrome ("acute hypoxic respiratory failure of unclear etiology"), list the top three differentials in order of likelihood with brief reasoning, and state the next diagnostic step. Attendings don't expect you to nail every diagnosis. They expect you to reason out loud in a way they can follow and correct.

Can I use abbreviations in a SOAP note?

Standard medical abbreviations are fine — HTN, T2DM, CKD, CHF, COPD. Avoid abbreviations that have multiple meanings in different contexts (BS could be blood sugar or bowel sounds; spell it out). Hospital policies vary on prohibited abbreviations — your institution probably has a list, and it's worth a 30-second skim.

What if I miss a finding the resident asks about?

Say so directly: "I didn't check for that — I'll go back and examine." Then go check. Pretending you did a part of the exam you didn't do is the fastest way to lose your senior's trust, and it can show up in a competency-based evaluation as a professionalism issue. The right move is always to admit it and fix it.

How long should a SOAP note be?

For a stable inpatient progress note, aim for something a teammate can read in 2-3 minutes. The exact length varies — a complex ICU patient might warrant a longer note than a stable medicine patient — but density matters more than length. A 500-word note with clear reasoning beats a 1,200-word note that buries the assessment.