Give every job one place for its records, evidence, and connected workflows.

Use Projects when information is spread across inspections, quotes, site records, documents, and activity but needs to remain connected to one job.

BEST FOR 01

Builders managing several active jobs

BEST FOR 02

Administrators connecting paperwork to projects

BEST FOR 03

Teams that need job history without searching multiple tools

How the workflow fits together

A Controlled Path From Input To Reviewed Record.

01
Create The Job
Set up the project and the basic context your team needs.
02
Connect Work
Associate sites, inspections, quotes, documents, and activity with the project.
03
Review The Trail
Use the project as the starting point for related records and next actions.

Expected outcomes

Limits and human review

Projects organises OneAdmin records; it is not a full construction scheduling or enterprise resource planning system.
Access to connected modules depends on plan, role, and rollout status.

Practical questions

Projects can provide context for sites, inspections, quotations, BYDA records, activity, and other supported module records.

No. Its primary role is organising job administration and connected records rather than detailed critical-path scheduling.

Connected modules

Keep access, parking, trading hours, and contacts with each job location.

Capture photos, defects, inspection findings, sign-off, and closeout evidence.

Create and track quotations, revisions, acceptance, and deposits.