Gather a few things See what you’ll need
- Notebook
- Pen
- Ruler or straight edge
Choose an exercise 4 things to try as you read
Decide what the columns mean
Each row identifies one task; every column must answer the same question. Johnston’s task version uses contexts, while community weekly adaptations use days. A header mixing Tuesday, email, and urgent makes the marks ambiguous. For this trial, use one named week and keep timed appointments in your usual calendar.
Compare the optionsWatch one intention move
Watch one intention move
Which point in the venue task do you want to inspect?
Read the words in this example
- One row, several columns
- M
- T
- W
- T
- F
- S
- S
- Task
- Email venue
- Print map
- Return books
Wednesday is an intention.
The dot identifies the intended day, not a completed action.
ONE WORKED EXAMPLE
A task moves into the next week
At Sunday review, “return borrowed baking tin” still has an uncompleted Friday dot. The tin is clean and ready, but the next chance to visit its owner is Tuesday.
Before
Copying the task into next week without updating the old cell leaves two pages that both appear to contain a current intention.
After
In the old matrix, Friday’s dot becomes > and a note reads “next week, p. 18.” On page 18, the same task has a Tuesday dot under the new week’s dates. After returning the tin, only that Tuesday dot becomes x.
What changed—and what to check
The cross-reference extends the move beyond one matrix. The old page shows where the intention went, while the new page carries its current status.
Try this check. Follow the old row’s reference and check that only the new week presents this task as still intended.
Give the task words most of the width
On A5 paper, try seven columns about 5 mm wide and a task area around 85 mm wide. These are illustrative dimensions: test your longest task in your own handwriting first. Leave comfortable margins and one writing line per row.
Write the full week dates above Mo, Tu, We, Th, Fr, Sa, Su. The diagrams use M/T/W/T/F/S/S in Monday–Sunday order; keep that order key beside single letters. Below the matrix, record dot = intended, x = completed, > = moved from this cell. Keep these meanings all week.
Write your versionWrite a key you can explain
Write a key you can explain
Edit the worked example into a note you can use.
Columns mean:Days of one named week
Open mark:Dot = intended day
Finish mark:x = action complete; > = moved from here
Your words have a place now.
Your marks need one stable meaning, including what a blank cell means.
- Words on this card
- 24
“Each row identifies one task; every column must answer the same question.”
Make each row small enough to finish
Write a task with a finish you can recognize: “email venue about access” or “return library books.” Keep project background elsewhere with a page reference. A dot marks the intended day and an empty cell stays unassigned. If two calls can finish separately, give them separate rows; one completion mark cannot explain which half of a combined task is done.
Follow one changed plan
The venue email starts with a Wednesday dot. You discover it needs a photograph you will take Thursday: change Wednesday’s dot to > and dot Thursday. The task wording stays put.
On Thursday, send the email and change Thursday’s dot to x. Sending is complete even while a reply is outstanding. Record “venue reply about access” on a waiting-for list so the finished action and open dependency each have a clear status.
See the differenceSeparate sending from waiting
Separate sending from waiting
Read the whole example before and after the change. The tinted lines show revised wording.
Tinted lines contain wording that differs between the two examples.
Before — Before sending
- One unfinished phrase
- Email venue / get answer
After — After sending
- Two clear records
- Done
- Email sent Thu
- Waiting
- Venue access reply
Read the whole example before and after the change.
Combining the request and reply makes completion ambiguous. The sent action closes; the reply gets a distinct waiting-for entry.
GO A LITTLE FURTHERRepair a row you can no longer read
Repair a row you can no longer read
If a mark lands in the wrong cell, strike it through and add a short correction such as “planned Thu.” For an unreadable trail of moves, copy the task to a clean row and label the old one “continued below.” Then check why it keeps moving. Printing a map may need a route decision first, so keep the blocked printing step in project notes.
GO A LITTLE FURTHERChange the question on another page
Change the question on another page
For a week with constantly changing days, try Calls, Desk, Out, and Waiting on a separate matrix. That is closer to Johnston’s task adaptation. Keep the daily matrix’s meaning unchanged through the week. Use contexts you actually need; retain real deadlines in the task wording or calendar rather than adding an undefined “urgent” column.
Close the week with a short decision
At the week’s end, read the unfinished words before copying them. Complete, carry forward, or cancel each row deliberately. Mark where a moved action now lives so next week has one current version. Leave completed rows in the old matrix; they need no new marks simply because the calendar has changed.
Try a what-ifOne row contains two separate calls
One row contains two separate calls
Consider this page before choosing your next move.
Your row says “call hall and printer.” The hall call is done, but the printer call still needs to happen. A single x would hide that difference.
Compare the three choices
How can you restore clear completion?
- Separate the calls into two rows and mark each actual status.
Each call has its own finishing point. Two rows let one be complete while the other remains intended.
- Mark the combined row complete and remember the other call.
The matrix would then say the whole row is done while depending on memory to preserve the remaining action.
- Add another intended dot on the same day without changing the wording.
Two marks still leave unclear which call each one represents unless the actions are distinguished.
Give separately finishable actions separately readable status.
What would you try?
Choose an option to see what it would do. You can explore all three.
Something for a future page?
The Washi Tape ShopAffiliate links: we may earn a commission if you buy through these links.
Where this idea began
The method references explain the underlying ideas. Community links show the questions and experiences that helped shape this guide; they are not a popularity ranking. The worked examples here are our own.
- Community discussionAlastair Method Weeklies
A contributor explains adapting month columns into weekly records and finding a full-month matrix harder to scan.
- Method creatorTo Do: The Alastair Method
Context columns sit beside task text; marks track relevant contexts and changing task status.
This guide adapts the context matrix into a paper practice example. It does not establish popularity or measured time savings.
Source checked 2026-09-05.



