An inspection submission always belongs to a jobcard. The jobcard owns its own jobs — labour and parts under each — so when an inspection turns up something that needs work, the place to record it is as a new (or updated) job on the same jobcard.
How the link works
- A submission is attached to a jobcard (
inspectionSubmissions.jobcardId) - The submission's schema is snapshotted at creation, so the questions and statuses stay frozen even if the template later changes
- Any jobs added to the same jobcard sit alongside the submission; both appear on the customer-facing printout
If you mark an item Rectified while filling the inspection, Pistonlog lets you update parts on the jobcard right there — see Rectified + update parts.
Translating findings to work
There isn't a dedicated "create job from inspection item" button — when an Advisory or Failure prompts new work, add the job from the jobcard's Jobs section as you normally would, with a description that references what the inspection found. The customer-facing print places jobs and the inspection report next to each other, so the relationship reads cleanly without a hard link.
When to add an Advisory vs a new job
- Advisory — flag it for the customer's awareness; not always work that's needed today
- New job marked
recommended— work you've offered the customer that they may want next visit (see Job authorisation statuses) - New job marked
authorised— work the customer has agreed to, do it now