Reviewing a small business workflow in Albany should include the moments when ordinary work cannot proceed. A documented process may look clear while the system is available and the usual person is present. The more revealing question is what happens when one of those assumptions fails.
These questions use a customer-order workflow as an example, from recording the request to arranging fulfilment. They support a practical review, rather than certify business continuity or replace emergency procedures. Any exercise should protect people, real orders and business information.
What exactly are we trying to keep working?
Choose a defined activity and identify the useful result. Recording an order, confirming its terms and dispatching it are related, but they are not the same event. A workflow review becomes vague when all three are called processing.
Map the information and people needed at each point. Include where an order’s status is recorded and how the next person knows work is ready. The government’s emergency-management planning guidance recommends identifying important products and services and considering alternatives if delivery arrangements fail. Begin with the activity whose interruption would matter most.
How would we notice that something had failed?
Ask what staff would observe, not simply which software might stop. An order could remain unassigned, a notification could be missed or the recorded quantity could differ from the request. The screen may still be available while the work has stalled.
Decide how such exceptions become visible and who checks them. A staff member repeatedly asking whether something happened is evidence of unclear status, rather than proof that the person responsible ignored it. Keep the review focused on the information needed to investigate.
Does the alternative depend on the same missing resource?
Trace the dependency behind the proposed backup. A second document stored in the unavailable system may not help. Another staff member cannot take over if only the absent person has the necessary authorised access or knows where the order details are kept.
Ask what the alternative actually requires: usable information, appropriate permissions, instructions and a way to record work. Do not solve access problems by sharing someone’s password. Where a supplier or specialist must assist, record how to contact them through an available route.
Is a data backup enough to restart the task?
No. It is necessary to understand what the backup covers and whether it can be used as intended. ASD’s small-business guidance asks businesses to consider backup scope, timing, storage, responsibility, retention and testing, including information in email and cloud accounts.
For the order workflow, identify which records would be available and which later changes might not be included. Ask the appropriate technical person how recovery is tested safely. A successful copy operation or an export icon does not establish that staff can resume the order task from the result.
What should staff say while the outcome is uncertain?
Agree who can contact affected customers and what information is reliable enough to share. A message saying the team is investigating an order differs from confirming a dispatch date that has not been checked.
Prepare a route for updating people as the position becomes clearer. Avoid promising that every request can continue unchanged during disruption. An honest temporary limitation may be more useful than a confident statement based on an inaccessible record.
- Which order or activity is affected?
- What has been verified and what remains unknown?
- Who owns the next check or customer update?
- What decision requires someone else’s approval?
How can we test the response without disrupting customers?
Start with an agreed discussion using invented order details. Describe a missing system or unavailable team member and follow the proposed response on paper. Do not deliberately disable a live service or alter customer records merely to make the exercise realistic.
Keep a list of steps that could be explained, steps that required information nobody had and assumptions needing technical verification. A discussion can reveal gaps, but it does not demonstrate an actual restore, safe operating capability or guaranteed recovery time. Plan any technical test with appropriately qualified assistance and clear safeguards.
What happens to temporary records afterwards?
Define how work recorded during disruption will be checked against the normal system before it is entered again. Include orders already acted on, corrections and requests that could not be completed. Otherwise, the restart can create duplicate work or lose a change made while the system was unavailable.
Assign responsibility for resolving conflicting records. Do not overwrite an unexplained difference simply to make totals agree. Follow the business’s information-handling requirements when retaining or disposing of temporary material.
When is the review complete?
Finish when the findings have led to clear actions, owners and a suitable follow-up check. Update instructions after changes to staff, systems or suppliers. The government’s guidance also recommends reviewing and rehearsing relevant plans, rather than leaving them untouched.
Keep emergency safety actions separate from ordinary workflow recovery and follow applicable emergency instructions when needed. The useful result is a better-understood order process: what can continue, what must pause and what evidence is needed before work is declared restored.