Developing Workable Manual Alternatives When Systems Are Unavailable

01Choose the transactions that genuinely need a workaround

Not every application function requires a paper alternative. Use business impact and minimum-service decisions to select urgent orders, safety inspections, incident notices or time-critical approvals that cannot wait for restoration. Define who may initiate a manual transaction and the circumstances that activate the method. Avoid leaving staff to decide individually which records are important under pressure.

Write a short process map showing the starting information, decision points, required authorization, physical or offline evidence and destination. Include transactions that must be stopped because information or competence is unavailable. A safe refusal path is part of a practical workaround.

Manual alternatives should be intentionally narrower than the automated system. If an ERP normally handles dozens of transaction types, the fallback might cover only authorized urgent releases. This reduces the chance of uncontrolled complexity. The process owner must also decide what work will not occur, how customers are informed and how deferred requests are preserved without being lost during recovery.

Technical context: ISO 22301:2019 — Business continuity management systems — Requirements (with Amd 1:2024) is one verified source for the concepts discussed here.

02Prepare the minimum information and materials

Identify the data needed to act without the normal system: verified customer identifiers, product specifications, inventory status, safety instructions, emergency contacts and authorized limits. Determine which information can be maintained offline without creating an uncontrolled privacy or security exposure. A printed list that is out of date may be more dangerous than no list.

Use numbered forms, approved offline exports or secured binders with clear effective dates, custody and access rules. Keep stock of required stationery and equipment at the point of use. Review whether alternative power, lighting, communications or scanning devices will actually be available during the chosen outage scenario.

Prepare critical information as controlled versions rather than a pile of ad hoc printouts. A backup customer list requires an update route, a custodian and safeguards for personal data. A warehouse stock snapshot needs an observation time and a rule for reservations made after the snapshot. Without these details, staff can act confidently on information that is already wrong.

03Preserve authority and segregation of duties

An unavailable workflow engine may have been enforcing approval limits, four-eye checks and restricted customer access. Translate those controls into a manual decision path. Identify the authorized approver and deputy, verification evidence and method for escalating an exception. If the normally required reviewer is unavailable, the business must have an approved delegation or stop the relevant transaction.

Do not imply that urgency cancels product safety or legal constraints. A manual transaction should be judged against the same essential acceptance criteria as the normal method. Document which compensating checks apply because automated validation is absent and how employees can raise uncertainty.

A manual sign-off must be achievable in the actual disruption. If the ordinary authorized signatory cannot be contacted, document the legal and operational basis of a deputy’s approval before any event occurs. For high-risk items, an offline form can carry a verification checklist and a two-person release box. A blank “approved” stamp is not the equivalent of a controlled authority decision.

04Control numbering, custody and duplicate risk

Allocate unique manual transaction references and record the originator, date, time, customer or asset, approvals and status. Secure completed forms from loss, alteration and unauthorized access. Distinguish transactions that are merely drafted from those executed or delivered. During an outage, staff may receive the same request by phone, email and paper, creating a real risk of duplicate service.

Give the manual register one authoritative owner and define a check for duplicates before action. Where several sites are operating offline, establish a numbering scheme that does not collide when information is later consolidated. Retain cancelled and corrected entries with a clear audit trail rather than silently erasing them.

Use locally unique serial ranges for forms at multiple sites. If the network fails everywhere, two warehouses should not issue the same document number. An inventory of unused and cancelled forms can prevent later uncertainty. Record which transactions were physically completed and which were only promised, so that service teams do not inadvertently repeat a shipment after restoration.

05Know the capacity and failure point of the manual process

A process that works for one sample may fail under volume. Test the rate at which trained people can complete and verify transactions, considering fatigue and handover between shifts. Estimate how long records can remain offline before reconciliation becomes impractical. These limits should inform the minimum-service commitment and activation threshold.

Prepare a simple backlog control showing pending, approved, completed and reconciled states. Establish what to do when demand exceeds safe manual capacity. If a critical verification step cannot be performed, halt the corresponding category and communicate the constraint clearly to affected customers.

Calculate the manual throughput with the actual slowest safeguard. A trained team may process orders quickly but the stock verification step can limit dispatch rate. Test a realistic set of requests and assess error detection. Where the safe capacity is insufficient, invoke the minimum-service prioritization rather than asking employees to bypass a check to increase volume.

06Design reconciliation before activation

Determine how offline records will be entered into the restored system, how duplicates will be prevented and how changes during the outage will be resolved. Assign people independent of the original processor to review material exceptions. Preserve a link between the manual source record and the final digital transaction so later complaints and audits can reconstruct the decision.

Agree the cutoff for stopping new manual entries, the business acceptance test for restored data and when temporary documents may be archived. Reconciliation can require substantial effort, so include it in recovery resources rather than treating it as optional cleanup. ICT restoration and business process restoration are different milestones.

Design the recovery reconciliation checklist to compare unique IDs, authorized values, stock movement and the final system posting. Discrepancies need investigation and an owner, not silent “adjustment to balance.” Preserve a link to each source document after digital entry. Finance and operations should agree the point at which it is safe to discontinue the temporary ledger.

07Exercise end to end, including recovery

Run an exercise with real operational staff and realistic missing information. Process a transaction under the approved manual rules, handle a duplicate, replace an absent approver and reconcile after the system is restored. Observe whether the forms are understandable and available at the actual worksite. A tabletop conversation alone cannot establish transaction throughput or data integrity.

ISO/IEC 27031:2025 guides ICT readiness for business continuity and complements business-level continuity planning under ISO 22301. The organization should demonstrate both the technological recovery and the business controls that function while systems are absent. Update the workaround after system changes, new data fields or failed tests.

When exercising, include a customer cancellation received through a second channel after a manual order was approved. This tests duplicate control, status changes and communication. Include a later return of the primary system and follow the same transaction to final reconciliation. A test that ends when paper paperwork is filed has not proved successful business recovery.

Closing Perspective

A workable manual alternative is a small, controlled operating system in its own right. It must produce safe transactions, preserve evidence and return data to the authoritative system without hiding errors.