Build the schedule from agreed work

Start with the service obligation and site, then assign a visit. RUNLY keeps due work, planned visits and completed work connected. An agreement’s operational cadence and its billing cadence can be managed separately.

A practical weekly planning routine

Review due work before filling the calendar. Confirm the site, expected scope and eligible staff. Check availability and overlapping work; RUNLY surfaces dispatch conflicts and requires a recorded reason for an override.

  • Review due recurring work and open service exceptions.
  • Choose the visit date and assigned staff.
  • Check conflicts and any missing-parts warning.
  • Give the field team the information needed to start.

Handle a customer moving a clean

Suppose a Tuesday clean moves to Thursday. Reschedule the existing service visit and record the reason rather than creating a second billable job. Check Thursday’s staffing conflicts, then review whether the recurring agreement itself needs any change. This example describes a workflow, not an automatic customer-notification service.

Handle a job that needs a second visit

Keep unresolved work open and arrange a return against the same work order. The original technician’s recorded time and materials remain part of its history. Review the agreement’s charging terms before billing.

Questions to test in a demo

Bring a real scheduling exception using sample data. Check crew eligibility, cancellation, reassignment, conflicting visits and the next due date. If you need driving-route optimization, SMS reminders or a customer booking portal, ask about those explicitly; they are not implied by the calendar.

See whether RUNLY fits your business

We’ll walk through the work that matters to you and discuss the scope of onboarding.

Request a demo