HELP
Time & Scheduling

Recurring Schedules

Repeating job templates that auto-generate jobs on a schedule. Maintenance contracts, regular service routes, monthly inspections.

Updated May 4, 2026 · 6 min read · For Owner

If you have customers on maintenance contracts or regular service schedules, you don’t want to create the same job every week or month. Recurring schedules handle that automatically: define the template once, Conduit generates the jobs ahead of time on the cadence you set.

01Create a recurring schedule

From the Recurring page (top nav), click + New Schedule. One modal covers the whole template — who it’s for, how often, who runs it. Conduit saves the schedule and uses it to auto-generate jobs going forward.

  1. Title. Descriptive: “Monthly HVAC Maintenance,” “Weekly lawn service.”
  2. Customer. Required. The schedule belongs to a customer.
  3. Project. Required. Dropdown is scoped to the selected customer’s projects (“Select customer first” until you pick one).
  4. Frequency. Weekly / Every 2 Weeks / Monthly / Quarterly / Annually (covered in tab 02).
  5. Preferred Time. Time of day the generated jobs will be scheduled at (e.g., 09:00 AM).
  6. Day of Month. Adapts to the frequency — Day of Month (1–28) for monthly+, Day of Week for weekly/biweekly.
  7. Start Date. When the schedule kicks in. First job generates at or after this date.
  8. End Date (optional). Leave blank for indefinite. Set a date to stop generating after.
  9. Assign To. Default technician for every generated job. Unassigned is allowed; you can assign per-job after generation.
  10. Create Schedule. Submit. The schedule lands in the list (tab 04) and starts generating per the rule.
New Recurring Schedule modal: Title, Customer, Project, Frequency + Preferred Time row, Day of Month, Start Date + End Date row, Assign To, Description, Create Schedule button
One modal covers the whole template. The Day field adapts to the frequency you pick — day-of-week for weekly, day-of-month for monthly+.

02Frequency

Pick how often the job recurs. The five fields below define the cadence completely — Conduit uses them to compute the next run date every cycle.

  1. Frequency dropdown. Weekly / Every 2 Weeks / Monthly / Quarterly / Annually.
  2. Preferred Time. Time of day generated jobs are scheduled at (e.g., 09:00 AM).
  3. Day field. Adapts to the frequency — day-of-week (Mon–Sun) for weekly/biweekly, day-of-month (1–28) for monthly/quarterly/annually.
  4. Start Date. When the schedule kicks in. First job generates on or after this date.
  5. End Date. Optional — leave blank for indefinite. Set a date to stop generating new jobs after that point.

The frequency summary shows on each schedule card in the list view: “Monthly on the 15th at 09:00.”

New Recurring Schedule modal focused on the cadence block: Frequency, Preferred Time, Day of Month, Start Date, End Date
Same form, focused on the cadence block. Frequency drives the day field (day-of-week for weekly, day-of-month otherwise).

03Generate days ahead

The generate days ahead setting controls how far in advance jobs are created.

  1. Set to 7 — jobs appear on your calendar a week before they’re due.
  2. Set to 30 — month of lead time (good for long-cycle quarterly schedules).
  3. Set to 1 — same-day generation (rare).

A background process runs daily. Each day at midnight (your company timezone), Conduit checks every active schedule and creates the next job if it falls within the lead-time window.

No manual intervention needed. Set it, forget it.

04Manage schedules

The Recurring list shows every schedule with its status, frequency summary, next-run date, generation count, and per-row lifecycle actions inline.

  1. + New Schedule. Top-right button — opens the modal from tab 01.
  2. ‘Active’ status badge. Per-row chip. Active / Paused / Completed (if past end date).
  3. Generate Now. Per-row action. Force-creates the next job today instead of waiting for the schedule cycle.
  4. Pause. Per-row action. Stops generation temporarily; switches to Resume when the schedule is paused. Existing generated jobs stay.
  5. Frequency summary. Auto-generated under each card title — “Monthly on the 15th at 09:00,” “Quarterly at 08:00,” etc.
  6. Next run + Generated count. Subtitle line shows when the next job will generate and how many jobs this schedule has produced to date.
Recurring Jobs list with + New Schedule button, three Active schedules, each with frequency summary, next-run date, generated job count, and Generate Now / Pause / Edit / Delete row actions
The list. Each schedule's frequency, next-run date, and generation count surface inline; per-row actions handle the lifecycle.

Edit and Delete sit next to Pause on each row. Edit opens the schedule modal to tweak frequency, time, or assignee; Delete removes the schedule but leaves already-generated jobs intact (they exist independently once generated).

05What gets created

Each generated job inherits:

  1. Title from the schedule (with date stamp appended optionally).
  2. Customer + Project.
  3. Job type, priority, assigned technician.
  4. Scheduled time based on the frequency rule + preferred time.
  5. Default duration if you set one on the schedule.

Your technicians see the generated job like any other job on their dashboard. They can mark it complete, log time against it, invoice it, all the same way.

That’s recurring schedules. Set it up once and Conduit keeps your maintenance work flowing. Next category: Purchase Orders & Vendors.

Was this guide helpful?