Skip to main content

How teams work on Builddar

The rest of the documentation is organized by feature — one guide per task. This section is organized the other way round: by job. Each page follows one role through one piece of work from start to finish, and links to the guide for every step.

Read the one that matches your job. Then use the feature guides as reference.

The four walkthroughs​

Architect: from OPR to reception​

Structure the project, walk it with the drawing set, log every observation against a zone, lift the contractors, and sign off with the evidence attached.

For architectes d'exécution, OPC, maîtrise d'œuvre and quality coordinators.

Developer: portfolio oversight​

Watch every project from one place. Compare contractor performance across projects, track reception readiness, and get the numbers on a schedule instead of by email.

For promoteurs, asset managers and development directors.

Project manager: daily site capture​

Capture defects on the phone with a photo, a pin on the plan, and a company — with no signal. Everything syncs when you're back online.

For site managers and conductors of works.

The site meeting report​

Convene the companies, record attendance, keep a point register that carries forward, and publish the compte rendu to everyone who needs it.

For whoever runs the weekly meeting.

What they have in common​

All four run on the same data. An observation captured on the phone during a site walk is the same issue the architect sees on the drawing, the same row the developer's contractor scorecard counts, and — if it's linked to a point — the same subject that appears on the meeting report.

Nothing is re-entered. That's the whole design.

Before you start​

If you haven't set up a project yet, do that first:

Last updated on