The Traffic Light Code in BDSM: Clearly Ambiguous.

Dan Apus Monoceros
Jun 13
8 min read

Everyone knows it: the traffic light code — Green, Yellow, Red — is considered the most widely used communication tool in BDSM and is described in many works as the gold standard. At first glance it seems trivial. In practice, however, it is a source of errors and problems that I want to highlight here. I personally know three completely contradictory versions and have heard of many more variations and interpretations. So it's time to clear things up. In addition, I'd like to share some further information and add-ons about the traffic light code in this article, and also make a case for alternative methods of symbolic communication that are more unambiguous.

There Is No Single Traffic Light Code…

... instead, there are countless variations, and depending on the region of the world, the play community, the age group, and so on, everyone is absolutely certain that their version is the correct one ;)

Which versions do I know? — I'll list the 3 most important ones in the order I encountered them.

Variant 1: Hold Logic

The first variant is the one I also first encountered.

Green: More please, we are far from the comfort zone.
Yellow: Comfort zone without challenges. I can stay here for a long time.
Red: This is the limit. I won't be able to take more, please don't go further. BUT no abort.
Safeword: immediate abort.

This interpretation is closest to the actual traffic light logic. It describes a kind of line — the sub's limit — that must not be crossed. Red therefore means the action must stop at this line. If it were to be crossed, the safeword would be called.

For many who use this interpretation, "Red" is the sweet spot — the point where exactly the right amount is happening — and they want to remain there as long as possible. For these players, it is very much about that love-hate relationship and the challenge that gives them strength. For some, however, this may already be too much, and they prefer to stay away from that limit.

I encountered this version with many older players and it was relatively widespread there. However, it is poorly documented and appears in only a few guides.

The actual emergency signal is a separate code word, such as Mayday or Fridge. Red is therefore not a safeword here.

This variant is particularly compelling because one can slowly approach a kind of maximum. Sub and Dom can approach gradually and then linger at the right point to get the most out of the session. However, if the line were crossed, the safeword would be next and the session would have to be aborted.

Variant 2: Stop Logic

Variant 2 looks different. Here, "Red" is already the safeword and must lead to immediate abort with subsequent aftercare. Accordingly, the logic is as follows:

Green: Everything is fine, continue as before (usually upon request).
Yellow: Limit in sight, slow down, adjust, but the scene continues.
Red: Immediate abort, aftercare begins.
NO separate safeword

This interpretation is currently most widespread among young people. It comes primarily from the online community and is often — but incorrectly — presented as the established standard.

"Fun" Fact or Warning: It is alarming that AIs present this variant as the only one. Many influencers who have their texts generated entirely by AIs copy this uncritically or jump on the bandwagon. At the same time — when you look at the sources more closely — such information comes from sources that are unreadable to humans, for example where black text is written on a black background.

For users of this code, "green" is the area in which play is allowed, "yellow" is practically the limit, and "red" is the safeword. The abort then comes with announcement... like a safeword in two phases. This variant is particularly strong when one regularly plays above the green comfort zone in order to come back to it. However, since "green" here is not a call for "more" but has already been defined as the perfect zone, the sub has little opportunity to invite the dom to more intense play. Also missing from this style of play is a clear, unambiguous safeword, since red is not a safeword for everyone but — as explained in V1 — merely marks the limit zone.

Intermediate Conclusion: Disasters Are Built In

If we look at just these two versions, it quickly becomes clear that disaster is built in. They approach the limit from different sides. Using V2 compared to V1 represents the exact opposite in a certain sense. V1 encourages others to push harder, up to the sweet spot, and V2 encourages others to do less, i.e. to return to the sweet spot in the green zone.

In practice, the following situations could then arise:

One partner plays V1 and the other V2. If the V1 player in the sub role says the word 'yellow,' they would be indicating that things are slowly coming to the right spot. But if the other person is using V2, they would assume that we're approaching the limit and tend to do less. With the signal word 'red,' it would be even more extreme — the V1 person would be expressing 'perfect, stay here,' while the V2 person would abort. A perfect scene would be ruined.

That said, this is still the harmless variant. If we imagine it the other way around, the sub using V2 would experience a severe violation of consent and an ignored safeword, with all conceivable consequences. Anyone here who only waits for the safeword and doesn't read empathetically or uses clear language alongside the traffic light code will quickly become an unwitting perpetrator.

Both sides are disappointing. If you forgot to clearly communicate the color code beforehand, you should always assume that 'yellow' is already a first signal for 'less.' Better a ruined session than a traumatic experience ;)

Variant 3: Control Logic

There are many other versions that fall between the two extremes. The variant presented here is the one I use for my own play parties. It places the sweet spot neither at the upper nor the lower end of the traffic light, but in the middle, and works as follows:

Green: More, harder, more intense.
Yellow: Just like this, please keep going.
Red: Less, softer.
Safeword: immediate abort.

