SOAP notes are straightforward in theory — four sections, clear purpose for each. In practice, the same mistakes show up repeatedly, even in notes written by experienced clinicians. The causes are predictable: time pressure, cognitive load, templating habits, and the gap between knowing the format and applying it under real clinical conditions.
This article covers the most common errors, why they matter, and specific fixes for each. At the end, you'll find a quality checklist you can use for self-review.
1. Missing subjective details
The subjective section often gets thin when clinicians are pressed for time. A chief complaint alone isn't enough. The HPI should include onset, duration, location, severity, modifying factors, and associated symptoms where relevant.
The problem: "Patient presents with back pain" tells the next reader almost nothing.
The fix: Capture the story. "Patient presents with lower back pain for 5 days after lifting furniture. Pain is 6/10, worse with bending, improved with ibuprofen. No radiation to legs, no numbness or weakness, no bowel/bladder changes."
The difference matters for clinical decision-making, billing (HPI elements support E/M coding), and continuity.
2. Mixing assessment and objective content
This is the single most common structural mistake. The objective section is for facts — what you measured, observed, or received as a test result. The assessment section is for interpretation — what those facts mean.
Examples of assessment content misplaced in the objective:
- "Lungs sound consistent with early pneumonia" (that's your interpretation)
- "Patient appears depressed" (that's a clinical judgment)
- "Rash likely represents contact dermatitis" (that's a diagnosis)
What belongs in the objective instead:
- "Scattered rhonchi in bilateral lower lobes"
- "Flat affect, poor eye contact, psychomotor retardation"
- "Erythematous, vesicular rash on bilateral dorsal hands with clear demarcation"
Save your interpretation for the A section. This separation protects you — if a future reviewer disagrees with your assessment, your objective findings still stand on their own.
3. Overly long notes
Length doesn't equal quality. Bloated notes often result from:
- Copied-forward history that wasn't updated or isn't relevant
- Templated review of systems where every system is listed regardless of relevance
- Duplicated information (same content appears in both the HPI and assessment)
- Normal exam findings for systems that weren't examined
The fix: Document what's relevant to this encounter. A follow-up for hypertension doesn't need a 14-system ROS or a full musculoskeletal exam. Document what you asked about, what you examined, and what's pertinent to today's clinical decision.
Concise, focused notes are easier to read, easier to code, and easier to defend.
4. Vague plan without specific next steps
"Follow up as needed" and "continue current management" are plan statements that don't help anyone — not your future self, not the covering provider, and not the patient.
Weak plan: "Continue medications. Follow up."
Strong plan: "Continue lisinopril 20 mg daily. Recheck BMP in 2 weeks to monitor potassium. Follow up in 4 weeks for blood pressure recheck. Patient instructed to call if dizziness, swelling, or BP consistently above 160 systolic."
A specific plan answers: What medication (dose, frequency)? What tests (and when)? What follow-up (and for what purpose)? What should the patient watch for?
5. Incomplete follow-up instructions
Related to vague plans — many notes omit safety-net guidance. When should the patient return sooner? What symptoms warrant an ER visit? What should they do if the medication causes side effects?
This information serves two purposes: it documents patient education (which supports billing and medicolegal protection), and it creates a clear decision point for the patient.
Include in your plan:
- Specific follow-up timeframe and purpose
- Conditions for returning sooner
- Red-flag symptoms that require emergency care
- Contact method for questions between visits
6. Undocumented pertinent negatives
Pertinent negatives are findings you looked for and didn't find. They demonstrate clinical reasoning and support your differential diagnosis.
If you're evaluating chest pain, documenting "no radiation to arm or jaw, no diaphoresis, no dyspnea" shows you considered cardiac causes. If you evaluated abdominal pain, "no rebound, no guarding, Murphy's negative" shows you assessed for surgical emergencies.
When to include pertinent negatives:
- When they support why you chose your diagnosis over a more serious alternative
- When they demonstrate appropriate evaluation for the presenting complaint
- When they'll help the next provider understand what was already ruled out
7. Copy-forward without verification
EHR templates make it easy to pull forward medication lists, problem lists, and social history from prior visits. The problem: those lists drift from reality.
A medication list that hasn't been reconciled in months may include discontinued drugs. A problem list may include resolved conditions. Social history from two years ago may not reflect current circumstances.
The rule: Only copy forward information you've verified during this encounter. If you didn't ask about medications today, don't attest to an updated medication list.
8. No connection between assessment and plan
The assessment and plan should read as a logical pair. Each diagnosis in your assessment should have a corresponding action in the plan. Each action in the plan should trace back to something in the assessment.
Disconnected example:
- Assessment: "Hypertension, uncontrolled"
- Plan: "Follow up in 3 months" (no medication change? No additional workup? The note implies you recognized the problem but didn't address it)
Connected example:
- Assessment: "Hypertension, uncontrolled on current regimen. Considering secondary causes given age of onset and resistance to two agents."
- Plan: "Add amlodipine 5 mg daily. Order renal artery duplex and aldosterone/renin ratio. Recheck BP in 4 weeks."
9. Using subjective language in the objective section
"Patient appears comfortable" or "patient seems in no distress" are subjective observations disguised as objective findings. Strictly speaking, they're clinical judgments — not measured values.
This is a minor point, and many clinicians include general appearance statements in the objective section by convention. If you do, keep it brief and move on to actual findings. The real risk is when unmeasurable impressions replace actual physical exam documentation.
10. Lack of clinician review on AI-generated notes
AI documentation tools produce fast, structured drafts. That speed creates a new mistake category: signing notes without adequate review.
Common issues in unreviewed AI notes:
- Medications listed at wrong doses (the AI misheard "20" as "12")
- Exam findings that were discussed but not performed appearing as documented
- Assessment that doesn't match the clinician's actual reasoning
- Plan items from a prior visit template bleeding into the current note
Clinicians should review AI-generated documentation before adding it to the medical record and should use Dictum in accordance with their organization's policies and applicable laws.
The review doesn't need to take long. For most encounters, scanning each section for accuracy takes 1-3 minutes. But that review is non-negotiable.
SOAP note quality checklist
Use this checklist for self-review before signing any note:
| # | Check | ✓ | |---|-------|---| | 1 | Chief complaint is clearly stated in the subjective section | | | 2 | HPI includes relevant elements (onset, duration, severity, modifying factors) | | | 3 | Medications and allergies are current and verified | | | 4 | Objective section contains only measurable/observable findings | | | 5 | Pertinent negatives are documented for the presenting complaint | | | 6 | No interpretive language in the objective section | | | 7 | Assessment includes specific diagnoses (not just symptoms) | | | 8 | Each assessment item has a corresponding plan element | | | 9 | Plan includes specific medications with doses and frequencies | | | 10 | Follow-up timing and purpose are documented | | | 11 | Safety-net / return-sooner instructions are included | | | 12 | No copied-forward information that wasn't verified today | | | 13 | Note length is appropriate — no unnecessary template filler | | | 14 | If AI-generated, all sections reviewed for accuracy before signing | |
How to build better documentation habits
Fixing documentation takes intentional practice. A few approaches that work:
Review one note per day critically. Pick yesterday's most complex note. Would a colleague find everything they need? Would an auditor see your reasoning? Would you understand it in 6 months?
Use consistent templates. Templates reduce the structural mistakes by guiding you through each section. Dictum's custom clinical templates let you define your preferred format so the output consistently matches your standards.
Read other providers' notes. Notice what's easy to follow and what's frustrating. Apply those observations to your own documentation.
Let AI handle the structure. When you use a tool like Dictum to generate AI SOAP notes, the mechanical sorting of content into correct sections happens automatically. Your review focuses on accuracy and completeness rather than organization.
For a complete breakdown of the SOAP format, read our guide on what a SOAP note is and how each section works. If you need a starting point for your documentation, try our SOAP note template.
Start documenting smarter
Good SOAP notes aren't about writing more. They're about putting the right information in the right place with enough specificity that the note serves its purpose — communication, billing, legal protection, and continuity.
Try Dictum free and let AI handle the formatting while you focus on clinical quality.