Level 6 · In practice

6.3Best practices & pitfalls

Goal: adopt the right reflexes for a healthy Project schedule and avoid the most frequent mistakes.

Estimated time: 10 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

Design: calendar set up, clear WBS, milestones, tasks linked through dependencies (no hard dates) and minimal constraints.
Mechanics: automatic mode, right task type, rates entered and overallocations resolved — the schedule stays accurate.
Steer: baseline saved before starting, progress updated regularly and communication in the right format.

Meriem's thread — the rule taped to the wall

After a quarter steering several sites in Algiers, Meriem taped her rule to the wall: a healthy schedule is linked, recalculates, is baselined and kept up to date. What mattered most was not one more feature, but a few habits — link rather than date, stay in automatic mode, set the baseline before starting — and a pitfall narrowly avoided: dates entered by hand that had frozen the whole schedule.

Choose a single habit to anchor in your routine, then move on to the next.

The planner's do's and don'ts

The difference between a professional schedule and a tinkered file comes down to a few habits. They are what keep the schedule healthy day after day, far more than the latest fashionable feature.

Link rather than date

A schedule built on dependencies recalculates on its own; a schedule dated by hand freezes and lies from the first slip. It is the profession's number-one reflex.

Prove rather than assume

Without a baseline, no measurable variance; without rates entered, costs at zero. You measure before asserting, and you keep progress up to date.

✓ Do

Set up the calendar (working days, time off) BEFORE entering tasks.
Work in automatic mode: the schedule recalculates.
Link tasks through dependencies rather than setting dates by hand.
Structure a clear WBS, place milestones on key steps and choose the right task type.
Set a baseline before starting, and keep it.

✗ Avoid

Enter dates by hand instead of linking tasks.
Leave all tasks in manual mode by default without knowing it.
Multiply rigid constraints (conflicts, broken recalculation).
Forget to enter rates (costs at zero).
Skip the baseline (no variance tracking).

Common misinterpretation: “tick every box every day”. No. These are habits to install one by one: choose one (e.g. link rather than date), anchor it in your routine, then move on to the next.

Text version of the diagram (SEO / screen readers / translation): 1) Structure side — calendar set up, clear WBS, milestones, tasks linked through dependencies (no hard dates), minimal constraints. 2) Mechanics side — automatic mode, right task type, rates entered, overallocations resolved. 3) Steering side — baseline saved before starting, progress updated, communication in the right format. Lesson: a healthy schedule is linked, recalculates, is baselined and kept up to date.

Script ready to say — checking a schedule's health (30 s)

“Am I linking rather than dating? Am I in automatic mode? Is my calendar right? Do I have a baseline? Is progress up to date? If any answer is no, I fix it before sharing.”

Reread this before considering a schedule reliable.

Script ready to say — explaining your reflexes (30 s)

“I structure then link, I stay in automatic mode, I set a baseline before starting and I update every week — that is a reliable schedule.”

One sentence to sum up a healthy practice.

Copy-paste template — schedule health check

[ ] Calendar set up (working days, time off)
[ ] Automatic mode (no tasks in manual mode)
[ ] Tasks linked (no hard dates)
[ ] Clear WBS + milestones
[ ] Rates entered (costs different from 0)
[ ] No red resources
[ ] Baseline saved

Copy-paste template — wrong track to correct

-- BEFORE: date entered by hand
Task B: starts 12/03 (frozen, no longer moves)
-- AFTER: dependency link
Task A (5 d) --FS--> Task B
-- The schedule recalculates when A slips

VSE / small budget

One habit per quarter is enough: link rather than date + set the baseline first, the rest afterwards.

Algiers SME

Adapt routines to local realities: irregular supplies, bad weather, several sites, a known point of contact.

Remote / hybrid

The number-one discipline at a distance: written update, variance vs baseline noted, even for small reviews.

Intercultural

Check local practices rather than assuming: a habit obvious to one person must be explained to every newcomer.

Caution: Generic reminder: golden rule — a healthy schedule is linked, recalculates, is baselined and kept up to date; never distribute a schedule frozen by hard dates or a baseline changed without consultation, and keep the original baseline.

48h challenge — apply it tomorrow

Put your schedule under the microscope: zero hard dates, zero tasks in manual mode, zero red resources, zero costs at zero. Fix the first variance you find.

Section exit checklist

I know the reflexes to adopt and the pitfalls to avoid.
I have checked the critical points of my schedule (links, auto mode, baseline).
I have done the 48h challenge or scheduled its date.

Self-assessment 1-5: consistency of good reflexes?pitfalls avoided?

← Previous : Recurring issues (playbook) (V3)Next : Toolkit (V3) →

Check your understanding

Before sharing a schedule, which reflex protects Meriem best?

💡

Golden rule: a schedule is linked, recalculates, is baselined and kept up to date — the rest (options, features) only reveals that base.