Booked something twice, or put a job in for the wrong customer? Delete it. It's the small bin icon in the bottom-left of the job's edit screen.
Where to find it
Open the job, tap the pencil to go into edit mode, and the bin sits to the left of Cancel and Save. That's the same place on your phone, on the Jobs list and on the schedule.
You'll only see it if your role can delete jobs. Owners and managers can by default; if an engineer needs to, that's a permission you switch on in Settings.
What happens to everything attached
Mucka tells you before you commit. If the job has anything on it, the confirmation names it:
This job has 1 invoice and 1 certificate attached. Deleting unlinks them, they stay on file but won't show this job. Delete anyway?
Nothing attached is deleted. Invoices, quotes, work orders and certificates all survive — they simply stop pointing at a job that no longer exists. You'll still find them in their own lists, and an invoice you've already sent is still owed and still chaseable.
That matters most for certificates. A gas or oil certificate is a legal document and deleting the job never destroys it, but it will no longer show against a job, so it's worth being sure before you go ahead.
When Mucka won't let you
- The job is in progress. Someone's on site. Complete it or cancel it first, then delete.
- The job came from JobLogic. Anything mirrored from JobLogic is read-only here — delete it in JobLogic and the change syncs back.
Common gotchas
- There's no undo. The job itself is gone for good. If you only want it off the board, cancel it instead — that takes it off your diary and out of your connected calendar while keeping it on the customer's record. See Cancel a job.
- Deleting one of a recurring series deletes that one occurrence, not the series.
- The customer isn't told. Deleting is a tidy-up on your side. If they're expecting you, message them as well.
- Anyone assigned gets a cancellation notification on their phone, so they stop planning around it.