SOAP note practice means repeatedly writing Subjective, Objective, Assessment, and Plan notes until the structure becomes automatic and your clinical reasoning shows clearly on the page. The fastest way to improve is to write short notes from a fixed template, then get specific, rubric-based feedback on each one. The sections below walk through what belongs in each part, worked examples you can copy, and timed exercises to build speed.
TL;DR:
- Writing SOAP notes with specific, rubric-based feedback accelerates skill development more effectively than writing numerous unreviewed notes.
- Common errors include mixing subjective and objective information and copying outdated data, which can lead to miscommunication and liability issues.
- Using structured templates, mnemonics, and targeted practice cases based on actual clinical content improves note accuracy and speed.
- Short, frequent practice sessions with immediate correction better build clinical reasoning and documentation habits than long, infrequent attempts.
- Faculty grading emphasizes header completeness, detailed HPI, specific plan actions, and accurate documentation, making structured, feedback-driven practice essential.
Table of Contents
- What goes in each SOAP section, with examples
- Common mistakes that drag down note quality
- Templates and worked examples you can copy
- How to practice and assess your own notes
- What faculty actually score and how to avoid losing points
- What actually moves the needle in SOAP note practice
- The gap in how most students practice SOAP notes
- Turn your encounters into practice cases automatically
- FAQ
- Sources
What goes in each SOAP section, with examples
Each letter in SOAP has a job. Subjective captures what the patient tells you. Objective captures what you measure or observe. Assessment is your interpretation. Plan is what happens next. Mixing these up is the single most common error graders flag, so knowing the boundary matters more than knowing fancy vocabulary.
The Subjective section opens with a one-line summary: age, sex, and chief complaint, something like "32-year-old woman presents with three days of sore throat and low-grade fever." From there, the history of present illness fills in using a mnemonic. Two common ones:
- OLDCARTS: Onset, Location, Duration, Character, Aggravating factors, Relieving factors, Timing, Severity.
- CLODIERSS: Character, Location, Onset, Duration, Intensity, Exacerbating factors, Relieving factors, Secondary symptoms, Severity.
A sample phrasing: "Pain began gradually two days ago, is sharp and localized to the right lower quadrant, worsens with movement, and is rated 7/10." That single sentence covers five OLDCARTS elements at once, which is exactly the density a good HPI needs.
Objective is where numbers and exam findings live, never the patient's own words about how they feel.
According to the StatPearls overview of SOAP documentation, the format exists as a cognitive framework that organizes clinical thinking in a predictable order, which is part of why graders and attendings scan notes the same way every time.
Assessment is the shortest section but carries the most weight. State the primary diagnosis, a brief differential if relevant, and a status phrase. For example: "Acute pharyngitis, likely viral; bacterial pharyngitis less likely given absence of exudate and negative rapid strep; patient stable." That single sentence does three jobs at once.
Plan follows the same problem-by-problem logic. Each active problem gets its own line with specific actions: medication name, dose, route, and frequency ("Amoxicillin 500 mg PO TID x 10 days"), monitoring instructions, and a follow-up timeframe ("Return if symptoms worsen or persist beyond 7 days"). Vague plans like "continue management" cost points on almost every rubric because they show no decision-making.
Common mistakes that drag down note quality
Most documentation errors fall into a few predictable categories, and nearly all of them are fixable with a habit change rather than more medical knowledge.
The most frequent mistake is placing subjective language in the Objective section, or vice versa. "Patient appears in pain" is subjective interpretation dressed up as an exam finding. The fix is to separate what the patient reports ("rates pain 8/10") from what you observe ("grimacing, guarding right lower quadrant").
Copy-forward is a second major risk. When a note carries yesterday's vitals or an outdated assessment into today's chart, it can mislead the next clinician who reads it. A consensus paper on EHR documentation identifies copy-forward and note bloat as recurring hazards that introduce errors and raise liability risk. The simple edit rule: never save a note from a template that still contains another day's data; retype the numbers that changed, every time.
Note bloat happens when notes balloon with irrelevant detail, making the actual clinical picture harder to find. The same consensus discussion describes APSO (Assessment and Plan first) as an alternative ordering some clinicians use specifically to cut down the time spent hunting for the plan in long electronic notes.
Pro Tip: Read your note out loud before submitting it. If a sentence doesn't change what the reader would do next, cut it.
An editing pass before you submit any note:
- Scan the Subjective section and delete any line that states a fact rather than the patient's report.
- Scan the Objective section and delete any line that interprets rather than measures.
- Confirm the Assessment includes a status phrase (stable, improving, worsening).
- Confirm every Plan item has a specific action, not a vague verb like "monitor" alone.
Templates and worked examples you can copy
A consistent header saves time and prevents missing fields, which is one of the most common rubric deductions. For clerkship and OSCE notes, the header should include patient identifiers (or de-identified placeholder), date and time, encounter type, and your name and role.
Ambulatory example (cough/URI):
- S: "19-year-old man presents with 4 days of cough, rhinorrhea, and mild sore throat. Denies fever, shortness of breath, or chest pain. No sick contacts reported."
- O: "Temp 37.1°C, HR 78, RR 14, SpO2 99%. Oropharynx mildly erythematous, lungs clear to auscultation bilaterally, no nasal congestion on exam."
- A: "Viral upper respiratory infection; low likelihood of bacterial sinusitis given absence of facial pain or purulent discharge."
- P: "Supportive care: rest, fluids, OTC analgesics as needed. Return if symptoms persist beyond 10 days or fever develops."
Each phrase above was chosen to match a specific OLDCARTS or exam element, so nothing is filler.
Inpatient progress example (problem-focused):
- S: "Patient reports improved energy overnight, pain now 3/10 down from 7/10."
- O: "Temp 37.0°C, HR 84, BP 124/80. Surgical site clean, dry, intact, no erythema."
- A: "Post-operative day 2, status post appendectomy, recovering as expected."
- P: "Continue current analgesia, advance diet as tolerated, plan discharge tomorrow if pain controlled and tolerating oral intake."
A quick-fill template structure for either case type:
| Field | What to include |
|---|---|
| Header | Date, time, encounter type, your role |
| S | One-line opener plus HPI mnemonic elements |
| O | Vitals, focused exam, dated labs/imaging |
| A | Diagnosis, brief differential, status phrase |
| P | Problem-specific actions with dose/route/frequency and follow-up timing |
How to practice and assess your own notes
Skill in SOAP writing comes from repetition under time pressure, not from reading more examples. A simple progression works well across a week or two of practice:
- Micro-practice: write three short notes (5 minutes each) from brief case prompts, focusing only on correct section placement.
- Intermediate practice: write two focused notes (10 minutes each) that include a full HPI and a problem-specific plan.
- Timed OSCE-style note: write one complete note in 20 minutes immediately after a simulated or real encounter, mimicking exam conditions.
You can build your own practice cases directly from real clinic encounters or lecture material. After seeing a patient, jot down the chief complaint and two or three exam findings while they're fresh, then expand those into a full note later. A 5-minute OSCE history framework using SOCRATES-style scripts pairs well with this approach, since it gives you a consistent way to elicit the Subjective details you'll need.
For feedback, three sources work well together: peer review (have a classmate check your section placement), preceptor questions (ask what they would have asked the patient that you didn't), and a self-audit using the editing checklist above. Short case practice templates for differential diagnosis can also sharpen the Assessment section specifically, since a tighter differential usually produces a tighter note.
What faculty actually score and how to avoid losing points
Academic rubrics tend to break SOAP notes into weighted categories rather than scoring them as a single impression. A SOAP note scoring rubric commonly allocates points across header completeness, HPI detail, objective documentation, assessment reasoning, plan specificity, and overall clarity or style.
Typical deduction patterns include:
- Missing header fields like date, time, or encounter type.
- An HPI that skips two or more OLDCARTS/CLODIERSS dimensions.
- Objective findings written as interpretations instead of measurements.
- A Plan section with vague verbs and no specific dose, route, or follow-up timeframe.
- Inconsistent formatting that makes the note harder to scan quickly.
Before submitting any graded note, confirm the rubric weighting with your preceptor or course director, since some programs weight Assessment more heavily while others weight Plan specificity higher. Asking for one targeted improvement point after each graded note, rather than general feedback, tends to produce faster gains than broad comments.
What actually moves the needle in SOAP note practice
A five-minute post-clinic habit builds skill fastest: jot the chief complaint, two exam findings, and your working diagnosis right after seeing a patient, then turn that into a full note within the hour while details are fresh. Generating extra practice cases from your own lecture material, including short AI-assisted OSCE role-play, can compress the repetition needed to internalize the format. One student profile describes moving from the 73rd to 92nd percentile while cutting study time in half using targeted practice questions, an illustrative case rather than a guarantee. Pair any practice method with feedback, since repetition alone without correction tends to reinforce the same mistakes.
The gap in how most students practice SOAP notes
Most advice on SOAP notes focuses on memorizing the four-letter acronym, as if knowing what S, O, A, and P stand for were the hard part. It isn't. The hard part is drawing the line between subjective and objective under time pressure, and that skill only comes from writing dozens of notes and getting told, specifically, where you crossed the line.
The conventional approach, read a textbook chapter, look at one example, then write notes during clerkship without structured feedback, produces slow improvement because errors go uncorrected for weeks. A tighter loop, short timed notes followed by rubric-based correction within a day, builds the pattern recognition that experienced clinicians rely on without thinking about it.
If you take one thing from this guide, prioritize feedback speed over note volume. Five notes corrected within 24 hours will teach you more than twenty notes graded a month later. Templates and mnemonics give you the scaffolding, but the scaffolding only helps once you know exactly which beam was wrong.
— Dr. Ahmed Abuzoor
Turn your encounters into practice cases automatically
Building SOAP note practice cases by hand takes time most clerkship students don't have between rotations. We built a tool to generate targeted practice material directly from your own lecture notes and course content, so the cases you write mirror what your professors and preceptors actually emphasize rather than generic textbook scenarios.
A typical workflow: upload your lecture notes or rotation material, generate a set of practice cases through our AI Question Generator, run timed OSCE simulations through AI OSCE Practice, and review each attempt against rubric-style feedback before moving to the next case. Try the free tier at Boardmaster to see how it fits your study routine.
FAQ
What is SOAP note practice and why does it matter?
SOAP note practice means repeatedly writing Subjective, Objective, Assessment, and Plan notes to build speed and accuracy in clinical documentation. According to the StatPearls overview, the format functions as a cognitive framework that organizes clinical reasoning, which is why consistent practice improves both note quality and diagnostic thinking.
What mnemonics help with writing the history of present illness?
OLDCART(S) and CLODIERSS are the two standard mnemonics used to capture HPI details like onset, location, duration, and severity, as outlined in a SOAP note refresher guide. Either one works well as long as you use it consistently across every note.
How long should a SOAP note practice session take?
A short practice session can run as little as 5 minutes for a micro-practice note, scaling up to 20 minutes for a full timed OSCE-style note. Shorter, more frequent sessions with fast feedback tend to build the skill faster than occasional long sessions.
What do faculty grading rubrics usually score?
Academic rubrics typically weight header completeness, HPI detail, objective documentation, assessment reasoning, and plan specificity, based on a SOAP note scoring rubric. Missing header fields and vague plan items are among the most common point losses.
What is the difference between SOAP and APSO formatting?
SOAP follows the traditional Subjective, Objective, Assessment, Plan order, while APSO moves Assessment and Plan to the front. A consensus discussion on EHR documentation describes APSO as an alternative some clinicians use to reduce the time spent searching for the plan in long electronic notes.
Sources
- StatPearls / NCBI: SOAP notes overview
- SOAP note refresher (Rowan SOM)
- SOAP note scoring rubric and assessment guidance (UNC faculty document)
- Consensus paper on inpatient EHR documentation (APSO discussion)