Skip to content

Construction

Overview

The Construction model groups the records needed for project delivery, field staffing, and commercial follow-up in one connected dataset. It covers planning before a job starts, execution on site, and the records finance and compliance teams use after work is complete.

You can set up departments, teams, roles, and disciplines; plan projects with milestones, tasks, and dependencies; schedule labor by shift and location; and keep worker qualifications linked to the assignments they are allowed to fill. Execution data such as time logged, materials used, invoices, credit notes, and payments are included in the same model so project and finance records stay connected.

A seeded example organization named Construction Demo Org is included, with the Industry field set to Construction. The demo data shows how projects, workforce scheduling, qualifications, compliance, and billing can be organized.

When to use this

Use the Construction model when you need to manage project work, labor, and commercial records together instead of handling them in separate systems.

  • You run construction projects that require project plans, task assignments, and site staffing.
  • Workers must hold specific Skills, Skill levels, or Certifications before they can accept a task or shift.
  • Supervisors capture Time logged, Materials used, and related project activity for later billing.
  • Your billing process relies on Approved time, Billing profiles, Rate cards, Project billing terms, and draft invoices.
  • You need to track project decisions, risks, compliance items, and tickets together with delivery work.
  • You want a construction-specific starting dataset, including the Construction Demo Org.

How it works

Organize your operating structure

Create records for administrative_units, departments, teams, roles, role_levels, disciplines, companies, members, user_roles, and user_groups. These records define who does the work, who manages it, and how people group for projects and scheduling.

Example: separate civil, electrical, and mechanical disciplines, assign supervisors to teams, and align workers to the companies or departments responsible for each part of a build.

Match people to work using qualifications

Use Skills, Skill categories, Skill levels, Certifications, Certification prerequisites, user_skills, and user_certifications. Attach qualification requirements to roles, tasks, task_templates, and shifts through collections such as skills_for_tasks, certifications_for_tasks, skills_for_template_tasks, and shift_certifications.

This ensures assignment decisions consider both availability and eligibility.

Plan projects in actionable pieces

Break projects into project_teams, milestones, epics, sprints, tasks, task_stages, task_assignments, and task_dependencies. Use project_templates and task_templates for repeatable jobs.

Dependencies and task stages let project managers represent real sequencing and day-to-day work for crews and supervisors.

Schedule field labor by shift

Use shifts, shift_types, shift_locations, shift_assignments, shift_templates, user_shift_preferences, and shift_swap_requests to plan coverage, define the type of shift, and manage reassignment.

Combine scheduling with qualification records (shift_skills, shift_certifications) to ensure the assigned worker meets the requirements for the site and task.

Carry execution activity into billing

Connect execution records to the billing workflow using approved time, billing_profiles, rate_cards, and rate_card_lines, plus project_billing_terms. Create invoice_header and invoice_detail records, and manage credit_note_header, credit_note_detail, payments, and payment_allocations for reconciliation.

This links delivered work to the records used to generate and track invoices.

Track risks, decisions, and supporting work

Record risks, decisions, decision_reviews, compliance_items, contracts, meeting_artifacts, meeting_transcript_entries, comments, notes, notifications, tickets, and ticket_attachments or ticket_messages alongside project work. These records document issues, decisions, compliance follow-ups, and meeting outputs that affect delivery.

Typical workflow

  1. Set up the operating structure: create administrative_units, departments, teams, roles, disciplines, companies, and user_groups.
  2. Define worker qualifications: add Skills, Skill levels, Certifications, and Certification prerequisites; maintain user_skills and user_certifications.
  3. Build the project: create a record in projects, assign project_teams, add milestones, and break work into epics, sprints, and tasks. Use task_stages and task_dependencies to reflect sequencing.
  4. Add work requirements: attach required skills or certifications to tasks, task_templates, roles, or shifts.
  5. Schedule labor: create shifts (by shift_types and shift_locations), assign workers, and manage shift_swap_requests. Verify each shift_assignment meets required qualifications.
  6. Capture execution details: record time in timesheet_headers and time_logged, track materials_used, expenses, notes, comments, and meeting_transcript_entries.
  7. Prepare billing: review approved, uninvoiced time, apply billing_profiles, project_billing_terms, and rate_cards, then create a draft invoice.
  8. Issue invoices and reconcile payments: create invoice_header and invoice_detail records, record payments, and allocate payments or issue credit notes as needed.
  9. Manage delivery issues: use risks, decisions, compliance_items, and tickets to track items that affect schedule, cost, or readiness.

Fields, controls, or options you may see

Field or option Collection or purpose
Industry Identifies the dataset as Construction
Project type project_types — classifies projects
Task stage task_stages — indicates a task’s workflow stage
Shift type shift_types — classifies scheduled shifts
Shift location shift_locations — identifies where a shift is worked
Skill level skill_levels — records proficiency for a skill
Billing profile billing_profiles — stores billing configuration
Rate card rate_cards and rate_card_lines — defines pricing for billable work

You will also interact with project_billing_terms, invoice_header, invoice_detail, payments, materials_used, compliance_items, and shift_swap_requests as part of delivery and billing workflows.

No user-facing skills or automation flows specific to Construction are present in the provided scope. The model supports qualification-aware workflows: skills and certifications attach to tasks, template tasks, roles, and shifts, so automations that enforce eligibility checks or prepare draft invoices from approved time are natural automation candidates in your environment. Meeting artifacts and transcripts are available for project documentation; any automated behavior that uses those records depends on how your system is configured.

Things to watch for

  • Treat availability and eligibility separately. A worker who is available may still lack required certifications or skills.
  • Keep templates separate from live records. project_templates, task_templates, and shift_templates are for reuse and are distinct from active projects, tasks, and shifts.
  • Billing typically requires multiple linked records: approved time, billing_profiles, project_billing_terms, rate_cards, invoice_header, and invoice_detail.
  • Use the appropriate record type for issues: tickets, risks, decisions, and compliance_items each serve different purposes.
  • The seeded demo dataset may include collections and records you do not use in production.
  • Exact statuses, approval flows, and role permissions vary by setup; confirm the project’s rules and permissions before rolling out processes.
  • Projects
  • Tasks
  • Scheduling and shifts
  • Skills and certifications
  • Timesheets and time logging
  • Billing and invoicing
  • Meetings and decisions
  • Tickets and service issues
  • Risk and compliance management