How to Write a SOAP Note: Format, Example, Template, and Checklist

A SOAP note is a clinical progress-note format that separates four different kinds of information: what the patient reports (Subjective), what the clinician observes or measures (Objective), what the clinician thinks the information means (Assessment), and what happens next (Plan).

The letters are easy to memorize. Writing a useful SOAP note is harder. A note can contain all four headings and still fail if symptoms are presented as facts, the assessment only repeats the history, or the plan does not connect to the problems discussed.

This guide shows how to write a SOAP note that another clinician can understand and act on. It includes an original fictional example, an adaptable SOAP note template, a quality checklist, common failure modes, and current documentation standards.

The short version: a strong SOAP note makes the clinical reasoning traceable from the patient’s story to the next action.

What is a SOAP note?

The SOAP acronym stands for Subjective, Objective, Assessment, and Plan. It grew from the problem-oriented medical record and remains one of the most widely used ways to organize a patient encounter.

The College of Physicians and Surgeons of Ontario’s documentation guidance calls SOAP a widely recommended method for documenting encounters. Its guidance maps patient-reported information to Subjective, measurable findings to Objective, the physician’s impression to Assessment, and management details to Plan. The NCBI Bookshelf overview of SOAP notes describes the same four-part structure and explains that the assessment should interpret the information recorded above it.

That is the practical SOAP notes meaning: the format is an evidence chain.

People sometimes search for “soap meaning medical” because the everyday word soap hides the purpose of the acronym. In medicine, SOAP is not a checklist of mandatory phrases. It is a way to make different layers of the encounter visible:

• the patient’s account;
• the clinician’s findings;
• the clinician’s interpretation; and
• the agreed next steps.

SOAP is also not the only acceptable soap documentation order. Some teams place Assessment and Plan first, use a specialty-specific template, or add sections such as Intervention and Evaluation. The correct format is the one that meets professional, organizational, payer, and jurisdictional requirements while communicating the encounter safely.

Before writing: know what the note must do

A medical note is not a transcript, memory dump, or billing worksheet with a patient story attached. Its primary job is to preserve clinically useful information and reasoning for future care.

Before entering the first sentence, identify three things:

1. The encounter focus. Why is the patient here today, and which problems are active?
2. The likely reader. What will the next clinician need to know without reopening every prior note?
3. The action to close. Is there a test, referral, medication decision, precaution, or follow-up interval that must remain visible?

This framing prevents a common failure: documenting everything available while obscuring what changed. The CPSO Medical Records Documentation policy expects records to be accurate, relevant, encounter-specific, attributable, and organized so they tell the story of care. A concise note can meet that standard. A long copied note can miss it.

How to write a SOAP note, step by step

The safest way to learn how to write a SOAP note is to treat each section as a different reasoning task. Do not draft all four sections in the same voice.

1. Start with the encounter focus

Write the reason for the encounter before expanding the history. For a single concern, this may be a one-line chief complaint. For a multi-problem follow-up, identify which conditions changed, which are stable, and which require decisions today.

A useful opening lets the reader answer, “Why did this encounter happen?” If that answer is buried halfway through the note, the soap format is not doing its job.

For evaluation and management services, current CMS documentation guidance says the record should capture the reason for the encounter, relevant history and findings, an assessment or diagnosis, the rationale for services, the care plan, the date, and the observer’s identity. SOAP can organize those elements, but the headings alone do not prove the service was documented adequately.

2. Write Subjective as the patient’s story

Subjective information comes from the patient, caregiver, or another clearly identified source. It may include:

• the chief concern in the patient’s own terms;
• onset, course, severity, triggers, relieving factors, and functional effect;
• relevant symptoms and meaningful negatives;
• changes since the last visit;
• medication use, adherence, adverse effects, and allergies when pertinent;
• relevant medical, family, or social context; and
• the patient’s goals, concerns, and preferences.

