What counts as work context.
Most work arrives as a short instruction: send the deck, reply to the client, fix the bug. The instruction is rarely the hard part. The hard part is everything around it. That surrounding information is work context, and it usually includes:
- People. Who asked, who is waiting, who is affected and who has the answer you need.
- Decisions. What was agreed, what was ruled out and who made the call.
- Promises. What you committed to, and what others committed to you.
- History. The earlier conversations and drafts that shaped where things stand now.
- Timing. When it’s due, what it depends on and what happens if it slips.
- Sources. Where each piece came from, so you can check it.
- The reason. Why the task exists and what it’s for.
The reason matters most, and it’s usually the first thing to go missing. A task without its reason is easy to finish in the wrong way.
One task, with and without its context.
Here is an illustrative task as it might appear on a list:
Submit launch proposal — 5 PM
Now the same task with its context attached:
Submit launch proposal — 5 PM
Why this matters: Sarah needs it to confirm the launch date with leadership tomorrow morning.
Context: In Monday’s review, you agreed to drop the pricing section. Sarah later asked in #launch for the revised timeline to be included.
Next step: Add the revised timeline, then send the draft to Sarah for a final check before 5 PM.
The first version is incomplete: it says what and when, but not why. The second answers the four questions every piece of work should: what needs your attention, why it matters, when it needs to happen and what the best next step is. What. Why. When. How.
Context switching vs context reconstruction.
Context switching is moving your attention from one task, tool or conversation to another.
Context reconstruction is what happens after you arrive: the hidden work of manually piecing together what happened, what changed, who said what, what was promised, what needs to happen next, why it matters and where the information came from.
| Question | Context switching | Context reconstruction |
|---|---|---|
| What is it? | Moving your attention between tasks or tools. | Rebuilding the story behind a piece of work before you can act on it. |
| When does it happen? | Every time you change what you’re working on. | When you come back to something after hours, days or weeks. |
| What does it cost? | Focus and momentum. | Time spent searching and asking again, and the risk of acting on an outdated picture. |
| What helps? | Fewer interruptions and batching similar work. | Keeping context attached to the work, so it’s there when you return. |
You can reduce switching with a calmer calendar. Reconstruction is harder to notice because it looks like ordinary work: scrolling back through a thread, rereading notes, asking a colleague what was agreed. It grows with every tool and conversation your work passes through.
Practical ways to keep context.
You don’t need special software. These habits work with any tool:
- Write the reason next to the task. One line on why it exists saves rereading the thread later.
- Record decisions where you’ll look for them, along with who made them and when.
- Separate what you owe from what you’re waiting on. They have different owners and different next steps.
- Keep the source. Note the meeting, message or document a commitment came from.
- Add changes instead of overwriting. When a date or scope moves, keep the original and note what changed.
- End each session with a next step, so tomorrow starts with an action rather than a search.
These habits work. Their weakness is that they depend on you doing the bookkeeping every time, across every tool, which is exactly what slips when work gets busy.
How Offscript approaches work context.
Offscript is a context-aware AI for work that connects information across your work and helps you understand what matters, why it matters and what to do next.
You capture thoughts, voice notes and conversations in the Mac app, and connect the tools where your work happens: today, Slack, Google Calendar and Linear (Linear appears when it’s enabled for your account). Offscript keeps track of the people, conversations, decisions and promises around your work, along with what changed, and brings that context forward when it’s relevant: before a conversation, when a reply is due or when something changes.
It doesn’t replace your judgment. Follow-up drafts wait for your review, and nothing is sent without your confirmation. The principle behind it is simple. Your work happens across tools. Your context should travel with you. See how Offscript works.
Questions about work context.
Is work context the same as notes?
No. Notes record what was said at one moment. Work context connects that record to the people, decisions, promises and later changes it affects, so it still makes sense when you come back to it.
Why is a task without context incomplete?
A task without its reason, source or timing is easy to do the wrong way, at the wrong time or for the wrong person. You either reconstruct the background before you can act, or you act on an outdated picture.
Does Offscript remember work context?
Yes, that’s its core job. Offscript keeps track of what was said, what changed and what was promised, so you don’t have to reconstruct it each time. You choose what to capture and connect.