What a session note is really for, the SOAP/DAP/BIRP structures, personal notes, the KVKK duty of access, third parties and documenting risk.
The session note is the most postponed and least discussed part of clinical practice. It is rarely taught at undergraduate or postgraduate level; supervision covers the case, but not the note itself. Most therapists end up acquiring a way of writing notes by trial and error, by copying a template they saw on placement, or without thinking about it at all.
For a while this causes no trouble. The trouble arrives when a client who terminated three years ago comes back, when a case has to be handed to a colleague, when a referral letter is requested, or when a client asks for their own records. At that moment you either have a record you can work from, or a sentence that begins “as far as I remember”.
The answer to this question determines everything else about how you write. A session note has four possible readers, and all four have to be held in mind at once.
Your future self. This is the most frequent reader by far. If you see twenty clients a week, most of the detail you can recall while writing a note will be gone three months later. The note’s real job is to put you back inside the process in thirty seconds, at the start of that session three months from now.
A colleague. A handover, cover during a holiday, joint work on a case, or the file passing to someone else in an unexpected situation. Will somebody who does not know your abbreviations, your private markings and the formulation in your head be able to work from this note?
The client. In Turkey, a client can request access to personal data concerning them. This is no remote possibility; litigation, divorce proceedings, insurance claims and custody files are the most common reasons. Writing a note on the assumption that the client will read it is a good discipline — it simplifies the language and it strips out unnecessary commentary.
An institution or a court. A court summons, an expert witness request, an internal audit. Unlikely as this is, when it happens what the note does not say matters as much as what it does.
These four readers do not pull against one another; they all face the same way. A note that serves all four is short, factual, dated, and shows its reasoning.
Treating the session note as the job of writing down what happened is the most common wrong frame. Notes written in that frame turn into a summary of the session: what the client said, what the therapist said. That kind of note is long, tiring to write, and almost useless when read.
Because what you need at the start of the next session is not what was discussed in the last one. What you need is this:
When the structure of the note is built to answer those questions, it becomes shorter to write and it does some work when read. That is the whole point of choosing a structure.
Three structures are in wide use. None is absolutely superior to the others; they sit differently in different practices.
The most established structure in healthcare. Four sections:
SOAP’s strength is that it physically separates observation from interpretation. That separation is valuable to everyone who reads the note later; which sentence is data and which is inference stays beyond dispute. Its weakness in a psychotherapy context is that the “objective” heading is too narrow — most of what is observable in a therapy room is nothing like as clean as a lab value.
SOAP adapted and simplified for psychotherapy:
For most solo practices in Turkey this is the most workable structure. Because it does not force the S/O split it is quicker to write, and it fits the nature of psychotherapy material better. The price is the risk of data and interpretation blurring together under one heading; the only defence against that is care in the language itself.
An intervention-focused structure, common in institutional settings:
What distinguishes BIRP is that it forces what the therapist did into the record. In SOAP and DAP the therapist’s own actions usually stay invisible; the note consists of the client’s account and the therapist’s interpretation, with nothing written about what was actually done in between. For supervision, and in the event of a handover, that information is critical. In group work, addiction programmes and practices that run structured protocols, BIRP is usually the best fit.
A practical test: can you write the note in five minutes after the session? If you cannot, the structure is too heavy for you, and within a few months the notes will start to pile up and then to lose quality.
Modality-specific templates — thought records and agenda structure for CBT, diary cards for DBT, mode tracking for schema therapy, session and SUD/VOC logs for EMDR — do not replace these three general structures; they sit inside them. Modality-specific fields get added to the “Data” section of a DAP, say, and the “Plan” section carries the protocol’s next step.
Changing the structure you have chosen does not corrupt older notes, but it does weaken comparability. So making the change on a particular date and recording that date makes looking back much easier later on.
This distinction is the most muddled point in clinical documentation, and muddling it produces both clinical and legal problems.
The session note is part of the client file. It is the formal record of the process: when the session took place, what was reported, what was observed, what was assessed, what was planned. It can be the subject of an access request, it is handed over on transfer, and it can be produced to the relevant authorities when required.
The personal note, or process note, is the therapist’s own thinking tool: hypotheses, countertransference reactions, questions to take to supervision, hunches not yet tested, impressions of the “this person reminds me of X” kind.
There are three reasons to keep the two apart.
The clinical reason. Writing an unverified hypothesis into the formal record turns that hypothesis into a fact over time. Three years later, whoever reads the file — you included — reads “possible narcissistic pattern” as “narcissistic pattern present”. The record should carry what has been established; the thinking happens elsewhere.
The legal reason. Turkish legislation does not define a separate category giving process notes special protection, as the US system does. The practical consequence is this: do not assume your personal notes are automatically shielded from an access request or a legal process. The real benefit of the distinction is not that it provides absolute protection, but that it keeps the formal record clean and defensible.
The ethical reason. Countertransference material is something to work on in supervision, not something to sit in the client’s file.
A rule that works in practice: every sentence that enters the file should be a sentence you could say to the client’s face. If it cannot be said, it either goes into the personal note or it does not get written at all.
Whether a note can be read comes down to a handful of writing habits, and every one of them can be learned.
Separate observation from inference. “He was angry” is an inference. “His voice rose, he interrupted me twice, he folded his arms” is an observation. The second takes longer to write but still means something three years later; the first carries no more than the writer’s impression on the day. If you are going to record an inference, write it alongside the observation and make it clear that it is an inference: “The tension observed may be a continuation of last week’s conversation.”
Quote where quotation earns its place. A client’s own sentence carries more information than ten lines of summary. Repeated phrases, core beliefs about the self and statements about risk in particular should be quoted directly. But three paragraphs of quotation every session makes the note unreadable.
Standardise your abbreviations. If you use abbreviations of your own, keep a key for them somewhere in the file. A note nobody but you can decode is a blank page to a colleague.
Use jargon sparingly. Terms like “transference”, “case formulation” and “schema mode” speed up communication between colleagues. But given the chance that the client will read the note, putting a one-sentence gloss beside a technical term is both a courteous and a safe habit.
Be careful with diagnostic language. A scale score above a cut-off is not a diagnosis. If you are not qualified to diagnose, or the assessment is not yet complete, the language has to show it: there is a large legal and clinical difference between “Depressive symptoms reported, PHQ-9 in the clinical range” and “Major depressive disorder”.
Date every note, and write it on time. A note written straight after the session and a note written three days later are not the same thing; in the second, detail is lost and impressions run together. A note written after the fact should be dated in a way that makes clear it was written after the fact.
Under Article 6 of KVKK — Turkey’s data protection law — psychotherapy records are special categories of personal data. Several consequences follow that bear directly on documentation.
You are the data controller. The duty to inform, to manage consent and to answer data subject requests in respect of your client’s clinical data rests with you. The software you use is the party processing that data on your behalf.
The data subject has a right of access. Article 11 of KVKK gives a person the right to learn whether data concerning them is being processed and to request information about it. In practice that means a client can ask for their own records. Answering the request is your obligation.
That obligation bears directly on how notes are written. Writing in the knowledge that the client may read it is not self-censorship; it is stripping out unnecessary commentary, moving the language closer to fact, and writing inferences together with their grounds. A well-written note is one that needs no defending when the client reads it.
A retention period has to be set. When the purpose for which the data was processed falls away, it has to be deleted, destroyed or anonymised. In practice that means setting a retention period for each type of record and committing it to a written policy. The periods prescribed by the relevant health legislation and your own professional obligation may differ; this period has to be determined by consulting the applicable rules, not by guessing.
Access has to be logged. There should be an answer to the question of who saw which file and when. In a multi-therapist clinic this is not only a compliance matter but a matter of trust within the team. Front desk staff not seeing clinical notes is a boundary set at the outset, not a setting added afterwards.
Correction is not deletion. Any later intervention in a note has to be traceable. Restricting a locked note to correction by addendum is the constraint that keeps the audit trail meaningful. Quietly deleting a mistake and rewriting it is one of the hardest things to explain in a legal process.
The cost of too much detail is not only time. A long note does not get read; an unread note is close to a note never written. Beyond that, every detail that enters the file is a detail that will be disclosed on the day the file has to be disclosed.
A practical filter: does this information affect a clinical decision?
If it does, it gets written. That a conflict at the client’s workplace is disrupting their sleep is clinically meaningful. Which project the conflict was about, who said what to whom, which day the meeting was held, generally is not.
Areas that call for particular care:
Sexual material. Write as much as is clinically necessary, in the most neutral language available. Detailed description is almost never necessary for a clinical decision.
Disclosures of illegal activity. If there is no clinical reason to record a client’s account of an offence committed in the past, it is better not to go into detail. Situations that trigger a duty to report are a separate matter and have to be assessed on their own.
Family secrets and private information about third parties. Covered separately below.
Too little detail carries its own cost, though. Hollow notes along the lines of “Session took place, process ongoing” look like a duty discharged while discharging no function at all. They cannot be defended in an audit, and they do nothing for clinical continuity.
Your client talks in session about their spouse, their mother, their manager. These people are not your clients, and everything you write about them will be disclosed on the day the file is shared.
Three habits help:
Attribute the source. The difference between “His wife drinks” and “Client reported that his wife drinks” is the difference between a claim of fact and a record of a statement. The second is accurate and defensible; the first enters something you have not verified into the record as fact.
Use names sparingly. Unless it is clinically necessary, referring to third parties by their role — spouse, older sister, senior manager — is enough. In divorce or custody files, how significant the names in a note can become is usually only understood afterwards.
Confine assessment to your client. Do not write a clinical assessment of someone you have never seen. “Possible narcissistic traits in the mother” is a claim entered into the record by a professional who has never assessed that person, and it cannot be defended.
In couples and family work this has to be thought through separately: whose record it is, whether what is said in individual meetings goes into the shared file, and what happens if one party makes an access request, are all matters to settle at the start of the process.
Notes on sessions involving risk call for a different order of rigour. Here the note’s function is not only clinical continuity; it is to show the reasoning behind the assessment made and the decision taken.
What a risk note should contain:
Two things to watch here. First, when a risk assessment is not carried out, that too has to be visible. A file in which the relevant item on a scale was endorsed but the subject was never opened in the session carries a gap that is hard to explain. If an assessment was made, it should be written down; if it was not, the reason it was not should be.
Second, a risk note must not be delayed. This is the one type of note that cannot be left until the next day. A risk note written immediately after the session and one written three days later carry different weight, clinically and legally alike.
Phone calls, messages and contacts with family members after a crisis also belong in the record. That they happened outside a session does not make them any less a clinical contact.
The biggest enemy of note-writing is timing. Arrangements that work:
Telling the client you take notes during the session, being open to showing them what you wrote if they are curious, and explaining at the outset where the records are kept, takes the note out of being a piece of bureaucracy sitting outside the relationship. For many clients it is a sign of being taken seriously.
Writing a good session note is not a writing skill but a clinical discipline. Choosing a structure, separating observation from inference, keeping personal notes out of the file, and recording risk on time — these are the things that keep the process still workable six months later.
We also covered how the draft, approval and lock steps are separated, and why the audit trail matters, in AI in therapy.
Let's talk through how this would work in your own practice.Book an intro call
In about fifteen minutes we'll walk you through the product on a demo built around your practice, and answer whatever is on your mind.
30-day money-back guarantee.