A Ten-Minute Daily Review for Busy Workdays

The next morning you open the laptop and cannot name the file that should come first. A ten-minute close the evening before leaves three traces: what actually finished, what is still waiting and who holds the next move, and the exact place to resume. Write it on paper or in the notes app you already use. No new software, and no report that someone else is expected to read.

What is worth writing down before you close the laptop?

Keep only what tomorrow morning can reopen.

1. What finished, in a form you can point to? An output is a result you can reopen tomorrow, named by a file or a row range, not by hours spent. "Closed 8 comments on PROJECT-ISSUES-v3" can be reopened. Here, PROJECT-ISSUES-v3 is a shared review sheet. "Two hours of meetings" cannot. A half-finished file still counts if you name the finished part: "comparison table, rows 1–12 filled, rows 13–20 empty." Stop at three finished items. The cap of three is this article's own convention, not a research result. A fourth line is usually the inbox copied out by hand.

2. What is still open, and who moves it? Keep an unanswered question, a decision that has not arrived, or a file you still have to read, and only when that item changes how tomorrow starts. Your next action and someone else's reply are different lines. For the other person, write a role and a time only when that time already exists in a message, a ticket or a calendar invite.

3. Where do you put your hands tomorrow? One small action, plus the file. "10:15 a.m., open PROJECT-ISSUES-v3, read rows 9 and 14" can start while the coffee is still hot. "Continue the project" does not tell you where to click.

The three questions above are the part you always write. The card below, a short note for yourself, has five fields. Two are optional: owner and due, and the separate file line. Leave those blank when nobody else holds the next step, or when the file name is already in the first action. The middle column is the made-up day told in the next section. The right column is yours.

Field	Illustrative example	Your entry
Completed output	8 comments closed on PROJECT-ISSUES-v3. Comparison table: rows 1–12 filled, 13–20 empty.	…
Open item	Rows 9 and 14 on PROJECT-ISSUES-v3 have no reply.	…
Owner / due	Reviewer. The "before 10:00 a.m." ask is already in the 3:10 p.m. message.	…
First action tomorrow	10:15 a.m., after the 8:30 a.m. meeting, open PROJECT-ISSUES-v3 and read rows 9 and 14.	…
File	PROJECT-ISSUES-v3	…

On a packed day, one sentence per field is enough. Leave owner and due blank when nobody else is holding the next step. Do not invent a clock time for a person you have not already asked.

If your job already requires a status note, a short update other people are expected to read, that note stays theirs. This card is the private line that gets you back into a file. You can copy the completed-output sentence into the status note. Do not forward the owner line as if it were a fresh assignment.

How a made-up Tuesday fills the card

None of the numbers below come from a real person's log. Morgan is a coordinator whose job is checking review comments.

Two files are on the desk. PROJECT-ISSUES-v3 is the shared review sheet. The comparison table is a separate file, still unfinished.

At 3:10 p.m. Morgan messages the reviewer and asks for a reply on rows 9 and 14 of PROJECT-ISSUES-v3 before 10:00 a.m. the next day.

A teammate at the next desk asks:

"Send v3 first thing tomorrow?"

Morgan answers:

"Not yet. Rows 9 and 14 are still with the reviewer. I'll open the sheet at 10:15, after the 8:30 meeting."

The exchange settles one fact. v3 cannot go out while those two rows have no reply. The 8:30 meeting is already on Wednesday morning's calendar, so those rows cannot be read inside it. The first open stretch after that meeting is 10:15 a.m.

Morgan sits down at 5:40 p.m. and stops at 5:50 p.m. PROJECT-ISSUES-v3 shows 8 comments closed. The comparison table stops at row 12, and rows 13–20 are still empty. Two finished items, under the cap of three. The inbox stays closed. There is no prize for a longer card.

Rows 9 and 14 still have no reviewer text. The card copies the 3:10 p.m. ask, a reply before 10:00 a.m., because that time is already in the message. It does not set a new deadline, and it does not paste the thread. The line shows the two row numbers and the role "reviewer." The first action is 10:15 a.m.: open PROJECT-ISSUES-v3 and read those rows. Tabs that have nothing to do with rows 9 and 14 can be closed. Tabs for work that is still running stay open.

