A weekly calendar can be full by Monday morning and still have no room for the work that matters. One delayed decision, revised drawing, or contractor’s question can throw it off. Separate commitments that must happen at a set time from work that can move, then leave room for changes before filling the remaining hours.
Plan around commitments, not a complete task list
Start with what cannot move: appointments, site visits, submission deadlines, scheduled reviews, and time away from work. Add the preparation and follow-up they require. A two-hour client meeting may also mean reviewing drawings beforehand and recording decisions afterward. Those hours count, even if they are not on the meeting invitation.
Next, choose a small number of outcomes that matter by the end of the week. Name the finished work, not just the activity. “Send the revised floor plan for client review” is easier to plan around than “work on the floor plan.” For a project team, the outcome might be a coordinated drawing package, a response to a permit comment, or a cost decision ready for approval. For an individual, it could be a completed draft or a confirmed appointment.
Keep everything else on a separate task list. A weekly plan is a decision about capacity, not an inventory of all the work still to be done. If a task has no realistic place this week, leave it on the longer list rather than assigning it a calendar slot you are likely to ignore.
Estimate available time before assigning it
An open calendar slot is not necessarily usable work time. Breaks, routine messages, and transitions between meetings take up part of it. Estimate how long your priority outcomes will take, using similar recent work where you can. If the last drawing review took most of a morning, a half-hour slot for the next one is unlikely to be enough.
Leave unassigned time in several parts of the week instead of putting all the spare capacity on Friday. How much you need depends on the work. Established tasks done alone may call for less reserve than a week involving site conditions, approvals, or several decision-makers. Treat that reserve as working capacity, not as an opening for another promise.
Say Tuesday has six hours between fixed meetings, and routine coordination usually takes an hour. Rather than assigning all six hours to design work, you might set aside three hours for a demanding task, one for a smaller one, and leave an hour unassigned. These are estimates for that day, not rules about how long the tasks should take.

Give different kinds of work different places
Protect work that needs sustained attention
Give demanding tasks blocks long enough to make progress without repeated restarts. Writing a design brief, reviewing technical drawings, or reconciling conflicting comments usually takes more continuous attention than routine correspondence. Place those blocks where interruptions are least likely for you; that might be early morning or the time after scheduled meetings.
Write the intended output in the calendar entry. “Review accessibility comments and mark required changes” gives you a clearer place to resume after an interruption than “project work.” It also identifies a portion of the work you could delegate.
Group short coordination tasks
Give messages, approvals, calls, and small administrative tasks regular windows so they do not break up every focus block. Urgent matters still need a route through. Agree on what qualifies as urgent and who should be contacted when a decision cannot wait. On a construction project, a safety issue or a question holding up scheduled work needs a different response from a request for a noncritical update.
Plan for dependencies, too. If a cost review requires updated quantities, schedule the quantity check first and confirm who will provide them. “Finalize budget” on the calendar will not resolve a missing input. When someone else controls the next step, note when you need their response and what you will do if it does not arrive.
Choose where flexibility belongs
Some work can move more easily than other work. Mark tasks as fixed, movable within the week, or conditional on another event:
- Fixed: a booked meeting, a submission cutoff, or a visit requiring site access.
- Movable: work that must be completed this week but can shift to another open block.
- Conditional: work that cannot start until feedback, information, or approval arrives.
Put fixed commitments in first. Give movable priorities named blocks, with an alternative opening in mind. Do not fill the week with conditional tasks on the assumption that their inputs will arrive on time. If client comments are due Wednesday, reserve time for them but identify independent work you can do if they are late.
When a new request comes in, ask what it would displace. Weigh its deadline, the consequences of delay, and its effect on other people’s work against what you already planned. New does not automatically mean more important. If taking it on will move a promised deliverable, tell the person affected rather than silently carrying both commitments forward.
Use a short review to keep the plan current
Spend a few minutes near the end of each workday checking what happened against the plan. Update unfinished work, check tomorrow’s dependencies, and decide whether unused reserve time should stay open. You do not need to rebuild the week every evening; change what the new information requires.
When several people or approvals are involved, add a slightly longer midweek check. Look for blocked tasks, approaching deadlines, and meetings that can no longer serve their purpose. If drawings are incomplete and a planned review cannot produce a decision, use that time to resolve the missing information, reschedule the review, and tell participants before they prepare for it.
Make a brief note of why work moved, without turning the plan into a detailed timesheet. “Awaiting survey,” “estimate took longer,” or “urgent site query” may be enough to reveal a pattern. Repeated delays caused by missing inputs point to a coordination issue; repeated underestimates call for larger work blocks next time.
A worked example for a changeable week
Suppose a project manager is due to issue a revised drawing set on Thursday. There is a team coordination meeting on Monday, a site visit on Tuesday, and client comments may arrive Wednesday. The manager reserves Monday afternoon for drawing review, time after Tuesday’s visit to record site observations, and Thursday morning for final checks. Wednesday afternoon stays partly open for comments. If they arrive late, that time can go toward updating the project decision log.
On Tuesday, the site visit reveals a condition that affects a drawing detail. The manager uses Wednesday’s open block to coordinate the revision, moves the decision-log update to Friday, and tells the client whether Thursday’s issue date is still feasible. Moving a calendar entry is only part of the response; the manager also checks the effect on the promised deliverable before the deadline arrives.

Before finishing the Friday review, the manager records the unresolved site question, who owns it, and when a response is due. Without that line, the task could disappear from the calendar while still holding up the project.
