Back to all articlesAutomation design

Order workflow actions by dependency rather than convenience

Alactic Editorial10 min read

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

A workflow can look orderly while making promises it cannot yet support. A customer receives a booking confirmation because the message step follows the assignment step—even though nobody has confirmed that the assigned person is available.

To order actions in an automation workflow, start with the evidence each action requires. Identify which earlier outcomes must be confirmed, make those outcomes explicit gates, and allow unrelated work to proceed in parallel. A previous action being attempted is not the same as its prerequisite being satisfied.

The practical question is not “What should the workflow do next?” It is “What must be true before this action is allowed to happen, and what evidence will establish that?” The worksheet below turns that question into an operating design that a business owner and workflow builder can review together.

1. Separate dependencies from a convenient list

A convenient sequence often follows the order in which actions were added: create a record, assign an owner, send a message, check availability, update the status. That order may be easy to build, but it does not describe the business conditions needed for each action.

Distinguish three kinds of relationship:

  • Required predecessor: the later action cannot produce a valid result without a confirmed earlier outcome. A firm booking confirmation requires an accepted booking.
  • Independent action: the work can proceed without the other action's result. Reviewing customer contact preferences and checking staff availability may be independent once both use the same verified request.
  • Convenient ordering: one action happens first for readability or workload management, not because the next action requires it. Treating this as a hard dependency creates unnecessary waiting.

Use a counterfactual test: if the earlier action never completed, could the later action still be valid, authorised, and accurate? If not, record a dependency. If yes, ask whether the order is merely a preference.

Do not interpret independence as permission to execute. An action can be independent of another task while still requiring its own authorisation.

2. Define completion as an observable business state

Weak completion labels hide the most important distinction in a workflow. “Processed,” “handled,” and “done” can mean that someone started work, submitted a request, or confirmed an outcome. Those are different states.

For each action, write a completion statement that another person could verify without guessing:

  • Not “availability checked,” but “the named scheduling owner has confirmed that the proposed slot and required staff are available.”
  • Not “message approved,” but “the designated approver has accepted this version of the message and the commitment it contains.”
  • Not “customer confirmed,” but “the required customer acceptance has been recorded against the agreed booking details.”

Evidence should identify the relevant request, the outcome, and who or what is authorised to establish it. Where the result can change, include when it was established and what would invalidate it.

Also distinguish authority to prepare work from authority to commit it. Someone may be allowed to draft a confirmation without being allowed to approve the booking. OWASP recommends least privilege, deny-by-default decisions, and permission checks for each request; these are useful security principles, not evidence that any particular product provides a control. See the OWASP authorization guidance.

A completed predecessor does not grant blanket permission for everything downstream. Each consequential action still needs an authorised actor and an applicable business decision.

3. Filled worksheet: a fictional appointment workflow

Hypothetical worked example: a fictional maintenance business receives a request for an on-site assessment. It wants to confirm a visit only after the request is sufficiently clear, a suitable slot is accepted internally, and the outbound communication is authorised. All roles, action labels, and evidence below are illustrative design choices, not customer results or product features.

The worksheet uses a repeated format so it can be copied into a document or task board. “Required predecessors” means confirmed outcomes, not merely actions that have been started.

Action A — Validate the service request
Required predecessors: Request received.
Completion evidence: Intake owner records the customer, site,
requested service, and unresolved questions; confirms that the
request is sufficient for scheduling assessment.
Authorised owner: Intake coordinator.
If unresolved: Seek clarification; do not claim a booking exists.

Action B — Confirm contact eligibility and route
Required predecessors: A complete.
Completion evidence: Contact reviewer records the intended
recipient, permission status, any opt-out, selected channel,
and applicable messaging route.
Authorised owner: Contact reviewer.
If unresolved: Block outbound contact through that route;
refer to the responsible human reviewer.

Action C — Confirm a suitable appointment option
Required predecessors: A complete.
Completion evidence: Scheduling owner records an available
slot, suitable staff, and the scope the appointment covers.
Authorised owner: Scheduling coordinator.
If unresolved: Ask for alternatives; no firm confirmation.

Action D — Prepare the confirmation draft
Required predecessors: A and C complete.
Completion evidence: A saved draft matches the verified
customer, site, slot, and agreed appointment scope.
Authorised owner: Communications preparer.
If unresolved: Correct the draft; do not release it.

Action E — Authorise the booking commitment
Required predecessors: C complete.
Completion evidence: Booking approver accepts the named slot,
staff assignment, and scope for this request.
Authorised owner: Booking approver.
If unresolved: Keep the booking proposed, not confirmed.

Action F — Approve outbound release
Required predecessors: B, D, and E complete.
Completion evidence: Release approver accepts the exact draft,
recipient, contact route, and underlying booking commitment;
checks that the supporting facts remain valid.
Authorised owner: Release approver.
If unresolved: Hold release and name the missing condition.

Action G — Perform the authorised send action
Required predecessors: F complete; eligibility, booking facts,
and authority remain valid at the point of action.
Completion evidence: A send outcome is recorded against the
approved message and request. Submission alone is not delivery.
Authorised owner: Designated sender or expressly authorised workflow.
If unresolved: Record the known outcome and route uncertainty
to the communications owner; do not assume delivery.

Action H — Record the communication outcome
Required predecessors: G has an observable outcome to record.
Completion evidence: Request record distinguishes the booking
state from the communication state and identifies any follow-up.
Authorised owner: Operations coordinator.
If unresolved: Leave the unknown explicit and assign review.