Use attribution when the source matters: “Patient reports…,” “Parent observed…,” or “Paramedic handover states….” Attribution is especially important when accounts differ or the patient cannot provide the history directly.

Keep interpretation out of this section. “Patient reports burning pain after meals” is subjective. “Symptoms are consistent with reflux” is an assessment. The distinction protects the record from turning a report into a diagnosis by accident.

Avoid inflating the history with a complete review of systems when only a focused review is relevant. Meaningful negatives help demonstrate what was considered; a copied wall of normal findings makes the important negatives harder to see.

3. Write Objective as observed or verified evidence

Objective information is what the clinician measured, observed, examined, or verified. Depending on the encounter, this can include:

• relevant vital signs;
• focused physical examination findings;
• laboratory, imaging, pathology, or diagnostic results;
• measurements from a validated device;
• medication administration or procedures performed;
• reviewed records or consultant findings; and
• observed function, appearance, behaviour, or response.

The word objective does not mean “certain.” A device can be inaccurate, a test may be preliminary, and an examination is limited by what was assessed. Document the source and limitations when they affect interpretation.

Do not convert patient statements into objective findings. “Home blood pressure reportedly 160/90” remains patient-reported until the data are verified or imported from a trusted source. Likewise, do not populate a comprehensive normal examination if a focused examination was performed.

A disciplined Objective section gives the Assessment something real to synthesize. It should not become a raw data warehouse. Include what changes the interpretation, supports the plan, or establishes an important baseline.

4. Write Assessment as clinical synthesis

Assessment is where the note stops collecting information and starts explaining it. Depending on role, scope, and setting, it may contain:

• the diagnosis or working diagnosis;
• a prioritized differential diagnosis;
• the status of each active problem;
• response to treatment;
• relevant risk or uncertainty;
• why a serious alternative is less or more likely; and
• how today’s findings change the previous impression.

Weak assessment: “Shoulder pain.”

Stronger assessment: “Right shoulder discomfort is improving after lifting, with no weakness documented on today’s focused exam; working impression remains muscular strain.”

The stronger version does not sound more impressive. It shows the link between the story, findings, and level of certainty. That link is the information another clinician needs.

Avoid overstating certainty. If the encounter supports a differential rather than a final diagnosis, say so. If the examination was limited, document the limitation. If two problems interact, explain the relationship rather than listing them as disconnected labels.

5. Write Plan as executable next steps

Plan translates the Assessment into actions. For each active problem, make the next step specific enough that the patient, care team, and future clinician can tell what should happen.

A plan may include:

• tests or monitoring and why they are needed;
• treatment selected, continued, changed, or stopped;
• medication details and reconciliation;
• procedures;
• consultation or referral and its purpose;
• patient education and shared decisions;
• precautions or thresholds for reassessment;
• follow-up timing;
• outstanding results and who will review them; and
• a decision the patient declined or deferred, including the documented discussion where required.

“Follow up as needed” is rarely as useful as a defined interval or condition. “Labs ordered” is weaker than naming the relevant test, the question it addresses, and the follow-up responsibility when those details reflect the real encounter.

Link the Plan to the Assessment problem by problem. In a multi-problem note, a numbered Assessment and Plan can prevent orders or follow-up from floating without a clear reason.

6. Reconcile, correct, and authenticate

Before signing, compare the note with:

• the encounter you remember;
• diagnoses and the current problem list;
• medications and allergy information;
• placed or pending orders;
• referrals;
• results reviewed;
• patient instructions; and
• the planned follow-up.

Then remove stale copied text, contradictory findings, unsupported certainty, and template fields that were not addressed. Confirm the date, author, and authentication requirements.

This last pass is part of SOAP charting, not optional polish. CPSO expects documentation as soon as possible, while CMS advises documenting during or soon after the visit to keep the record correct. Local rules determine how late entries, addenda, co-signatures, and corrections must be handled.

