Operations

Jobs

Work phases within a project — defining scope, budget, and timelines for structured project delivery.

A job is the primary subdivision of a project. Where a project represents the overall client engagement, a job represents a distinct phase, workstream, or deliverable within it. Tasks and time entries can be attached to a job, which is in turn attached to a project. This hierarchy — Project → Job → Task → Timesheet — gives you cost tracking at every level of granularity.

The New Job form, and the cards and tabs on a job's page.

Accessing Jobs

Navigate to: Operations → Projects → Jobs view → New, or open a project → Jobs tab → New Job

A job always belongs to a project; the Project field is pre-filled when you start from the project page.

Job Fields

Job — field reference

Field	Required?	Details
Project	Yes	The project this job belongs to. Pre-filled when creating from within a project page.
Job Title	Yes	The name of this phase or deliverable. Should clearly identify what this job covers: "Phase 1 — Discovery and Requirements", "Backend API Development", "Site Installation — Singapore", "Post-Launch Support".
Description	No	Scope, objectives, or acceptance criteria for this job. Useful for defining what "complete" means for this job.
Manager	No	The team member responsible for delivering this job.
Budget	No	The budget allocated to this job in monetary terms. Shown as a card on the job page and as the Budget column in the Jobs view.
Hourly Rate	No	A default rate per hour for time logged against this job.
Start Date	No	Planned start date for this job.
End Date	No	Planned end date for this job. Not enforced — work continues until the job is manually marked complete.
Delivery Date	No	The committed date for this job's deliverable, as agreed with the client. Separate from End Date.
Status	No	Not Started (default), In Progress, On Hold, Completed, Cancelled.
Deliverables	No	A list of specific outputs expected from this job, shown as a checklist on the job page.

Job Status Options

🚨On Hold and Completed are stored the wrong way round

The status picker and the job page's Mark Completed / Put On Hold actions do not store what they say. Choosing "Completed" saves the job as On Hold, and choosing "On Hold" saves it as Completed — the numeric codes the form sends are the reverse of what the server reads. The job detail page then re-displays the picker's own labels, so it looks correct there, while the projects list, the job counts, and every report read the server's value and show the opposite.

Until this is fixed: do not trust a job's status on the detail page, and do not use status to drive any decision. If you must record completion, say so in the description. "Cancelled" is also not a status the server recognises for a job, so a job marked Cancelled is stored as a value with no meaning.

Status	Meaning
Not Started	Job is defined but work has not begun. The job page offers Mark In Progress.
In Progress	Work is active. Team members log time and costs accrue.
On Hold	Intended for work temporarily paused. Picking it currently stores the job as Completed on the server — see the warning above.
Completed	Intended for a job whose deliverables are all accepted. Picking it currently stores the job as On Hold on the server — see the warning above.
Cancelled	Offered in the picker, but the server has no Cancelled state for a job. Time already logged is retained either way.

Status does not gate time entry — the form accepts time against any job the team member can see.

The Job Page

The job page shows four cards — Budget, Hours Logged (from its tasks' time), Tasks (done / total) and Deliverables — and a progress bar, followed by eight tabs: Dashboard, Deliverables, Tasks, Documents, Costing, Comment, Attachment, History. Quick-create shortcuts raise an Invoice, Estimate, Sales Receipt, Bill, Purchase Order or Expense linked to the job's project.

Linking Jobs to Invoices

Documents raised from the job page's quick-create shortcuts are linked to the project and appear on both the job's and the project's Documents tab. Invoice lines are not generated from time entries automatically — use the Hours Logged card and the Costing tab to decide what to bill for each phase.

💡Match job structure to your invoicing cadence

If you invoice clients at milestone completion, create one job per milestone. If you invoice monthly by phase, create one job per phase and invoice all approved timesheets within it at month end. The job structure directly shapes how project invoices are organized, so plan the hierarchy around how your client expects to receive bills.

Projects — the project a job belongs to
Tasks — the work items inside a job
Timesheets — logging time against a job