Help Center

Usage Scenarios & Examples

Scenario 1 — The Freelance Consultant

Profile: Maya works independently, billing multiple clients by the hour. She needs accurate time records for invoicing and wants to know how her time splits between billable and non-billable work each week.

Monday morning

Maya starts her day with a client deliverable.

Push: Prepare Q2 financial summary ✓ Billable

She works steadily. At 10:30 her phone rings — a client needs a quick answer. She pushes the call onto the stack:

Push: Client call — Acme Corp ✓ Billable

Ten minutes later the call is done.

Pop → Client call — Acme Corp ends (10 min recorded)

The financial summary is now back at the top of the stack and actively recording time again.

At 12:00 she finishes the summary.

Pop → Prepare Q2 financial summary ends (2h 20m recorded, split across two sessions)

After lunch she spends time on her own business admin.

Push: Update website portfolio — not billable

At 2:15 an urgent email arrives from a different client.

Push: Review contract draft — Beta Ltd ✓ Billable

She reviews the contract, responds, and pops it off.

Pop → Review contract draft — Beta Ltd ends (45 min)

The portfolio task is back at the top and timing resumes.

Pop → Update website portfolio ends (1h 10m)

At the end of the week Maya opens Reports, sets the filter to Billable Only, and generates a weekly report. She can see every billable task, the total hours, and can export it straight to CSV for her invoice. The non-billable portfolio work is excluded automatically.

Scenario 2 — The Developer with Frequent Interruptions

Profile: James is a software developer on a small team. His day is constantly interrupted by questions from colleagues, code reviews, and support issues. He wants to understand how much of his time actually goes to focused development versus reactive work.

A typical afternoon

James starts focused work on a new feature.

Push: Feature — user authentication module ✓ Billable

Twenty minutes in, a colleague asks for help with a bug.

Push: Help Sam — login redirect bug

The bug takes longer than expected. His manager pings him about a pull request that needs urgent review.

Push: PR review — payment gateway

He reviews and approves the PR.

Pop → PR review — payment gateway ends (15 min)

The colleague's bug is back at the top. James picks up where he left off.

Pop → Help Sam — login redirect bug ends (35 min)

The feature task is back at the top and timing resumes. James works on it until end of day.

Pop → Feature — user authentication module ends (recorded across two sessions: 20 min + 2h 10m = 2h 30m total)

At the end of the month James runs a monthly report and filters by non-billable to see how much time went to internal support and reviews. He shares it with his manager during their one-on-one to make a case for fewer interruptions during focused work blocks.

Scenario 3 — Forgetting to Pop

Profile: Sarah occasionally gets pulled away from her desk unexpectedly and forgets to pop her current task before she leaves.

The situation

Sarah pushes a task at 2:00 PM.

Push: Draft newsletter content

At 3:15 she is called into an unplanned meeting and walks away from her desk without popping. The meeting runs until 5:00 and she does not return to her desk that day.

The next morning she opens Work Stack Manager and clicks Peek. The panel shows:

Active task: Draft newsletter content
Started: Yesterday 2:00 PM
Time on stack: 17h 23m

She knows immediately something is wrong. She pops the task first to close the session:

Pop → Draft newsletter content ends (17h 23m recorded — clearly incorrect)

Now that the session is closed she goes to the Sessions tab, selects Draft newsletter content, and finds the session that was just closed. She clicks Edit and enters the correct end time:

New end time: 2024-03-15 15:15:00

The session is corrected to 1h 15m — the actual time she worked on it. Her report data is now accurate.

Scenario 4 — Recurring Daily Tasks

Profile: Tom has several tasks he does every single day — a morning standup call, checking emails, and a daily report. He wants tracking these to be as fast as possible.

Using recent history

On his first day using Work Stack Manager, Tom pushes his morning tasks manually. By day two, all three names appear in his Recent History badges. His morning routine now takes three clicks:

1. Click Morning standup badge → tick Billable → Push
2. Pop when standup ends
3. Click Email triage badge → Push
4. Pop when done
5. Click Daily report badge → Push
6. Pop when done

No typing required. Each task is tracked accurately with minimal friction.

At the end of the month Tom generates a monthly report and can immediately see how much time his daily recurring tasks consume in aggregate — useful data when reviewing how his time is actually spent versus how he thought it was spent.

Scenario 5 — End of Day Routine

Profile: All users benefit from a consistent end-of-day habit.

A clean close

Before finishing for the day, take 30 seconds to close out the stack properly.

1. Click Peek to confirm what is currently active and verify the time looks correct
2. Pop the active task if you have finished it
3. If you are mid-task and will continue tomorrow, pop it anyway — it will appear in your recent history tomorrow and you can push it again to start a new session
4. Confirm the stack is empty

