DRO at Bedtime: Reinforcing Behavioral Quietude Without Extinction

The Excuse Me protocol is time-based DRO in a costume, and once you see the interval math, the fading rule, and the parent-fidelity script underneath it, you can run it without ever asking a family to ride out a nighttime extinction burst. That matters, because at bedtime the BCBA is not in the room. Mom or Dad is. The plan has to survive their tired hands, their soft heart, and a kid who has every reason to call out one more time. A clean DRO schedule for behavioral quietude does that. It pays the kid for an absence of behavior at intervals you have set on purpose, it fades up only when the data say so, and it drops back the second a kid misses a step. No punishment. No burst. No promises you cannot keep at 2 a.m.

Why bedtime is a DRO situation (the dead man's test problem with sleep)#

Every BCBA learns the dead man's test early. If a dead person can do it, it is not a behavior. Sitting still. Not yelling. Not getting up. By that rule, the thing we want at bedtime is not really a behavior at all. That is the whole problem with treating sleep transition like a normal target. You cannot reinforce nothing in a vacuum. You have to define the conditions under which the absence counts. Dr. Emily Ice calls this state behavioral quietude, and she pulls it straight from the sleep literature.

the behavior for the transition to sleep is actually an absence of behavior under the right conditions. And this is coined behavioral quietude in the literature.

DRO is the schedule that fits. Differential reinforcement of other behavior pays the learner when a target behavior does not happen for a set period of time. At bedtime, the target you want to drop is anything that breaks the transition into sleep. Calling out for Mom. Getting out of bed. Asking for water. Repeating a request. The "other" you are paying is the quiet body in the quiet room. DRO lets you reinforce that without ever needing the kid to emit a separate replacement response, which would compete with the very state you are building.

Setting the DRO interval from a baseline calm-in-bed measure#

Do not pick an interval out of the air. Pull it from your data. Five nights of a sleep journal will tell you how long this kid actually stays quiet in bed before they call out, get up, or escalate. That number is your starting interval. If the kid is calm for two minutes before the first call-out, your first interval is two minutes. Not three. Not five. Two. The whole point of a DRO interval is that the kid hits it. If they do not contact reinforcement on night one, the schedule is dead before it starts.

A few rules of thumb for the baseline pull:

• Use a five-night minimum. Sleep is noisy. One bad night does not mean the kid cannot tolerate four minutes.
• Pull the median calm interval, not the mean. One outlier night will pull a mean up and set you up to fail.
• If the data are messy or the family is new to journaling, start conservative. A one-minute interval that the kid crushes beats a four-minute interval that ends in a tantrum.

Once you have the number, write it on the protocol and tell the parent: this is where we start tonight.

Picking the reinforcer for an in-bed DRO without breaking sleep dependencies#

This is where a lot of bedtime DROs quietly fail. The point of behavioral sleep treatment is to let sleep itself be the reinforcer once the transition opens up. Pile a high-strength reinforcer on top of the quiet interval, and you have just built a competing contingency that the kid will hold out for. Worse, if the reinforcer is something the kid then needs every time they cycle into a light sleep stage, you have created a brand-new sleep dependency. The fix is to use low-strength, brief, in-context attention as the DRO payoff. A check-in. A short "I love you, goodnight." A gentle hand on the shoulder.

Three filters for picking the reinforcer:

1. It can be delivered without fully waking the kid.
2. It does not require Mom or Dad to stay in the room.
3. It can be faded out cleanly once the kid is sleeping through.

Tangible reinforcers, snacks, screens, and long snuggle sessions all fail at least one of these. Save the bigger reinforcement for morning. Pair waking with the good stuff and you sharpen sleep as the primary reinforcer overnight.

How the Excuse Me protocol is actually time-based DRO in disguise#

The Excuse Me protocol is the parent-friendly skin on top of the schedule. Dr. Ice has used it for years because it gives families a behavior to do, not just a behavior to withhold. The parent walks in, gives low-quality attention for a moment, and then says something like, "Excuse me, I need to go check the laundry, I will be right back." Then they leave. They come back at the next planned interval, do the same thing, and leave again. The kid is being reinforced for behavioral quietude on a time-based schedule. The "excuse me" line is a parent-fidelity tool, not a magic phrase.

If their baseline is they will hang out in bed, quiet and calm for two minutes, we're going to start at two minutes. Then over the night, you can shake that out, you're going to fade out the time, extend it slightly

Two things the BCBA has to get right when teaching this:

• The attention has to be low quality. If the parent climbs in for a five-minute cuddle, you are not running DRO, you are running a thick schedule of social reinforcement on a noncontingent fixed time schedule, and you will not be able to fade it.
• The exit has to be calm and matter-of-fact. The "excuse me" line is what lets the parent leave without negotiating. It gives them a script.

Fading the interval up one drop per night when the kid is successful#

Fading is dead simple, and that is the point. On a successful night, you drop the first interval off the schedule. The kid started at two minutes, four minutes, six minutes. Tonight you start at four minutes and walk up from there. Across a week, the kid is now in bed quiet for ten or fifteen minutes between check-ins, and the parent is in the room maybe twice before the kid is out.

A few teams move in thirty-minute jumps. Dr. Ice has found that fifteen-minute jumps fit more learners. The numbers matter less than the rule: one jump per successful night, no skipping. The kid does not get a vote. The data do.

What to do when a kid fails an interval (drop back, don't punish)#

This is the part the team has to rehearse before night one, because a failure will happen and the parent's instinct will be to punish or to escalate. Neither. You drop the interval back one step and hold it.

if a child engages in sleep-interfering behaviors at interval three, say, the parent can return to interval two and hold constant to encourage success.

"Hold constant" is doing a lot of work in that sentence. You are not dropping back for one interval. You are not dropping back for one night. You are dropping back until the kid is contacting reinforcement reliably at that step again. Then you start fading up from there. The kid wins again. The parent wins again. The schedule stays alive.

This is also where the "no extinction" line lives. If you try to push through the failure with planned ignoring, you will get a burst, and the burst will happen in a dark house at midnight with a tired parent who is alone with it.

don't push for extinction because you're not going to be there to walk through the extinction burst at nighttime when everybody's already tired and it's hard enough

Pairing DRO with sleep dependency upgrades so it doesn't create new ones#

A DRO schedule that runs on parental presence is a DRO schedule that builds a new sleep dependency. That is why the protocol is paired with stimulus control work. While the parent is fading their check-ins up, you are also installing SDs that will travel through the night with the kid. The classic one is a white noise machine turned on as the very last step of the bedtime routine and off as the very first step of the wake-up routine. The kid stops needing the parent to fall asleep, because the SD for sleep is something that stays in the room until morning.

This is the difference between a DRO that holds at 30 days and one that collapses the first time a parent has to travel. If the schedule is the only thing keeping bedtime calm, you are one bad week away from starting over. If the schedule is layered onto an SD that the kid actually owns, the win sticks.

Parent fidelity scripts (what to say when you walk back in)#

The script is the protocol. If the parent freelances at the door, the schedule breaks. Write the script down. Practice it in the kickoff meeting. Hand it to the parent on a card if you have to.

Three lines that almost always work:

• "I love you, goodnight." Said quietly, from the door, no closer.
• "Excuse me, I need to go check on something, I will be right back."
• "You did such a good job staying in bed. I will see you in the morning."

Things to keep off the script:

• Any question. "Are you okay?" reopens the negotiation.
• Any new demand. "Lay down" turns the check-in into an SD for instruction-following.
• Any long sentence. Long means the kid heard you, and long means you are still in the room.

When the parent has a script, the protocol gets simpler to coach and easier to run on a Tuesday night when everyone is fried.

FAQ#

Isn't reinforcing quiet just teaching them to wait for the snack? Not if you pick the reinforcer with care. The DRO payoff at bedtime is low-strength attention, not a tangible. The kid is being paid in a calm check-in, which fades out cleanly. If the payoff is a snack or a screen, you have built a competing contingency and the kid will hold out for it. Keep the payoff small and in-context, and the quiet generalizes.

How short should the first DRO interval be? As short as your baseline data say. If the kid is calm in bed for two minutes before they call out, start at two minutes. The first interval has to be a layup. If you are not sure, start shorter than you think. You can always fade up. You cannot un-burn a kid on a schedule that paid out zero on night one.

What reinforcer doesn't ruin the sleep transition? Low-quality parental attention delivered briefly. A check-in, a short goodnight, a hand on the shoulder. Avoid tangibles in the room. Save the high-value reinforcement for the wake-up routine so the kid is not lying in bed waiting for it.

Do I deliver the reinforcer in the room or after wake-up? Both, but at different strengths. In the room, deliver only the low-strength check-in from the Excuse Me script. After wake-up, deliver the bigger pairing, breakfast, attention, preferred activity, so the morning is what the kid is biologically pulling toward.

When do I fade DRO out entirely? When the intervals have grown to the point that the kid is asleep before the second check-in for a stretch of nights and the night wakings have dropped to baseline. At that point, you are no longer running a schedule, you are running a bedtime routine.

Bridge to your next move#

DRO is the schedule that holds bedtime together without asking a parent to ride out a burst. The interval comes from the data. The fade comes from success. The drop-back comes from a miss. The Excuse Me script keeps the parent in the protocol instead of in the negotiation. Layer it onto a white noise SD, pair the wake-up with the bigger reinforcement, and you have a treatment package that survives the nights you are not in the room.

If you want the full hour, watch the recording with Dr. Emily Ice. She walks the four-term contingency for sleep, the assessment menu, and the rest of her top-three behavioral sleep technologies in detail.