Projavio is in private beta — applications now open for UK construction consultancies.

Module · Onboarding

The first half-hour that decides every project number for the next two years.

A guided onboarding flow that captures client, sector, programme intent, scope, procurement route and team in one sitting — then feeds estimates, cost report, cashflow, programme and benchmarking with the same canonical data.

Why bad onboarding compounds

When the project record is half-empty, every downstream module guesses.

The onboarding step is the moment to capture sector, GIA, programme intent, procurement route, and the team. When it's skipped or half-done, every cost-report, cashflow, benchmark and report after it has to ask the same questions again — and the answers diverge.

Setup is a Word doc someone forgets

The intake template lives in a folder; the senior QS fills it in occasionally; the data never reaches Projavio so every module asks the same questions again.

Sector tagging is inconsistent

One PM tags it "QSR", another "Quick Service Restaurant", a third leaves it blank. Benchmarks across the portfolio compare apples to oranges.

Programme intent is in someone's head

Whether the client wants Bronze / Silver / Gold tier, the procurement route, the target start — known to one person at week one and to no one by week six.

What's inside

A guided intake that actually finishes.

Sector + tier

Pick from the workspace-managed sector taxonomy + quality tier (Bronze / Silver / Gold). Drives benchmark estimates and PCSR forecasting from day one.

Client + scope

Link the project to a client record (or create one inline). Capture scope and procurement route — JCT / NEC / D&B / traditional.

Programme intent

Target start, target completion, gateway dates. Seeds the programme module and the cashflow S-curve.

Floor area + value

GIA in m² and target value. Seeds the benchmark estimator and feeds £/m² metrics across reporting.

Team assignment

Pick the Lead PM, Lead CM, Cost Coordinator at intake. Permissions and notifications follow automatically.

Phase + status seed

Set the starting phase + status. Project record moves through phases later; the kick-off state is captured here.

Who uses it

Built for the person opening the project — and every later module that reads it.

Project Coordinators

A guided form takes 20 minutes once. Replaces the intake-Word-doc plus the chase-the-PM-for-details cycle.

Project Managers

Project intent captured at kick-off — your QS doesn't come back two weeks later asking "what tier was this?".

Directors

Every new project has a complete record on day one. Portfolio-level questions answer themselves because the data is consistent.

See onboarding fill the rest of Projavio.

A 20-minute walkthrough — capture a project from blank, watch the modules light up.

Frequently asked questions

Is onboarding required to create a project?

A minimal project record can be created without going through the full onboarding form, but downstream modules (benchmark estimates, cashflow forecasts, reports) work best when sector, GIA, value and tier are captured. Onboarding is the path for the canonical setup.

Can we customise the onboarding fields?

The field set is workspace-aware — sector taxonomy, tier labels and procurement route options are managed in workspace settings. Adding new fields beyond the defaults is on the roadmap.

What if we onboarded in the old way?

Existing projects can be retrofitted by editing the project record fields directly. The Onboarding form is the canonical capture path; the underlying data lives on the project record itself.

Make onboarding the first thing — not the postponed thing.

Capture the project once. Every module that follows reads it for free.