This ensures:

• All sessions are closed with accurate end times
• Tomorrow's reports start clean
• No stale sessions accumulate over time

Scenario 6 — Preparing a Client Invoice

Profile: Elena tracks all client work as billable and needs to invoice at the end of each month.

Monthly invoicing in four steps

1. Open the Reports tab
2. Select Monthly as the period
3. Set the filter to Billable Only
4. Click Export CSV

The downloaded CSV contains every billable task for the month with total hours for each. Elena opens it in her spreadsheet, multiplies each row by her hourly rate, and her invoice is ready.

For clients billed at different rates, Elena uses a naming convention that identifies the client in the task name — for example Acme — strategy meeting and Acme — development work. When she exports the CSV she can filter by client name in her spreadsheet to get per-client totals instantly.

Scenario 7 — Planning a Structured Day

Profile: Phillip is a project manager with four important deliverables that must be completed by end of day. He knows from experience that his day will be pulled in multiple directions, and he wants a strategy that keeps him anchored to his goals despite the interruptions.

Preloading the stack

Phillip starts his morning by loading all four priority tasks onto the stack before doing anything else. The key is to push them in reverse order — the task he wants to work on first goes on last, so it sits at the top.

He pushes them one by one:

Push: Write board meeting notes ✓ Billable (last priority — goes on first, sits at bottom)

Push: Review Q3 budget forecast ✓ Billable

Push: Finalise project timeline ✓ Billable

Push: Prepare client presentation ✓ Billable (first priority — goes on last, sits at top)

His stack now looks like this:

The stack is his plan for the day, visible at a glance. He starts work on the presentation immediately.

Handling interruptions without losing focus

At 10:00 a colleague stops by with an urgent staffing question.

Push: Staffing issue — cover for Thursday

Phillip deals with it quickly.

Pop → Staffing issue — cover for Thursday ends (12 min)

The presentation is back at the top and timing resumes from where it left off.

At 11:30 his phone rings — an unexpected supplier call.

Push: Supplier call — office equipment

Pop → Supplier call — office equipment ends (20 min)

Back to the presentation, which is top of stack again. He finishes it just before lunch.

Pop → Prepare client presentation ends (3h 10m total, across three sessions)

The stack automatically reveals his next priority:

No decision required about what to work on next. The stack tells him.

Working through the afternoon

Phillip works through the remaining tasks one by one, pushing and popping any interruptions as they arise. By 4:45 he has completed all four priorities:

Pop → Finalise project timeline ends (1h 40m) Pop → Review Q3 budget forecast ends (1h 15m) Pop → Write board meeting notes ends (55m)

The stack is empty. Every priority task is done. Despite five interruptions across the day, Phillip never lost track of where he was or what came next — the stack managed that for him.

At end of day he clicks Peek, confirms the stack is empty, and opens the Reports tab to review his daily totals before closing up.

Scenario 8 — Personal Productivity at Home

Profile: Maria is a housewife and part-time legal assistant who works from home. Her day blends family responsibilities, household tasks, and professional work. She uses Work Stack Manager to bring the same clarity to her home life that professionals bring to the office — knowing exactly where her time goes and ensuring her billable work is accurately recorded for her employer.

A typical morning

Maria starts her day with the family.

Push: Breakfast and morning routine

The children are fed and ready. She takes them to school.

Pop → Breakfast and morning routine ends (45 min)

Push: School run

Pop → School run ends (20 min)

Back home, she switches into work mode for her legal assistant role.

Push: Schedule consultations — Attorney Davis ✓ Billable

She works through the calendar, coordinating with clients by email and phone. Halfway through, she realises she needs to put a load of laundry on before she forgets.

Rather than stopping her work entirely, she quickly deals with it and captures it honestly:

Push: Laundry

Pop → Laundry ends (5 min)

The consultation scheduling task is back at the top and timing resumes. She finishes the scheduling.

Pop → Schedule consultations — Attorney Davis ends (55 min billable)

Midday

Maria takes a break to prepare lunch and do some cleaning before the afternoon shift.

Push: Lunch preparation

Pop → Lunch preparation ends (30 min)

Push: Clean kitchen and living room

Pop → Clean kitchen and living room ends (40 min)

She returns to her legal assistant work for the afternoon.

Push: Information gathering — Johnson case ✓ Billable

Push: Send client emails — Attorney Davis ✓ Billable

She drafts and sends several client emails, then returns to the research task.

Pop → Send client emails — Attorney Davis ends (25 min)

The information gathering task is back at the top.

Pop → Information gathering — Johnson case ends (1h 20m)

School pickup and evening

Push: School pickup

Pop → School pickup ends (25 min)

Push: Help children with homework

Pop → Help children with homework ends (45 min)

