Projects
In one sentence: A Project is an umbrella record that groups multiple jobs (and their quotes, invoices, purchases, appointments, and timers) for one customer, so a large piece of work can be managed and tracked as a whole.
What Is This?
Some work is too big to be one job. A shop fit-out, a multi-visit installation, a building phase — these involve many separate jobs over weeks or months, often for different teams. A Project ties all of those jobs together under one record for a single customer, with one responsible employee, so the office can see the whole engagement in one place.
A project is not a job itself — it does no work of its own. It is a container: jobs are linked to it, and the project view rolls up everything those jobs produce.
Why Does This Matter?
Without projects, a customer with 15 related jobs is just 15 rows in the jobs list. Nobody can easily answer "how is the Smith warehouse fit-out going?" or "how much time have we spent on that contract?" Projects solve this:
- The office sees all the jobs for the engagement, and how many are still open
- Time logged across all the project's jobs is visible (and exportable) in one place
- Quotes, invoices, and purchase orders raised against the project's jobs are gathered on the project record
- The project cannot be closed while jobs are still open — so nothing falls through the cracks
How It Works
Creating a project
Projects are created from the Projects area (a "Projects" permission controls access to the module).
Required fields:
- Customer — the customer the project belongs to
- Contact — the person at the customer for this project
- Description — what the project is
- Start date — when the project begins
- Assigned Employee — the person responsible for the project (the project manager)
- Store — required only for multi-store businesses
Optional fields:
- Location — the default site for the project
- Due date — when the project should finish
- Budget — a budget amount for tracking (cannot be negative)
While creating, the screen shows the customer's existing projects on the side, so you can check whether a project already exists before creating a duplicate.
Linking jobs to a project
There are two ways:
- Create a job from the project — open the project, go to the Jobs tab, and create a new job. It is linked to the project automatically, and the customer is fixed to the project's customer.
A job belongs to at most one project, and the project and job must be for the same customer.
The project page
The project detail page has tabs that gather everything from the linked jobs:
| Tab | What it shows |
|---|---|
| Project Details | The project's own fields — customer, contact, dates, budget, assigned employee |
| Jobs | All jobs linked to the project, with counts |
| Timers | Time entries across all the project's jobs |
| Appointments | Appointments for the project's jobs (shown if you have the Appointments permission) |
| Quotes / Invoices / Purchases | Shown when linked records exist and you have the relevant permission |
| Attachments | Files attached to the project |
| Messages | Communication on the project |
A project sheet PDF can also be exported from the project, and the project's job timers can be exported to Excel.
Closing a project
When all the work is done, the project is closed. The system checks for open jobs first: if any job linked to the project is still open, closing is refused and you are told how many open jobs remain. Close (or unlink) those jobs first, then close the project.
Key Terms
| Term | What It Means |
|---|---|
| Project | The umbrella record grouping related jobs for one customer |
| Assigned Employee | The staff member responsible for the project overall |
| Budget | An optional amount recorded on the project for cost tracking |
| Open job | A job that has not yet been closed — blocks project closure |
Common Scenarios
Scenario: A customer signs off a large fit-out with many visits
What the customer sees: One engagement, invoiced as the work progresses. What happens in the system: A project is created for the customer; each visit or workstream is a job linked to the project. Quotes and invoices raised on those jobs appear on the project's tabs. What staff should know: Create the project first, then create the jobs from the project's Jobs tab so they link automatically.
Scenario: "I can't close the project"
What the customer sees: Nothing — this is internal. What happens in the system: The close action is refused with a message about the number of open jobs linked to the project. What staff should know: Every linked job must be closed before the project can close. Use the Jobs tab to find the stragglers.
Important Rules & Gotchas
- A project belongs to one customer — you cannot mix jobs from different customers in one project
- A project cannot be closed while any linked job is open — this is enforced, not just a guideline
- Jobs created from a project have their customer locked to the project's customer
- The Projects module is permission-controlled — staff without the permission won't see it
- The budget field is for tracking only; it does not limit invoicing