Skip to main content

Projects

Projects are the central organizing element of the system.
Nearly everything you do—tasks, schedules, deliverables, locations, and communication—connects back to a project.

If you understand projects, the rest of the system makes sense.

What Is a Project?​

A project represents a defined unit of work.

A project might be:

  • A development site
  • A design effort
  • A construction phase
  • A study, report, or review
  • Ongoing client work

No matter the size or complexity, a project acts as the single source of truth for everything related to that work.

Why Projects Are the Hub​

Projects exist to keep work:

  • Organized
  • Searchable
  • Traceable
  • Scalable

Instead of scattering information across unrelated tools, the system keeps everything connected through the project.

This means:

  • You always know why something exists
  • Context is never lost
  • Reporting and scheduling stay accurate

What Belongs to a Project​

A project can contain many different types of information.

Common Items Attached to Projects​

  • Tasks
    Individual action items required to complete the work

  • Deliverables
    Tangible outputs such as plans, reports, or submittals

  • Milestones
    Key dates or checkpoints within deliverables

  • Schedules & Bookings
    When work happens and who is assigned

  • Resources & Crews
    People, teams, or equipment working on the project

  • Locations & Properties
    Where the work takes place

  • Comments & Activity
    Notes, decisions, meetings, and communication history

Each of these items exists in the context of a project.

One Project, Many Views​

A project is not tied to a single screen or tool.

You may interact with a project through:

  • A table
  • A task board
  • A timeline or Gantt view
  • A calendar
  • A map
  • A detailed record view

These are simply different ways of viewing the same project data.

Changing something in one place updates it everywhere.

Project Lifecycle​

Projects typically move through stages.

While the exact stages may vary, a common flow looks like this:

  1. Proposed
    Work is being discussed or scoped

  2. Active
    Work is underway

  3. On Hold
    Temporarily paused

  4. Completed
    Work is finished

  5. Cancelled
    Work will not proceed

Project status helps drive:

  • Visibility
  • Scheduling behavior
  • Reporting
  • Filtering across the system

Projects and Ownership​

Projects are usually associated with:

  • A client
  • A project manager or lead
  • A location or property

This information helps:

  • Assign responsibility
  • Control access
  • Filter and group work

What Projects Do Not Do​

Projects are organizers — not tasks themselves.

A project:

  • ❌ Is not a task
  • ❌ Is not a schedule entry
  • ❌ Does not represent a single action

Instead, it contains and coordinates all of those things.

Why This Matters​

By centering everything around projects, the system can:

  • Scale from small jobs to complex programs
  • Keep teams aligned
  • Reduce duplication
  • Maintain a clear audit trail
  • Support future automation and reporting

Once projects are defined correctly, everything else falls into place.

What’s Next​

Now that you understand projects as the hub, the next sections explain the items that attach to them—starting with:

➡️ Tasks

Tasks represent the day-to-day actions that move a project forward.