CONSENT + POWER Q&A

  • Coerced consent occurs when agreement is obtained through pressure, urgency, imbalance of power, or lack of meaningful alternatives. Consent given under threat, time pressure, or incomplete information is not clean consent.

  • Yes. Consent can be revoked or modified at any time, especially when new information emerges or when consent was provided under pressure.

  • No. Refusing consent is a lawful assertion of boundaries. Noncompliance implies obligation; consent implies choice.

  • No. Consent does not require justification. Explanation is optional, not required.

  • No. Written communication protects all parties by creating clarity and records. Resistance to documentation is often a red flag.

  • Power imbalance (e.g., parent vs. school, patient vs. hospital, employee vs. employer) increases the risk of coerced consent because refusal carries perceived consequences.

  • No. Standard practice does not override individual rights, needs, or consent boundaries.

  • A recommendation suggests an option. A requirement must be grounded in written policy or law. Asking for documentation clarifies the difference.

  • Yes. Processing speed, sensory load, and stress can impact decision-making. Needing time is an access need, not a failure.

  • Document the refusal in writing immediately and request clarification, remedy, or review. Seek advocacy if the issue persists.

  • No. Slowing a system is a regulation strategy that restores clarity, consent, and safety.

  • When:

    • consent refusal is ignored

    • retaliation occurs

    • services are removed

    • harm results from forced action

    Scripts help. Backup matters.

  • Most people are taught to comply, not consent.
    This FAQ exists to clarify rights, normalize boundaries, and interrupt coercive norms across systems.