Tickets and required parts
How a ticket's required parts come from its task, how they get confirmed when the work is done, and how to override them for a ticket that genuinely needs something different.
A ticket doesn't have a live connection to its task's parts list — it takes a snapshot the moment it's linked, the same way everything else in LockLedger treats a template as a starting point, not an ongoing rule.
Where required parts come from
When a ticket is linked to a task, its Required Parts field is copied from whatever that task's template says right now. If you edit the task's required-parts list later, existing tickets already linked to it don't change — but a ticket does resync automatically every time its linked task changes, picking up that task's current template at that moment.
A task shared across several machines has one required-parts list, not one per machine
A task linked to more than one piece of equipment shares a single required-parts list across all of them — each machine gets its own PM schedule, but not its own parts list. See Creating tasks and PM schedules for how a task's own setup works.
Confirming parts at completion
Closing a ticket (Clock Out) is gated on confirming what parts actually got used. You'll be asked to confirm quantities against the required list — or say no parts were used at all — before the ticket can complete. If the job needed something the task's template didn't call for, you can log extra parts the same way; that doesn't change what was "required", it just records what actually happened.
Overriding required parts on a ticket
Sometimes a specific ticket genuinely needs a different parts list than its task's template — a one-off repair on a PM ticket, for instance. An Admin or Manager can set that directly from the ticket form with Override Required Parts. The field then shows an — Overridden label so it's obvious at a glance that this ticket isn't following its task's template anymore.
An override is permanent, not a one-time skip
Once a ticket is overridden, it stops automatically resyncing from its task — forever, not just for this save. Even if you later change which task the ticket is linked to, the required parts won't update on their own anymore. Most people assume changing the task relinks the parts list too; on an overridden ticket, it doesn't.
To go back to following the task's template, an Admin or Manager uses Resync from Task on the same ticket. That clears the override and immediately re-derives the required parts from whatever the linked task currently says.
Not using LockLedger yet? Join the pilot
support@getlockledger.com