iyedy docs, home
FR Lire en françaisOpen iyedy (opens in a new tab)

Record a decision

A decision says what was agreed about a diagram and why. iyedy records it in the governance register, pinned to the saved version it was taken on, with its conditions, their owners and due dates. The checks then tell you when a condition is late or the design moved on.

On this page
Guide · 5 minAll plansUpdated 29 Oct 2026

Before you start

  • Editor or owner of the workspace: only editors and owners record decisions. A contributor can mark a condition they own as met.
  • The diagram open, saved in the version the decision is about. A decision pins the saved model at the moment you record it.

Record a decision on a diagram

  1. Open the dialog

    With the Claims Platform open, choose Record review decision… in the Governance menu. The dialog says which version it pins, for example model version 14 now.

  2. Choose the outcome

    Pick one: Approve, Approve with conditions, Reject or Defer. Give it a Title (Claims API calls Fraud Scoring synchronously) and, if you like, the Forum that took it (Review board, design authority…).

  3. Add the conditions

    For an approval with conditions, select Add condition for each one: what must be done, the Owner of the condition and a Due date. An approval with conditions needs at least one.

  4. Write why, and record it

    Under Rationale and notes, write the reasons and the options you set aside. Tick Save a named version for this decision to mark the version in the history. Select Record decision.

    The register lists the decision with its key, such as RD-0001, its outcome and its open conditions (1 of 1 condition open). The Standards register shows it as a decision.

Record a decision from a finding

When you keep a finding on purpose, record why as a decision. On the finding, in the review, select Create a decision (MADR). The form is filled from the finding, in the MADR layout:

  • Title, for example PERF-07: intended deviation on Claims API;
  • Context and problem: what the rule reports and why it matters;
  • Options considered: apply the fix, or keep the deviation with this decision;
  • Decision and why, which you write, and Consequences.

Select Record the decision. It goes to the governance register, linked to the rule and the version.

Follow its conditions

A condition is Open, Met or Waived. Its owner marks it met; an editor or owner can waive it with a note. Two checks watch decisions:

Rule Fires when
GOV-03 Overdue condition A condition is still open past its due date.
GOV-04 Changed since the review decision The diagram changed after the version the decision pinned: The model has changed since this decision.

Change or retire a decision

A recorded decision is not edited away. Open it in the Governance register and set it to Superseded when a newer decision replaces it, or Withdrawn when it no longer stands. Recording a decision never changes the diagram itself.

If it doesn't work

“Only editors and owners record decisions.”

Your role on this workspace does not record decisions. Ask an editor or an owner, or ask for the role: see Roles and permissions.

“Open a diagram from the library to record a decision on it”

A decision is pinned to a diagram version. Open the diagram from your library first, then record it.

GOV-04 appears right after a decision

The diagram was edited after the version the decision pinned. Submit the changes for review, or record a new decision on this version.

More: Standards, Review and sign off a version.

Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.

What went wrong?

Don't write personal data.

Navigation

iyedy docs, home
Lire en françaisOpen iyedy

↑ ↓ moveEnter openCtrl Enter new tabSearching English docs ·