Skip to main content
LockLedger

Creating tasks and PM schedules

How a task template works, how to link it to more than one machine, and how a PM (preventive maintenance) schedule keeps recurring work firing on its own.

Updated September 25, 2026AdminManager

A task is a work template — a title, a set of details, and a required-parts list — that gets linked to one or more machines. It's what a ticket actually points to when work needs to be scheduled or logged against a specific piece of equipment.

Creating a task

From Tasks, New Task creates a task already linked to one machine (you'll pick which one from the form) — a task can never exist with zero linked equipment, so creation and that first link happen together. From there, fill in the title, details, and expected hours, and use Add Parts to set the required-parts list.

Linking more than one machine

If several machines at a site all get the same procedure — say, a filter change that applies to four identical pumps — one task can cover all of them. Use Link another machine in the Linked Equipment section to add another piece of equipment from the same site. The task's title, details, and required parts are shared across every linked machine; there's exactly one required-parts list, not one per machine.

What isn't shared: each linked machine gets its own independent PM schedule. Select any machine in the Linked Equipment list to switch to editing its own due date, interval, last-done date, and history without affecting its siblings.

A task is locked to one site

Every machine you link to a task has to be at the same site the task was created for — the Site field is fixed and read-only once a task exists. Link another machine only offers equipment at that site.

Removing a linked machine

Remove on any row in Linked Equipment unlinks that machine and discards its PM schedule — the task keeps running for whatever's left. The last remaining machine can't be removed this way, since a task can't exist with zero links; delete the task instead if you want it gone entirely.

PM schedules

Turning on Is PM for a machine reveals its schedule fields: PM Interval Days (how often it recurs), PM Due Date, Last PM Date, and PM Status. Once a task is PM-enabled, LockLedger creates a ticket for it automatically as the due date approaches — no one has to remember to schedule it by hand. When that ticket is completed, Last PM Date and the next PM Due Date roll forward on their own, based on the interval.

Status moves from Current → PM Needed → Overdue on its own as the due date approaches and passes.

Linking a new machine to an existing PM task

If the task you're linking to is already PM-enabled, the new machine inherits that PM interval automatically — you're only asked for its own due date. This keeps a newly-added machine on the same recurring schedule as its siblings from day one, instead of silently starting out with no schedule at all. Link stays disabled until that due date is filled in.

A due date is required, not optional, on a PM task

Every machine on a PM task needs its own due date — there's no fallback or default to guess one for you. If you're not sure yet, pick your best estimate; you can always correct it later from that machine's own schedule.

Open Tasks

Not using LockLedger yet? Join the pilot

support@getlockledger.com