Note
How to Pick Your Pilot Project
Every contractor who decides to put one project on a proper timeline faces the same question first: which project?
The wrong answer is the most obvious one. Most people reach for their biggest project because that is where the money is, or their most troubled one because that is where the pain is. Both tend to produce the same result: a schedule too complicated to prove anything, where every stumble in week two gets blamed on the method rather than the complexity of the starting point.
The right choice is simpler: the project that will bill its next stage within the next 30 days.
Why does a billing date in the next 30 days change everything?
A timeline without a live financial consequence is a planning exercise. The billing date is what makes the schedule honest.
When the next stage payment depends on work being finished by a specific date, the timeline stops being decorative. People update it because something real is at stake. The site manager marks zones finished because the invoice is waiting. The shop confirms a delivery date because the install crew is arriving Thursday and the billing pin is on Friday.
Remove the near-term billing event and you still have a schedule, but it is a schedule without force. You can track whether it is working but you cannot feel whether it is working. That difference matters in week two, when people are busy and updating the bars competes with running the site.
A project that bills within 30 days gives you a test with real consequences. If the system works, an invoice goes out that would not have gone out as cleanly without it. If it stumbles, you find out while the project is still live and you can adjust.
What makes a project the right size for a first install?
Four things point to the right choice.
A billing event inside 30 days. This is the primary criterion. A project billing its next stage in three weeks gives the timeline a real target from day one.
Two names available: one who holds the plan and one on site. The timeline is updated by two people, not a team. One knows where the bars stand; the other knows which zones are finished. If neither name can give 30 minutes on a Tuesday for four weeks, the pilot will stall before it proves anything.
Five to twelve active bars during the install window. Fewer than five and the timeline tells you nothing a notebook would not. More than fifteen on a project nobody has documented before tends to produce a setup that is still being debated in week three.
Not your most critical or most troubled project. A project in crisis makes the method look like the problem. Save the difficult ones for when the approach is already familiar.
A worked example: three projects, one clear choice
A contractor runs three projects at once. Project A is a commercial fit-out with zone work in progress, billing stage 4 in 12 days, with shop fabrication involved. Project B is a residential renovation, billing its final stage in 38 days, all materials bought from suppliers. Project C is a factory installation at early stages, billing in 75 days, the largest of the three by contract value.
Project C is the wrong choice. The billing event is too far away for week one to feel like anything beyond paperwork, and the size means setup takes most of the first two weeks.
Project B is reasonable, but the billing event sits outside the 30-day window and there is no shop coordination to make visible.
Project A is the right choice. The billing event in 12 days means the timeline is live from the start. Shop delivery dates attach to install bars where they actually affect the schedule. The billing pin at day 12 is the first real test.
How do you break a tie if two projects both bill within 30 days?
Choose the one where your own fabrication shop feeds the site. A project depending on shop delivery for an install bar is where the timeline earns its keep. The conflict between shop capacity and install dates is most likely invisible until the install crew is already standing idle. That is what becomes visible first on a well-run pilot.
A project that buys from suppliers and runs one trade is simpler to manage. It makes a good second project. The pilot with shop involvement gives you more signal in less time.
What if no current project bills in the next 30 days?
Pick the one with the earliest upcoming billing date and start. A billing event in 45 days is still a real target. The first weeks are heavier on setup than on live tracking, but the structure is the same.
If the earliest date is more than 60 days away, the first three weeks will feel administrative rather than operational. That is not a reason to wait. It is a reason to be honest that the system will feel different once a billing date enters the ten-day window.
Who should know you are treating this project differently?
The owner. Not the word “pilot” specifically. The relevant fact: this project runs on a documented timeline with billing stages as named points, reviewed together for 30 minutes every Tuesday.
The site team needs to know that the two questions answered in the chat group each week are the official update method, not an extra check-in. If the team feels like they are reporting twice, they will stop doing one.
FAQ
Is the biggest project automatically the wrong choice for a first install?
Not automatically. If the largest project also bills soonest and two names are available, it is the right choice. The risk is that setting up fifteen or more bars from scratch takes most of the first two weeks, leaving little time for the timeline to run before the first billing test. The billing date matters more than the bar count.
Can I run two pilot projects at the same time?
In practice, no. Two projects split the same two names across two update cycles and two Tuesday reviews. Most contractors who try this find neither gets a full setup in the first two weeks. The second project runs better because the method is familiar by then, not because it ran at the same time.
What if the project I want to start with has a difficult client relationship?
A difficult relationship is a signal to choose a different project first. The install requires the owner present when criteria are agreed and 30 minutes a week for four Tuesdays. A client unlikely to engage with that will turn setup into a negotiation. Save that relationship for when the method is proven on a project that ran cleanly.
If you want to map which of your current projects makes the clearest starting point, a 45-minute call covers that. We look at the projects you have running, check which billing dates are closest, and work out which one gives the sharpest picture. You leave with that answer either way.