Renovation project programme template and scheduling guide

Start with the work package

Identify the scope and location you want to plan. A complete house renovation and a single-room package need different levels of detail. The blank sheet has twelve fixed task rows, so choose a manageable package rather than squeezing every activity in the business into one timeline.

List activities with an identifiable outcome. "Fit selected items" can be useful when its scope is defined in the work pack. "Continue work" gives little help in deciding what must finish before another activity starts.

Include preparation and procurement where they affect the sequence. A task that produces no visible site progress can still govern when the team can fit something. Keep the relevant specification, drawing or supply arrangement available alongside the planning assumptions.

Use the example for model structure rather than as a prescribed trade sequence. Actual inspections, technical requirements and safe working arrangements depend on the project. Replace the activities with the work and review points your competent team establishes.

Fill in the yellow inputs

On Your programme, enter the start date and use the yellow cells for task names, owners, status, durations, predecessor IDs, earliest start days and constraint notes. Grey cells contain formulas and should remain intact.

Durations are positive whole working days. Each task has an ID fixed to its row. Keep those IDs and rows in place; inserting or sorting rows would change the lookup structure that connects predecessor finishes to later starts.

Use zero in a predecessor field when no earlier task governs that input. Enter an earlier task ID when there is a dependency. If two activities must finish before the next begins, use both predecessor columns; the later finish determines the earliest calculated start.

The Not before day input sets a further earliest working-day number. Day 1 is the first working day on or after the start date. Use that field for an explicit planning constraint, while retaining the reason in the note column so a colleague can understand it.

Understand the dependency calculation

The model starts a dependent task no earlier than the working day after its predecessor finishes. A task starting on day 3 with a duration of two days finishes on day 4. Its finish-to-start successor can begin on day 5.

With two predecessors, the sheet waits for both. If one finishes on day 7 and another on day 8, the successor begins no earlier than day 9. A later Not before day can push that start further; an earlier one does not override the dependencies.

Dependencies must point to earlier IDs. That keeps the sequence directed forward and avoids making a task depend on itself. An incomplete or invalid predecessor produces a check message rather than an invented finish date.

This simple model does not calculate alternative dependency types, float or a full critical path. It also does not decide whether two tasks can use the same person simultaneously. Inspect those constraints separately instead of treating a calculated date as a confirmed assignment.

Set the working calendar

The date formulas exclude Saturdays and Sundays. Add relevant actual non-working dates in the yellow cells on the separate tab, such as a planned closure or a holiday your team will observe. The template does not populate a UK holiday calendar automatically.

Check how you express supplier lead times. The example models them as working-day durations. A commitment stated in calendar days or as an actual delivery date needs appropriate conversion or a different planning constraint before entering it.

The displayed grid covers working days 1 to 30. Start and finish dates can still calculate beyond that range, but the visible bar will not show later days. Review the date columns if the final task exceeds the grid rather than assuming the blank area means no work remains.

Follow the worked programme

The sample begins with two days for scope and selections. Materials lead time then runs for five working days, finishing on day 7. Site preparation also starts after the initial decision and finishes on day 4.

The first-stage installation follows preparation and finishes on day 7. A one-day readiness review follows on day 8. Fitting selected items depends on both the materials task and that review, so it starts on day 9 and finishes on day 12.

Three finishing days follow, then a one-day snag review and handover ends on day 16. Those durations illustrate the spreadsheet arithmetic. They are not benchmark allowances for a bathroom, kitchen or other refurbishment.

Notice that the procurement and preparation branches overlap. The sheet does not move every activity into a single line simply because they concern the same project. The dependency choices explain which tasks can progress before both branches meet.

Test the delivery delay

The Delivery delay tab changes the materials allowance from five to nine working days. Its finish moves from day 7 to day 11. Preparation and the readiness branch retain their earlier dates because they do not depend on that supply task in this example.

Fitting now waits until day 12, finishes on day 15 and passes the delay into finishing and handover. The final task finishes on day 19. A four-day increase in lead time creates a three-day change to the overall modelled finish because the original branches had different finish dates.

Test one real dependency in the same way using a saved copy. Change the relevant duration or earliest start, then inspect which later dates move. If a task moves that should not, review its predecessor choice rather than manually overriding the formula.

Review readiness and crew separately

The owner and readiness fields are descriptive. A status of Waiting does not automatically stop the date calculation. Use the notes to identify missing access, selections or review decisions, and resolve them before relying on a planned attendance date.

Check overlapping activities against actual people, locations and equipment. Two rows may have compatible dependencies while still needing the same person. The worksheet exposes the proposed sequence; your scheduling review must resolve that resource conflict.

Keep a baseline copy and a dated revision when the plan changes. Explain any proposed effect on customer dates through the actual agreement process. Changing a spreadsheet does not silently reschedule a Booking, amend a subcontract or confirm a delivery promise.

Build your first programme

Choose one defined renovation package and list its tasks, durations and earlier dependencies. Add the relevant non-working dates, inspect the calculated sequence and identify the first missing readiness decision.

Then test one delivery delay and review the tasks that move. Keep the workbook beside the actual work pack so the team can check the scope and constraints behind each date. The useful programme explains its timing rather than presenting dates without reasons.