Test the Capacity and Exit Plan of a Manual Workaround

Purpose and scope

A continuity plan may say use a spreadsheet or record requests on paper during an outage. That is a starting idea, not a complete fallback. The business needs to know what the manual route can handle, which controls remain necessary, and how the temporary work will be reconciled when normal systems return.

Choose one critical workflow and define the permitted fallback with its responsible owners. Safety, privacy, financial, and regulatory controls still apply during disruption. Some activities may need to pause rather than move into an improvised process that cannot meet those controls.

Define the reduced service

State which requests can be accepted, which actions can be completed, and which must wait. A manual arrangement may support recording a request without being able to confirm inventory, eligibility, or payment. The customer-facing wording should reflect that limit.

The Ready.gov continuity template includes documenting forms and resources for manual workarounds. The operational framework below develops that narrow planning idea into a testable workflow. It is not a promise that any particular paper or spreadsheet process is suitable for every business.

Create the minimum complete record

Use a unique temporary reference, received time, necessary request details, current owner, permitted action, and status. Collect only information needed for the approved fallback. Avoid placing full payment credentials or unnecessary sensitive data in a temporary worksheet because the usual system is unavailable.

Make the record usable by the next person. If a request depends on a verbal detail, capture the relevant non-sensitive instruction in the approved form rather than expecting the original staff member to remember it later. Define where records are stored and who can access them.

Measure throughput with a controlled sample

Run a safe practice set containing ordinary requests and realistic exceptions. Time the whole handling process, including verification, recording, handoff, and review. Do not measure only the fastest form entry and call that the fallback's capacity.

Suppose an illustrative manual route takes an average of six minutes per request during a small test. One person has at most ten such requests per hour before breaks, interruptions, complex cases, and other duties. If ordinary demand is thirty requests per hour, one person cannot maintain the normal service level. These invented figures expose the relationship; they do not establish a staffing benchmark.

Include quality and rework

Inspect the sample records for missing information, duplicate references, ambiguous status, and unauthorized actions. A faster route that produces unusable records shifts work into reconciliation and may create additional risk. Count the effort to correct sample errors when estimating capacity.

Add a second reviewer where the approved control requires it. If the normal system automatically checks a condition that people cannot reliably verify manually, decide whether that action must pause. Do not silently drop the check and continue promising the same service.

Set an overload trigger

Define what happens when incoming work exceeds the safe fallback capacity. Options may include reducing accepted scope, extending an accurately communicated response estimate, adding qualified staff, or pausing an activity. The authorized owner should decide based on the actual obligations and consequences.

Use observable triggers such as queue age, unreviewed items, or capacity limits, with a clear escalation route. A growing pile of temporary records should not remain invisible because the ordinary dashboard is down. Keep the fallback's own status review simple and dependable.

Plan the return before starting the fallback

Decide how temporary references will map to the main system, who will enter or import records, and how duplicates will be detected. Identify which actions have already happened so they are not repeated. A manually confirmed shipment or approved refund must not be replayed as though it were a new request.

Preserve the temporary record until reconciliation and required retention are complete. Do not destroy the only evidence of an outage-period action immediately after typing a summary into the main system. Follow the organization's records and privacy requirements for final retention or disposal.

Test a short recovery sequence

Use the practice records to simulate returning to the normal system in an approved environment. Confirm that each record is matched, completed, held for review, or identified as a duplicate. Reconcile totals and inspect exceptions rather than assuming a successful import means the work is correct.

For an illustrative appointment process, the fallback may have recorded requests without confirming slots. On recovery, the team must resolve availability and communicate the confirmed outcome. Automatically treating every request as an appointment would convert a limited temporary service into an unsupported commitment.

Keep the materials available when needed

Store approved forms, role instructions, contact routes, and necessary non-secret reference information where they remain accessible under the planned outage. Test that access without disabling production. A fallback document inside the only unavailable application is not ready for the scenario it describes.

Train the people expected to use the process and identify when retraining is needed. A manual fallback used rarely can become unfamiliar or stale, especially after changes to forms, products, or approval rules.

The finished workaround has a defined scope, measured capacity, quality controls, an overload response, and a reconciliation route. It may provide a reduced service, and that can be valuable. The important point is that the business knows what it can safely promise while the normal route is unavailable and how it will return without losing or duplicating work.