Operations
Work Items — every job, one record
Project, job, event, order, delivery, service call — one shape for every kind of work. Tasks, files, assignments, status, and history all live under the work item.
The problem
Different industries call them different things — projects, jobs, deliveries, calls — but the data shape is almost always the same. Maintaining seven separate concepts is a tax on the team.
How it works
- Step 01
Create the work item
Pick the type, attach a client, set due date + priority.
- Step 02
Add tasks + assignments
Break it down into tasks, assign to team members, attach files.
- Step 03
Track to completion
Move through draft → scheduled → active → completed; activity log captures every change.
What's included
Universal type field
Pick from project, job, event, order, delivery, service_call, invoice_only.
Tasks + assignments
Built-in task list with assignees + due dates.
File attachments
Attach photos, docs, PDFs — stored in S3 (see Storage architecture).
Priority + status
low / medium / high / urgent; draft → completed.
Calendar-aware
Schedule events created from work items show in the calendar.
Activity log
Every status change and field edit is timestamped + user-attributed.
Why teams choose this
- One data shape across every kind of work the team takes on.
- Reusable across industries — same record powers a service call and a multi-day construction job.
- Calendar + tasks + files + activity all hang off the same row.
- Reports and dashboards aggregate across types without per-type wiring.
What it looks like
Screenshot
Work item detail
Screenshot
Task list
Screenshot
Assignment grid
Use cases
Field service ticket
Service call with one task, one tech, one invoice.
Multi-day project
Construction job with phased tasks, milestone payments, multiple assignees.
Recurring delivery
Standing weekly delivery with route + driver assigned.
Works well with
Frequently asked
What's a work item exactly?
A polymorphic record that backs every kind of work — a service call, a multi-day project, a delivery, an event. Type is a field, not a table.
Do I have to pick a type?
Yes — but you can change it later. The default is 'project'.
Can a work item have no client?
Yes — internal jobs or work for future-prospects don't need a client link.
How does this differ from 'jobs' in other tools?
Most tools call a work record a 'job' and bolt on extra concepts for projects, deliveries, events. We unified them — same record, different type.
Can two people own a work item?
Yes — assign as many team members as you need. Each gets the work item on their My Work dashboard.
Are files attached to work items public?
Visibility is per-file. Default is organization_only. See the Files feature for the full taxonomy.
Try Work Items — every job, one record
Free for small teams. Activate it on your account in one click.