Dispatch demoMade-up tasks · no model is calledBack to Dispatch 한국어0 of 5 tried

Dispatch 2026-09-10 (Thu)

Design draft first — it slipped yesterday · replies after lunchas of 09:10

TSK-1Feature design draftTSK-2Sort out pending replies

16h over1 in progress0 with no progress logged for 5+ days

This week (~09/11)

16h over

Need 21h · Have 5h

In progress

1 item(s)

up to 3 at once

no progress logged for 5+ days

0 item(s)

Do it now5

17h

Start now or the deadline is gone

Feature design draft

H4hHard 09/09(Wed)3 workdays late

Fold in review notes through section 2

2026-09-07

Split the design into three parts — screens, storage, failure paths

Narrow down the slowdown

H4hSoft 09/11(Fri)deferred 2x1 workday late

Time the earlier of the two slow stretches

2026-09-07

Twenty identical runs, only three were slow — something else is in play

Bump the third-party libraries

H4hHard 09/11(Fri)1 workday late

Start with the two failing tests

2026-09-07

Two went up as they were; the other two changed how they are called

Tidy up the bug report form

M3hSoft 09/10(Thu)deferred 1x1 workday late

Keep only the three fields that get filled in

Refresh the manual screenshots

M2hSoft 09/10(Thu)1 workday late

Start with the four screens that changed

Do it today2

Start today to meet the deadline

Sort out pending replies

H2hSoft 09/11(Fri)

Draft the answers and get them checked

Build a set of test data

M2hSoft 09/11(Fri)

Start with the three most common shapes

This week3

Start it this week

Write the weekly report

H1hHard 09/11(Fri)Recurring

Collect what happened this week

Update the release runbook

M3hSoft 09/14(Mon)

Rewrite the two steps that changed

Fill in the first glossary entries

M1hSoft 09/14(Mon)

Start with the words meetings trip over

Next week1

Start it next week

Write down the code review bar

M2hSoft 09/18(Fri)

Put down what we actually look at now

Waiting4

Cannot act on it · the deadline still holds

Get the accessibility review back

M1hSoft 09/18(Fri)My turn 09/14(Mon)

Waiting — not my turn

Get review comments back

M1hSoft 09/12(Sat)My turn 09/16(Wed)

Waiting — not my turn

⚠️ The reply is due 09/16(Wed), after the start date 09/10(Thu) — starting once it arrives misses the deadline

Wait on the retention policy sign-off

H1hSoft 09/22(Tue)My turn 09/17(Thu)

Waiting — not my turn

Get the translation review back

M2hSoft 09/30(Wed)My turn 09/24(Thu)

Waiting — not my turn

No date set3

Set a deadline or delete it

Clean up the config files

Drop the values nothing reads

Group the feedback by theme

Work back from last quarter

Check tool license renewal

Start from the expiry date

Still room6

23h

Not time to start yet

Find where the build time goes

Soft 09/22(Tue)

Time each stage

Rework the alert rules

Soft 09/25(Fri)

Count what fired last month

Decide how to run the retro

Soft 09/25(Fri)

Write down what did not work last time

Update the onboarding notes

Soft 09/30(Wed)

Ask where the first week gets stuck

Prepare quarterly training material

Soft 10/02(Fri)Worked on today

Pick what carries over from last time

2026-09-10

Picked three pieces that carry over as they are

Pick the dashboard metrics

Soft 10/08(Thu)

Drop the ones nobody looks at

Keep an eye on it2

Keeps slipping unless time is set aside

Draft the incident response steps

Settle who looks at it first

Try a restore from backup

Run last month's copy through once

How the available hours are worked out · 1 recurring item(s), 1h

Math: Available 6h − recurring 1h
Taken off first: Recurring and waiting — not hours I can spend this week
Focus hours: 3h — cannot be measured exactly, so a typical value is used
About the estimates: Over and spare are estimates · a cue to check whether the schedule needs adjusting

Recurring 1 item(s) · 1h

Taken off the available hours first (not adjustable) · cards carry a Recurring badge · today's recurring work counts toward “Do it today”