Note
Two Projects on One Timeline
The assumption most contractors carry into a second project is that it needs its own tracking setup: a separate spreadsheet, a separate chat group, a separate update rhythm. Two projects, two systems.
That assumption is what makes the second project feel like twice the work. The admin doubles because nothing from the first project carries over. The switching cost between two disconnected systems is where the time goes, not the projects themselves.
Why does running two projects feel like double the admin?
The answer is not the volume of work. It is the absence of one shared structure.
When project A lives in a spreadsheet and project B lives in a LINE group, keeping both current requires two entirely separate update habits. The person managing both has to context-switch between two formats, two rhythms, and two places where information might be out of date. Every question about either project starts with finding the right tab or scrolling back through the right chat.
The update cost per project stays constant because the method is never shared. Two projects, two costs. Three projects, three costs.
The alternative is a shared method that makes each project update the same shape regardless of which one it is. Once the method is familiar, adding a second project is lighter than starting the first was, because the setup is already done.
What does a shared timeline structure look like?
Three layers: bars for the work, billing stage pins on the same line as the bars they belong to, and material delivery dates attached to the bars that depend on them.
Adding a second project means adding a second set of bars in the same format. The billing pins follow the same row logic. The delivery dates attach the same way. The weekly review covers both sets in the same 30-minute slot, not 30 minutes per project. The two pre-meeting questions cover both projects at once: which zones finished this week, and what is shipping from the shop. The answers arrive in the same channel, and the switching cost drops because the questions are identical for every project on the timeline.
Does adding a second project double the number of bars to update?
Not in practice. A single project runs 12 to 18 bars during an active installation window. Two projects at different stages rarely have both at peak activity at the same time. One may be in week three of an install window while the other is still in the material delivery phase, with three or four active bars.
The realistic combined bar count is usually 15 to 25 moving bars in any given week. A bar only needs a weekly update if it is about to change position or is at risk of doing so. A bar where the work is done or has not yet started holds its position until something changes. The review covers what is moving, not the whole timeline.
A worked example: two commercial fit-out projects
A contractor runs two commercial fit-out projects. Project A is in week four, covering zones 8 through 12, with a billing pin six days away. Project B is in week two, completing shop fabrication for the first installation batch. The billing pin for project B is 19 days out. Three bars are active.
Tuesday review: for project A, zones 8 and 9 are finished, one delivery is confirmed for Wednesday, and the billing pin at day 6 holds. For project B, the shop confirms the first batch ships Friday, keeping the week 3 install start on schedule. No zone is at risk in either project.
Time in the room: 27 minutes. Two projects, one agenda.
What breaks first when you add a second project too early?
The most common failure is not the review collapsing. It is the billing stage of the first project getting less attention in the week the second project starts.
New setup pulls focus. Shop questions for project B arrive in the same chat group as project A. Someone forgets to send the pre-meeting questions. The Tuesday session runs long catching up on updates that should have arrived before the session started. By the time the billing pin on project A is due, the person who holds the plan is configuring something for project B.
The billing date slips not because of a site problem but because the billing stage was not on the same visible line as the work when the distraction arrived.
This is why starting a second project before the first method is running reliably costs more than the calendar suggests. The method has to be automatic enough that a busy week does not require a conscious decision to keep it current.
When is a second project ready to join the timeline?
The signal is behavioural, not a calendar date.
The first project is ready to share a timeline with a second one when the Tuesday review runs without anyone being reminded it is happening. When the two pre-meeting questions go out without a prompt. When the person who holds the plan can describe the billing pin’s status in one sentence without checking anything first.
That typically takes three to four weekly reviews after the bars are in place. At that point, adding a second set of bars does not disturb the rhythm. The review absorbs the new project the same way it absorbed week five of the first one.
FAQ
How many bars is too many for one weekly review?
Above 25 moving bars in a single week, the session tends to run past 30 minutes unless the pre-meeting answers were read before anyone sat down. The fix is not splitting into two sessions. It is being precise about which bars count as moving: a bar that will not change position before next week does not need a live discussion. It gets confirmed in one line.
Can one person hold the plan for both projects at once?
Usually yes, when both run on the same method. The risk arrives when both billing pins land in the same week, or when a major shop delivery for one project coincides with a stage submission for the other. Those weeks need the review to be protected, not shortened. The agenda stays the same: bars, shop, decision needed.
Does the approach only work if you have a fabrication shop?
No. When a shop does not feed the site, the second pre-meeting question becomes which supplier deliveries are confirmed for this week rather than what is shipping from the shop. The structure is identical. The answers come from different people, but the review agenda does not change.
If you want to see what a combined two-project timeline looks like before the second project starts, a 45-minute call covers that. We walk one live project together, map where the bars stand, and work out at what point a second set of bars would add to the rhythm without disrupting it.