> ## Documentation Index > Fetch the complete documentation index at: https://docs.compensable.live/llms.txt > Use this file to discover all available pages before exploring further. # Compliance overview > How compliance checks run in the calling path itself, what's enforced, and where the firm stays in control. Compensable runs its compliance checks inside the calling path, not beside it. Before an outbound call or text goes out, and again while a call is live, the platform checks the same policies your firm configured: consent, quiet hours, opt-outs, and the rest. It checks them in code, not in a document someone has to remember to follow. Every check's outcome, allowed or denied, is written to your organization's audit trail. Your firm owns the policies. You set the recording policy, the consent basis your campaigns require, and (where the platform allows it) the calling-hours defaults. Compensable enforces what you've configured; it does not decide your compliance program for you. ## What's enforced in the calling path * **Consent requirements.** Every outbound touch checks a recorded consent attestation before it goes out. A missing or insufficient basis blocks the touch. * **Quiet hours.** Outbound calls, texts, and voicemail drops are checked against the lead's local time, using whichever is stricter: the federal calling window or the lead's state statute. * **Opt-outs and Do-Not-Call.** A STOP reply, a DNC flag, or an opt-out already on file stops every future touch across every channel, immediately. * **Frequency caps.** Rolling per-channel and cross-channel limits stop a lead from being contacted too often in a given window. * **Recording consent.** Whether a call is recorded, and whether an in-call notice is required, follows the recording policy your organization has set, including two-party-consent states. * **AI disclosure and all-party-consent tracking.** Each jurisdiction's disclosure and consent requirements are tracked against the lead's location, and calls that need closer review are flagged for a human rather than auto-qualified. * **Audit trail.** Every check above, and every admin override of one, is appended to a tamper-evident, per-call record you can verify on demand. Two of these, quiet hours and frequency caps, can be loosened, but only by an organization admin taking an explicit, counsel-attested action that records who accepted the liability and why. Consent, opt-out, DNC, and destination checks are not configurable by anyone. No admin action turns them off. See [Consent and quiet hours](/guides/compliance/consent-and-quiet-hours) for how that override works. Compensable is not a law firm and this documentation is not legal advice. The platform gives you governance controls and an evidentiary record; your firm is still responsible for its own compliance program, including obtaining and documenting the consent your calling and texting activity requires under the TCPA and applicable state law. ## Where to go next * [Consent and quiet hours](/guides/compliance/consent-and-quiet-hours): how outbound touches are gated, and what happens when one is blocked. * [Call recording](/guides/compliance/recording): when calls are recorded, and how that decision is made. * [Data and erasure](/guides/compliance/data-and-erasure): what's kept about a caller or lead, and how to request deletion.