Trip templates

A trip template is a saved plan plus a recurrence. The plan is everything a trip needs — type, origin, priority, the whole route with its tasks, optionally a driver and a vehicle. The recurrence says which days it should run. Cooriroo then creates the trips for you, ahead of time, on the window you choose.

Templates are for work that repeats: a morning restaurant run, a Tuesday and Thursday warehouse shuttle, a monthly service visit. For a route you will run once, or twice, use the trip wizard directly — it can also start from a template or duplicate an existing trip.

Three groups of settings, and the route.

• The plan. Name, description, trip type, priority, category, origin, estimated duration, notes, tags and any custom fields. A driver and a vehicle can be attached, and every generated trip inherits them.
• The recurrence. A repeat rule, the date it starts from, and the time of day each trip should be scheduled for.
• The generation settings. How many days ahead to create trips, and any dates to leave out.
• The route. The same stops a trip has — location, linked destination, geofence radii, time on site, task order — each with its own list of tasks. Those task definitions are applied to the generated trip once its stops exist.

A generated trip is created as a draft, not as a scheduled trip. Its notes record which template produced it. That gives you a review step: generation fills the week, and a dispatcher schedules what should actually go out.

The recurrence editor offers four presets and a custom builder. Custom lets you repeat daily, weekly or monthly, every N periods, on chosen days of the week, and either forever, after a number of occurrences, or until a date. Underneath it is a standard iCalendar repeat rule, so anything you can express there can also be set through the API.

Generation happens two ways. Automatically, as a scheduled job that walks every active template and fills its generate-ahead window — 7 days unless you change it, and anything from 1 to 365. And on demand, from the template itself, where you pick a date range.

An on-demand run previews first. The preview expands exactly the dates a confirmed run would create, including the ones it would skip and why, so what you approve is what you get. The only thing a preview cannot predict is a live scheduling conflict, since a conflicting trip can appear between the preview and the confirmation.

Both runs report the same two lists: the trips created, each with any conflict warnings, and the dates skipped, each with a reason.

A template is active, paused or archived. Only active templates generate, so pausing is how you stop a recurrence for a holiday period without losing the plan. The templates list filters on exactly these three, plus All, and searches names and descriptions.

Every save bumps the template’s version and stores a snapshot, so the history of a recurrence is recoverable — useful when a route quietly changed three months ago and nobody can remember when.

Deleting a template does not touch the trips it already generated. Those are real trips with their own numbers, statuses and history, and they carry on exactly as they were.