Kretsheets

Nothing here
was typed in.

Colors are computed from the dates and the dependencies.

One place, every angle — schedules, documents, money and people that never disagree.

Every house down the side, every step across the top, and the cells can see each other.

Move one date, and every date that depends on it moves with it.

Already have an account? Sign in
The Kretsheets board: six houses down the side, every build step across the top, each cell coloured by whether it is complete, late, or waiting on an upstream step.
The board, as it actually renders. Green is done, red is late or blocked, amber means nobody is on it yet — and none of those colors was chosen by hand. The company is a sample built for this page; the software is not.
The board, with six houses and eighteen build steps, most cells green and one house showing red.
The Board · a sample company, Northlight Homes
01 · See it all

Every house down the side, every step across the top.

One grid holding every job you have and every move each one still has to make.

  1. Nothing lives in a second place.

    The board is not a report somebody assembles on Friday out of four other files. It is the database, drawn — so there is no version of it that can be out of date.

  2. The colour is computed, not chosen.

    Green is done. Red is late, or waiting on something overdue. Amber means nobody is on it yet, or the crew you want is booked on another job. Nobody sets these by hand, so nobody can forget to.

  3. A house that is fine looks fine.

    You are not reading rows hunting for the problem. The problem is the only thing on the screen that is not green.

The schedule room: build steps drawn as bars across a calendar, with a dashed baseline behind them.
The Schedule · the same six houses, drawn against time
02 · Move one date

Move one date, and every date behind it moves too.

Drag a bar and the work that depends on it recalculates over your real working calendar — weekends and shutdowns included.

  1. The dependencies are real.

    Framing waits on the foundation, which waits on the hole, which waits on the permit. You say that once. It then holds for every house you ever build.

  2. It proposes. It never overwrites.

    Your plan does not move because software decided it should. You are shown what it would become, and you accept it or you leave it exactly where it was.

  3. The dashed line is what you promised.

    The baseline stays put when the work moves, because drift is only meaningful against something that refuses to drift with it.

The documents room: each piece of paperwork with the stage it has reached, who owns it, and the build step it is holding up.
Documents · every page, and the step it stands in front of
03 · The paper drives the work

The roof isn't late because the roofer is slow.

It is late because nobody sent him the plan. That is the sentence a spreadsheet physically cannot hold, so this holds it instead.

  1. A document can hold up a step.

    A permit, a truss drawing, an inspection. Name what a step is waiting on, and the schedule waits with it — without anybody remembering to go and move a date.

  2. So a delay has a reason attached.

    Not that a house is behind, but behind what, and whose desk that thing is sitting on right now.

  3. One lot here is behind an email.

    The plan set was approved and sitting there the whole time. Nobody sent it, so the roof never started, and everything behind the roof queued up behind four minutes of somebody's attention.

Come and look at it.

Bring a job you are running right now. It is the only honest test.

Already have an account? Sign in