Skip to main content

Overview

This platform is designed to organize work around projects while keeping tasks, schedules, people, and locations connected and easy to manage.

Rather than forcing you to jump between separate tools, everything here is built to work together through a shared structure.

This section explains the core ideas behind how the system is organized.

The Big Picture​

At the center of the system is the Project.

A project represents a unit of work — something you are planning, designing, managing, or delivering. Nearly everything else in the system connects to a project in some way.

Think of projects as the hub, with related information branching out from them.

The Project-Centered Model​

Most activity in the system belongs to a project:

  • Tasks describe what needs to be done
  • Deliverables define what must be produced
  • Schedules show when work happens
  • Resources and crews show who is doing the work
  • Locations show where the work occurs
  • Comments capture communication and decisions

By anchoring everything to a project, the system stays organized, searchable, and consistent.

How Information Connects​

Instead of duplicating data across tools, the system links information together.

For example:

  • A task belongs to a project
  • A deliverable belongs to a project and may contain tasks
  • A scheduled booking belongs to a project and a resource
  • A map location is tied to the project’s property
  • Comments stay attached to the project or item they relate to

This means:

  • Updates stay in sync
  • Reports remain accurate
  • Context is never lost

Widgets vs. Concepts​

You may interact with the system through widgets like tables, calendars, maps, and boards.

Widgets are ways to view and work with information — they are not the information itself.

For example:

  • The Task Board shows tasks
  • The Gantt view shows timelines
  • The Map shows locations
  • Tables show structured lists
  • The Record Viewer shows detailed information

All of these are simply different views of the same connected data.

Why This Matters​

This approach allows you to:

  • Work the way that makes sense for you
  • Switch between views without losing context
  • Keep teams aligned around the same information
  • Scale from small jobs to complex, multi-phase projects

It also ensures that as the system grows, new tools fit naturally into the existing structure.

What’s Next​

Now that you understand the overall structure, the next sections dive deeper into each core concept, starting with the most important one:

➡️ Projects

Each section explains:

  • What the concept represents
  • How it fits into the system
  • How it connects to other parts of the platform
  • Where you’ll interact with it day to day