ResolveOpsInquiry
Explore

Operations &
technology
consulting.

We configure approval workflows, connect business applications and reconcile the records behind your reports.

View consulting services
Illustration of an operations specialist connecting business applications
Illustration of connected business tools and a workflow

Request approvals

Request forms, approval routing and a return path when information is missing.

Application connections

Connections between applications, with rules for new records, updates, duplicates and failed transfers.

Report reconciliation

Reconcile conflicting totals and trace the dates, filters and adjustments behind a report.

System options

A review of the applications you use and the options for changing them.

Preparing a technology change for use? Read about delivery support

Give incomplete work a return route.

An approval should reach the decision maker with the information they need. If a cost center is missing, the request goes back to its author before finance reviews it.

Illustrative purchase request: a complete request moves to finance.

Workflow design and approval rules
Request authorPurchase requestSupplier · Amount · Cost center
Return to authorAdd the cost center
Finance reviewerReview the purchase

The required information is present. The request moves to finance for a decision, with its author retained in the record.

Record your own approval route

Enter one step per line. The worksheet adds fields for the responsible person, the information needed and the return route for incomplete work.

Complete the fields with the teams involved, then copy the result. Entries are not saved when you leave the page.

Worksheet instructions

For example: receive the request, check its details, approve it, schedule the work. Enter up to 20 steps. Copy your worksheet to keep it; the text stays on this page and is not sent to us.

Add a step to see the worksheet fields.

Test the route before it goes live.

A completed request checks only part of a workflow. We also test the exceptions covered by the agreed scope, using representative records with the people who will operate the process.

  • Try a request with missing information. Check who receives it and what they are asked to supply.
  • Make a correction after approval. Check whether the change requires another decision.
  • Use the substitute-approver route. Confirm the decision stays within delegated authority.

Record the expected outcome alongside what happened. Unresolved exceptions stay visible when your team reviews the change.

Release readiness checks

Trial conditions

Request type
Required information
Decision authority
Expected destination

Example record structure

Trial result

Route taken
Decision recorded
Exception observed
Action still required

Operating records

Rules the operating team needs.

The person managing a queue needs to know what can proceed and what requires a decision. We record those rules with the configuration, including exceptions that the system cannot resolve on its own.

Example operating record

Approval route

  • Request and required information
  • Decision authority and substitutes
  • Where incomplete work returns

Approval route

Who can approve a request

Your organization sets approval authority. We translate the agreed rules into the form and routing configuration, including what happens when the usual approver is unavailable.

  • The route identifies the role allowed to make the decision.
  • A substitute approver needs the appropriate authority, not just access to the queue.
Check approval exceptions
What happens to incomplete work

A returned request needs a destination and a reason. We specify which information is missing, who supplies it and when the receiving team should look at the request again.

  • The original request and the correction remain identifiable.
  • The receiving team can tell whether the corrected item is ready.
Set the receiving conditions
When a transfer can be retried

A timeout does not prove that the destination rejected a record. We check how the connection identifies an existing record before allowing another attempt.

  • The operator can distinguish a rejected transfer from an unknown outcome.
  • Recovery instructions name the checks to complete before a retry and when to stop.
Read the recovery procedure
Which records belong in a report

We trace a reported total back to its source records. The definition needs to account for the reporting period, included statuses and adjustments, so the next review uses the same basis.

  • Differences are recorded separately from unexplained balances.
  • Changes to dates, filters or adjustments have a named reviewer.
Compare two report totals