Things3 Weekly Review mode shortcut(s)4 minutes read | 781 words by Ruben Berenguel
This is how I handle the dreaded GTD (Getting Things Done) weekly review when using Things 3.
This post will only make sense if
- You are a user of Things3, and heavy on Getting Things Done
- Shortcuts app
- You have or can install the shortcuts _Weekly Review _and Update weekly review hash
- You have Drafts or Bear app (either could be used, the shortcut linked below uses Drafts)
Initial setup (around 10-30 minutes depending on the amount of projects you have)
Create a note in Drafts (you can put it in the note archive) with some text, does’t matter what you write. I used the letter a when I created these shortcuts and the weekly workflow.
Get the document id from the draft (with the draft open, press the i Information button, select UUID and press copy) and set it up on all the shortcuts, as the UUID in the action Get Draft Contents.
Run the shortcut Update weekly review hash. This will open your draft and add a new line below it, should look similar to 54f74fbfb94518a527a36474dc904c25 (this is the text you introduced, hashed). Copy this and add it to the end of the Notes section of any project (or, if you fancy, task) you want to be included in your weekly review in Things3. You only need to do this long manual part once. Note that you can’t add areas to review (since this is based on notes and areas don’t have notes).
Finally, add your Things3 authorization token to the Weekly Review shortcut.
When the time to review arrives, run the shortcut Weekly Review. This will open Things3, searching for any project containing the hash in your draft. Switch to selection mode, select a bunch of projects (I usually do it in blocks of 5-10), press the 3 dots ➡️ Share ➡️ Copy link. Then press the Shortcuts “go back” link at the top left of your device to go back to Shortcuts.
The Weekly Review shortcut will now work with your clipboard contents to modify these projects. First, you’ll get a notification telling you how many projects are going to be reviewed. Once you press OK, the first one will open in Things3. Adjust the project as needed (edit the title, schedule it, add tasks…) and then delete the hash from the end of the notes section (you can do this later, but I find it easier at this point). Once finish, press the Shorcuts “go back” button to go back to Shortcuts. This will bring you back to Things3, but at the end of the notes section you will have a different hash. This is as what it should be 😃 Press the Shorcuts “go back” again, and this procedure will repeat for all the projects you “shared” in the previous step.
Step wise it looks like:
- Run Weekly Review
- Select some projects
- … -> Share -> Copy link
- Go back to shortcuts via the quick link
- Say OK to the amount of projects to review
- Review the project
- Delete the hash from notes
- Go back to shortcuts
- You are back on Things. You can still edit the project if you have anything to add or do
- Go back to shortcuts
And here’s a video so you can see it in action:
By deleting the previous hash you ensure already reviewed projects don’t show again if you exit the workflow from Shortcuts and need to run Weekly Review again. Also makes the review process start-stoppable, so you can do a few projects today, a few tomorrow and then “finish”.
In writing, it sounds slow, but it’s super fast in practice (weekly review took me around 2 hours before, now takes me around 30-45 minutes, the amount of projects I have has increased, not diminished). The main advantage I have is that I can specify which projects are to be reviewed and which not beforehand (for instance, if I decide a Someday/Maybe project should move to action state, I just add current week’s hash to its notes and is ready to be reviewed).
Once there are no projects left to review, run Update weekly review hash, which will set you up for next week’s review.
Keep in mind though you need to remember to add this week’s hash to any new project you create. Usually this just means open another project, copy the hash from it and add it to the notes section. Usually I do this as part of my daily inbox purge: I create new projects outside of any area (or more like, in the area I consider to be the project inbox), and when I clean my inboxes I add the hashes.