The booking platform stops loading while one truck is already on the road. The office has yesterday's route printout, a driver has a newer message, and a customer is asking to change the collection time. The immediate problem is deciding which instructions each person should follow.

An inflatable rental booking system outage needs a temporary dispatch process with a known starting point, one coordinator and a record of every subsequent change. This guide covers that interruption and the return to your main system. Equipment checks and customer approvals still follow their usual procedures.

Prepare a Copy You Can Actually Open Offline

Before dispatch, save the confirmed jobs and their current instructions in a format your authorized team can open without signing into the booking service. A cloud shortcut is not an offline copy. Test the files with the connection disabled, including any documents the crew needs to access.

Mark the export date, time and time zone. Include booking references, allocated physical unit IDs, delivery and collection windows, site contacts, assigned crews and references to the relevant confirmed documents. For similar commercial bounce houses, keep the individual unit reference beside the listing name; a theme alone may identify several units.

Reuse your existing delivery-day crew checklist rather than creating another loading sheet. The backup packet preserves known instructions. It does not prove that the equipment remains available after the export time. Give each crew only the records it needs, and keep the master copy with the coordinator.

Establish the Last Verified Position

When access fails, name the person coordinating dispatch during the interruption. Tell the office and crews which contact to use and which snapshot is the starting point. Confirm which instructions crews already received and what they have actually completed since that snapshot.

Separate three groups: confirmed jobs supported by accessible records, existing jobs with unresolved information, and new inquiries. Do not turn a new inquiry into a confirmed booking because an old availability screen appears to show an unused unit. Another booking or equipment restriction may have been entered since the export.

If you cannot establish the equipment allocation, required documents or current instructions for a job, leave the affected action pending while the responsible person checks it. An outage does not make a missing approval unnecessary. Record the gap and who is resolving it instead of filling it from memory.

Keep One Temporary Change Log

Use a paper master log or another agreed record that the coordinator can maintain during the interruption. Give each event a unique temporary reference and link it to the existing booking. Record when the information arrived, who supplied it, what changed and who needs to act.

A useful rental booking outage checklist distinguishes a request from an instruction, and an instruction from completed work:

Keep the original request and later decisions together. Cross-reference related events rather than overwriting the first entry. If two people report different collection times, record the conflict and resolve it before issuing another instruction.

Send Changes with a Reference and Require a Reply

During offline dispatch, the coordinator should send a specific change against a specific booking. Include the temporary reference, the instruction being replaced, the new instruction and the person expected to acknowledge it. Ask the recipient to confirm what they understood.

For example, “Change O-004, booking B-EXAMPLE: collection now agreed for 18:00; replaces the 17:00 instruction on snapshot S-01” is clearer than “collect later.” These references are illustrative internal labels. Record the acknowledgement separately; an unanswered message remains unacknowledged.

Keep superseded instructions as history and clearly mark the active version. If the job involves inflatable water slides, carry forward the confirmed model and configuration rather than shortening the instruction to “the slide.” Any equipment replacement still goes through the customer substitution confirmation process; a temporary dispatch note cannot approve it.

Record new inquiries for later confirmation when availability cannot be checked reliably. Avoid having separate office staff reserve the same apparent gap in independent notebooks.

Reconcile Before Returning to Normal Operation

Start rental dispatch recovery by checking whether the platform has retained transactions or edits submitted before or during the interruption. A failed-looking screen may have left the outcome uncertain. Compare records before retrying an action.

Work through the temporary log by booking and event reference. For each entry, identify what was requested, what was agreed, what the crew actually did and what the platform currently shows. Enter only the confirmed update that is still missing, using the system's normal permissions and workflow.

Do not recreate an existing booking merely to capture an outage note. Likewise, a customer saying they paid is information to verify, not an instruction to charge again. Have an authorized person check the original payment service and record its confirmed reference or leave payment unresolved. Keep card details out of the temporary dispatch log.

Give every reconciled entry an updater, time and destination record reference. Keep unresolved conflicts assigned to a named owner. Then tell the team when the main system becomes authoritative again and how any remaining exceptions will be handled. Preserve the outage log with the affected job records so the sequence remains understandable.

Work Through One Collection-Time Change

Consider this fictional exercise, with all times in the same recorded local time zone. Snapshot S-01 was saved at 06:30. The platform becomes unavailable at 07:00. At 07:10, a customer asks to move collection from 17:00 to 18:00. The coordinator records O-004 against the existing booking, checks with the assigned crew and records the agreed change. The crew acknowledges the revised instruction at 07:15.

At 08:00, platform access returns. The coordinator finds the original booking still showing 17:00 and checks that no second booking or later amendment exists. They update the collection instruction, attach the temporary event reference and retain the acknowledgement. Collection has not happened yet, so it remains scheduled rather than completed.

If the platform already showed the agreed change, the coordinator would link the evidence and resolve any difference instead of entering it again. The purpose of the log is to preserve the sequence, not generate a second version of the booking.

Test the Handoff Before the Next Busy Day

Run a short practice with a fictional booking: open the backup without a connection, send one numbered change, record a crew reply and reconcile it against a test record. Check whether another authorized coordinator can follow the sequence without asking the original writer to explain it.

Keep any software capability questions in your platform review. A local file and a temporary log do not give every application an offline mode. What your team needs is a dependable way to distinguish the last verified plan, later decisions, acknowledged instructions and actual work until the main record catches up.