How to stay organized at work: 6 moves that work
To stay organized at work, write every request in one place, turn what you promised into a task, and give anything you're waiting on a follow-up date. This guide covers requests that arrive by email, chat and meetings, how to trade one commitment for another, a first week of steps, and what to do when the list falls behind.
Why work requests get lost
A request arrives in email. Another one lands in chat while you're halfway through something else. A meeting ends with three people each expecting a different thing from you. Every source holds part of the picture, and none of them holds all of what you've agreed to do.
The requests don't disappear. They wait in three places at once, each one easy to forget, because the last thing you did was answer something else. You end up with a job that feels busy and no list that shows both.
A general to-do list handles the easy case, a request you make for yourself. Work adds three things a plain list doesn't cover: the requests come from other people, some of them are promises you made out loud, and some of them can't move until someone else does something. Our guide on how to make a to-do list covers building the list, and how to prioritize tasks covers ranking it. This guide is about the other three.
This page is about everyday work requests and the week they land in. If work has started to affect your sleep, your health or your mood, a doctor is the right person to talk to.
Six moves to keep work requests straight
Do them in order the first time. After that, the fourth and sixth moves are the ones you'll use every day.
-
Write the request as one action
A request is easy to lose while it's still a topic. "Attendee count" and "room access" each turn into a task when you name the next move: "Send the updated attendee count to Dana", "Ask the venue who opens the room". One action per task, and you can tell what's still open.
-
Write down what you promised
Most work requests arrive one way and leave another. A colleague says "can you send the numbers by Thursday" in a meeting, and the meeting ends before you write it down. Write the promise as a task with the person and the date in it: "Send Priya the October numbers by Thursday". A promise made out loud is the one you're most likely to forget.
-
Record the deadline you were given
Ask when the work is needed and write that date down. "By Friday" can mean Friday morning, the end of Friday or the end of the week, and the difference decides what fits. Leave an item undated when nobody's asked for a date, rather than inventing one. When two things land on the same day and only one fits, deciding which comes first is a separate job.
-
Give waiting items a follow-up date
Some work isn't yours to move. The supplier owes a quote, the venue owes an answer. Write those as a waiting item with two things in it: who you're waiting on, and the date you'll check back. "Check for the supplier reply on Wednesday" keeps the promise visible. A nudge you've sent isn't a closed item, so keep the task until the answer lands.
-
Trade a commitment when new work won't fit
New work arrives and the week is full. Say which promise moves, in the same message where you ask for the new one: "I can send the attendee count Thursday and the report Monday, or the report Thursday and the count Monday. Which comes first?" Write the answer down and change the date on the task, so the trade becomes a decision instead of a guess and the other person can plan around it.
-
Check requests in batches
Pick two times a day to read messages and the requests waiting on you, and let the rest wait for the next slot. The research below found that people took longer to get back into a task after it was interrupted, and that interruptions which fitted the task they were already doing did less harm than the ones that came from nowhere. People also interrupt themselves almost as often as others do.
One week of Morgan's requests
Morgan coordinates a training day at work. Here is one week of requests, and what Morgan does with them. They arrive out of order, from three different places, and one of them waits on somebody else.
Example request breakdown
- Long-termRun the training day on time
- Mid-termConfirm the venue, supplier and count
- Short-termAsk the venue who can open the room
We wrote this example ourselves. Morgan's week is fictional, and every request in it is the kind that arrives by email, chat or in a meeting. The three lines show where a request sits: the aim it serves, the outcome it needs, and the next move.
On Monday an email from Dana asks for an updated attendee count by Thursday. A colleague asks in chat for Morgan to chase the supplier's quote. In the morning meeting a colleague asks who can open the room. Morgan writes three tasks, one for each, and leaves the rest of each request where it already lives.
The attendee count has a real date, so it goes on Thursday. The quote isn't Morgan's to move until the supplier replies, so it becomes a waiting item: "Check for the supplier reply on Wednesday". The room question gets today's task, because the answer changes the training plan: "Ask the venue who can open the room".
On Tuesday the manager asks for another report by Thursday. Morgan checks what's already promised and answers with the trade: "I can send the attendee count Thursday and the report Monday, or the report Thursday and the count Monday. Which comes first?" The manager picks the report. Morgan moves the count to Monday and holds a decision that's now written down instead of remembered.
One more idea, comparing room layouts for next year's event, has no date and nobody waiting on it. It stays on Someday until a request makes it real, and it costs nothing to leave it there.
The screenshot is the same week as a list in LeapSteps: today's request with its subtasks open, the reply to the supplier already marked done, and under Upcoming the follow-up for Wednesday and the attendee count for Thursday, with AI working on the update. A request with a date and one without a date sit in different places, so you can see at a glance what's still open.
Keep every work request in LeapStepsGet it for Windows
To try this in the app, see the AI to-do list page: how a request turns into a task you can act on.
Your first week
Six short tasks to get the system in place. The aim this week is one clean list and one promise you can see, not a perfect week.
- Choose one place for work requests5 min One list you'll really look at. Two lists means you read neither.
- Collect the requests from one source15 min Pick email or chat, not both, and mark where you stopped so the next source starts there.
- Write two promises as tasks10 min Something you agreed to do in a meeting, with the person and the date in the task.
- Give one waiting item a follow-up date5 min Who you're waiting on, and the day you'll check. The item stays open until the answer lands.
- Check one day against your calendar and make a trade10 min Two things due on the same day, one that moves, and the message that says so.
- Review your list at the same time each week15 min A fixed slot, like Friday afternoon, so the list depends on a time rather than on a calm moment turning up.
When the review slot arrives, you're looking for three things: dates that are close, items waiting on someone else, and projects with no next action. The Stanford guide on keeping to-do lists suggests the same habit for a weekly list, and our guide to weekly planning shows how to carry those decisions into the week ahead.
What the research says
Two findings the moves lean on, and what each one changes about the way you work.
-
Stanford Center for Teaching and Learning
Write tasks, not projects
A task is something you can do in one sitting, ideally in 30 minutes or less. A project takes several tasks to finish. The same guide recommends picking a regular time each week to write your weekly list, so the list gets made on a schedule.
Read the guide -
Brumby, Janssen and Mark
Interruptions cost you the resumption
Controlled experiments, cognitive models and observational studies all point the same way: interruptions take time to recover from and can lead to errors, shorter interruptions do less damage than long ones, and interruptions that fit the task you were already doing do less damage than the ones that don't. People also interrupt themselves almost as often as others do.
Read the chapter
These findings test the ideas behind the method, not the app itself. Checked November 12, 2026.
When the system stops working
A missed request or a missed review doesn't mean you start over. Open the list you have and take the next move.
-
The requests are scattered again.
Pick one source and capture what's open there. Don't wait for every inbox to be empty, and mark where you stopped so the next source picks up from there. In LeapSteps a list keeps its own tasks apart from "Today" and "Upcoming", so work waits in its own place without going missing.
-
Today is already full.
Check the dates and the time you have, then move the work that can wait. When two commitments clash, ask the people affected which one moves and write the answer down. Press and hold a task that can wait and drag it onto the "Someday" header, so today's list holds fewer things you won't finish.
-
A waiting item has gone quiet.
Write a short follow-up that says what you need and by when, and give the item a new check date. If the answer is still pending, keep it open. Your part is done when you ask, not when the answer arrives.
-
You missed the weekly review.
Start with the dates that are closest, then take one project at a time. Add a next action or a follow-up date, then come back to the rest when you have room. A shorter reset beats waiting for a free hour.
Questions, answered
How do I keep track of requests from email, chat and meetings?
Write each request down in one place and leave the source material where it belongs. Use a verb, note who asked, and record a real date if there's one. A link to the message or the name of the meeting is often enough to find the detail again. After a meeting, check your notes for the promises you made and turn each one into its own task. If someone else owns the next move, write a follow-up with a check date instead of a task. Review the same place every week so it becomes the place you trust.
How do I stay organized when several projects need attention?
Give each active project a name you recognize, and make sure each one has a next action or a waiting note. Look across the projects during your review rather than planning each one on its own, because that's where two deadlines landing on the same day shows up. Keep the background and the decisions in the project's own notes, and put the action you own on your list. If new work won't fit, use the list to have the trade conversation with the person setting priorities, so you make the choice together.
How often should I review my work list?
Pick a regular time each week and treat it as an appointment, the way the Stanford guide on keeping to-do lists suggests for a weekly list. Friday afternoon or Sunday evening are common choices, and the slot matters less than keeping the same one. In that review you're looking for three things: dates that are close, items waiting on somebody else, and projects with no next action. Leave with decisions rather than a fresh backlog. If your work changes week to week, shorten the review instead of skipping it. A ten-minute reset that happens beats an hour that never does.
Should I use lists or labels for work tasks?
Use separate lists for areas you open and review apart, such as work and home, and labels for the things your tasks have in common, such as a project name. A list holds one set of tasks with its own order. A label is a tag, so one task can carry several of them without sitting in several places. Start with a handful of names you recognize at a glance, and add another only when it helps you find work. If you're classifying more than acting, cut the names back.
Can an app help me stay organized at work?
It can hold the requests and the promises so you stop carrying them, though it can't make anyone answer their email. LeapSteps is our app. It's a to-do list where any task can link to a goal's next step, AI drafts smaller steps when you tap Generate, and the Plan sorts itself into "Today", "Upcoming" and "Someday". A list keeps its own tasks apart from "Today" and "Upcoming", and "Add to Plan" brings a task over when it's time. Sharing a project with colleagues needs Pro: with Pro you can set up a Team of up to five people. What no app does is chase a supplier for you, and that follow-up is still yours to send.
Give every request a place
LeapSteps gives you dated tasks for the work you've promised and follow-ups you can date like any other task, with the list in one place you can come back to. Explore the AI to-do list for more about the app.
Get LeapSteps
Free to start. Pro comes with a 7-day free trial.
LeapSteps isn't currently offered in the European Union, the European Economic Area or the United Kingdom.
Keep going
For a bigger aim behind this week's work, read how to achieve your goals.
- Guide How to prioritize tasks Choose what comes first when several tasks compete.
- Guide Weekly planning Review your commitments and plan the week ahead.
- Guide How to make a to-do list Build one list you can come back to.
- Side project A side project after a day job Keep the day job's requests out of your evenings.
Sources
- Stanford Center for Teaching and Learning: Keeping To-Do Lists.
- Duncan P. Brumby, Christian P. Janssen and Gloria Mark: How Do Interruptions Affect Productivity?, in Rethinking Productivity in Software Engineering, Springer, 2019.
Checked November 12, 2026. The work example and the suggested times are ours.