Skip to content

Business Operations & Automation

Project operations: status nobody has to ask for

A replacement, a renovation or a commercial job runs over weeks and passes through survey, permit, equipment, install, inspection and handover. Project operations keeps that chain as one plan, so when one milestone slips, everything that depends on it moves by the same amount and the customer, crew and anyone else affected hear the new dates the same day. We build the plan around your project types and the people who need to hear.
Talk through your projectsSee the handoffs ↓
PR-14 · boiler replacement · Acme, 220 Lake Sthandover was Fri Dec 4handover now Fri Dec 11Nov 2Nov 9Nov 16Nov 23Nov 30Dec 7Site surveyPermitrevised drawing neededBoiler orderedRemove and installafter permitInspectionafter installHandoverafter inspectiontodayAcme's managernew install week and handover, Dec 11Crew T3, T4install moved to the week of Nov 30Inspector bookingmoved to Dec 9

Everyone asks where the project is

A project that runs over weeks has a dozen people waiting on it: the customer, the crew, the supplier, the inspector, the office. Its status lives in the project manager's head and a spreadsheet, so each of them calls to ask. When something slips, the dates that depend on it are updated one phone call at a time, and someone always hears last.

Project operations keeps the project as a plan of milestones, each with the handoffs it depends on and the people who need to know. A change to one milestone moves everything downstream, tells the people affected, and shows everyone the same status, without the project manager rewriting the schedule by hand.

Today, and with project operations

Today

  1. 01The plan lives in one person's head and a spreadsheet.
  2. 02The customer, crew and supplier call to ask for status.
  3. 03A slipped permit means rewriting dates by hand.
  4. 04Some people hear about the change on the day.

The crew arrives for an install the permit doesn't allow yet.

With project operations

  1. 01One plan with milestones, handoffs and dependencies.
  2. 02Each handoff has a condition that has to be true.
  3. 03A slip moves every date that depends on it.
  4. 04Everyone affected hears the new dates the same day.
  5. 05The customer sees status in their portal without calling.

Status is a page people check, not a call they make.

Every handoff has a condition

Survey → designMeasurements and photos are attachedThe project manager
Permit → installThe permit is approved and on fileThe crew, the customer
Equipment → installDelivered and checked against the orderThe crew
Install → inspectionThe install checklist is completeThe inspector booking, the customer
Inspection → handoverPassed, with the report filedThe customer, the office
Handover → invoicingThe customer has signed offAccounts

One project, three views

The same plan, seen by the customer, the crew and the manager.

PR-14 · your boiler replacement

status
waiting on the permit
what changed
the city asked for a revised drawing; we've sent it
install
week of Nov 30
handover
Fri Dec 11
your part
access to the plant room on install days

What changes from one business to the next

Project typesReplacements, renovations, commercial work, and their usual milestones
DependenciesWhat each milestone waits for
Handoff conditionsWhat has to be true before the next step starts
Who hearsThe customer, crew, suppliers and inspectors for each change
Where status showsThe customer's portal, the crew's app, the office's board

A common starting point is your field service or project tool for the jobs themselves, with the plan, dependencies and status in PostgreSQL, n8n or Trigger.dev moving dates and sending notices, and a portal page for customers. These are starting candidates, not requirements.

Is project operations the right fit?

Good fit

  • Some of your work runs over weeks, with several steps and people.
  • Customers and crews call to ask for status.
  • A slip in one step regularly catches someone out.

Avoid when

  • Every job is a single visit.
  • One person runs every project and nobody else needs the dates.

How we'd approach it

Most of the early work is mapping your project types, their dependencies and what must be true before each handoff.

  1. 01

    Understand

    As much as the problem needs

    We map how the work runs today: who does what, which systems hold the records, and where it breaks.

  2. 02

    Design

    Decided before it's built

    Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.

  3. 03

    Build

    Connected to what you use

    We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.

Related systems

The capabilities underneath

For your industry

Questions about project operations

Does this replace our project management tool?

Not necessarily. If your tool holds the jobs well, the system adds dependencies, handoff conditions and notices around it. If the plan only lives in a spreadsheet, it becomes the plan.

Who decides when a date moves?

The project manager. The system proposes the knock-on changes and sends them once they're confirmed, unless your rules say a change of that kind can go straight out.

Can customers see the plan?

They see what's useful to them: status, what changed, the next dates and anything they need to do. The internal detail stays internal.

What about projects with subcontractors?

Subcontractors are people who hear about changes like anyone else, by email or text, and can confirm their dates without needing an account.

Know where every project stands without asking

Tell us how a long job is tracked today. We'll show you what happens to the plan when one milestone slips.

Start a project