Editorial review: 9 October 2026
Organise commitments before filling the calendar
Organizational skills include turning requests into usable task records, identifying dependencies, comparing commitments with available time and keeping unfinished work visible. A long list is not enough if it hides incompatible deadlines or treats an unknown input as available.
This guide uses a complete original scheduling exercise. You will see an infeasible first plan, a request to the person who owns the deadlines, an expressly supplied revised instruction and a finite completion record. The people and tasks are fictional. Their exercise durations are supplied assumptions, not estimates for your own workplace or proof of a productivity gain.
Harvard Law School's professionalism guide advises clarifying assignment requirements and deadlines and raising a need for assistance in advance. That guidance comes from its legal-career context. The scheduling method below is an editorial exercise, not an institution's prescribed framework or a universal workplace policy.
Convert each request into an identifiable task
A useful record separates the required output from the input, time assumption and deadline. If you do not know a deadline or lack an input, label that gap. Avoid replacing missing information with a reassuring calendar entry.
For the exercise, Mehul has a single uninterrupted work window from 9:00 to 10:30: 90 minutes. The scenario specifies that he performs one task at a time. His coordinator, Dina, owns the following outputs and deadlines:
| Task | Supplied duration | Requirement and deadline |
|---|---|---|
| A | 35 minutes | Format six supplied headings; deliver by 9:45 |
| B | 40 minutes | Check eight supplied item identifiers; deliver by 10:30 |
| C | 25 minutes after input is available | Assemble a note using an approved paragraph; deliver by 10:15 |
The headings and identifiers are available at 9:00. The approved paragraph for C is not available, and its arrival time is unknown. Mehul has no authority in this scenario to approve a substitute paragraph or change Dina's deadlines.
These facts define the problem. They do not say which task is most important to the organisation. Nor do they establish that interrupting one task and working on another makes either task take less time.
Show why the original commitment is infeasible
If all three inputs were ready, the supplied task durations would total 35 + 40 + 25 = 100 minutes. That exceeds the 90-minute window by 10 minutes. With sequential work, all three cannot finish inside the window under the given duration assumptions.
There is also a dependency problem: C cannot begin on the supplied basis until its approved paragraph is available. Its duration is not zero while waiting. It remains 25 minutes after that input becomes available. The unknown arrival time makes the original promise even less justified; it does not create spare capacity.
Consider A followed by B. A would occupy 9:00–9:35, leaving time before its 9:45 deadline. B would occupy 9:35–10:15, finishing before its 10:30 deadline. That leaves 15 minutes in the window, insufficient for C's supplied 25 minutes. Starting C at 10:15 would also miss C's original deadline even if its paragraph were ready then.
You can establish this conflict without knowing the organisation's priorities. What you cannot establish is permission to drop C or move its deadline. A usable organisational record makes both the arithmetic and that authority boundary visible.
Make the clarification request concrete
An original message from Mehul to Dina could read:
I have 90 minutes from 9:00 to 10:30. A and B take 35 and 40 minutes under our exercise assumptions, so they can finish by 9:35 and 10:15 if performed in that order. C needs another 25 minutes after its approved paragraph arrives; that paragraph is not available and its arrival time is unknown. I cannot commit to all three existing deadlines. Please confirm the priority or revised deadline and the route for C's approved input.
The message identifies the conflict and requests a decision from the actual deadline owner. It does not blame another worker for the missing paragraph or assert that a request has already been accepted. Sending such a message in a real workplace is an action; a drafted example is not proof of that action or its outcome.
Apply only the reply that is actually supplied
The next fact in this fictional exercise is Dina's explicit reply: complete A and B in that order within the morning window; move C's deadline to 11:30; do not begin C until its approved paragraph is supplied. The exercise also gives Mehul a separate work window from 11:00 to 11:30.
The revised plan is:
| Window | Planned work | Condition or limit |
|---|---|---|
| 9:00–9:35 | A | Available headings; 35-minute assumption |
| 9:35–10:15 | B | Available identifiers; 40-minute assumption |
| 10:15–10:30 | Unallocated time | Not enough to fit C's 25 minutes |
| 11:00–11:25 | C, conditionally | Only if the approved paragraph is available at 11:00 |
The extra morning time is not reported as a measured productivity saving. It is simply unallocated time after the two scheduled tasks. The conditional C slot has five minutes before the revised deadline, but it does not guarantee timely completion if the input arrives later.
For example, if the paragraph arrives at 11:10, the same 25-minute assumption places C's finish at 11:35. That would miss the new 11:30 deadline. This is a separate calculation from the conditional plan, not evidence that the paragraph actually arrived at 11:10.
Record completion separately from the plan
The fictional exercise now supplies two observations: Mehul finished A at 9:35 and B at 10:15. No paragraph arrival or completed C is supplied. The completion record therefore reads:
A — completed 9:35; six supplied headings formatted.
B — completed 10:15; eight supplied identifiers checked.
C — pending approved paragraph; no start or completion recorded.
Revised C deadline — 11:30, confirmed by Dina in the exercise.
Conditional C plan — 11:00–11:25 if approved input is available.
Marking C “done” because it has a calendar slot would be incorrect. Marking it “cancelled” would also be unsupported. Its actual state is pending input, with a revised deadline and a conditional plan.
When adapting this record to your own work, identify where the completed output can be found within the authorised system. Do not copy confidential documents into a public portfolio to prove organisational skill. An interview explanation can use an appropriate description of your contribution without exposing protected material.
Use the exercise to explain your approach
A bounded interview answer might say: “In this practice exercise, I recorded three tasks, compared their 100-minute total with a 90-minute window and identified an unavailable dependency. I asked the deadline owner to clarify the plan. After the supplied reply, I completed A and B at the recorded times and left C visibly pending.”
That answer describes actual exercise work and its remaining limit. It does not claim that the whole project succeeded, that communication caused a time saving or that Mehul determined the organisation's priorities independently.
The analytical-skills guide explains numerical comparisons and the limits of their conclusions. The teamwork guide helps distinguish your own contribution from the team's shared output. Use them for related evidence, while keeping this article focused on commitments, capacity and dependencies.
Frequently asked questions
Should I schedule tasks whose inputs are missing? A conditional slot can help planning, provided the dependency and uncertainty stay visible. It is not a completion promise.
Can prioritisation fix insufficient time by itself? It can inform what is done first or deferred, but it does not change the supplied durations. Obtain any required approval to change commitments.
Does an accepted plan prove the work is completed? No. Record observations and delivered outputs separately from approval and intended actions.
Must I use a particular app? This exercise works with a simple table or note. It does not establish that a paid tool, productivity score or elaborate calendar system is necessary.