Notice that this workflow does not require successful delivery before the business can record what happened. Recording a failed or uncertain communication outcome is valid work. It does, however, prevent a send attempt from being labelled as customer receipt.

4. Read the worksheet as a dependency diagram

Prose diagram for the hypothetical workflow: A is the entry gate. Once A is complete, B and C can proceed in parallel. After C is confirmed, D and E can proceed in parallel. F is a join: it waits for B, D, and E, regardless of which finishes first. G follows F only while the underlying conditions remain valid. H records the observable result of G without upgrading an uncertain outcome into success.

This structure allows useful preparation without allowing premature commitment. Contact review does not need to wait for the scheduling decision. Drafting does not need to wait for the booking approver, provided the draft remains internal and clearly unapproved.

Parallel work also creates a trade-off. Drafting before final booking approval may save elapsed time, but a rejected slot means revising the draft. Waiting for approval reduces that rework but lengthens the path. Choose deliberately based on the cost of preparation and the consequence of error.

Do not add a dependency simply to make the diagram tidy. Conversely, do not remove a dependency merely to make the workflow look faster. The safe boundary is whether the action uses an unconfirmed fact or makes an unauthorised commitment.

5. Make gates check evidence, not elapsed time

A delay is not completion evidence. Waiting for a scheduling response does not establish availability, however long the workflow waits. Likewise, the absence of an objection is not an approval unless the business has explicitly defined and authorised that decision process.

For each gate, specify what happens when evidence is present, missing, negative, or uncertain:

  • Present and applicable: the action may proceed if its other conditions and authorisation are satisfied.
  • Missing: hold the dependent action and name the owner responsible for obtaining the evidence.
  • Negative: take the defined alternative path, such as offering another appointment, rather than continuing the original commitment.
  • Uncertain or contradictory: escalate for a decision instead of interpreting uncertainty as approval.

Check whether each join requires all predecessors or an explicit alternative. In the worksheet, F needs contact eligibility, an accurate draft, and an approved commitment. Completing any one of them is insufficient.

For a WhatsApp route, keep recipient permission, opt-outs, message preparation, template approval, and delivery distinct. Approved templates are used to initiate Platform conversations and outside the customer-service window; that window opens or resets with a user message and lasts 24 hours. Template approval does not guarantee delivery. Check the current WhatsApp Business Messaging Policy for precise requirements, and provide a clear human escalation path. These channel conditions sit alongside the business dependencies; they do not replace booking approval.

6. Plan for changed facts and blocked actions

A dependency can be satisfied and later become invalid. An appointment option may change after a draft is prepared. A recipient may opt out before release. An approver may accept an earlier version rather than the version now awaiting action.

Write an invalidation rule beside any evidence that can become stale. In the hypothetical worksheet, changing the appointment slot invalidates the draft's accuracy and the booking approval. The contact review might remain applicable if the recipient and route are unchanged, but that should be checked rather than assumed.

Recovery should return to the affected decision, not automatically restart every action or blindly continue from the last recorded step:

  1. Identify the changed fact and the evidence it invalidates.
  2. Hold actions that rely on that evidence.
  3. Preserve independent completed work where it remains applicable.
  4. Assign a human owner to resolve the changed condition.
  5. Obtain fresh approval for any changed commitment or outbound content.

If an incorrect confirmation has already been sent, changing an internal status does not correct the customer's understanding. A responsible person must assess the discrepancy and authorise an appropriate correction through an eligible route.

This is business recovery planning, not a specification for integration behaviour, transaction guarantees, or system retries. Those implementation questions need separate treatment.

7. Review the design with counterexamples

A dependency review is more useful when it challenges the happy path. Use hypothetical walkthroughs to test whether the worksheet produces an unambiguous next decision:

  • Contact review finishes first: B completes while C remains unresolved. The workflow may continue scheduling work, but cannot release a booking confirmation.
  • Booking approval is refused: E rejects the proposed slot after D has prepared a draft. F remains blocked; the draft is not evidence of an approved booking.
  • The recipient opts out: earlier contact evidence no longer supports the selected route. Release must stop even if the booking is otherwise approved.
  • A send is submitted without a confirmed delivery outcome: H records what is known. It must not label the customer as having received or accepted the message.

For each walkthrough, ask the reviewer to identify the blocked action, the missing or invalid evidence, the responsible owner, and the allowed next step. If reviewers disagree, the worksheet is not yet precise enough.

8. Apply the worksheet to one live workflow

Choose a workflow that makes an external commitment: confirming an appointment, accepting an order, or notifying a customer of an agreed change. List its actions as they currently operate, then rewrite each action with required predecessors, completion evidence, authority, and a blocked-state owner.

Before changing execution, measure the design itself: count actions without explicit prerequisites, gates that rely on vague completion labels, and blocked states without an owner. Review a defined sample of recent cases for dependent actions taken before their prerequisites were confirmed. Use those findings as a baseline, not as proof of what automation will improve.

The immediate deliverable is a reviewed dependency map with no unexplained release gate. After any approved change, examine whether premature actions and avoidable waiting have decreased, while also checking for extra review work or bottlenecks. A sound sequence should make both permission to proceed and the reason to stop observable.

Automation designWorkflow dependenciesOperational controlsApprovals

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