Recertification clock
Nedir Recertification clock?
Bu terim şu anda yalnızca İngilizce olarak sunulmaktadır.
A recertification clock is the review countdown that starts the moment a compliance registration reaches `active` and counts down to its next required re-attestation. The clock gives the verdict operators read to know whether their filing is current or past due: current, due soon, or overdue. For registerable frameworks like the FCC Robocall Mitigation Database (RMD), the interval is configurable per organization (a default of 365 days, up to 3650), and some registries restart their clock on every successful certification or re-vet.
More detail
The verdict moves with the deadline, not with the calendar: on the RMD, `current` reads until ~30 days from the review date, then flips to `due_soon`, then to `overdue` once the date passes (`overdue: true` on the read response), and back to `current` after a successful remediation-and-submit cycle restarts the clock.
The clock sits beside the update-window cadence, not replaces it: the frecert_interval_days set the annual review deadline, while the regulatory update window (for FCC filings, 10 business days) still applies to any change you make — plan both, because a current recert verdict does not excuse a stale address or DBA change.
Some frameworks recompute their clock every time a certification lands: the RMD interval resets on each certification, and every successful re-vet on a 10DLC pattern resets the 30-day cooling clock for the sender-pool spread alert it triggered, so coverage recertification cadence differs by framework.
Sık sorulan sorular
- Does every compliance framework carry a recertification clock?
- No — it applies to registrations that require re-attestation rather than one-time filings. The RMD and attestation frameworks where Orbit returns `recertification` verdicts run on one; for frameworks that don't, check the registry's endpoint semantics before relying on a 'never overdue' state.
- If I re-certify early, do I get a fresh clock?
- Yes for frameworks like the RMD — every successful certification or remediation cycle restarts the deadline from the certification timestamp, so an early re-attestation pushes your review date out. A `due_soon` state after an early re-cert goes back to `current` again.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.