Illustrative idea · PURCHASING
Require two approvals for purchase requests
Route a purchase request through two independent reviewers before the requester proceeds.
Get two independent approvals before making a change.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
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.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
Proposed changeA 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.”
Work through the request.
Clear tasks, with review where it matters.
- Submit a change request
- Open a review period
- Invite two reviewers
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.
What this workflow could do
Collects change requests, asks two different reviewers to decide, and records the outcome.
Review points proposed in this idea
The requester cannot approve their own request, and one reviewer cannot count twice. Approval does not make the record change automatically.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
The requester identifies the record, describes the proposed change, and explains why it is needed.
-
Mark the request as pending with its deadline and the number of distinct approvals required.
-
Give each reviewer the request details so they can consider it and respond independently.
-
Keep each reviewer’s approval or decline, including responses that cannot be accepted.
-
Do not accept the requester’s own approval or count a second response from the same reviewer as another approval.
-
Approve only when two different reviewers approve before the deadline. Otherwise, close without approval and show the requester the outcome.
-
After approval, the requester or authorized owner makes the final record change.
Step 1 of 7
Submit a change request
The requester identifies the record, describes the proposed change, and explains why it is needed.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Choose eligible reviewers
List the people who may review requests and confirm how they will submit their decisions.
- 02
Set the review rules
Choose the review period and require approval from two different reviewers.
- 03
Prepare request and decision messages
Make sure requesters can describe the change and reviewers can see enough detail to decide.
- 04
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.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation