The whiteboard in the office still says framing starts Monday. The man who moved it to Thursday told two people, and neither of them writes on the whiteboard.

The office needs one answer — who is where next week — and a stack of week views makes somebody flip pages and add it up. One surface you pan means next Tuesday and next spring are the same glance, so a double booking shows up while it can still be moved. It stays smooth under a finger: a drag moves a picture, and nothing redraws until you have travelled about half a screen.

You open four jobs one after another to answer one question — which of them is behind — and by the fourth you have forgotten what the first one said.

A foreman reads colour and position faster than words, so a collapsed row has to say where the job is without opening it. The names and colours come from the stage list the job started on — a company that calls it Post Set sees Post Set — and editing the stage template later changes the next job, never one already underway.

Framing has been in progress for nine days, the customer asks how it is going, and the honest answer is that nobody in the office knows whether that means day two or day eight.

Nobody trusts a percentage somebody typed, and a customer asking how it's going deserves better than a guess. Counting the ticked checkpoints means the bar moves during framing, not only at the end of it. A stage with no checkpoints falls back to stages done over stages total, so it never sits at zero forever.

A customer rings about his garage, you know the job is on the board somewhere, and you scroll past it twice because you are looking for a name and the row says the building size first.

When a customer rings, whoever answers needs his job in seconds, not after scrolling past thirty bars. Search sits in the toolbar rather than the project column on purpose: a row added to that column would push every name out of line with its own bar, and the whole chart is read by that alignment.

Six chained stages each counted through a weekend, and the build has drifted more than a week before anyone has lifted a hammer.

A crew boss trusts a date he can see is possible. Shading the days nobody works makes a bar running through a weekend look wrong at a glance, instead of hiding the maths where nobody checks it. The band follows the company's week, so a Saturday crew's bars simply cross it — which reads correctly.

Two crews found out they were booked on the same site the morning of, by phone, already in the trucks — and the three idle days each of the other two sat through that month appeared nowhere at all.

Crews take vacations and shops shut for a week, and a schedule that only shows work is quietly promising every crew is free every day. Drawing time off and idle gaps on the same timeline lets the office book around them instead of finding out from the truck. An overlap is flagged, not blocked — sometimes the vacation moves and sometimes the job does, and only you know which.

Concrete slips two days, so the schedule is edited in a spreadsheet, and the crew leader is working from a screenshot of the version before that.

The office has to move one stage when the concrete sub can only come on the 14th — without dragging the whole build behind it. Quick-edit moves that one stage and reflows nothing, and the schedule notices afterwards if the result breaks its own order. The panel also warns when a stage now starts before the job does or ends after it.

"Every time I change the start date it goes out till February, and every time I get the end date back to September it changes the start date back to May. I'm sure I'm doing something wrong, I just don't know what."

A builder fighting his own dates assumes the mistake is his; naming the stage that broke the order ends the guessing in one look. The repair is offered, never forced, and "that's intentional" is remembered for the job — the schedule does not get to argue with the man running it.

The siding crew has been stopped since Tuesday waiting on trim, and the office finds out on Friday when the customer asks why nothing has changed.

An owner scanning the board should land on trouble, not on the busiest job. Motion is kept for problems only — healthy work gets a still arrow — so the pulsing triangle never turns into wallpaper. Variance is measured when a stage closes, actual days against planned, so the number on the bar is a measurement, not an opinion.

To answer "is the Hostetler job on track?" somebody opens six panels one after another, and by the sixth has forgotten what the first one said.

The office opens a job to answer one question, and the closed cards answer most of them without another click. Red for late, amber for waiting on someone and green for done keep the eye on what needs a decision. The board stays for where and when; everything else is one gesture away.

Two contracts came back the same week; one starts in March and one starts whenever the permit clears, and both are drawn on next Monday.

The office needs to trust that every bar is a build somebody decided to start. A board that filled itself from contract signatures would fill with jobs that have no real start date yet. One deliberate press creates the stages, checkpoints and dates, so the schedule only shows work that is really coming.

A sub sees you have eleven jobs on and four crews running, and the next quote he gives you is priced for a builder who cannot say no.

A sub works better when he sees his own jobs clearly — and you are better off when he cannot count yours. The list is filtered before anything is drawn, time-off rows included, so a slip in the screen still shows nothing. The rule and where it is enforced live in roles and permissions; how crews' own links are sent and revoked is on the crew field portal.

The Yoder machine shed finished in August, and when Mr. Yoder calls about a door in March nobody can find the job without scrolling back through months of bars.

An owner wants the live board clean but the past builds close — for the warranty call, the repeat customer, the photos. Completed keeps them one click away with their phases done, without anyone inventing crew logs to make them look finished, so the crew numbers stay honest. Archive and Delete keep the typed-word gate because a job carries a contract, invoices and logged hours.

A customer sees you have nine other jobs on and immediately starts wondering which one his crew is really at today.

Customers relax when they see their own build moving and get nervous when they see your whole book. So they get a separate page that shows only their job, fed from the same stages as this board — their progress cannot drift from yours, and there is no toggle one slip away from showing them everything.

The concrete crew is booked on a job filed under the framing crew, so their filter shows nothing and they hear about Thursday's pour on Wednesday night.

Concrete and framing crews overlap on real post-frame jobs, and a schedule that knows only one crew per job hides the other until he shows up. Filtering by any crew on the job means the concrete boss sees every pour he is booked for, and the office sees who still hasn't accepted — fewer no-shows and fewer "nobody told me".