Back to all articlesAutomation design

Resume a workflow after human review without using stale approval

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

All scenarios, names, identifiers, amounts, quantities, dates, and times in this article are hypothetical. The workflow controls described are recommended operating designs, not claims about existing product capabilities.

A reviewer approves an offer at noon. Before the workflow resumes, someone changes the quantity or the proposed delivery date becomes unavailable. A workflow that remembers only “approved” can now carry out something nobody actually reviewed.

To resume safely, bind approval to a specific proposal and its relevant facts. At resumption, compare the current proposal with the approved snapshot, check expiry and current eligibility, and establish whether the intended action has already happened. Continue only if those conditions hold. Otherwise, return to the appropriate check or decision.

The operating question is not just “Did someone approve this?” It is “Does this approval still apply to this action, under these facts, now?”

1. Define exactly what the reviewer approves

An approval needs a clear object. “Approve this customer” or “Approve this workflow” is too broad. Specify the proposed action, its target, the content or terms being approved, and the assumptions that make it acceptable.

For a customer offer, that might mean approval to send one particular offer revision to one contact. It does not also authorise accepting an order, reserving stock, changing the price, or sending a later revision.

Keep three things separate:

  • Reviewed facts: the proposal revision and supporting information the reviewer saw.
  • Decision: approve, reject, or request changes, with explicit conditions.
  • Execution eligibility: whether that approved action remains eligible when execution resumes.

An approval can remain an accurate historical record while no longer being usable for execution. Mark it superseded or expired rather than rewriting the decision as though approval never occurred.

Conditions must support an observable comparison. In a hypothetical offer, “quantity remains 24 units and total remains $1,200” is testable. “Approved if everything still looks good” leaves the resume logic undefined.

2. Separate proposal revisions from internal record changes

Define the revision boundary before deciding which changes invalidate approval. Otherwise, a harmless internal edit may be permitted by one rule but treated as a new proposal by another.

Use three distinct categories:

  • Proposal fields: the approved action, recipient, products, quantity, price, dates, and customer-facing content. A change to any field inside this boundary creates a proposal revision and requires renewed review.
  • Supporting facts: availability, request status, and other conditions that determine whether the unchanged proposal can proceed. Refreshing these facts triggers an eligibility check, not automatically a proposal revision.
  • Internal metadata: explicitly excluded reporting labels or internal notes. Permitted edits here do not create a proposal revision or supersede approval.

Compare approved proposal fields, not the record’s general modification timestamp. A record can change without the proposal changing. Conversely, an unchanged revision identifier is insufficient if someone edited a proposal field without creating the required revision; treat that inconsistency as unresolved.

Keep the incidental-edit list narrow. A note is incidental only if it is excluded from the outgoing offer and does not affect its meaning, eligibility, or execution. A note instructing someone to use another recipient is not harmless metadata. Unclassified differences should pause for resolution rather than silently pass.

3. Use a filled review-resumption worksheet

This fictional worksheet is a reusable starting point. Replace its fields and rules for the actual workflow while preserving the distinction between proposal, supporting facts, and metadata.

Case and approved snapshot

  • Case: OFFER-218; approved proposal revision 3.
  • Action: send revision 3 once by email. Sending does not reserve stock or confirm an order.
  • Recipient: Maya Chen at Northfield Studio, using the recipient address stored in the approved snapshot.
  • Proposal: 24 desk organisers; total $1,200; proposed dispatch on 18 June; complete outgoing offer text retained with the snapshot.
  • Supporting facts: availability supports the quantity and dispatch date; the customer request remains open.
  • Decision: approved at 10:00 on 12 June.
  • Boundary: sending this offer only; no authority to accept an order, reserve goods, substitute products, or alter terms.

Revision and change rules

  • Proposal revision boundary: action, recipient address, product, quantity, total, dispatch date, and outgoing offer text. Changing any of these creates revision 4 and supersedes revision 3’s execution approval.
  • Supporting-fact update: refresh availability and customer-request status without creating a proposal revision. If the facts no longer support the unchanged offer, block execution.
  • Permitted metadata update: change an internal reporting label or add an internal note only when it neither enters the outgoing offer nor changes its assumptions or execution instructions. This does not create a proposal revision.
  • Unclassified difference: pause for human resolution. Do not treat it as incidental by default.

Expiry and required resume comparison

  • Time expiry: approval expires at 16:00 on 12 June, under this hypothetical internal rule.
  • Event expiry: a new proposal revision supersedes approval; customer withdrawal closes the send path. A permitted metadata update triggers neither event.
  • Every resume attempt: compare current proposal fields with the approved snapshot, confirm the proposal revision, refresh supporting facts, check expiry, and inspect action state.
  • Execution conditions: proposal fields match revision 3, approval is unexpired, availability supports the offer, the request is open, and no completed or unresolved send prevents another attempt.
  • Unknown outcome: hold for reconciliation. A missing success record alone does not prove nothing was sent.

Decision paths

Approve: Record the decision against revision 3, then resume at the eligibility check, not directly at send. Attempt the approved action only after all conditions pass. Route proposal changes to renewed review; refresh supporting facts before deciding whether an unchanged proposal remains eligible.

