Sign in to Peak Brain Path
Sign in to access your courses, books, and progress tracker. New here? Signing in creates your account automatically.
Want to explore courses first?
Browse courses and booksSign in to access your courses, books, and progress tracker. New here? Signing in creates your account automatically.
Want to explore courses first?
Browse courses and booksModule 19
Chapter 19 · 1.5 h · 8 quiz items · pass at 80%
BCIA Domain VIII is the mechanics of running a session competently, and this module is the procedural core. It covers the pre-session checks, the baseline, the three threshold-setting methods, the reward and inhibit configuration, and the session note that makes the record defensible. The quiz proves the learner can set a threshold correctly and document a session to clinical standard.
The client is in the chair. You have done the intake, set expectations, obtained consent, and chosen a protocol. Now you have forty-five minutes to run a session that teaches the brain something and produces a record you could defend a year from now. This chapter is the procedure: the sequence from the impedance check at the start to the signed note at the end, and the decisions you make at each step that determine whether the session trains the brain or just entertains it.
The protocol chapters gave you the targets, the reward bands, the inhibit bands, the sites. This chapter is about execution, the part of Domain VIII that lives in the moment-to-moment running of a session. Most of it comes down to two things done well: a clean signal and a threshold the client can actually meet often enough to learn from. Get those right and the protocol works. Get them wrong and a sound protocol produces nothing, because you are either training noise or starving the client of the feedback that drives the learning.
A session starts before the training does, with three checks that take a few minutes and prevent most of the ways a session goes wrong.
The impedance check. Impedance is the quality of the electrical contact between the electrode and the scalp, and it is the gate on everything downstream. High impedance means a noisy signal, and a noisy signal trains nothing useful or, worse, trains an artifact. After you place each electrode, with conductive gel or paste at the site, the software reports the impedance at each location. The standard target is below 5 kΩ, and the values across active sites should be reasonably balanced, because a large mismatch between two electrodes degrades the differential amplification the system relies on. If a site reads high, the fix is mechanical: prep the skin again, add gel, reseat the electrode, check the connection. Do not start training on a site that will not come down. Chapter 6 covered why impedance and the common-mode rejection it enables matter at the level of the amplifier; here the point is operational. No clean signal, no session.
The mental status check. Before you train, take a minute to read the person. How did they sleep? How is the mood this morning? Anything happen since the last session, a stressor, an illness, a bad night? This is not small talk. The client's state shapes what the EEG looks like today and whether a noisy session reflects a protocol problem or just a hard week, and it is the data you do not otherwise have. A client who slept three hours and skipped breakfast is not going to produce the same session as one who is rested, and you want to know that before you interpret the running display.
The medication update. Ask what changed. A new prescription, a missed dose, a stimulant taken an hour ago, a benzodiazepine started since the last visit, all of these shift the EEG, and the shift changes both the baseline and the response to the protocol. Chapter 10 detailed the drug-by-drug effects; in the session, the discipline is to ask at every visit and to write down the answer, because a medication change is one of the first things you check when a client's data looks different than it should.
Before you set a threshold, you take a baseline: a short recording of the client's resting activity that tells you where they are starting today and gives you the numbers to set the reward and inhibit levels against.
The standard sequence is a few minutes of eyes open, then eyes closed, then eyes open again, watching the activity in the bands the protocol targets. Eyes open and eyes closed look different, and the difference itself is informative. Posterior alpha should rise with the eyes closed and drop, or block, when they open, and a client whose alpha fails to do that is showing you something about their rest-and-engage switching. The baseline also catches the day's confounds: an unusually high theta from poor sleep, an elevated high beta from anxiety walking in the door, a muscle artifact from a tense jaw.
The baseline matters because thresholds are set relative to the client's own activity, not to a fixed microvolt value. Amplitudes vary widely between people and between sites, so a reward level that is easy for one client is impossible for another, and a level that worked last week may be wrong today if the client's state has shifted. Take the baseline every session, even on a stable protocol, so what you set the client to chase is anchored to where they actually are this morning.
A threshold is the level the trained activity must reach to trigger a reward, and it is where the most sessions are won or lost. The principle underneath every method is the same: the client must succeed often enough the brain can detect what produced the reward. Set the threshold so success comes too rarely and no learning happens, because an unrewarded brain cannot tell what it did right. There are three common ways to set it.
The standard deviation method. Take the baseline of the reward band, compute its mean and standard deviation, and set the threshold a fixed distance from that mean, commonly around one standard deviation in the direction you want to train. This anchors the threshold to the client's own distribution of activity. Rewarding above roughly one standard deviation from the mean targets the upper portion of the client's current range, which is demanding enough to require the trained state but reachable enough to be learnable. The same logic runs in reverse for an inhibit: set the threshold so the client is below it most of the time and loses the reward when the inhibited band spikes.
The percentile method. Set the threshold so the client meets it some target percentage of the time at baseline, around 60 percent. A reward rate near 60 percent means the client succeeds more often than not, which keeps the operant contingency learnable, while still having to work for a meaningful fraction of the rewards. This is the same target the standard-deviation method approximates, expressed as a hit rate rather than a distance from the mean, and it is the more intuitive way to think about what the client is experiencing: a little better than half their attempts land.
Manual titration. Watch the reward rate live and adjust the threshold by hand to hold the client in the productive zone. Many systems also offer auto-thresholding, which continuously adjusts the level to hold a target reward rate as the client's activity drifts. Auto-thresholding is reasonable and saves attention, but understand what it is doing, because it can mask progress: a client whose underlying activity is improving can show a flat apparent performance because the software keeps moving the bar to hold the hit rate constant. Whichever method you use, the discipline is the same. Start conservatively, with thresholds loose enough that success comes readily early in a course, then tighten as the client improves, the way you add weight as a lifter gets stronger. A 60 to 70 percent reward rate early is teaching; a 20 percent rate is frustrating, and a frustrated client does not learn the contingency.
The threshold sets how high the bar is. The bandwidth sets what the bar is measuring, and the configuration of reward and inhibit bands is where the protocol logic meets the moment.
A standard surface protocol rewards activity in a target band and inhibits activity in one or more others. SMR rewards 12 to 15 Hz at a sensorimotor site while inhibiting the theta below and the high beta above, so the client is pushed toward the narrow sensorimotor rhythm without drifting into drowsiness or tension. Theta/beta rewards low beta, commonly 15 to 18 Hz, while inhibiting theta in the 4 to 8 Hz range, with a high-beta inhibit added so you are not rewarding the client into an anxious, over-activated state while chasing beta. The inhibits are not decoration. They keep the trained state in the productive middle by taking the reward away when the brain wanders toward the patterns you do not want.
Bandwidth is a real choice with a real tradeoff. A narrow reward band trains a more specific rhythm but is harder for the client to hit; a wider band is easier but less precise. SMR proper is a specific 12 to 15 Hz rhythm, not broadband beta, and a reward band widened too far stops training SMR and starts training something less useful. When you are settling on a target, start with the textbook band, watch whether the client can engage it, and narrow or widen from there based on the hit rate and the response. One caution carries over from Chapter 14: software platforms label these bands differently, so confirm what a given system means by "SMR" or "low beta" rather than assuming the edges match the textbook. The physiology is the same across platforms; the labels are not.
The feedback has to be readable as feedback. The brain associates a state with a reward only if the reward arrives close enough in time to the state that produced it and with enough structure the client's system can register the contingency.
Two timing parameters matter. The first is how quickly the reward follows the target state, the delay between the brain hitting the threshold and the feedback responding. Too long a delay and the contingency blurs, because the rewarded state has already passed by the time the signal arrives. The second is how densely the reward is delivered. Reward given too quickly or too continuously gives the client no time to register what produced it; the feedback becomes a wash of constant signal rather than a discriminable event. A short hold time, where the brain has to sustain the target state briefly before the reward triggers, makes the contingency cleaner by ensuring the reward marks a real state rather than a momentary flicker.
The most common beginner error in this layer is feedback too fast or too dense, the reward firing so continuously there is no contingency to learn. The feedback needs enough structure the rewarded state stands out from the unrewarded one. If the client is getting near-constant reward, the threshold is too loose or the timing is too dense, and either way the brain is not learning a discrimination.
A clinical session has a length, and more is not better. Surface arousal-regulation sessions run 20 to 40 minutes of actual training. Thirty minutes is the standard for theta/beta and SMR; 20 minutes can suffice for younger children or fatigue-prone clients; 40 minutes is toward the upper end before session fatigue starts working against you.
The reason to cap it is attention and the trained rhythm both fatigue, and a tired client late in an overlong session is consolidating fatigue rather than the trained state. A sixty-minute attention-training session in a nine-year-old is training exhaustion, not attention. Match the length to the client's capacity and stop while they can still engage. Within the session, a workable shape runs a brief baseline, then training delivered in blocks of several minutes with short rest intervals between them rather than one unbroken stretch, then a brief settling period at the end. The rest intervals matter because both attention and the rhythm recover in a short break, and a client who resets briefly re-engages better than one pushed straight through.
How often the client trains is a parameter like any other, and it has a clinical answer. The standard is two to four times per week, with three times per week the default in office practice and four for home-training clients who are not young, fragile, or highly sensitive.
The clinical consensus among experienced practitioners is training three times a week is roughly twice as impactful as twice a week, and four times a week yields diminishing returns on the same protocol compared to three. This is widely shared clinical experience rather than a published dose-comparison trial, and you should hold it as such. Where four sessions a week earns its place is when you are running multiple protocols, using the extra sessions to work different targets rather than hammering one harder.
The thing to advise against is three days in a row. Pushing back-to-back-to-back, lacking recovery days, produces overtraining, which in neurofeedback looks like getting the adverse effect instead of the intended one: more activation instead of calm, more fatigue instead of energy, disrupted sleep, a spacey rather than focused state. It is the brain equivalent of overtraining at the gym, tearing down faster than the system rebuilds. The workable spacing puts a rest day between most sessions: a Monday-Wednesday-Friday pattern, or Tuesday-Thursday-Saturday, or a four-day pattern that still avoids long unbroken runs. Less than twice a week means the gains from one session fade before the next reinforces them, and the learning curve flattens.
While the session runs, the display is telling you something, and reading it is part of the work. The running trace shows the reward band, the inhibit bands, the hit rate, and a trend across the session, and what you are watching for is whether the session is moving the way your protocol rationale predicted.
A session engaging the system shows the reward band trending up across the blocks, the inhibited activity settling, the hit rate climbing as the client finds the state. A session going nowhere shows a flat trace, no movement in either direction, which might mean the threshold is set wrong, the signal is contaminated, or the protocol is not engaging this client. A session moving the wrong way, the inhibited band climbing, the client visibly more activated, is information you act on rather than wait out.
Hold the within-session reading lightly, though. What the client produces in the chair is weak evidence about whether the protocol is working over the course, because the immediate session is noisy and the real signal lives in the days after. A good-looking session is not proof of trait change, and a flat session is not proof of failure. Use the running display to catch problems in the moment, a bad threshold, a contaminated signal, a wrong-direction response, and leave the verdict on whether the protocol is working to the longer arc Chapter 20 develops. The within-session indicators tell you whether this session is running cleanly; the trend across sessions and the client's between-session reports tell you whether the protocol is right.
You do not stop a session by switching off the screen and sending the client into traffic. The end of the session has a shape, and skipping it sends a client back into the day in whatever state the training left them.
Build in a brief settling period before the client stands up. A few minutes off the active feedback, sitting quietly, lets an activated nervous system come down and an alpha-class session resurface from its drift. This matters most after protocols that move arousal in either direction: a client who trained an activating protocol may be revved, and a client who trained alpha or alpha-theta may be in a soft, internally turned state that needs a few minutes to reorient before they drive. Take the electrodes off, let them sit, bring the conversation back to the room.
Then open the conversation. Ask what they noticed: during the session, and over the days since the last one. This is where you collect the between-session data that the EEG cannot give you, the sleep change, the mood shift, the thing that happened at work. A client reports the most useful information in the unstructured minute after the electrodes come off, when they are not performing and not on the device. Listen for the small things, because the small things are where the protocol is doing its work, and the client who learns you want the good, the bad, and the strange gives you a better readout than the one who thinks you only want good news.
The session is not finished until the note is written. The note is the artifact the session produces, and a defensible clinical record is one a different clinician could pick up cold and understand both what happened and why. A note recording the parameters but not the reasoning is a log of decisions without the judgment behind them; a note recording only the client's report is a case record without the clinical thinking that makes it useful.
A clean session note captures four things, which map onto the SOAP structure the field uses:
Updating all four at every session sounds like overhead and is not: a sentence each for the subjective and objective, the thread sentence for the assessment, the named next move for the plan, two to four minutes for a clean case. The value compounds across a forty-session course, because the note is what carries the case from one session to the next and from one clinician to another. The most common documentation failure is the note written only in the plan, the protocol change recorded but the reasoning omitted, so three weeks later no one can say why the site changed. Chapter 20 develops how the notes aggregate into an outcome record across the course; Chapter 23 covers what the record has to contain to meet your professional and privacy obligations. In the session, the rule is simple: the session ends when the note is complete, not when the client leaves.
A session runs as a fixed sequence. Check impedance and get every active site under 5 kΩ before anything else. Read the client's state and ask what changed in sleep and medication. Take an eyes-open, eyes-closed, eyes-open baseline to see where they are starting and to set thresholds against their own activity. Set the reward threshold so the client succeeds around 60 percent of the time, by the standard-deviation method, the percentile method, or manual titration, and start loose, then tighten as they improve. Configure reward and inhibit bands to the protocol, watching the bandwidth tradeoff between specificity and reachability. Deliver feedback that is timed and structured enough to be readable, not so fast or dense that the contingency washes out. Run 20 to 40 minutes in blocks with rest intervals, end with a settling period and an open debrief, and write the four-part note before the client is out the door.
For the BCN exam, fix the operational numbers and the logic behind them. Impedance target below 5 kΩ, balanced across sites. Threshold set for roughly a 60 percent reward rate, by standard deviation, percentile, or manual methods, because the client has to succeed often enough to learn the contingency. Reward and inhibit configurations for the core protocols, and the bandwidth tradeoff. Session length 20 to 40 minutes, capped because fatigue consolidates instead of the trained state. Frequency two to four times a week, three the default, never three days in a row because of overtraining. Within-session indicators read as real-time quality control, not as proof of trait change. A de-arousal period at the end before the client drives. And a four-part session note, subjective, objective, assessment, plan, written every session, because the session is not finished until the record is. The session is the unit of the work, and running it well is the difference between training a brain and running a machine.