Product

Scheduling and operations

Scheduling and operations in Stackap Business turns a confirmed customer into a booking, a recurring plan, a job with a checklist and a crew that checks in on site.

What it does

The booking is the spine of the whole system. It joins a client, a service, a time, an assigned team, a price, a payment status and the lead source. Creating, rescheduling and reassigning a booking each happen as one atomic database operation, and an availability engine with conflict checks stops a worker being booked twice.

Recurring work is generated rather than re-entered. A recurring schedule produces bookings on a rolling basis, accepts one-off exceptions, can be paused or cancelled, and feeds a forecast of future revenue. Jobs add a checklist, photos, expenses and a budget line by line, so the cost of a job can be compared with its price.

Crews have their own portal. Workers see their jobs on a map, check in and out with location distance rules, and are flagged if they check in late. Availability and overrides are tracked per worker, and a calendar view shows the schedule.

How it works

Cleaning is where this is deepest, including multi-property clients and team assignments. The same booking model carries towing, pest control and salon work, each with its own services and rules, but with less proof behind it.

Early-access scope

• Route optimization exists in code, but how well it performs across large crews has not been evaluated. We do not claim automatic dispatch optimization.
• There is no general timesheet. Time is recorded as job sessions and check-in and check-out, which is enough for jobs but not a full time-and-attendance product.
• Inventory is partial: items and material links exist, but stock levels, locations and warehouses do not.
• The native mobile app is separate from this software. The crew portal works in a browser and installs as a web app.

Questions

Last updated 2026-10-03.