How to Mark Location-Dependent Tasks When You Alternate Between Home and the Office

What makes a task truly location-dependent?

Ask: “If I were at the other location right now, could I complete this next action with the tools and access I have?” If yes, the task is flexible. If no, mark the place that holds what is missing. This is a practical adaptation of context-based task lists, which map actions to the people, places, and tools needed to do them. Getting Things Done’s guide to context lists

For example, “draft the project update” is probably flexible if the document is accessible on your laptop from either location. “Scan the signed paper form” is office-dependent if the form and scanner are at the office. “Compare the printed proof with the original” is home-dependent if the original is stored at home. A task does not become office-only merely because it is work, nor home-only because it is easier to concentrate there.

Make the action concrete before assigning a place. “Finish the report” may conceal several steps: open the shared spreadsheet, check a printed figure, draft the summary, and send it to a colleague. If only the printed check requires the office, split that out or identify it clearly; do not label the whole outcome office-only if later steps can happen elsewhere. Microsoft To Do’s task guidance likewise treats steps as a way to break a larger task into more actionable pieces. Microsoft’s instructions for task steps, notes, and tags

Use a one-mark test for each real constraint

Keep the location vocabulary small: for many hybrid workers, two marks—Home and Office—are enough. Add one only when it changes what you can do on that day. A short test helps keep the list accurate:

Name the next physical or digital action in a verb phrase: “sign the paper copy,” “update the shared spreadsheet,” or “test the office printer.”

Identify the specific dependency: paper original, office-only equipment, a local file, or a colleague who is only available in person.

Ask whether that dependency can travel, be accessed remotely, or be replaced with an available equivalent.

If it cannot, add the single place mark that tells you where the action becomes possible. Otherwise, leave it unmarked.

This is an intentionally minimal rule, not a requirement to tag every task. Getting Things Done’s context guidance describes contexts in terms of the tools, places, and people actions require, and suggests starting with basic lists before adding finer ones. Getting started with context lists

Distinguish place from schedule, deadline, and preference

A location mark answers “where can I do this?” A date answers “when do I plan to do this?” A deadline answers “by when must it be finished?” These are different facts. If a task must be finished Friday and requires the office printer, record both the real deadline and the office dependency. If you already know you will be in the office Thursday, you might schedule the task for Thursday, but that planned date does not replace its deadline.

Preference is different too. You may prefer to write at home, but if the writing can be done at the office, it is still flexible. Treating a preference as a hard constraint can hide useful work on a day when plans change. Conversely, a task that needs a particular physical item remains location-dependent even if you would rather do it elsewhere.

Sometimes access, rather than geography, is the real constraint. A file may be available only through an office workstation or a person may need to be present for a hand-off. In that case, mark the place only if it reliably represents the dependency; a concise note such as “use locked workstation” may be clearer than a vague location tag. If the constraint is temporary, remove the mark when access changes.

Fit marked tasks into known home and office days

Use your actual work-location calendar as the planning boundary. On a day you expect to be in the office, scan the Office-marked tasks and choose those that are ready, timely, and feasible. Do the same for Home-marked tasks on home days. Leave flexible tasks visible for either setting. This produces a useful short list without creating separate copies of every task for each work location.

Consider a sample week where Monday and Thursday are office days, while Tuesday, Wednesday, and Friday are home days. The list might contain:

Task: Update a shared presentation; Mark: None; Why: The file is available at either location.

Task: Scan the signed expense form; Mark: Office; Why: The paper form and scanner are at the office.

Task: Sort the sample folders; Mark: Home; Why: The physical folders are stored at home.

Task: Ask a teammate about a decision; Mark: Office, if in-person discussion is required; Why: The colleague is available in person on the office day.

Task: Check a number in the shared dashboard; Mark: None; Why: It can be checked from either location.

On Monday, handle the office-only scan and the in-person question if they are due or ready. On Tuesday, the folder task is available at home. The shared presentation can be done on either day; choose based on priority, time, or the rest of the workload. The dates in this example are illustrative, not a recommended schedule.

If a planned office day changes, the mark still tells you what is blocked and what remains possible. Move the office-dependent action to the next known office day or arrange access to the needed item; do not silently reclassify it as flexible. Keep the due date visible so a location conflict becomes apparent early enough to make a practical adjustment.

Choose a mark that stays useful in your task list

A plain text prefix such as [Office] or a simple tag is enough. If your task app already supports labels, tags, or notes, use the smallest feature that makes the constraint easy to see. Microsoft To Do supports task tags that can be selected or searched, while Todoist describes labels as a way to group tasks and filters as custom views based on criteria such as labels and dates. Microsoft To Do tags · Todoist labels and filters glossary

You do not need separate Home and Office task lists if one list with visible marks works for you. If you use filters, a view for Office-marked tasks can help when you arrive there, but keep flexible actions in your ordinary list rather than tagging them Anywhere by default. A filter can only surface the information you entered; it cannot tell whether a file, device, or person is truly unavailable elsewhere. Todoist’s documentation explains how its filters combine criteria such as labels and dates, which can support this kind of view if you already use the app. Todoist’s filter guide

A location-triggered alert is a different tool from a location mark. Apple Reminders, for example, can notify you when you arrive at or leave a location, which is useful for reminders tied to a geographic trigger. For ordinary work planning across known home and office days, a visible mark on the task is usually the clearer way to identify a dependency and select work for that day. Apple Support on Reminders

Review marks when the underlying constraint changes

Recheck a mark when you bring the item home, gain remote access, change equipment, or stop needing an in-person hand-off. Remove it once the other location can support the same next action. If only one step in a multi-step task is restricted, keep the mark on that step rather than letting it block the rest of the work.

A quick weekly pass can catch stale location marks: read each marked action, name the thing that makes the location necessary, and confirm that it is still there or still inaccessible elsewhere. If you cannot name a concrete dependency, remove the mark or rewrite the action to reveal what is actually needed. The point is to make the next choice easier: marked tasks show what today’s location enables, and unmarked tasks stay available wherever you work.

Keep exploring this topic