Your make-ready whiteboard is a scheduling tool that cannot schedule

Almost every property has a make-ready board. Units down the left, stages across the top, magnets or dry-erase marks in the grid.

It works, and the reason it works is that it answers the one question a property manager asks twenty times a day: what is ready to lease. What it cannot answer is the question that determines turn time, which is what happens next and when.

A board shows state, and turn time is set by sequence

The distinction is worth being precise about, because it explains why boards persist and why they stop scaling.

A board is a state display. Unit 214 is in paint. That is true, useful, and current.

Turn time is a function of sequence and dependency. Unit 214 is in paint, paint finishes Thursday, carpet is booked for Friday, and the carpet vendor has four other units that week. If paint slips a day, carpet does not slip a day, it slips to the following Tuesday, because the vendor's Friday slot goes to somebody else.

That cascade is where turn days actually get lost, and a board has nowhere to record it. The magnet does not know the carpet vendor's calendar.

The four failures a board produces at scale

Vendor bottlenecks stay invisible until they bite. Three units waiting on the same painter look like three independent units in paint. The board shows parallel work. The reality is serial.

Nobody can see the plan, only the present. A regional asking "will 214 be ready by the 15th" gets an opinion, because the board holds no dates.

It has no history. At the end of the quarter you cannot answer which stage runs long, because the board was erased. Every operator who has tried to reduce turn time has hit this: you cannot improve a cycle you never measured.

It exists at one property. A regional over twelve properties has twelve boards in twelve offices, and no portfolio view. This is the failure that scales worst, and it is the reason multi-site operators eventually stop defending the board.

What a scheduling version has to hold

Four things the board does not.

A stage with a target date and an owner. Not "in paint," but "in paint, due Thursday, assigned to Marcus." The date is what turns a status into a commitment.

Dependencies between stages. Carpet cannot start until paint closes. When paint slips, the system should show carpet slipping, rather than leaving somebody to work it out.

Vendor capacity across units. If one painter covers four properties, the schedule needs to know that, or every property schedules the painter for Thursday independently.

Timestamps that persist. Every stage entry and exit, recorded, so the average time in each stage is a number you can pull instead of a thing people believe.

That last one is the whole return. Without stage timestamps, "our turns take 12 days" is folklore. With them, you find out that paint takes 1.5 days and the gap between move-out and scope takes 3.

The gap before work starts is usually the biggest one

Worth stating separately because it surprises people.

When operators first measure stage timestamps, the longest stage is frequently not a trade. It is the interval between the resident's keys coming back and anyone scoping the unit. Nobody is working, nothing is scheduled, and the unit is vacant at full cost.

That gap responds to process rather than to labor. It closes when move-out triggers a scope inspection automatically instead of waiting for someone to notice, which is a systems change rather than a staffing one.

Our own portfolio numbers on this: Ayla saw a 51% reduction in make-ready time after moving off manual coordination, and 48% at that property specifically, not portfolio-wide. Most of that came out of coordination time rather than out of the trades working faster.

Where GetDone lands, and what it does not do

Make-ready boards with stage tracking, target dates, assignment, and timestamps that persist for reporting, across every property rather than per office.

What we do not do: vendor capacity planning across a shared trade calendar. If your painter covers eight properties, GetDone will not tell you their Thursday is already full. That is a real gap and it is on the request list rather than in the product. Today the mitigation is that the schedule is visible portfolio-wide, so a regional can see the collision, which is better than twelve whiteboards and less than a capacity model.

Keep the board

The recommendation is not to take the whiteboard down.

Keep it as the glanceable state display it is good at, and put the dates, dependencies, and timestamps somewhere they persist. The board tells the leasing office what is ready. The system tells the regional what will be ready, and tells you next quarter which stage to attack.

What is your average time between move-out and first scope?