5.4Templates & scheduling best practices
The essentials in 30 seconds
- Templates (.mpt) capture know-how: a model project (tasks, milestones, calendar, generic resources) that you reuse to start a similar project.
- A healthy schedule: automatic mode, linked tasks, minimal constraints, clear WBS, milestones, baseline, kept up to date.
- You check the schedule before sharing it: no floating tasks, no stray constraints, no forgotten overloads.
Running mini-case — Meriem capitalizes a template and makes a schedule reliable
Meriem, a project manager at an engineering & construction (BTP) company in Algiers, regularly starts sites of the same kind: studies, permits, structural works, finishing works. Rather than starting from a blank page each time, she saves her best schedule as a template (.mpt): standard tasks, milestones, indicative durations, generic resources and calendar. The new site therefore starts faster and more accurately. Before sharing a schedule, she performs a health check: are the tasks linked (rather than dated by hand)? Few stray constraints? Is the baseline set and progress kept up to date? Where a task “floats” without a link, she fixes it. Her schedule becomes professional, reliable and easy to maintain.
Standalone case for this section: it comes back in the lesson, the diagram, the script and the 48h challenge of section 5.4.
1. Capitalizing with templates
You do not start from zero on every project: templates capture know-how. A template is a model project — tasks, milestones, indicative durations, generic resources, calendar — that you reuse to start a similar project. Project provides built-in templates and lets you create your own (save a project as .mpt). Meriem thus builds a library by type of site: each new project starts faster and more accurately.
2. A healthy schedule
A few best practices guarantee a healthy schedule: automatic mode, linking tasks rather than setting dates by hand, minimizing rigid constraints, keeping a clear WBS, adding milestones, saving a baseline and keeping the schedule up to date. These rules chain together: a linked schedule recalculates, a baseline makes it possible to measure variances, and regular tracking keeps it alive.
3. Checking before sharing
You check the schedule before sharing it: no unlinked tasks that “float”, no stray constraints, no forgotten overloads, no inconsistent dates. This is the synthesis of the whole guide: a quick check — tasks linked? few constraints? baseline set? up to date? — is enough to diagnose the health of a schedule and to distinguish professional work from a patched-together file.
🔎 Concrete example — 🔎 Concrete example — The health check
Meriem makes a quick diagnosis of her schedule before sharing it:
Tasks linked? Few constraints? Baseline set? Up to date?
No unlinked tasks that float? No forgotten overloads?
→ save the best project as a reusable .mpt template.Result: a professional, reliable schedule that is easy to maintain.
Reflex: capitalize a library of templates by project type.
Section vocabulary
- Template (.mpt)
- Reusable model project (tasks, milestones, calendar, generic resources) to start a similar project quickly.
Simple example: Meriem saves her best site as an .mpt template.
What it is not: starting from a blank page on every project.
Reflex: template = reusable model project.
- Healthy schedule
- A well-built schedule: auto mode, linked tasks, few constraints, clear WBS, up to date and without anomalies.
Simple example: Meriem checks that her schedule is linked and baselined.
What it is not: unlinked tasks that float.
Reflex: link rather than date.
- Best practices
- Proven scheduling rules (link rather than date, add milestones, baseline, update) that guarantee reliability.
Simple example: Meriem sets milestones and a baseline on her schedule.
What it is not: multiplying rigid constraints.
Reflex: they distinguish a pro schedule from a patched-together file.
- Schedule check
- Checking for anomalies: unlinked tasks, stray constraints, overloads, inconsistent dates.
Simple example: Meriem fixes a floating task before sharing.
What it is not: sharing without checking.
Reflex: check before sharing.
- Capitalization
- Reusing know-how (templates, lessons learned) from one project to the next to save time and improve quality.
Simple example: Meriem builds a library of templates by type of site.
What it is not: reinventing every project from scratch.
Reflex: capitalizing = starting faster and more accurately.
In practice — In practice — Reuse templates and make the schedule reliable
- Start from a template (built-in or in-house) to begin a similar project, rather than from a blank page.
- Save a good project as a template (.mpt) to reuse and standardize it in your team.
- Apply best practices: automatic mode, linked tasks, minimal constraints, clear WBS, milestones, baseline.
- Check the schedule: identify unlinked tasks, stray constraints and forgotten overloads, then fix them.
Step-by-step script — make a schedule reliable like Meriem (10 min)
1) Choose a suitable template (.mpt) or save your best project as a template. 2) Create the new project from this template. 3) Check automatic mode and that tasks are linked (no dates entered by hand). 4) Reduce rigid constraints and clarify the WBS; set milestones. 5) Save a baseline and date it. 6) Perform the health check: floating tasks, stray constraints, forgotten overloads.
A healthy schedule is recognized by a quick check: linked, few constraints, baselined, up to date.
Copy-paste template — my schedule health check
Starting template: ___ (.mpt built-in or in-house)
[ ] Automatic mode enabled
[ ] Tasks linked (no dates entered by hand)
[ ] Minimal constraints · clear WBS · milestones set
[ ] Baseline saved
[ ] No unlinked task that “floats” · no forgotten overload
Last update: ___
Rule: capitalize a template, link, add milestones, baseline, check.In-house template
Meriem saves her best site schedule as a reusable .mpt template.
Built-in template
Meriem starts from a provided template to discover a standard structure, then adapts it.
Health check
Meriem tracks down floating tasks and stray constraints before sharing.
Library
Meriem builds a library of templates by project type for her team.
✓ Best practices
- Start from a template rather than a blank page.
- Apply best practices: link, add milestones, baseline, keep up to date.
- Perform a health check before sharing the schedule.
✗ Common pitfalls
- Entering dates by hand rather than linking tasks.
- Leaving tasks “floating” without a link.
- Forgetting the baseline or never updating progress.
Key takeaways
- Templates (.mpt) capture know-how: you do not start from zero.
- Healthy schedule: auto mode, linked tasks, minimal constraints, clear WBS, milestones, baseline, up to date.
- Check: no floating tasks, no stray constraints, no forgotten overloads.
- These practices distinguish a professional schedule from a patched-together file.
48h challenge — apply it tomorrow
Like Meriem, save one of your projects as a template (.mpt), then start a new project from this template. Then perform the health check: linked tasks, minimal constraints, baseline set, no floating tasks. Write in one sentence the time saved.
- I can explain what an .mpt template captures.
- I know what makes a healthy schedule (link, add milestones, baseline, up to date).
- I know how to check a schedule before sharing it.
Frequently asked questions
What are the most common mistakes that make a schedule “unhealthy”?
The classics: entering dates by hand instead of linking tasks (the schedule no longer recalculates); leaving everything in manual mode; multiplying rigid constraints; tasks with no predecessor or successor that “float”; forgetting the baseline; never updating progress. Each one breaks a property of a living schedule. A quick check is enough to diagnose the health of the schedule.
Is it better to create your own templates or use the provided ones?
Built-in templates are a good starting point to discover standard structures and get inspiration. But for an organization, nothing beats its own templates: they reflect your real processes, your usual phases, your standard resources and your standards. After a few successful projects, save the best one as an .mpt template and refine it with lessons learned.
What is a healthy schedule?