Developments and plots
A development is the scheme container. Plot jobs underneath hold tasks, site diary, files, finances, and snags. Use a standalone job when you only run one site.
Development overview with plots table
desktop
When to use this
Use a development when several units share a site, client, or contract defaults.
Use a standalone job for one house or one contract with no plots.
Before you start
- Developments are available in the workspace.
- Optional: a customer for the developer or client.
Add the development
On Jobs, choose Add job, then set Development to + Add development…. Enter the scheme name and optional developer or client.
You can also turn an existing standalone job into a scheme later from Overview → Details → Advanced.
Add plots
Open the development and Add plot, or create a job and set Development to this scheme. Each plot is a full job.
Set scheme defaults
On the development overview, set Contract rules and UK compliance so new plots inherit them.
Development → scheme settings tiles
desktop
What lives where
| On the development | On each plot |
|---|---|
| Scheme name and site identity | Tasks and programme |
| Contract rules defaults | Site diary and snagging |
| UK compliance defaults (CDM and CIS) | Files, activity, finances |
| Aggregated scheme value | Quotes, variations, invoices |
Do not log diary entries or snags on the development. Raise them on the plot (or standalone job) where the work happened.
Development overview
Tiles on the scheme:
- Plots: active and archived count
- Scheme value: sum of plot contract values
- Contract rules: payment and variation defaults for new plots
- UK compliance: CDM and CIS defaults for plots on the scheme
The plots table lists each plot with status. Open a plot for day-to-day work.
Jobs list
Group Jobs by Development to nest plots under schemes. Independent jobs are standalone jobs with no parent.
Star a development to pin it like any other job. From a development group you can Add plot or edit the scheme.
What done looks like
- The scheme exists on Jobs.
- At least one plot is linked.
- New plots pick up contract rules (and UK compliance when you set them).
- Site work happens on plots, not on the development record.
Common mistakes
- Running tasks, diary, and invoices on the development because that is the name everyone uses on site. Rename the scheme if you need, and keep operations on plots.
- Adding plot 2 as a second standalone job, then losing the shared defaults.
- Expecting pipeline status on the development. Status is tracked on each plot.
Turn an existing job into a development
If you started with one job and later need plots:
- Open Overview → Details and expand Advanced.
- Choose Mark as development. Confirm you understand it becomes a scheme record.
- Optionally create a plot for existing operational work. Tasks, files, and invoices already on the job stay on the development until you move them. New work should go on the plot.