A complete SOAP note example

The example below is an original fictional composite with no real patient information. It shows how the four sections connect in one concise note.

Why this SOAP note example works

The Subjective section preserves the patient’s experience and meaningful negatives without adding a conclusion. The Objective section records a focused examination without claiming findings that were not assessed. The Assessment states a working impression and level of certainty. The Plan records the decisions that need to be reconciled.

The example is also intentionally concise. A complex patient with multiple active conditions, medication changes, risk discussion, and pending results would require more detail. A minor follow-up may require less. Quality depends on whether the record supports safe continuity, not on reaching a particular word count.

SOAP note template you can adapt

A SOAP note template should prompt good reasoning without pre-writing the encounter. The following structure can be adapted to a specialty or EHR:

SUBJECTIVE
Reason for encounter:
Source of history:
Relevant history and interval change:
Associated symptoms and meaningful negatives:
Medication use, allergies, function, goals, and concerns:
 
OBJECTIVE
Relevant vital signs or measurements:
Focused examination or observations:
Relevant results or records reviewed:
Limitations of examination or data:
 
ASSESSMENT
Problem 1: status, working diagnosis or differential, reasoning, uncertainty:
Problem 2: status, working diagnosis or differential, reasoning, uncertainty:
 
PLAN
Problem 1: tests, treatment, medication, education, precautions, follow-up:
Problem 2: tests, treatment, medication, education, precautions, follow-up:
Outstanding results and owner:
Patient decisions, consent, or declined recommendations where applicable:

Do not paste this soap notes template unchanged into every chart. Remove inapplicable prompts, add specialty-required fields, and confirm that the final note matches the actual encounter. A useful template reduces omissions and prompts the writer to verify each field.

For a broader discussion of reusable formats, see our guide to medical documentation templates and snippets.

A transparent SOAP note quality checklist

Use the checklist below before authentication or during peer review. It is intentionally visible so quality is judged against the same standard each time.

The checklist is not a scoring system for note length. A short note can pass every item. A long note can fail because the assessment is vague, the plan is disconnected, or copied information conflicts with today’s encounter.

Common SOAP note mistakes and how to correct them

Subjective and Objective are blended

Problem: Patient-reported measurements or interpretations appear as verified findings.

Correction: Attribute the source. Keep symptoms and reports in Subjective; put observed or verified findings in Objective; reserve interpretation for Assessment.

Objective becomes a data dump

Problem: The note reproduces every laboratory value, imaging sentence, or normal examination field.

Correction: Include the data that support the assessment, change management, establish a meaningful baseline, or meet a specific requirement. Link to the source report where the EHR supports it.

Assessment only renames the complaint

Problem: “Cough” becomes “Assessment: cough” without synthesis.

Correction: State status, likely explanation, relevant uncertainty, response to treatment, or the differential appropriate to the encounter.

Plan is vague or orphaned

Problem: “Monitor,” “refer,” or “follow up” appears without timing, rationale, owner, or a linked problem.

Correction: Number active problems and make the corresponding actions explicit. Reconcile the note with actual orders and patient instructions.

Old text is copied forward

Problem: A prior examination, medication list, or diagnosis survives even though it was not verified today.

Correction: Treat copied text as unverified until reviewed. CPSO requires each encounter’s documentation to be unique and accurate. AHRQ PSNet’s analysis of copy-and-paste risks describes how stale or misattributed information can propagate through an EHR and obscure the patient’s real story.

Abbreviations create ambiguity

Problem: A shortened term or dose expression can be interpreted more than one way.

Correction: Follow the organization’s standardized terminology. The Joint Commission’s April 2026 guidance applies its prohibited abbreviations and dose-designation list to medication-related documentation in both handwritten and electronic records.

The note disagrees with the orders

Problem: The Plan states that a medication changed or a test was ordered, but the corresponding order list says something else.

