A project manager's week template: office work, site commitments and reporting
The manager works on a laboratory fit-out and a clinic renovation. The laboratory needs a site conversation before an owner decision, while the clinic's reporting inputs arrive later. Copying one generic office week would leave both jobs apparently scheduled without respecting their different receiving dates.
Build a reusable personal pattern from the projects' actual decision and reporting needs. Place office analysis, site commitments, preparation and received meetings together, keeping each project's dates identifiable. The template should make work feasible rather than impose a Monday cost review or an empty billing week on everyone. Revise it when the commitments change, including during the week.
Connect the office pattern to actual project receivers
- List the owned duties and their sources. Identify cost and forecast work, site visits, owner inputs, document reviews and reporting responsibilities that actually belong to you. Confirm due dates, participants and expected outputs with the relevant teams. A recurring task name does not establish a universal frequency or transfer the coordinator's authority to the manager's calendar.
- Place preparation before the receiving date. Work backward from the real meeting or submission to input gathering, review and your defined contribution. Include travel and site access. Distinguish a proposed visit from confirmed participant availability. Scheduling an owner call before the necessary site information arrives does not make that information available; resolve the sequence rather than inventing a forecast answer.
- Keep the projects' needs distinguishable. Show which job owns each commitment and which period can genuinely serve shared administration. Check conflicts and avoid counting one block twice. Arrange received delegation or another time when both projects need attention together. Preserve required response routes; declaring billing week empty cannot make other site or owner responsibilities disappear.
- Review exceptions and share useful availability. Give site teams the information they need about your visits, response periods and cover. Check actual inputs and changes before copying the next week. Update altered dates and assignment decisions with their receivers. A standing pattern can support predictable contact without guaranteeing that every visit occurs on the same day throughout the project.
Common mistakes
- Imposing example weekdays on different project rhythms.
- Holding the owner conversation before its inputs are ready.
- Counting one work block against two incompatible commitments.
- Protecting billing by silently dropping all other duties.
Checklist
A project-manager week should show
- Owned duties and their actual source dates.
- Prepared inputs before receiving commitments.
- Confirmed visits, travel and access.
- Separate project needs and received conflict responses.
- Shared availability, cover and current exceptions.
Check your understanding
The baseline site visit is Thursday, but the owner needs its input Wednesday. Should the template decide the sequence?