This approach uses the traffic light as a control mechanism rather than a state reflection. V1 and V2 normally describe the sub's state in relation to the boundary — how far away from it we are. In V3, the traffic light code communicates the sub's desire for change.

It should come as no surprise to either side, but it does invite both sides to move a little and rethink. This variant is also used at many events and is likewise widespread.

Play primarily takes place in the 'yellow' zone, and 'green' = 'more' or 'red' = 'less' can be used to communicate clearly and explicitly. A safeword would operate independently of the traffic light code. This means the safeword would be clearly recognizable, and also two-stage — you would first say 'red' and then the safeword.

From lived experience, this is a very well-functioning variant that requires no compromises and overcomes typical problems.

Additional Colors

None of the variants mentioned is perfect, and there are always interesting approaches to compensate for their limitations. Additional colors have become established, for example. They make communication more nuanced, but at the same time increase complexity — and therefore the need for clarification before play.

Orange is most commonly used as an intermediate step between yellow and red. Many people who use 'orange' have their own logic, which often works something like this:

Green: More, harder, more intense.
Yellow: We've reached a good plateau.
Orange: Sweet spot between too much and too little.
Red: Less, otherwise it can quickly become too much.
Safeword: immediate abort.

But here too, there are many people who define this differently.

Blue is used very creatively as a signal word and isn't part of the traffic light at all. One variant I've heard in my workshops (and now use myself) is that blue is used for off-topic matters — for example, 'my nose itches, can you scratch it for me,' 'my foot has fallen asleep,' 'I need a sip of water.' Blue briefly steps outside the scene dynamic without ending it, and allows for a pragmatic intervention in reality that has nothing to do with consent, pain level, or control.

Another use I found online at LARP-Wiki: here Blue is a 'boostword' in the sense of 'more, harder, more intense,' as an additional scale level above Green (which also makes a lot of sense for V2 and overcomes its problem in this case).

The same applies here: anyone using additional colors must clarify their meaning beforehand — otherwise the conflicts that arise with just three colors are amplified.

Pink or Red as a delayed safeword. Some subs use the safeword reflexively too early — the mind wants to stop, but the body still has reserves — and if they had continued for just 10 more seconds, the mind would have understood that it was bearable. Those who recognize this in themselves and have explicitly agreed on it together can establish a brief run-on rule: after a stop signal, the top continues at the same level for approximately 15 seconds, and the sub has the opportunity within that window to withdraw the signal if they realize they can manage after all. Important: this is an extension for experienced couples, based on explicit mutual agreement. This must be explicitly agreed upon in advance. You can also assign the signal color pink to this "I want to try a little longer."

The Most Important Point: Most People Don't Question It

Precisely because the traffic light code is so well-known, most people don't question it. The traffic light code has achieved the status of a cultural commonplace — 'traffic lights, everyone knows that' — and that is exactly what makes it dangerous. The knee-jerk reaction of 'that's obviously clear' is the actual blind spot: three compatible-sounding systems run under the same name, and as long as this isn't addressed, each side assumes their own interpretation is the obvious one.

Practical Consequences

There is no single traffic light code. Never assume that when you play with someone, you have the same understanding of the code. 'We use the traffic light code!?' is not an agreement — it's an opportunity to clarify it. For example, respond with: 'Sure. For me, red means X, yellow Y, green Z — does that work?'
Always use an unambiguous, independent safeword. Even if the traffic light communication seems to fit, a clear stop word helps and protects both sides. Red should not be the safeword, as it may already carry a different meaning for others. Also consider non-verbal safewords.
At events, there are usually binding house rules for everyone. Each event should designate one variant as valid and make the emergency signal binding for all. The event's emergency signal must not be redefined by individual play groups — this also affects third-party intervention, whether it's an awareness team or bystanders who assume they've just heard an emergency signal.
In an unclear situation, use the most restrictive interpretation. In spontaneous encounters or with new partners, 'red' should always be treated as a stop, and 'yellow' should lead to a reduction in play. An unnecessarily ended scene is repairable; an ignored withdrawal of consent often is not.
Use alternatives to the traffic light. Instead of the traffic light code, which carries very different meanings within the community, you can also use a different code that is less prone to confusion. You can say 'more,' 'good,' and 'less,' use thumbs up, sideways, or down, or use a numerical system such as a pain scale.
Clear words instead of a code. Not every form of communication needs to be coded. 'Please slower,' 'more of that,' 'short pause' work just as well in many situations — especially where the scene doesn't rely on strict role-play language to begin with.

Conclusion

The traffic light code is not the standard it is often advertised as. As long as this isn't acknowledged, every variant carries the potential for conflict — from harmless misunderstandings to genuine boundary violations where both sides have applied their own code 'correctly.'

The most common mistake is not using the wrong code — it's assuming the code is unambiguous. The takeaway: don't abandon it, but treat it like any other tool: learn to use it properly and find the right settings.