Correction: Reconcile the narrative, orders, medication list, referrals, and after-visit information before signing. The final note and operational record should tell the same story.

SOAP, APSO, SOAPIE, DAP, and other note formats

The standard SOAP note format is useful, but it is not sacred. Different settings arrange the same reasoning differently.

• SOAP: Subjective, Objective, Assessment, Plan. Familiar and logical for documenting a new or changing problem.
• APSO: Assessment, Plan, Subjective, Objective. Moves decisions to the top for faster scanning. In a small simulation involving 16 primary care physicians, APSO-oriented prototypes improved speed, task success, or usability for several information-finding tasks compared with a traditional SOAP display; that does not prove APSO is superior in every workflow.
• SOAPIE: Subjective, Objective, Assessment, Plan, Intervention, Evaluation. Often useful when the action performed and response must be documented explicitly.
• DAP: Data, Assessment, Plan. Common in some behavioural health and allied-health settings.
• Problem-oriented Assessment and Plan: Organizes each active problem with its own reasoning and actions, which can make multi-problem visits easier to follow.

Choose a format that matches the clinical setting, professional scope, EHR, and local requirements. The content and reasoning matter more than loyalty to one heading order.

How AI medical scribes fit into SOAP documentation

An AI medical scribe can sort permitted encounter information into a SOAP note draft. That can reduce clerical effort, but it also creates specific review risks:

• a symptom may be moved from Subjective into Objective;
• a normal finding may be invented or pulled from a template;
• the Assessment may sound more certain than the clinician was;
• a plan discussed hypothetically may be written as an order;
• medication dose, laterality, timing, or negation may be wrong; and
• the note may become longer without becoming more useful.

The safe boundary is the same as for other documentation assistance: the clinician supplies judgment and authenticates the record. Our guide to what a medical scribe does explains the human, remote, and AI workflows in more detail.

When evaluating an AI-generated SOAP note, do not ask only whether it “looks right.” Compare it with the encounter and measure meaningful omissions, unsupported additions, corrections, and review time. The ONC SAFER Guides offer current, system-level practices for assessing the safe use of EHR technology.

To see the product workflow, learn how Vero drafts a SOAP note for clinician review.

Documentation standards still come before the acronym

SOAP can help organize a record; it does not replace the rules that apply to the record.

In Ontario, CPSO expects the medical record to document the presenting complaint, focused history, relevant assessment and examination, diagnosis or differential, treatment and response, and a management and follow-up plan where indicated. In the United States, CMS documentation expectations for E/M services similarly emphasize the encounter reason, relevant history and findings, assessment or diagnosis, rationale, plan, date, and author identity.

Other professions and jurisdictions may define different content, timing, signature, retention, correction, and access requirements. Payer rules can also differ from clinical best practice. Use the applicable professional standards and organizational policy rather than assuming that a SOAP heading makes a note compliant.

Patients may also read the record. Clear attribution, neutral language, meaningful abbreviations, and visible reasoning improve the note for clinicians and for the person whose care it describes. For the accountability boundary, see who is legally responsible for a patient medical record.

Bottom line

A strong SOAP note is not four labelled boxes. It is a clear chain:

Subjective tells the patient’s story. Objective records the evidence. Assessment explains what the clinician thinks. Plan makes the next step visible.

Use the format to expose reasoning, not to generate more text. Keep the note relevant, reconcile it with orders and instructions, and authenticate it according to the standards that apply to your role and setting.

Sources and further reading

• CPSO: Medical Records Documentation
• CPSO: Advice to the Profession: Medical Records Documentation
• CMS: Evaluation & Management Services documentation requirements
• The Joint Commission: Abbreviations, acronyms, symbols, and dose designations
• NCBI Bookshelf: SOAP Notes
• AHRQ PSNet: Copy-and-paste notes and autopopulated text in the EHR
• ONC: 2025 SAFER Guides
• PubMed: Dynamic electronic health record note prototype