Push: Dinner preparation

Pop → Dinner preparation ends (50 min)

End of day

Maria opens Reports, filters by Billable Only, and sees her professional hours clearly separated from her family and household time:

She submits this to her employer accurately and without guesswork. She also runs an unfiltered daily report out of personal curiosity and sees that her total tracked day — family, household, and work combined — accounted for just over seven hours of purposeful activity.

Work Stack Manager does not judge how time is spent. It simply records it faithfully, whether the task is drafting a legal document or making dinner.

Scenario 9 — Staying Within a Billable Time Budget

Profile: Jim is a freelance copywriter whose contracts include a fixed cap: no single billable task may exceed one hour without prior client approval. He uses the Active Task Time Limit alert as a safeguard so he never accidentally bills over the agreed limit.

Setting up the alert

Before starting work Jim opens Preferences → Task Alerts and sets the Active Task Time Limit to 60 minutes. He saves his preferences. From this point on, whenever the task at the top of his stack has been active for a full hour, a notification appears automatically — no timers or sticky notes required.

A focused writing session

Jim sits down to work on a new project.

Push: Write product descriptions — Hartwell Co ✓ Billable

He works through the descriptions, fully absorbed in the copy. An hour passes without him noticing. The alert fires:

Active Task Time Limit Reached You have been working on: Write product descriptions — Hartwell Co Active for: 1h 0m Configured limit: 60 minutes

Jim pauses and reviews his progress. He has completed four of the six descriptions — solid work, but not quite done. He has two choices.

Option A — Stop here and bill what he has done

If the remaining descriptions can reasonably wait, he pops the task now to close the session cleanly within budget and will push it again later as a second separately-approved session.

Pop → Write product descriptions — Hartwell Co ends (1h) (Session recorded — one hour, on budget)

He contacts the client to confirm approval for a follow-up session before continuing.

Option B — Snooze and finish without interruption

The client has already verbally approved up to 90 minutes for this batch. Jim clicks Snooze 5 min to dismiss the alert temporarily and keeps writing. Five minutes later, having finished the final two descriptions, he pops the task himself.

Pop → Write product descriptions — Hartwell Co ends (1h 12m)

The five-minute snooze gave him enough runway to reach a natural stopping point without the alert re-firing every minute.

Why it matters

Without the alert Jim would have no signal at all that an hour had passed — he would only discover the overage when he checked the clock or generated his report. The Active Task Time Limit turns a potential billing mistake into a deliberate, informed decision made in the moment.

Scenario 10 — Keeping a Busy Stack Moving

Profile: Jovanni is an account manager who frequently carries four or five active tasks on his stack at once — client calls pending, proposals mid-draft, internal requests in progress. His problem is not interruptions; it is forgetting that work is sitting below the active item waiting for his attention. He uses the Inactivity Reminder to make sure nothing gets buried and stalls.

Setting up the alert

Jovanni opens Preferences → Task Alerts and sets the Inactivity Reminder to 30 minutes. He saves his preferences. The dashboard will now alert him whenever any item below the top of the stack has been waiting more than thirty minutes without becoming active.

A morning of stacked work

Jovanni starts his day with several things already in motion.

Here is his stack at 9:00 AM:

He works through the call prep and handles the Nguyen call. The call runs long and pulls him into follow-up emails directly related to it. Thirty-five minutes have elapsed since he pushed the stack. The alert fires:

Tasks Waiting for Attention The following tasks have been inactive for a while:

• Internal team briefing notes — waiting 30m
• Follow up on contract revision — Delvecchio — waiting 30m
• Prepare renewal quote — Okafor account — waiting 30m

Jovanni dismisses the modal and reconsiders his work stack. The Nguyen follow-up is nearly done — he will finish it and pop. He notes that the Delvecchio contract revision has a deadline this afternoon; he should move it up the stack next.

Pop → Client call prep — Nguyen ends (30 min)

With the Nguyen work closed, the briefing notes are now top of stack. That task is not urgent today — he pops it to clear the way, making the Delvecchio contract revision the new active task.

Pop → Internal team briefing notes ends (30 min idle — no time billed, session discarded or edited to zero)

The Delvecchio contract revision is now at the top and active. He works through it, pops it when done, and moves on through the rest of his stack.

Why it matters

Without the reminder Jovanni might spend the entire morning on Nguyen-related emails while the Delvecchio deadline crept closer, invisible beneath the surface of the stack. The alert surfaced the buried work at the thirty-minute mark — early enough to reprioritise before anything became urgent.

The inactivity alert does not tell Jovanni what to do. It simply ensures he makes a conscious choice about his stack rather than letting items wait passively and indefinitely.

Previous: User Guide — Features & Interface Next: Frequently Asked Questions