Reject: Close this proposal’s send path and retain the reason. A later proposal requires a separate decision linked to the history; it cannot inherit approval from another revision.

Request changes: Return to preparation with the requested edits. This outcome grants no execution approval. Proposal edits create revision 4, which must receive a new decision.

Worked comparison after approval

At 10:15, the coordinator changes the internal reporting label from “June pipeline” to “Priority follow-up.” The label is excluded metadata, so the proposal remains revision 3. At resumption, the proposal fields still match. If the other checks pass, renewed review is unnecessary.

In a separate branch of the example, the coordinator changes quantity from 24 to 30 at 10:20. This creates revision 4. At 10:25, resumption detects the changed quantity and revision, supersedes the old execution approval, and routes revision 4 to review. Nothing is sent under revision 3’s approval, even if the new total remains $1,200.

4. Choose the correct resume destination

“Resume” should identify a state, not mean “continue from the next line.” Choose the destination according to what is no longer reliable.

  • Return to a check when the proposal is unchanged but a time-sensitive supporting fact needs refreshing.
  • Return to a decision when the proposal changes, approval expires, or changed facts fall outside the approved conditions.
  • Return to preparation when failed eligibility requires a different proposal before anyone can review it.
  • Reach the action only after the checks pass and the intended action remains exactly what was approved.
  • Close or hold when the request is withdrawn, the proposal is rejected, or necessary information remains unresolved.

In the worksheet, refreshed availability that still supports the identical offer does not itself demand another review. Availability that no longer supports the dispatch date blocks sending. Preparation must establish a viable proposal; changed terms then require a new decision.

This avoids both repeated review of unchanged proposals and the opposite mistake: treating a successful data refresh as approval of changed terms.

5. Protect the interval between checking and acting

Facts can change after the resume check but before execution. Keep that interval short and, where supported, make the action conditional on the expected proposal revision.

A recommended design carries the approved revision identifier into the action attempt and refuses to proceed if the current proposal no longer matches. Supporting facts may also need their own freshness conditions. A recently checked quantity is not necessarily a reservation.

If the execution system cannot preserve those conditions, document the limitation and choose a fallback, such as an immediate recheck or manual handoff. Another check narrows the gap; it does not make checking and acting indivisible.

Duplicate resume events present a different problem. Use a durable identity for the intended action and distinguish pending, successful, failed, and unresolved attempts. Two resume events should not independently create two sends. This execution-state design complements the approval comparison; it does not replace it.

6. Recover from failures without extending approval

A technical failure does not broaden authority or restart the approval clock. Every retry must still meet the original conditions.

  • Definitely not executed: the action stopped before submission. Retry through the eligibility check while approval remains usable.
  • Execution confirmed: retain completion and do not repeat the action when another resume event arrives.
  • Outcome uncertain: submission may have succeeded, but confirmation is missing. Reconcile before retrying; escalate if the result cannot be established.

If approval expires during an interruption, preserve the failed attempt and obtain a fresh decision before another attempt. Scheduling a retry must not extend expiry.

Missing supporting data should produce a waiting or escalation state, not a default pass. Give the operator a specific reason, such as “availability could not be refreshed” or “previous send outcome unresolved,” plus a named next step. That makes recovery actionable without pretending the workflow knows more than it does.

7. Keep a record that explains the result

An operator should be able to determine why an approved proposal ran, stopped, or returned for review without reconstructing scattered notes.

Retain the reviewed snapshot, proposal revision, decision, conditions, expiry, and decision time. For each resume attempt, record proposal-field comparison results, relevant supporting facts, metadata-only differences, selected destination, and action outcome.

Keep decision and execution status separate. “Approved, then expired” differs from “rejected.” “Approved, outcome unresolved” differs from “completed.” Collapsing them into one status encourages unsafe retries and misleading reports.

For renewed review, present a difference summary alongside the complete current proposal. Explain the actual reason, such as “quantity changed,” rather than a generic “validation failed.”

8. Test the boundary before enabling real actions

Use fictional records to test expected destinations before enabling execution:

  1. Approve an unchanged proposal: it passes checks and reaches the intended action once.
  2. Change a proposal field: a new revision requires renewed review.
  3. Edit permitted metadata: no proposal revision is created, and approval remains usable if other checks pass.
  4. Change a proposal field without updating its revision: the inconsistency blocks execution.
  5. Resume after expiry: a fresh decision is required.
  6. Make a supporting fact unavailable: the workflow waits or escalates.
  7. Repeat a resume event after completion: no duplicate action occurs.
  8. Simulate an uncertain outcome: reconciliation precedes retry.
  9. Record rejection or request changes: neither outcome reaches execution.

Record expected and observed destinations for each test: check, preparation, decision, action, closed, or unresolved. Investigate mismatches before enabling resumption. If implementing this practice with Alactic, check the relevant workspace and current plan for availability; this worksheet does not establish that a particular control exists.

Automation designHuman reviewWorkflow operations

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications