Hand the work over to your future self
By the end of the day, Julia had sent the client a proposal, replied to messages and made some progress on another calculation. Yet the list still looks unfinished: the client has not replied, the calculation has no checkmark and she does not know where to start tomorrow. She could stay another hour and try to “clear the backlog.” Or she could first bring her notes into line with what actually happened.
A brief review passes on context rather than adding another work shift. Its result: you know what is finished, what you are waiting for and which action you will resume with. Julia's story is illustrative; this approach does not promise to improve every reader's sleep or remove anxiety.
- Fact
Record what was actually done, without dismissing or embellishing it.
- Open question
Separate your own unfinished action from waiting for someone else's reply.
- Restart point
Leave a specific next step instead of a general “continue working.”
GTD's review guidance makes a useful distinction: reviewing your system and doing the work you find are different activities. The original material is about the weekly review. Here we suggest a narrower editorial practice for ending the day, rather than a shortened replacement for the whole methodology.
First, mark what has already happened
Look at the actions you worked on today. If the email was sent, mark sending it as complete. If the document is prepared but not yet checked, describe the result honestly. You do not have to leave a completed action open just because a larger goal has not yet been reached.
This review helps distinguish “worked a lot” from “got the needed result,” but does not require judging yourself by the number of checkmarks. A lengthy review of a complex calculation can matter more than ten quick replies. If the task title does not show substantial progress, record it briefly in the description.
Someone else's reply is not your unfinished sending task
After sending the proposal, Julia is waiting for the client's decision. She cannot do their part of the work, but she can choose when to check for a reply and what to do if there is none. So she creates a separate action: “Check whether a reply to the proposal has arrived.” She chooses the day based on the agreement and situation, rather than automatically putting it on tomorrow's list.
- I have not done it yet
The calculation has not been checked. It needs my next step and time to do it.
- I have done it and am waiting
The proposal has been sent. It needs a clear time to check for a reply, not resending it without a reason.
If someone promised to reply by a specific deadline, keep a record of that agreement. If there is no deadline, first consider when a follow-up would be appropriate. This article does not suggest a universal reminder interval: it depends on the context and your relationship with the recipient.
Leave a short note for unfinished work
The phrase “continue calculation” will make you remember where you stopped all over again tomorrow. A more useful note: “Prices for two items are entered. The third has no delivery date. First, open the colleague's email and check for a reply; then update the total.” It gives the current state, a missing condition and the first action.
A useful restart point answers three questions: what is already there, what is missing and what to do first. Do not rewrite the entire day's history. The note is for whoever does the work next—even if that is you.
If a colleague will continue the work, add access to the necessary material and check that the next step makes sense without a verbal explanation. Do not put confidential information in a public note for convenience. Even in a personal task, it helps to keep only the context actually needed for the action.
Carry a decision into tomorrow, not today's entire list
Open the coming day and account for meetings, promised deadlines and available windows. Choose a few actions you are actually ready to put there. If a task does not fit, decide what happens to it: another day, less scope, clarification of conditions or a revised commitment.
- It makes sense tomorrow, and there is time
Give a specific action a day. Make sure the necessary inputs are already available.
- A decision is needed first
Record the question or pending response. Do not present uncertainty as work that is ready to do.
Julia does not move everything to the next day: the pending client reply has its own check date, and the calculation gets a clear next step. This lets the morning list reflect actual possibilities. If a promised deadline is already at risk, communicate that in time—rescheduling in a planner cannot replace a conversation.
Set a boundary and end the review
You do not have to finish with an empty list. It is enough to keep important open questions from getting lost and give the next work a clear starting point. If the review keeps turning into an extra hour of task execution, separate the actions you find from the review itself and choose their time separately.
The next day, check whether the note helped you start without a lengthy reconstruction. If not, refine it: perhaps a link, input data or a clear action was missing. The quality of this small process depends on how useful it is when returning, not on how polished the evening report looks.
Set aside separate time for regularly reviewing all your commitments. Ending the day has a more modest purpose: avoiding the need to reconstruct known context in the morning. Start with one work task and see what is actually worth preserving between sessions.
More questions to clarify
How many minutes should this review take?
There is no fixed standard here. Limit the scope to the day's important changes. If you need a full review of projects and commitments, set aside separate time for it.
What if the day ended unexpectedly?
Save the available result and leave at least one restart point. The full review can wait; what matters more is keeping an important condition or promise from getting lost.
Was this helpful?
Rate the article and tell us what was missing. Your feedback goes to the Sinqly team and will not be published on the site.
Sources and notes
- Kelly Forrister, GTD: Review—the distinction between reviewing and doing work; original material on the weekly review
- The suggested process reflects editorial practice; it does not promise identical results for everyone.
Overdue tasks: review the backlog instead of carrying the worry forward
You do not have to promise yourself you will do everything tomorrow. Here is how to separate live commitments from outdated entries and make your list meaningful again.
Task breakdown: how to turn a large job into clear steps
What task breakdown means, how to choose a way to divide the work and when to stop. A client proposal example, common mistakes and moving your finished plan into Sinqly.
“It's urgent”: where to put a task when your day is already full
A new task does not create new hours. How to clarify urgency, choose the smallest useful result and agree on what will move.