Skip to content
StoryStoryBristlecone ConstructionBristlecone ConstructionKI — Kinetic Intelligence
esc

Scheduling

A job is a sequencing problem. Trades have to land in the right order, and the client needs dates they can plan around — when demo starts, when the kitchen is usable again, when they get their house back.

This area holds the dates the project is judged on, and the record of how they have changed.

A milestone is a key date on a project: permit issued, demolition complete, rough-in done, substantial completion. Each one is a real record carrying both a target date and an actual date, not a line in a status email.

Milestones are short by design. They mark the moments that matter to the people paying for and living through the work, rather than tracking every task on site.

A milestones report pulls them together across a project, so the dates can be read in one place instead of assembled from meeting notes.

The Schedule module sits in the Admin Portal’s Construction section and is managed there only — it is not fed from the Field App. This instance does not run a CPM (critical path method) schedule or a four-week look-ahead.

Milestone dates change. Materials arrive late, an inspection gets rescheduled, a wall opens up and reveals something.

KI keeps the history. Changes to a milestone are recorded as they happen, and snapshots preserve what the dates looked like at points in time. That means “has this date moved, and when” has an answer on the record.

Movement in a schedule is normal. Movement nobody can trace is the problem, and keeping the history is how the second one is avoided.

The project’s milestones and their dates, in the Client Portal. When a date changes the prior date is not overwritten out of existence — the record shows the change, so the conversation starts from the same facts on both sides. The Schedule tab also carries project updates with photos and notes of what happened on a given date.