A job is one visit to a client's address. Mucka books the date, picks the engineer and warns you if anyone's double-booked, all before you tap save.
Ask Mucka
Open Mucka and say something like:
"Schedule the Walker boiler install for Tuesday at 9, three hours, give it to Marcus."
Mucka pulls up the client, drafts the appointment with date, duration and engineer, and shows it for you to approve. One tap to send the calendar invite and engineer's job sheet, one tap to dismiss.
If you only know half the details ("book the Walkers in for Tuesday morning"), Mucka asks for the missing bits rather than guessing.
Or use the form
Head to Jobs in the sidebar and tap New job. Fill in:
- Client the work's for
- Job type (boiler install, EICR, breakdown, etc., from your trade's set)
- What's the job? — the work in your customer's words, right under the job type. This is where "renew the cold-water storage tank to comply with the L8 water regulations" goes
- Date and start time
- End date and end time — both default to the same day, so an ordinary job is already filled in. Set the end date to a later day and it becomes a run of days (see Book work that runs over several days).
- Lead engineer (and supporting engineers if it's a two-handed job)
- Internal notes — just for you and your team (access codes, parts to bring)
Hit save and Mucka books it.
Two boxes for words, and the difference matters
The job type is a category — Plumbing Insp., Leak Repair — and it's what your durations, colours and certificate prompts hang off, so it's worth picking a real one. The job itself goes in the two boxes:
- What's the job? is customer-facing. It prints on the job sheet under Work requested, it can go into your confirmation texts as what the job is, and searching for a word in it finds the job.
- Internal notes is not. Gate codes, where the boiler is, the dog in the back garden, anything you wouldn't want read out — it stays inside Mucka and reaches no document and no customer.
Both stay editable for the life of the job, so you can add to either after it's booked. If you book a run of days, every day carries the same description — it's one piece of work, not five.
Underneath the notes on a job you've already saved there's also a Note timeline: dated entries added as the work goes on, which is a different thing again from the job's own two boxes.
Not certain yet?
Tick Pencil it in near the bottom of the form (or just say "pencil them in for Thursday"). The slot is held and shows shaded in the diary, but the customer is told nothing until you confirm it. See pencil a job in.
Double-booking warnings
If the engineer you've picked already has something else on at that time, Mucka flags it inline before you save. That's another job, a personal appointment, or anything in their connected Google or Microsoft calendar. Personal ones just say Personal time — you're told the slot's taken, not what it's taken by. You can:
- Pick a different engineer
- Move the time
- Override and book anyway (sometimes you know two short jobs back-to-back works)
After it's booked
Mucka quietly handles the rest:
- The engineer sees the job on their schedule
- The client gets an appointment confirmation if you've set those up
- The job appears on the Schedule and Live Map pages
- Quote details (if there was one) carry through so the engineer has the price and scope on site
Finished it early?
Got ahead and did tomorrow's job today? Just mark it complete (and invoice it if you're ready). You don't need to move the date first.
The job keeps the date you originally booked it for, so your schedule still shows when it was meant to happen and Mucka can tell you that you finished a day early. What changes is that it stops counting as work you've still got on:
- Mucka won't tell you you're booked in on it
- Your morning and evening summaries won't count it in tomorrow's total
- The slot frees up, so you can book something else into it
- Your receptionist will offer that time to callers again
You still get the credit for it. Ask Mucka what you got done today, or read your evening summary, and it counts everything you actually finished today, whatever day it was booked for: "five done, including tomorrow's boiler swap."
If you'd rather the diary showed the day you actually did it, edit the job and change the date. Most people don't bother.
Job with no client on it?
Sometimes a job lands in the diary before anyone's put a client on it. The job's page shows No client assigned on its Client card.
Tap Assign client on that card (on your phone it's the add-person button, where the edit pencil usually sits), then pick the right person. Typing searches your whole client book, not just the first page. If they're brand new, Add new client inside the picker opens the full new client form, and the job takes them the moment you save. Quotes, invoices and certificates raised from the job pick the client up from there.
A job type and a day is enough to book something. You don't need the client or the address in front of you — put the work in the diary while you're thinking about it and fill the rest in later.
Mucka won't let you forget it, either. Any booked job still short of a client or a work address gets named in your morning briefing and your end-of-day summary — "Flat Roof Install on Monday — no client or address on it yet" — one by one, not as a count. Finished jobs are left out, so nothing chases you about work you've already done and invoiced.
Told Mucka about a job and never came back to it?
Say you fire off a message on WhatsApp — "got that flat roof to do Monday, and a painting job starting Tuesday" — and Mucka comes back asking who they're for. If you get distracted and never answer, that used to be the end of it.
Now it isn't. When Mucka asks you something on WhatsApp and hasn't put anything in the system that turn, it quietly makes a note of what you said. Come back to it and that's the end of it, nothing lands on your list. Leave it a few hours and what you said goes onto your to-do list, in your own words, due first thing the next morning. Answer Mucka and get the job booked and it ticks itself off. Ignore it and it keeps turning up until you deal with it, which is the point.
Whose schedule am I looking at?
The Schedule page shows the whole business by default: every engineer's jobs together. On your phone, tap the filter button next to the date selector and choose Everyone, Just me, or tick the engineers you want to see. On desktop, use the All Engineers filter, and each engineer has their own row.
Booked a time but not picked an engineer yet? The job still shows, marked No engineer assigned in amber, and an Unassigned lane appears so nothing slips through. On desktop you can drag a job out of that lane onto an engineer's row to assign it.
Work address
Some jobs happen somewhere other than the client's own address: a landlord's rental, a managed flat, a second site. Pick the Property on the job and Mucka treats that as the work address.
Once it's set, that's the address everywhere the job appears: the job page, the jobs list, the schedule, your phone, the home-screen widget, CarPlay, the calendar invite, and the arrival time the On Time Tracker works out. Tap it to open maps. The client's address stays on their record for invoicing.
Leave the property blank and nothing changes: the job shows the client's address, same as always.
Mucka won't guess it in silence. If the client has only one address on file, Mucka fills it in for you and asks you to tick that the work really is there. One tap when it's right, and a prompt to pick the real address when it isn't. That matters most for landlords: their own house is often the only address you've got for them, and it's rarely where the work is. If the client has two or more addresses, Mucka asks which one before it lets you save, rather than picking a side.
You can also just ask Mucka. "Set the work address on Monday's boiler service to 5 Central Avenue" does the same thing.
The address doesn't have to be one you've used before. Say a new one and Mucka checks it against Royal Mail, reads it back to you, then saves it as a property under that client, so it's there ready next time. If the client already has the address on file, Mucka picks it up rather than asking you to read it out again.
Naming the tenant works the same way: "the tenant there is Steve Gray, their number's 07709 463387" attaches them to the property, not to a note on this one job. See adding tenants to a property.
Common gotchas
- Recurring jobs (weekly clean, monthly service). Set the recurrence at create-time. Mucka books the whole series in one go.
- Multi-site clients. Mucka asks which property before saving a new job for a client with more than one on file, so you can't send the engineer the wrong way by leaving it blank. You can still choose No property if the work is somewhere you've not been before.
- All-day jobs. Set duration to 8 hours rather than "until done". Mucka uses duration to spot conflicts later in the day.