Which version has approval?
Check the review and notice period for the current contract proposal.
The question
A mock contract change needs 3 distinct reviewer approvals for the exact published version. The version must also be public for at least 24 hours before release.
| Value | |
|---|---|
| Publication hour | 0 |
| Approvals for A | 3 |
| Scheduled release hour | 26 |
The clock measures hours from the first publication.
“Does the release plan meet both conditions?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Check the first version
What would you do here? Open the move you’d make.
Check only whether the scheduled release is after hour 24.
Tempting, but it misses something. Waiting long enough does not supply the three required approvals.
State that A meets both conditions on the supplied record.
The strong move. The time and approval conditions apply to the same proposal version.
See how a strong candidate says it
“Proposal A has three approvals. At hour 26 it has been public for 26 hours. It meets both conditions on this record.”
Why it works: The time and approval conditions apply to the same proposal version.
Step 2: Check what was approved
What would you do here? Open the move you’d make.
Match the version on the review and publication records.
The strong move. A familiar title does not show that the reviewers saw the current action.
Match the proposal title and the release ticket.
Tempting, but it misses something. A revision can keep the same title and ticket while changing the authorization rule.
See how a strong candidate says it
“I’d check that the published content, approval record and proposed action all refer to the same version.”
Why it works: A familiar title does not show that the reviewers saw the current action.
Step 3: Recheck the current version
Proposal B was published at hour 18 and supersedes A. It changes an authorization rule. All 3 existing approvals refer to A.
What would you do here? Open the move you’d make.
Keep B in review and check its own time and approvals.
The strong move. B has its own publication time and needs approvals for its own content.
Carry the wait and three approvals from A over to B.
Tempting, but it misses something. The three reviews and the first publication apply to A. The current proposal is B.
See how a strong candidate says it
“At hour 26, B has waited 8 hours and has no eligible approvals. The earliest time is hour 42, 16 hours after the schedule, if three reviewers approve B by then.”
Why it works: B has its own publication time and needs approvals for its own content.
Step 4: Give the review decision
What would you do here? Open the move you’d make.
Treat hour 42 as an unconditional release time.
Tempting, but it misses something. Hour 42 meets the wait condition. The three approvals for B are still required.
Confirm the elapsed time and three fresh approvals for B.
The strong move. The owner can see both conditions that prevent the scheduled release.
See how a strong candidate says it
“I’d keep B in review. I’d tell the governance owner which version is current, which approvals are missing and when the notice condition can be met.”
Why it works: The owner can see both conditions that prevent the scheduled release.
The answer, in short
- Decision
- Keep proposal B in review.
- Because
- At hour 26 the current proposal has waited 8 hours and has zero eligible approvals.
- What would change it
- Three approvals for B and at least 24 hours since its own publication would satisfy the brief.
Common traps
- Using a title as the proposal version.
- Treating the notice period as approval.
Check your answer
- I checked both initial conditions.
- I matched approval to version.
- I recalculated the new notice period.
- I named the missing approvals.
Last reviewed Nov 11, 2026