{"id":22901297,"url":"https://github.com/mooerslab/time-blocks","last_synced_at":"2026-03-19T23:57:09.458Z","repository":{"id":238185603,"uuid":"796049604","full_name":"MooersLab/time-blocks","owner":"MooersLab","description":"PDF of Form for daily schedule as time blocks.","archived":false,"fork":false,"pushed_at":"2024-06-04T10:08:04.000Z","size":272,"stargazers_count":2,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-02-07T03:42:03.100Z","etag":null,"topics":["daily-planning","daily-schedule","daily-scheduling","efficiency-analysis","efficiency-tool","getting-things-done","gtd","personal-productivity","project-management","time-blocking","time-blocks","time-management","to-be-done","to-be-dones","work-life-balance"],"latest_commit_sha":null,"homepage":"","language":"TeX","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/MooersLab.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-05-04T19:31:26.000Z","updated_at":"2024-06-19T01:40:19.000Z","dependencies_parsed_at":"2024-05-04T20:30:18.332Z","dependency_job_id":"97a3bc8a-502e-48c1-85be-3842c570140c","html_url":"https://github.com/MooersLab/time-blocks","commit_stats":null,"previous_names":["mooerslab/time-blocks"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MooersLab%2Ftime-blocks","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MooersLab%2Ftime-blocks/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MooersLab%2Ftime-blocks/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/MooersLab%2Ftime-blocks/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/MooersLab","download_url":"https://codeload.github.com/MooersLab/time-blocks/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246591783,"owners_count":20801984,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["daily-planning","daily-schedule","daily-scheduling","efficiency-analysis","efficiency-tool","getting-things-done","gtd","personal-productivity","project-management","time-blocking","time-blocks","time-management","to-be-done","to-be-dones","work-life-balance"],"created_at":"2024-12-14T01:32:48.152Z","updated_at":"2026-01-11T01:45:40.450Z","avatar_url":"https://github.com/MooersLab.png","language":"TeX","funding_links":[],"categories":[],"sub_categories":[],"readme":"![Version](https://img.shields.io/static/v1?label=time-blocks\u0026message=0.3\u0026color=brightcolor)\n[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)\n\n# Flexible management of daily schedule with time blocks\n\n\u003cp align=\"center\"\u003e\n\u003cimg src=\"/images/inaction.png\" width=\"450\" \u003e\n\u003c/p\u003e\n \n## Problem addressed\nThis form is meant to help academics who have to manage several writing projects (e.g., research articles, grant applications, progress reports, grant reviews, manuscript reviews, lectures, seminars, platform talks, letters of support, letters of recommendation, and books) in parallel. \nThey have a finite amount of time that they have to manage wisely.\nOften, a time range will be scheduled for a particular writing task.\nHowever, if the writing session is going well, many writers will continue writing and shift other discretionary tasks further down on their schedule.\nThis downward shifting of other tasks is a pain when using pen and paper.\nThis can be done perhaps a little more easily in an electronic format.\n\nHowever, I needed something simple that would work on paper.\nDr. Cal Newport describes a simple approach in his 2016 book *Deep work: Rules for focused success in a distracted world*.\nHe sets up several columns at the start of the day.\nThe initial schedule goes in the leftmost column while the others remain blank. \nAs soon as a change in the schedule occurs, he writes the updated schedule in the next column to the right.\nThis process is repeated as changes occur to the schedule.\nThis form is at the heart of Dr. Newport's comprehensive approach, which includes to-do lists.\nHe describes his full approach in his 2020 book *Time-Block Planner: A Daily Method of Deep Work in a Distracted World*.\n\nI do not follow his full approach because I manage my to-dos in *org-agenda* in *Emacs*.\nI would not need this paper form if org-mode could handle time blocking.\nIt currently lacks this ability, so I must use this paper supplement.\nNonetheless, I like the portability and flexibility of the paper form.\nI carry it around with me on a clipboard.\n\nFor Emacsens (a.k.a., Emacs users), the table presented here could be re-implemented as an org table in an org file.\nIt could also be re-implemented in Mardown and Typst.\nI plan to make such templates when time permits.\n\nAt the end of the day or during your weekly planning session, you can reflect on the origins of the schedule changes and the amount of time required to complete certain tasks.\nThese data can drive the setting up of future schedules.\nAs you gain insights into your work habits, you might be able to minimize the number of schedule revisions you make during the day.\n\nYes, this is a low-technology solution.\nHowever, it is robust to disruptions in technology.\n\n## Instructions\n\nThe file `main.pdf` contains a two-page form. \n\n- Print out multiple copies of the form.\n- Enter planned activities in the leftmost column.\n- When an interruption occurs or time spent on one activity is extended, add the extension in the next column to the right and enter the revised schedule below it.\n- If you must make more than three revised schedules, you have a time management problem!\n\nThe PDF was generated from the `main.tex` file with LaTeX.\nEdit the time in the leftmost column in `main.tex` file to suit your own schedule. \nThe form eliminates the need for a ruler to draw the columns and time blocks.\n\n## Wired variant for recurring events\n\nThe wired variant *wired.pdf* demonstrates how to be more efficient when recurring events occur, such as in a writing schedule.\nThe recurring nature of these tasks bakes them into your daily schedule, so you do not have to waste time and energy scheduling them.\n\n\u003cp align=\"center\"\u003e\n\u003cimg src=\"/images/wired.png\" width=\"600\" \u003e\n\u003c/p\u003e\n\nIf you follow a rigid writing schedule for generative writing and write when you are unlikely to be disrupted, like before other workers show up, you could modify the form to contain one to three-time blocks of 90-180 minutes dedicated to a writing project.\nThe example above shows three time blocks of 120, 90, and 90 minutes each.\nThese are labeled writing blocks A, B, and C.\nAs professional writers will admit, you can sustain only four to five hours of generative writing daily without burning out.\n\nYou can assign these time blocks to different writing projects in the row at the top.\nThe order of assignments could vary daily to break the temporal context.\nAlso, the three writing projects selected can be varied during the course of a week. \nI use a project number with a keyword as a memory prompt for the project's name.\nI have a simple system, but that is another story.\n\nThe schedule for our superhuman academic hardwires five hours of progress on three vital writing projects before the first lab member arrives at 9:00 a.m.\nIn practice, there should be a 15-minute break between writing projects to ease switching between projects.\nIn addition, due to mental bandwidth limitations, it is easier to work on two parallel projects rather than on three.\nThe first three-hour block is enough time to accomplish a lot but not too long to exhaust oneself.\nThe momentum for generative writing that has been built up can then be transferred to project B for 90-120 minutes.\nThe file *wired2.pdf* has a three-hour time block for project A and a two-hour block for project B.\n\nThe rest of our fantasy day can be spent on supportive activities for the writing projects, such as data analysis, figure preparation, slideshow preparation, literature retrieval, and reading related papers to obtain new ideas for the next writing session.\nThe remainder of the day is often spent instead on supervising, teaching, meetings, service, and administrative chores, but at least the vital writing activities have been accomplished.\n\nIf you print out a week's worth of forms, you can block out the recurring events and calendar events (e.g., classes, committee meetings, seminars, workshops)  throughout the week during a weekly planning session.\nThis may reduce the time spent on daily planning at the start of the day and free it for generative writing.\n\nThis approach can support the continuation of writing during traveling to scientific meetings and service on national committees.\nFor service on grant review panels, it may be best to use the generative writing blocks to prepare presentations about grant applications being reviewed because these reviews require your full mental bandwidth.\n\n## Coming soon\n\nVariants of wired.tex translated to Markdown, Typst, and Org-mode to ease adoption and customization by non LaTeX users.\n\n\n## Update history\n|Version      | Changes                                                                                                                                    | Date                 |\n|:-----------:|:------------------------------------------------------------------------------------------------------------------------------------------:|:--------------------:|\n| Version 0.2 |  Added badges funding, and update table                                                                                                    | 2024 May 4           |\n| Version 0.3 | Elaborated on why and how to use this form.  Added the wired variants and included images.                                                 | 2024 June 2          |\n\n## Funding\n- NIH: R01 CA242845, R01 AI088011\n- NIH: P30 CA225520 (PI: R. Mannel); P20GM103640 and P30GM145423 (PI: A. West)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmooerslab%2Ftime-blocks","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmooerslab%2Ftime-blocks","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmooerslab%2Ftime-blocks/lists"}