Negotiating from the Bottom

CNC bottom negotiation is sometimes misunderstood as simply agreeing to what a top proposes. This misunderstanding is worth correcting explicitly: the CNC Bottom's role in negotiation is active, specific, and essential to the quality of what gets built. The bottom has knowledge that the top cannot have without their input: what the bottom needs from the experience, what their specific triggers and limits are, what their processing patterns look like, and what they need on the other side. This knowledge is not optional; it is the material the consent architecture is built from.

A CNC Bottom who enters negotiation with a clear sense of what they want from the scenario, what they want to remain outside it, and what safety structure they need is contributing meaningfully to a planning process that will produce a better and safer scene. A CNC Bottom who waits for the top to propose everything and then agrees or declines is abdicating a responsibility that belongs to them as well.

Being active in negotiation does not mean trying to control every element of the scenario; the appeal of CNC for many bottoms includes a degree of surprise and uncertainty within negotiated parameters. What active negotiation means is taking responsibility for establishing those parameters thoroughly, communicating the self-knowledge that makes them specific, and ensuring that the safety structure is robust before any scene begins.

Thorough CNC negotiation from the bottom's side covers several distinct areas. The scenario itself: what narrative framework you are agreeing to, what activities it may include, what it may not include, what emotional states you expect it to produce, and what its duration and setting will be. Your triggers and limits: the specific content, actions, or conditions you are excluding from the scenario, and the less obvious triggers you need the top to understand even if they might seem unrelated to the broad scenario type.

The stop signal is one of the most important elements the bottom needs to specify and confirm. The CNC Bottom must be certain that the stop signal is absolutely clear, distinct from anything that might appear in the scenario's fiction, and physically accessible in any condition the scenario might produce. If the scenario involves physical restraint, can you still produce the stop signal? If you are likely to reach a state of intense disorientation, is the stop signal simple enough that it remains accessible in that state? These questions need honest answers before the scene begins.

Aftercare needs are something the bottom should specify explicitly rather than leaving to the top's assumptions. What do you need immediately after the scene ends? What might you need in the following day or two if drop arrives? Who else should know you might need support? These specifications should be part of the negotiation record, not an improvisation after the scene.

Writing down what you have negotiated serves the bottom's interests in several ways. It ensures that both parties have the same detailed understanding of what has been agreed; it provides a reference to review before the scene in a moment of clarity rather than in the emotional charge of scene preparation; and it creates a record that can be updated as your understanding of yourself develops and as the dynamic with a specific partner evolves.

Some CNC Bottoms maintain documentation not only as a record of specific agreements but as a living document of their developing practice: what scenarios they have explored, what they noticed, what they would adjust, and how their self-knowledge has evolved. This kind of documentation is a form of reflective practice that makes subsequent negotiation richer and more precise.

The bottom should be involved in the creation of the written document, not simply receive a document the top has created and sign off on it. If the document is to reflect the bottom's genuine self-knowledge and current needs, the bottom needs to have contributed to its content actively. Some CNC practitioners write sections of their negotiation documents collaboratively in real time during the negotiation conversation; others draft sections separately and then combine them; others work from structured templates. Any approach that results in a document that genuinely reflects both parties' current understanding is serving its purpose.

The stop signal in CNC deserves special attention from the bottom's perspective because it is the bottom's primary real-time safety tool in a scenario specifically designed to simulate its absence. The choice of stop signal is consequently one of the most important decisions in CNC negotiation, and it should be made with full attention rather than as an afterthought.

Physical stop signals are preferred by many experienced CNC practitioners because they do not require verbal production and remain accessible even when language is difficult or when verbalization is part of the scenario's fiction. Dropping a held object, a specific number of taps on a surface or the top's body, or a specific physical position change are all physical stop signals that can communicate clearly. The specific signal chosen should be something you can produce in the positions and states the scenario is likely to involve.

Practicing the stop signal before the scene is not a formality; it is how both parties confirm that the signal is actually clear and accessible under conditions resembling those of the scene. Some CNC practitioners practice their stop signals explicitly as part of pre-scene preparation, verifying that the signal produces the intended response from the top and that the bottom can produce it reliably. This practice should happen before every scene rather than being considered a one-time exercise.