Introduction to Builddar

Builddar is a construction quality management platform. It helps teams on a construction project track defects and quality issues (often called snagging or punch lists), mark them up on drawings, run inspection checklists, manage project documents, and produce professional reports — on the web and offline on mobile.

This guide explains how Builddar is organized so the rest of the documentation makes sense.

How Builddar is organized

Everything in Builddar lives inside a clear hierarchy:

• Organization — your company's workspace. It holds your branding, your people, and shared catalogs (like trades and zone types). Every account belongs to an organization.
• Project — a construction project (a building, a site, a development). A project belongs to one organization and contains everything below.
• Inside each project:
  • Zones — the spatial breakdown of the project (buildings, floors, rooms, areas).
  • Drawings — plans you upload, on which you can pin issues.
  • Issues — the quality defects and tasks your team tracks and resolves.
  • Companies — the contractors and firms working on the project.
  • Checklists — inspection templates and the checklists you run from them.
  • Documents — files organized in folders, with review and versioning.
  • Reports — PDF and Excel outputs generated from your issues.
  • Workflow — the set of statuses an issue moves through.

Key concepts

Concept	What it is
Issue	A single quality defect or task. Has a status, an assignee, a location (zone/drawing pin), comments, photos, and an activity history.
Zone	A location in the project. Zones form a tree based on Zone Types (e.g. Building → Floor → Room).
Drawing	An uploaded plan. Issues can be pinned to an exact spot on a drawing.
Company	A contractor or firm on the project. Issues and access are often scoped by company.
Checklist	A structured inspection. You build a template, then create instances of it to fill in on site.
Document	A file in the project's document library, with folders, versions, and an approval workflow.
Report	A generated PDF or Excel summarizing issues, based on a report template.
Workflow	The statuses (and allowed transitions between them) that an issue can have.

Roles: who can do what

Builddar has two layers of roles.

Organization roles

Set when someone joins your organization:

• Admin — full control of the organization. Creates projects, invites people, manages branding and shared catalogs. Org admins can access every project in the org.
• Member — belongs to the organization and works on the specific projects they're added to.
• Guest — an external participant with limited, company-scoped access.

Project roles

Set per project, for each member:

• Manager — full control of the project: settings, members, workflow, templates, and all day-to-day work.
• Collaborator — the operational role. Creates and updates issues, runs checklists, uploads documents, and generates reports.
• Guest — company-scoped and mostly read-only. Sees only their own company's issues, can change issue status and comment, but cannot create issues or manage anything.

note

Some features (such as checklists and custom report templates) also depend on your organization's plan, separately from your role.

The typical journey

Most teams follow this path:

1. Sign up and create (or join) an organization.
2. Set up the organization — branding, language, and shared catalogs.
3. Create a project.
4. Set up the project — build zones, upload drawings, add companies, invite members, and define the issue workflow.
5. Activate the project so the team can start logging issues.
6. Work day to day — create and track issues, run checklists, manage documents, and generate reports.

The rest of the documentation follows roughly this order. If you're brand new, start with Sign up and log in, then the Quick start.