See the work as a kanban board.
One column per list. Drag a card to move it. Statuses are yours to define, so a checklist can say things a job status can't.
Lists, statuses, dependencies, dates, time, materials and files on every task, with a Timeline and Calendar to see the plan. Big jobs split into child jobs that roll up to one board. Tasks stay native ServiceM8 checklist items, so the crew keeps ticking them in the app.
Every view reads the same job checklist. Pick the one that fits the moment. Nothing to sync, nothing to copy.
One column per list. Drag a card to move it. Statuses are yours to define, so a checklist can say things a job status can't.
Gantt charts show tasks with dependency arrows and the longest chain. Move one date and the cascade proposes new dates for everything downstream.
Scheduled tasks on their days. Unscheduled ones wait down the side until you drop them in.
Status, dates, estimate, tracked and billed, one row per task. The place for bulk edits.
A multi-job project drawn as a mind map. Parent, child jobs, lists and tasks, with a detail panel for whatever you click.
In Progress, Up Next, On hold. Whatever fits your work. Reminders, assignment, starring and watching on every task.
Start, end, duration, effort and what each task waits on. The cascade respects the working week and who is available.
Track time on a task and bill it. Post materials to the job in one click. Billed against unbilled, per task and per project.
Attach from the device or from the job card. Mark a file restricted so only the right staff can open it.
Turn a list into its own child job. The parent board rolls up every child's tasks, time and money in one place.
Lists, tasks, durations, effort and dependencies. Never dates. Apply one and the plan is scheduled from day one.
Changes reach every board in about 30 seconds. Needs attention flags overdue and blocked work. Read-only snapshots for clients. Per-staff access.
The Project Summary lists progress, overdue count and risk for every project. Who did what goes into the job diary.
Four short reads on the ideas behind the add-on. Ten minutes, start to finish.
Most work in ServiceM8 is a job and should stay that way. How to spot the work that needs more than a job can hold.
Read the guide →Several ways to look at a project. Two are where you'll spend your time, and one question tells you which.
Read the guide →From a marked job to a working board. Build it by hand, write it as plain text, or save a finished project as a template.
Read the guide →Materials didn't land. Monday's plan is wrong by Wednesday. What the add-on does about it, and what it deliberately doesn't.
Read the guide →Four short reads: job or project, Board or Timeline, setting up your first project, and working the plan when it changes. Ten minutes, start to finish.
Straight answers: what the app is and is not, where the data lives, and why it polls, waits and saves the way it does.
Teaches ChatGPT, Claude or Copilot the template language. Give it the file and describe the job; it hands back a template ready to paste.
Project Checklist installs straight into your ServiceM8 account. Use the link below to activate it. Not sure yet? Try the interactive demo first, on a sample job.
Honest disclosure of the technical caveats. Mostly common-sense, worth flagging up front.
The board opens from the job card in the Online Dispatch Board (the web app). Field staff don't need the board: tasks are ordinary ServiceM8 checklist items, so they see and tick them in the ServiceM8 app as usual, and the board picks that up within about 30 seconds.
Nothing leaves ServiceM8. Tasks are native job checklist items. The board's extra data (statuses, plans, materials, links, order) is kept in ServiceM8's own add-on storage for that job, private to this add-on. Uninstall and your checklist items are still on the job.
The add-on writes checklists, notes, materials, attachments, bookings and contacts, so its permission list is long. It only touches the jobs you open a board on, plus a few account-wide settings notes it keeps for templates and preferences.
Accounts on the earlier release (v0.6, the Checklist Kanban era) were upgraded in place in August 2026. Each job migrates the first time its board is opened. The old notes are kept read-only, so nothing is lost and support can roll a job back if ever needed.
Time recorded on a task is written as a job note in a format Job Time Entry (4.2 and later) understands, so project time can also be logged from Job Time Entry and shows up against the right task on the board.