Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Path
  • CDC/RDC Glossary
  • CDC/RDC Metrics Reference
  • CDC/RDC Interview Prep
  • CDC/RDC Signoff Cheatsheet
  • Clock Domains and Failure Modes8
  • Metastability and Synchronizers16
  • CDC Protocols and Handshakes16
  • Reconvergence and Gray Coding16
  • Reset Domain Crossing16
  • Architecture and Design Rules16
  • CDC Signoff Methodology24
    • CDC Tool Flow
    • CDC Constraints and STA
    • CDC Waiver Policy
      • When to Waive
      • Evidence for a Waiver
      • Waiver Review and Expiry
      • Waiver Anti-Patterns
    • CDC Review Gate
    • CDC Signoff Dashboard
    • Formal and Simulation CDC Verification
  • RDC Signoff16
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹CDC Waiver Policy
  1. Topics
  2. CDC & RDC
  3. CDC Signoff Methodology
  4. CDC Waiver Policy
  5. Waiver Review and Expiry

Part 7 · CDC Signoff Methodology · Advanced

Waiver Review and Expiry

Who reviews waivers, how scope is limited, and why every waiver is tied to a revision and expires on change.

On this page

    Evidence without review is filing, not signoff. Waivers are reviewed by people with the standing to reject them, scoped so narrowly that reuse requires a new review, and tied to a design revision so that change re-opens them automatically. This lesson defines the reviewers, the scope rules, and the expiry machinery.

    Who reviews

    Reviewer

    Role in the review

    Can approve alone?

    Design owner

    Confirms the protocol argument matches the real design intent

    No

    Verification or signoff owner

    Confirms the evidence actually demonstrates the argument

    No

    Both together

    Joint approval records that intent and evidence agree

    Yes — this is the only approval

    The design owner cannot approve alone because they are grading their own assumption; the signoff owner cannot approve alone because they cannot confirm intent. Joint approval is the whole point of the meeting.

    Scope limits

    • One waiver covers one finding on one instance: never a class, a module, or a bus en bloc.

    • The waiver names the design revision it was reviewed against; a new revision re-opens it for confirmation, not automatic renewal.

    • The waiver names the change that kills it — typically any RTL, constraint, or clocking change touching the crossing — so expiry is a decision made at review time, not in a crisis.

    • Mode-limited waivers (test-only, debug-only) name the mode and the mechanism that enforces it.

    Expiry on change

    Expiry is administrative, not personal: when the named revision is superseded, the waiver returns to the open list until someone confirms the argument still holds on the new revision. This is deliberately annoying — the friction is what stops waivers surviving changes they were never reviewed against. The dashboard tracks waiver age and revision currency so stale waivers are visible before they are dangerous.

    Common pitfall

    Auto-renewing all waivers onto the next revision “because nothing relevant changed” skips the very check that would confirm nothing relevant changed. Renewal is a review outcome, never a default.

    Check yourself A waiver approved on revision C is carried onto revision D, where the crossing moved hierarchy. What went wrong procedurally?

    The waiver was scoped to revision C and should have re-opened on the change. Carrying it forward treated a revision-tied permission as permanent.

    Check yourself Why must design and signoff owners approve jointly?

    Design confirms the argument matches intent; signoff confirms the evidence demonstrates the argument. Either alone leaves one half of the claim unchecked.

    Related topics

    • Evidence for a Waiver

    • Waiver Anti-Patterns

    • Trend and Regression

    Previous

    105 / 179

    Next: Waiver Anti-Patterns

    Up next

    Up nextWaiver Anti-Patterns

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • When to Waive