Free Soft Play Rental Weekend Delivery and Setup Capacity Calculator

Test a proposed weekend before accepting it. Enter bookings, bundle quantities, vehicle capacity, crew availability, loading, travel, setup, collection, cleaning, and repair holds; the calculator returns feasible or not feasible, identifies inventory and time collisions, and shows the first constraint that breaks the plan. The $0 offer includes a working browser calculator, a visible preview, an optional XLSX weekend run sheet, bundle-level stock and turnaround planning, exception flags, and filled solo-versus-two-crew examples.

Frame the Weekend as a Constraint Test, Not a Booking List

A paid reservation is not automatically a deliverable reservation. The calculator frames each proposed weekend as a shared-resource test: complete bundles, vehicle space, crew minutes, delivery and collection windows, cleaning turnaround, and repair holds must all fit. For example, Saturday bookings at 10:00 and 13:00 may use different sets yet still fail because one van needs two load runs or the solo installer cannot finish a 45-minute setup after 35 minutes of travel. The result is FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS, followed by the first broken constraint, affected bookings, late-window minutes, and the smallest modeled correction.

This is planning evidence, not a promise that traffic, weather, access, customer delays, or damage will cooperate. It only evaluates the times and capacities entered. Use the exported run sheet to confirm assumptions with the crew; retain the checklist for site-access, loading, and exception checks before accepting the booking.

Enter the Weekend in Operational Units the Model Can Test

Start with timezone, depot, weekend boundaries, crew shifts, and each vehicle's usable capacity. For example, use one van with 18 load units, Sam available 07:00–18:00, and Jo available 09:00–15:00. Define each bundle by components: White Set A needs 12 blocks, one ball pit, two mats, and one gate. Add unavailable periods, a Sunday repair hold, and 40 cleaning minutes before reuse.

Then enter each proposed booking's bundle, load units, address or travel minutes, delivery window, event time, collection window, setup, and teardown. Example: BK-104 requires White Set A, 14 units, delivery 09:00–09:30, 35 minutes travel, 45 minutes setup, and collection 16:00–16:30. Conservative buffers reduce overbooking but may reject workable jobs; optimistic entries do the reverse. Save the browser result, move accepted jobs into the XLSX run sheet and turnaround board, and use the CSV scorecard and checklist to document assumptions and exceptions.

Define Dispatchable Capacity and Scheduling Assumptions

Start with capacity you can actually dispatch, not total inventory owned. Record the operating timezone, depot, crew shifts, usable vehicle spaces, complete bundles, repair holds, and cleaning minutes. A set missing one required block is unavailable. Treat travel, loading, setup, teardown, and collection as scheduled work; enter buffers explicitly rather than hiding them inside estimates.

The model assumes each booking keeps its assigned components until collection and cleaning finish. Shared pieces therefore cannot support overlapping events. Vehicle capacity is measured in declared load units, so bulky layouts may require two runs even when their item count looks small. Outputs show FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS, plus the first broken constraint, affected bookings, late minutes, and cleaning-ready time.

These results are planning evidence, not a traffic or staffing guarantee. Use checklist.csv to validate inputs, guide.md to document conventions, and scorecard.csv to compare reruns.

Filled Saturday Baseline: Van Capacity Breaks First

Baseline: Saturday, one van holding 10 load units, one crew scheduled 08:00–18:00, and two bundles. Booking A uses six units, requires 30 minutes from the depot, 45 minutes for setup by 09:30, collection at 12:00, 30 minutes for teardown, and 60 minutes for cleaning. Booking B uses seven units, sits 25 minutes from both depot and A, and needs setup by 14:00, collection at 17:00, teardown, and 75 cleaning minutes. Reloading takes 20 minutes.

The result is INFEASIBLE. After A’s collection, teardown ends at 12:30; returning, reloading, driving, and setting up B finishes at 14:30, 30 minutes late. Inventory is sufficient, but the van sequence breaks first. Raising capacity to 13 units avoids the reload and returns FEASIBLE WITH EXCEPTIONS because cleaning exceeds the shift. Adding a 13:00–20:00 crew clears it.

Export to the XLSX run sheet; use roi_calculator.csv to compare vehicle and labor costs.

How the weekend feasibility calculation works

Start with usable resources, not headline inventory: complete bundles after repair holds, vehicle load slots, crew shifts, and each booking’s delivery, setup, event, collection, teardown, travel, and cleaning times. The calculator orders activities on one timeline, reserves bundle components through cleaning-ready time, converts each booking’s load requirement into vehicle runs, then checks window lateness and crew overlap. Its output is FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS, plus the first broken constraint and affected bookings.

