Re-assert evidence before it lapses

Steps

1. On the Control center, the decision queue lists each lapsed re-assertion, with the person who decides.

2. Open the system’s record, for example Claims routing. Its banner says when the re-assertion lapsed, and that the approval stands.

3. Under Re-assertion, choose Re-assert the entry.

4. In Re-assertion, check the entry against the declarations since the last re-assertion and the last gate record. Attach a file if you have one, such as a monitoring report or a re-test.

5. Say what it rests on: the declarations on the chain and any file, or your word only, which the record then says. Write what you checked and, if it is late, why it lapsed. Confirm that every typed field is still true, and sign on Re-assertion.

Good to know

• Each re-assertion is a signed record and resets the interval.
• If you cannot confirm the entry, escalate it. The CRO, as accountable executive, decides, and nothing is re-asserted meanwhile.
• The register owner sets the interval in days. A new entry starts at the tenant interval, never above its tier’s maximum. See Re-assertion interval.
• The owner gets a reminder email that opens the re-assertion.

Where in the product

• Claims routing

These open the prototype, on fictional institutions. People are shown as roles.

Related guides

• Sign a gate with a reason

  Read the gate record and its evidence, then sign, return or reject it with a reason, as the named approver.

• Record a validation (G2)

  Attach the report, record the findings, what was not examined and any dissent, then sign G2.

• Build and share an evidence pack

  Choose the systems and dates, sign the pack with a cover note, and share it with an examiner key.