Project Checklist guides · Reference

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.

Project Checklist keeps each job's board data in a small store that ServiceM8 provides. Every job gets its own store, and every store is the same size: 64 KB. That is the one hard limit in the app. ServiceM8 sets it, so it cannot be raised.

Notes, time entries and files do not count. They are ServiceM8 records on the job. The limit is about the board's own planning data: statuses, dates, estimates, materials, links and settings.

What uses the space

Two things share a job's store.

Every task has a small record. What it costs depends on what the task carries.

A task with… costs about
a status only 150 bytes
dates and an estimate 250 bytes
materials or files 350 to 500 bytes
each dependency link 150 bytes more

Archived tasks keep their record. Restore needs it. So an archived task still counts.

The board's own settings. List order, colours, nesting, and the time-entry note map. 5 to 10 KB on any board, and it does not grow much: the note map is capped.

How many tasks is that

Over a job's whole life, live and archived together:

Shape of job Tasks, about
Checklist job. Statuses, few dates. 350
Planned project. Dates, estimates and dependencies on most tasks. 180
Planned, with materials or files on most tasks. 120

A normal project never comes near these. The boards that do are the ones that never end: a weekly meeting log, a standing maintenance job, a year-long retainer.

How to see where you stand

Open the board's ⋮ menu and choose Board settings. The Storage section shows a bar against the 64 KB, and what is using it: board settings, live tasks, archived tasks, and the parts of each.

When a board reaches 250 tasks, or 80% of its store, a row appears in Needs attention. It links to the same section.

What to do when a board is getting full

Archiving does not free space. The archived task keeps its dates and materials so it can be restored.

What frees space is spreading the work across jobs. Every job has its own 64 KB, and a parent board shows all of its children.

  • Start the next phase as a child job. ⋮ menu > Child jobs… > Create a new job. The child shows on the parent's board, so nothing is lost from view.
  • Convert a list to a child job. List menu > Convert to child job… The list's tasks move to the new job, with their dates and materials.

For a board that never ends, start a new child job each quarter or each year.

What happens at the limit

Nothing is lost. A save that will not fit is refused, and the board says so. Move some work to a child job, then save again.