For example, enter two Saturday bookings, one bundle, a van holding one bundle, a 09:00–14:00 solo shift, 35-minute travel legs, 45-minute setup, and 30-minute teardown. If Booking B needs delivery at 11:00 while Booking A still occupies the van and crew, the result is INFEASIBLE despite stock. Rerun with a second crew, wider window, or smaller compatible bundle. The change identifies a correction; it cannot predict traffic, damage, or customer delays.

Interpret the first constraint and use each working file

Interpret the status by tracing the first constraint, not by averaging utilization. A 62% bundle-utilization result can still fail when the only matching ball-pit set is on repair hold, cleaning finishes after its next load time, or two collections overlap one crew shift. FEASIBLE WITH EXCEPTIONS means the schedule works only under a declared condition, such as a 20-minute delivery-window extension or an owner completing one collection. Record that assumption beside the affected booking and rerun the original case if it changes.

Export the run sheet for crew sequencing, inventory-bundle planner for component reservations, and turnaround board for cleaning-ready times. Use the filled solo-versus-two-crew examples to audit input effects before entering live bookings. The scorecard and checklist support acceptance review; the remaining CSV files organize vendor, pricing, return, demo, and RFP decisions. Outputs remain estimates, so confirm routes, vehicle limits, stock condition, and staff availability.

Where Weekend Feasibility Models Commonly Fail

A FEASIBLE result is only as reliable as the schedule entered. Common failures include treating a three-piece bundle as available when one climber is on repair hold, omitting return travel, assuming a van carries two sets without measured load data, or scheduling the same worker for overlapping setup and collection windows.

For example, Booking A may require delivery by 10:00, 45 minutes of travel, 40 minutes of setup, and one full van load. Booking B at 11:15 looks open until depot loading and the return leg are added. The output should expose the first broken constraint, affected bookings, late-window minutes, extra load runs, and cleaning-ready time—not merely show utilization.

Weather, traffic, venue access, delays, and damage remain outside evidence unless entered as buffers or holds. A green result is therefore a planning test, not a promise. Re-run after every booking, crew, vehicle, or inventory change.

Build and Run the Weekend Test in Six Passes

Begin with the operating timezone, depot, weekend crew shifts, and measured vehicle capacity. Enter complete bundles, component counts, unavailable periods, repair holds, and cleaning minutes. One test could use Van 1 at 12 load units, Crew A from 07:00–19:00, and a 90-minute turnaround.

Add every booking’s delivery and collection windows, travel legs, setup and teardown duration, bundle, and load units. Run the model; read FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS; then inspect the first constraint, affected bookings, and late minutes. Rerun after changing one variable: add a 30-minute buffer, assign Crew B, split a van run, or decline the booking.

Export scenarios to the XLSX run sheet; use the inventory-bundle planner for stock and turnaround board for cleaning. guide.md defines fields; scorecard.csv and checklist.csv support review and dispatch. demo_questions.csv, vendor_shortlist.csv, pricing_matrix.csv, roi_calculator.csv, and rfp_questions.csv record discovery, comparison, assumptions, scenarios, and requirements—not proof of costs.

Choose the Right Tool for Weekend Feasibility

Choose the browser calculator when the immediate question is whether a proposed weekend fits. Enter, for example, three bundles, one repair-held arch, a 12-unit van, one crew working 08:00–19:00, 35-minute travel, 45-minute setups, and fixed delivery and collection windows. The result identifies FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS, plus the first broken constraint and minimum corrective change.

Use a general rental platform when you mainly need quotes, deposits, customer records, or dispatch; use a reservation tracker when bookings are simple and manual conflict checks are acceptable. Neither alternative should be assumed to calculate crew sequences, cleaning readiness, or multi-run vehicle loads unless its current documentation proves it.

The optional workbook supports deeper planning: the run sheet sequences stops, the bundle planner exposes component shortages, and the turnaround board tracks cleaning. Filled solo-versus-two-crew examples show the tradeoff between added labor and wider booking capacity.

Verify Assumptions, Evidence, and Saved Decisions

Treat the model as a decision aid, not proof a job will run to plan. Output reliability depends on entered stock, travel, durations, windows, crew shifts, and repair holds. For example, Booking B may show 25 late-window minutes because a 16-unit load requires two van runs; verify route time, parking, venue rules, and handover responsibility before accepting it.

