"Maintenance Schedules: interval plans that never miss a service"

What it is

Maintenance Schedules is a small, self-contained tool inside Equipment (and Fleet) for the one job neither section does automatically: reminding you when a specific unit is due for a specific service. Age, calibration windows, and rental pressure are things Verinode reads and flags on its own from your equipment records. A recurring oil change, filter swap, or coil clean is different: nobody logs "change the filter every 90 days" as a purchase invoice or a condition note, so Verinode has no way to know that cadence unless you tell it once.

That is what this tool is for. You pick an asset, a piece of equipment or a fleet vehicle, name the service, and set how often it repeats. Verinode tracks the rest: it computes when the service is next due, flags it as it approaches, and rolls the date forward the moment you mark it done. This is not part of the equipment detector and does not feed a peer benchmark or a Findings decision. It is a plain, operator-set reminder list, the restoration-specific equivalent of a maintenance log, minus the spreadsheet.

Where to find it

Maintenance Schedules is not a page of its own. It opens as a center overlay (Verinode calls this a "deck") from the Take Action row on two sections:

• Equipment, at iq.verinode.ai/equipment
• Fleet, at iq.verinode.ai/fleet

On both, look for the tile labeled Maintenance Schedules with the subtitle Never miss a service. It sits alongside the Ask IQ tile and your open decision tiles, marked with a small pulsing Live dot in the top right and a Start pill in the corner. Click anywhere on the tile and the overlay opens on top of the page, your left sidebar and the IQ agent panel stay live behind it. On mobile, the same tile appears on the Equipment home screen.

The Overview tab

Overview is what you land on the first time you open the deck. It always shows three things:

• A short line of value: "Set the service interval once." with the reason underneath: "We flag what's due so a filter, an oil change, a calibration never slips."
• A "What you'll get" preview: a sample "Coming due" list showing what a filled-in schedule looks like, for example an air mover due for a filter change in a matter of days, a box truck due for an oil service in a few weeks, and a dehumidifier on a 90-day coil-clean cadence. A caption underneath is explicit that this is a sample: "Example. Yours flags what's due as you set intervals."
• A "Your schedules once you start" block. Before you have set anything, this is a placeholder, two dashed, muted rows reading "What's due, soonest first" and "Overdue services, flagged", showing you the shape of the real list without faking data.

While you are on this tab, a button pinned to the bottom of the overlay reads Set a maintenance schedule. Clicking it jumps you straight to the Set a schedule tab, so you never have to hunt for where to start.

The Due tab

Once you have at least one schedule, a second tab appears in the strip across the top, labeled Due, with a small count next to it showing how many schedules are on file. (This tab is not shown at all until your first schedule exists, an empty tab is not part of the design here.)

Each schedule is a single flat row, soonest due first:

• Top line. The asset name and the service name together, for example "Air mover #3 · Filter change" or "Box truck · Oil service."
• Second line. The cadence, then the due read-out, separated by a middle dot: "Every 90 days" (or miles, or hours, matching whatever unit you set), then one of:

- "Due in N days" when the next service is still ahead, in plain text. - "Due today", in Ember Red, when today is the day. - "Overdue by N days", in Ember Red, when the due date has already passed. - "Not yet serviced", when the schedule has never had a last-service date recorded. - "Last done [date]", when the interval is set in miles or hours rather than days, which has no due-date countdown (more on why below).

• Two controls, right-aligned. Remove, a plain text link that deletes the schedule outright with no confirmation step, and Serviced, a bordered button.

Rows are sorted by next-due date, soonest (and any overdue rows, which sort even earlier) first. Schedules with no computed due date, because they run on miles or hours, or because they have never been serviced, sort to the bottom of the list.

Marking a schedule Serviced

Clicking Serviced does two things in one step: it stamps today as the schedule's last-service date, and it recomputes the next-due date by adding the interval to today, not to the old due date. That distinction matters. If a filter change was overdue by two weeks and you finally get to it, clicking Serviced does not just push the original due date out by the interval, it resets the clock from the day you actually did the work. The next due date is always "today plus the interval," so a late service never leaves the schedule permanently behind.

This only produces a new due date for day-based intervals. A schedule set in miles or hours records that it was serviced today, but has no next-due countdown to roll forward, since Verinode has no live odometer or runtime reading to compare against (see below).

Remove deletes the schedule entirely, it does not pause it or archive it. There is currently no way to pause a schedule from this list, only to delete it or let it run.

Setting a new schedule (the Set a schedule tab)

This tab is always present, whether or not you already have schedules running. If you have no equipment and no fleet vehicles on file at all, it shows a single line instead of a form: "Add equipment or a vehicle first. Schedules build on your assets." Add a unit or a vehicle first, then come back.

Once you have at least one asset, the form asks for four things:

1. 1Asset. A dropdown grouped into two sections, Equipment and Fleet, listing every unit and vehicle you have on file by name. It defaults to your first piece of equipment (or your first vehicle if you have no equipment logged).
2. 2Service. A free-text name for what you are scheduling, for example "Filter change" or "Oil service." There is no preset list, you write it the way you would say it.
3. 3Every / Unit. A number and a unit dropdown: days, miles, or hours. The form opens defaulted to 90 days, adjust either field to match the real cadence.
4. 4Last done. A date picker, defaulted to today. This is the anchor Verinode uses to compute the first due date.

If you pick miles or hours instead of days, a line appears under the fields: "We record the cadence and when it was last done. A due-date countdown needs a day-based interval." Verinode has no way to read a live odometer or an hour meter, so a miles- or hours-based schedule tracks the interval and the last-service date faithfully, it just cannot count down to a specific calendar date the way a days-based schedule can.

Click Set the schedule to save it. If you have not picked an asset, left the service name blank, or left the interval at zero, the form stops you with: "Pick an asset, name the service, and set an interval." Once it saves, the service-name field clears so you can add another schedule to the same asset right away, but the asset and interval fields stay as you left them, which is convenient if a single truck has three or four separate services on different cadences.

Empty states, summarized

• No equipment or vehicles at all. The Set a schedule tab reads "Add equipment or a vehicle first. Schedules build on your assets," and the Overview tab's preview block still shows the sample "Coming due" list so you know what you are working toward.
• Assets exist, no schedules set yet. The Due tab does not appear in the tab strip. Overview shows the two dashed placeholder rows, "What's due, soonest first" and "Overdue services, flagged."
• At least one schedule exists. The Due tab appears with its count, listing every schedule soonest-due first, red where something is due today or overdue.

Best-practice example

Say you run three air movers, a dehumidifier, and a box truck. Open Maintenance Schedules from the Equipment Take Action row and go to Set a schedule. Add a filter-change schedule on the first air mover at every 90 days, a coil-clean on the dehumidifier at every 90 days, and an oil service on the box truck at every 5,000 miles. The days-based schedules get real due dates; the miles-based one records the cadence but waits for you to log service manually since there is no live odometer feed.

A few weeks later, open the deck again. The Due tab shows the air mover's filter change due in a matter of days and the dehumidifier's coil clean further out, sorted with the soonest first. When the filter change comes due, do the work and click Serviced, the row recomputes its next due date from that day forward and drops back down the list behind everything else. If you let one slip, it turns red and reads "Overdue by N days" instead of quietly falling off the list, so a missed service stays visible until you clear it.

Related articles

• Equipment: your fleet at a glance
• Take Action: equipment decisions and empty states
• Condition tab: the gauge cluster and attention lists

Data sources