At 10:15 the next morning, two branches are enough. If the rows now contain replies, Morgan reads them and only then chooses whether v3 can be sent or still needs a change. Tuesday night could not know that text. If the rows are still empty, one short chase names row 9 and row 14 and stops there. No retelling of the day. No new hour written onto the personal card.

Three sentences almost survived and should not have:

"Meetings and messages all day. Tell the reviewer to finish before 10. Continue the project."

The first has no file name. The second turns a message sent at 3:10 p.m. into a new order. The third does not say which file opens.

The half-finished comparison table does not win the first action. v3 is blocked on two rows, and someone has already asked whether it can be sent. A blocked promise comes before a file that is merely incomplete. If there were no v3 and nobody waiting, the first action would be the comparison table at row 13, still inside a gap Morgan controls, not inside the 8:30 meeting.

When ten minutes is too much

Ten minutes is this article's own convention for a few trial evenings, not a score you have to hit. In the example, Morgan starts at 5:40 p.m. and stops at 5:50 p.m. Write it in a single pass if you like. Keep a stopping time either way.

Pick the shape before you start, from the day you just had.

A day with your own files and someone else's unanswered reply uses all five fields, as Tuesday does.

A day that was almost only meetings, with one file still to reopen, uses one sentence per field. "No file closed" is a valid completed line. It is not a mark against the day.

When the day never touches a file, write one line for the first thing tomorrow, even if that thing is a call or a sentence you still have to send, then stop.

Past the time you meant to stop, write the first action and the file name, then shut the machine. The card is not a reason to stay.

On-call work means you are the person covering urgent calls. That work, and a shift handover, use the team's form first. This personal card does not replace an incident log or a handover record. Only if a separate file of yours is still unfinished after that form do you add one restart line, for that file alone.

The morning calendar moves the restart. With no meeting at 8:30, the action can sit at the start of the workday, still with a file name and row numbers. When the whole morning is already booked, move the action to the first open gap, even if that gap is after lunch. Do not write "during the 8:30 meeting" unless opening this file is the work of that meeting.

The Cornell Learning Strategies Center page is written for students. It suggests separating fixed commitments from time you can still arrange, and leaving room for rest. It does not measure whether an end-of-day card helps people at work. Morgan's example uses only that boundary. The 8:30 meeting is fixed. 10:15 is a gap Morgan can still place. Rest sits outside the card. 5:50 p.m. is when Morgan stops in the example. Cornell does not prescribe that clock time.

The three questions also do not answer where the hours went. That question belongs to a time audit: record the blocks, then look at them. The card does not lay out tomorrow's whole day either. That is time blocking, matching a block of time to a deliverable. From a ten-minute close you only need the file and the first action. Protecting 10:15 so the action can actually happen is the other article's job.

Several projects at once still keep the cap of three finished outputs. The open list holds only items that change tomorrow's first step. Unread mail is not an open list. A decision that has no file yet should be written as an action with a place to land: "type three questions into rows 9 and 14," not "think more about v3."

What you keep after three workdays

Try three workdays. Skip days that already have an on-call or shift form. If you miss an evening, do not rebuild it from memory to keep a streak. The next evening records only the files you actually touched that day. A reconstructed card turns into a story, and in the morning you still will not know which row to open.

The next morning, check what you actually opened.

If you opened the named file without searching the inbox, and someone else held a reply that day, keep all five fields.

When the owner line was blank all three days because nothing was waiting on another person, drop that field until a real dependency shows up. Leave the other fields.

When only the restart line changed the file you touched at the start of the day, and you never reread the rest, keep the restart line and the file name. Drop the other fields until a day actually has a dependency.

Do not choose by how many lines you produced. A longer card is not a better day. Wednesday's meeting can still run long. The card did not fail when that happens. It named a file.

Stop narrating the day when you start counting boxes in order to grade yourself. Go back to one line: the file, and the first action. Stay there until that line is used the next morning. If after three workdays the line still does not change which file you open, drop the card. A note that does not change the first file is not worth ten minutes.