ambacti
Explore workflows

CHANGE CONTROL · Workflow idea

Get two independent approvals before making a change.

A requester describes the change they want. Two different reviewers consider the request and submit their decisions. Once approved, an authorized owner makes the final change.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
Proposed change
Produces
The request is approved only after two distinct reviewers approve it within the review period. Otherwise, it closes without approval. The final record change is a separate action.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A request to update a shared business record

“The requester identifies the record, describes the proposed change, and explains why it is needed. The request stays pending while two different reviewers decide.”
An example request · Make it specific to your team.

02 / The work

7 tasks.
One useful outcome.

Collects change requests, asks two different reviewers to decide, and records the outcome.

  1. Submit a change request

    The requester identifies the record, describes the proposed change, and explains why it is needed.

  2. Open a review period

    Mark the request as pending with its deadline and the number of distinct approvals required.

  3. Invite two reviewers

    Give each reviewer the request details so they can consider it and respond independently.

  4. Record each decision

    Keep each reviewer’s approval or decline, including responses that cannot be accepted.

  5. Check reviewer independence

    Do not accept the requester’s own approval or count a second response from the same reviewer as another approval.

  6. Close the request with an outcome

    Approve only when two different reviewers approve before the deadline. Otherwise, close without approval and show the requester the outcome.

  7. Make the approved change separately

    After approval, the requester or authorized owner makes the final record change.

03 / The result

Something useful.
Something to build on.

The request is approved only after two distinct reviewers approve it within the review period. Otherwise, it closes without approval. The final record change is a separate action.

AmbactiWorkflow folio · 7 steps

Require two approvals for record changes

Reviews & approvals · Example outcome

The handoff

The request is approved only after two distinct reviewers approve it within the review period. Otherwise, it closes without approval. The final record change is a separate action.

Keep in mind

The requester cannot approve their own request, and one reviewer cannot count twice. Approval does not make the record change automatically.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Choose eligible reviewers

List the people who may review requests and confirm how they will submit their decisions.

Set the review rules

Choose the review period and require approval from two different reviewers.

Prepare request and decision messages

Make sure requesters can describe the change and reviewers can see enough detail to decide.

Check the approval cases

Test two valid approvals, a requester attempting to approve, a repeated reviewer, a decline, and a request that reaches its deadline.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