The market evidence is limited and dated. On 2026-08-03, the reviewed results showed one paid tracker, broad rental platforms, a startup guide, and discussion of inventory, distance, labor, damage, and missed-booking risk. Those sources demonstrate relevance, not calculator accuracy, universal demand, or competitor feature absence.

Audit the working files: compare scorecard.csv with the result, run checklist.csv before dispatch, and use demo_questions.csv for missing assumptions. Review vendor_shortlist.csv, pricing_matrix.csv, roi_calculator.csv, and rfp_questions.csv before buying software; save guide.md with the scenario.

Run a Real Weekend Feasibility Check Before Confirming

Start with one proposed weekend, not your entire booking history. Set Europe/Istanbul, depot, one van with 18 usable load units, and a solo shift from 08:00–20:00. Add each complete bundle, component quantities, repair holds, and cleaning minutes. Then enter booking A: delivery 09:00–10:00, 45 minutes travel, 60 minutes setup, 12 load units; booking B: delivery 11:30–12:00, 35 minutes travel, 45 minutes setup, 10 load units. Include collection and teardown windows rather than assuming the outbound plan proves the return plan.

The calculator returns FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS, plus required load runs, late-window minutes, overlaps, cleaning-ready times, utilization, and the first failing constraint. Treat its result as a planning test based only on entered durations and availability; traffic, access delays, weather, and unexpected damage remain operator judgments. Adjust one input at a time so the corrective change stays visible.

Convert the First Constraint Into a Measurable Action Plan

After the run, record the constraint, affected booking, and minimum correction. If booking B misses its 12:00 cutoff by 25 minutes because the van needs a second trip, test three scenarios: extend the window to 12:30, assign a second 10-unit vehicle, or reduce the bundle by two load units. Compare feasibility, late minutes, crew overlap, and vehicle utilization. The cheapest change may still be fragile if it leaves no recovery buffer.

Export the run sheet for dispatch, verify complete sets in the inventory-bundle planner, and hold returns on the turnaround board until cleaning-ready. Filled solo-versus-two-crew examples demonstrate sequence auditing, not a prediction. Use checklist.csv before confirmation, scorecard.csv for the decision, and roi_calculator.csv for editable costs. Next, enter one real pending booking, rerun one correction, and confirm late minutes reach zero without creating an inventory, crew, cleaning, or vehicle conflict.

FAQ

Who is this soft play weekend capacity calculator for?

It is for small soft-play, bounce-house, and toddler-party rental operators who need to test a proposed weekend before accepting bookings. The calculator models limited bundles, vehicles, crews, travel, setup, collection, cleaning, and repair holds together. It is a planning aid for operational feasibility, not a replacement for contracts, dispatch judgment, safety checks, or a full rental-management platform.

What information do I enter into the calculator?

Enter the weekend dates, operating timezone, depot, crew shifts, vehicles, and usable load capacity. Then add complete bundles with component quantities, unavailable periods, repair holds, and cleaning duration, followed by each proposed booking’s delivery, event, collection, travel, setup, teardown, bundle, and load requirements. Results are only as accurate as these inputs and the operating assumptions you record.

What results does the calculator provide?

The calculator returns FEASIBLE, INFEASIBLE, or FEASIBLE WITH EXCEPTIONS for the proposed weekend. It also shows inventory conflicts, required vehicle-load runs, crew and time collisions, late-window minutes, cleaning-ready times, utilization, affected bookings, exception flags, and the first constraint that breaks feasibility. You can adjust a booking, window, bundle, vehicle, or crew and rerun the scenario.

Is the soft play rental capacity calculator free?

Yes. The public browser calculator costs $0 and includes the core feasibility test, examples, visible preview, and save or export workflow described for the free product. No paid upgrade is required to receive a result or identify the constraining resource. Because it is a decision model, it does not verify real-world traffic, staff attendance, equipment condition, measurements, or data entered by the operator.

How does the optional $19 upgrade differ from the free calculator?

The optional $19 upgrade is offered only after the operator records a first real checkout. It extends the workflow with more detailed XLSX operations tools for bundle-level stock, vehicle-load runs, setup and collection windows, cleaning turnarounds, exception flags, and filled solo-versus-two-crew examples. The free calculator remains usable and retains its core inputs, feasibility result, conflict checks, examples, and save or export workflow.