Read before you plan.
Four short reads on the ideas behind Project Checklist: what makes a job a project, which view to work in, how to set one up, and what to do when the plan slips. Read them in order the first time; after that, dip in.
-
Is this a job, or is it a project?
Most work in ServiceM8 is a job and should stay that way. Here's how to spot the work that needs more than a job can hold.
Read the guide → -
Board or Timeline: which one for this project?
Project Checklist gives you several ways to look at a project. Two of them are where you'll spend your time, and one question tells you which.
Read the guide → -
Setting up your first project
From a marked job to a working board. Build it by hand, write the whole thing as plain text, or save a finished project as a template for next time.
Read the guide → -
Working the plan when it changes
Materials didn't land. The plan you built on Monday is wrong by Wednesday. Here's what Project Checklist does about it, and what it deliberately doesn't.
Read the guide →
Take all four with you: PDF · Markdown
-
Template guide for AI assistants
The plain-text template language: lists, tasks, notes, ids, durations, effort, dependencies and a start date, with a complete example. Give this page or the .md file to an AI assistant and describe the job. Read it · Download the .md
-
Limits: how much one job can hold
Each job's board data lives in a 64 KB store that ServiceM8 provides. What uses the space, what a task costs, three shapes of job measured against the limit, and what to do when a board is getting full. Read it
-
FAQ: what it does, what it does not, and how it behaves
Straight answers: what the app is and is not, where the data lives, what it will not do that a construction platform does, and why an add-on polls, waits and saves the way it does. Read it · Download the .md · Download the PDF