The Daily Log is a simple running record of day-to-day project activity. It captures what happened, what decisions were made, and what needs follow-up — without the overhead of formal reporting.When to use it• During active project stages to track informal notes and observations• To record ad-hoc conversations, phone calls, and quick decisions• As a personal reference for the Project Manager between formal reports• To capture issues before they are formally raised in the Issue RegisterWhat it helps you capture• Date and brief description of activity or event• Actions taken or decisions made• Follow-up items and who owns them• Reference to related documents or communicationsWho typically owns itProject Manager — maintained daily and reviewed weekly.Related Glidepath processes• Control Stage (CS) — daily tracking supports stage monitoring• Manage Product Delivery (MP) — logs team activity and work package progressRelated templates• GLP002 Lessons Log — significant events from Daily Log may become lessons• GLP011 Issue Register — formal escalation of captured problems• GLP026 Checkpoint Report — summary of Daily Log entries for Work Package reviewsPractical use noteIn an ICT software rollout, the Project Manager uses the Daily Log to note: “14/03 — Spoke with vendor about API latency. Agreed to add monitoring. Follow up next week.” This informal record becomes invaluable when the same issue resurfaces three weeks later.
Glidepath