Consent Is Not a One-Time Event: What Real Agreement Looks Like at Work

Let's start with what this post is not about.

In most workplaces, the word consent lives in compliance training. It belongs to HR, to legal, to the frameworks organizations build to protect employees from harm. That work matters. But it has also narrowed the word to the point where many people hesitate to use it outside that specific context — which is a loss, because consent as a communication practice is something else entirely.

Consent as a communication practice is the ongoing, explicit negotiation of what someone is actually agreeing to — and the conditions under which that agreement holds. It is less a legal concept than a relational one. And in the context of how work actually gets done, it is almost entirely absent from how most organizations operate.

That absence has a cost.

What We Usually Do Instead

The default in most professional environments is assumption. A task is assigned; agreement is implied by the absence of objection. A project scope expands; the original "yes" is treated as covering the new territory. A deadline moves; the person doing the work absorbs the shift without anyone checking whether absorption is actually possible.

This is not malicious. It is the shape that efficiency takes when communication is compressed. But from a nervous system standpoint, it creates a persistent low-grade problem.

Stephen Porges' Polyvagal Theory describes the nervous system as continuously scanning the environment for signals of safety or threat — a process he calls neuroception. One of the clearest safety signals a nervous system can receive is the experience of having agency: the sense that you have genuine input into what is being asked of you and a real mechanism for saying so when something changes. When that agency is absent — when agreement is assumed rather than invited — the nervous system registers the gap, even when the person consciously accepts the situation without complaint.

Over time, that gap accumulates. People become less forthcoming. They hedge. They say yes when they mean "yes, but I'm not sure how." They stop raising problems early because the environment has not established that raising problems is safe. The work still gets done, or most of it does, but the communication infrastructure underneath it becomes brittle.

Genuine consent — not as a legal threshold, but as a communication practice — is what repairs that brittleness.

Consent Is a Negotiation, Not a Signature

The most useful reframe is this: consent is not a moment. It is a process.

In high-stakes fields that require real-time coordination under pressure — emergency medicine, aviation, elite athletic performance — teams use explicit negotiation protocols before engagement: what are we doing, what does each person need, what are the conditions under which we pause or change course, and how will we signal that? These conversations happen not because participants distrust each other but because trust is built through explicit agreement, not assumed from it.

The same logic applies to how work gets assigned and executed in organizations.

A genuine consent practice in the workplace has three components, and they map onto the beginning, middle, and end of any significant piece of work.

‍Before the work begins: negotiation. This is the conversation that establishes not just what is being asked, but whether the person being asked has the capacity, clarity, and resources to do it. It is where parameters get named — scope, timeline, delivery requirements, and the procedure for getting more information or support as needed. It is also where the person receiving the assignment gets to ask, honestly, whether this is something they can take on and under what conditions.

This is not a lengthy or formal process. It is often a five-minute conversation that most leaders skip because it feels like overhead. The irony is that skipping it consistently creates far more overhead downstream in the form of errors, delays, misaligned outputs, and the slow erosion of trust.

‍During the work: renegotiation. This is the part almost no one builds in deliberately, and it is where most consent failures in organizations actually happen.

Scope changes. Priorities shift. The person doing the work discovers that the task is different than it appeared at the outset. If there is no established mechanism for raising those changes — no low-friction way to say "something has shifted and I need to renegotiate" — then people absorb the change silently and the nervous system carries the load. The original agreement no longer reflects the actual situation, but no one has named that.

Building in renegotiation means establishing, explicitly, that it is both possible and welcome to raise a change in conditions without penalty. This is a leadership responsibility. The person with less organizational power in a dynamic will not create this mechanism on their own — the risk of doing so feels too high. The person with more power has to make the opening.

‍After the work is complete: repair and acknowledgment. High-pressure work has a physiological cost. A sprint toward a deadline, a difficult client presentation, a project that required sustained effort over an extended period — these leave a mark on the nervous system, even when the outcome is good.

Most organizations move immediately to the next thing. What this communicates, unintentionally, is that the person who did the work is valued for the output, not the effort. Over time, that message degrades motivation and erodes the sense that the organization is a safe place to expend significant energy.

A brief, genuine acknowledgment after demanding work — not a performance review, not a metric, but a human recognition that something was asked and given — is the closing of a loop that the nervous system actually needs. It signals that the relationship that sustained the work is still intact.

When You Are Not the One Holding the Authority

A consent practice looks different depending on where you sit in the exchange — and if you are not the one with organizational authority, the work is less about creating conditions for others and more about understanding your own responses well enough to participate honestly.

The nervous system has a tendency, under social pressure, to front-load agreeableness. When someone with authority over your work makes a request, the body often resolves toward yes before the mind has fully assessed whether yes is accurate. This is not weakness or poor judgment — it is the nervous system doing what it is built to do in the presence of a perceived power differential: minimize friction to preserve the relationship. The problem is that a yes produced by that calculus is not a genuine agreement. It is a social maneuver, and it tends to generate the very problems — overcommitment, silent absorption, late-surfacing errors — that erode trust over time.

The practice here begins not with what you say, but with what you notice. Before you respond to a significant ask, there is value in a brief internal inventory: Do I actually understand what is being requested? Do I have a realistic picture of what saying yes would require? Is there something I need to know before I can answer honestly? These are not stalling questions. They are the foundation of a response that the other person can actually rely on.

From there, the quality of your participation depends on your willingness to bring concrete information into the conversation rather than managing impressions. An organization's consent culture — the degree to which renegotiation is genuinely safe — is partly a leadership responsibility, but it is also built incrementally by individuals who are willing to be specific when something is not working. Specificity is what makes a concern actionable rather than atmospheric. It also, perhaps counterintuitively, tends to read as competence: the person who can name exactly what they need and why is demonstrating mastery of their own workload, not fragility.

What this requires, ultimately, is a willingness to treat your own honest assessment as information the other person needs — rather than something to be managed or softened into palatability. That is a form of professional trust. And like most forms of trust, it tends to generate more of itself when offered.

The Trust That Comes After

None of this is complicated in principle. The difficulty is cultural. Most organizations have implicit norms that treat asking for clarity as inefficiency, pushing back as insubordination, and raising problems mid-project as failure. Those norms produce the opposite of what they intend — not a leaner, faster operation, but one where problems surface late, where people hold back their actual assessment of a situation, and where the nervous system learns that honesty is not safe.

A genuine consent practice — one where agreement is invited rather than assumed, where renegotiation is possible without penalty, and where the effort behind work is acknowledged — builds something that no onboarding program or team-building exercise can manufacture: the experience of safety in the relationship between the organization and the people who do its work.

When the nervous system registers that safety, communication opens. People say what is actually true. Problems surface when they are still small. The work that results is not just better executed — it is built on a foundation that holds under pressure.

That is what real agreement looks like. And it begins with treating consent as a practice rather than a formality.

‍

‍Want to look at the communication infrastructure in your own organization — where it holds and where it doesn't? Schedule a free consultation and we'll start there.

‍

References

‍

1. Porges, S. W. (2011). The Polyvagal Theory: Neurophysiological Foundations of Emotions, Attachment, Communication, and Self-Regulation. W. W. Norton & Company.
2. Porges, S. W. (2017). The Pocket Guide to the Polyvagal Theory: The Transformative Power of Feeling Safe. W. W. Norton & Company.
3. Brown, B. (2018). Dare to Lead: Brave Work, Tough Conversations, Whole Hearts. Random House.

‍

‍