Project Schedule: [Project name]

Schedule baseline for the project: milestones, activities with durations and dependencies, a gantt chart, resource loading, schedule risks and buffers, and the log of approved schedule changes. Based on common project management practice. Replace every [bracketed] value and every row marked Example.

1. Scheduling approach

The schedule was developed from the WBS ([WBS-001]) by defining activities per work package, sequencing them with dependency logic, estimating durations with the owners, and analysing the critical path. Durations are in working days. The project manager updates actuals and forecasts every [Friday]; the baseline changes only through approved change requests.

2. Milestones

The milestone table is the headline view used in status reports.

3. Activity list

Activities are listed with their WBS reference, duration, dependencies and owner.

4. Gantt chart

The chart shows the baseline schedule by workstream; critical path activities are highlighted.

5. Critical path

The critical path runs A01, A02, A04, A07, A09 to M4, with a total duration of [78] working days and zero float. Any slip on these activities moves go-live unless absorbed by the project buffer.

Near-critical paths (float of [5] days or less): [A05 Integration build, float 5 days]. These are monitored weekly alongside the critical path.

6. Resource loading

Resource demand per role and month is compared with availability; overallocations are resolved by levelling or by adding capacity.

Levelling actions: [for example, shift A05 start by 5 days within its float; request 0.5 FTE tester from QA pool for month 4].

7. Schedule risks and buffers

The following risks could delay milestones; they are also recorded in the RAID log.

Buffer policy: a project buffer of [10] working days sits before M4. Buffer consumption is reported as a percentage; more than [50%] consumed before UAT starts triggers a recovery plan.

$\text{Buffer consumed} = \frac{\text{Days of buffer used}}{\text{Total buffer days}} \times 100\%$

8. Schedule change log

Approved changes to the schedule baseline are recorded below.

Standard and licence note

Based on common project management practice for schedule development, critical path analysis and schedule control. This template is original text written for this collection. Template licence: MIT.