
What changed (Nov 06, 2026): Merged from the student assignment tracker guide: Excel/Google Sheets setup and school-plus-personal FAQs, course color-coding, in-class capture, and time-blocked sessions on crowded days; added Google Sheets and Excel help sources for dropdowns and highlight rules.
An assignment tracker is one list of every graded deliverable: what it is, which course it belongs to, when it is due, what stage it is in, and where the instructions live. A good tracker does more than store deadlines. It shows you when to start, which week is overloaded, and what to do next. You can keep one on paper, in a spreadsheet, or in an app; this guide shows the setup in AFFiNE, where the task list can sit next to your notes.
Quick start: List every deadline from your syllabi with six fields: task, course, due date and time, status, priority, and a link to the instructions. Split anything that takes more than one sitting into milestones with their own dates. Check the list for five minutes a day and plan the next seven days once a week. To skip the setup, copy the free Assignment Tracker template and adapt it using the steps below.
Editorial note: Written by Allen for the AFFiNE content team, refreshed October 3, 2026, and updated November 6, 2026 with spreadsheet, color-coding, and personal-task guidance. AFFiNE makes the app and template described here. We checked the template's contents, AFFiNE's release notes, and the outside sources listed at the end on the dates shown there. Courses, tasks, and dates in the examples and diagrams are illustrative, and the diagrams are drawings, not screenshots. A tracker helps you plan; it does not guarantee better grades.
Each row is one deliverable with one deadline. Six fields are enough for most students:
| Field | Example | Why it matters |
|---|---|---|
| Task | Biology lab report | Names the deliverable, not the topic |
| Course | BIO 101 | Keeps several classes in one list |
| Due | Fri, Oct 16, 11:59 PM | Records the real cutoff, including time and time zone |
| Status | In progress | Shows the next stage of work |
| Priority | High | Breaks ties between nearby deadlines |
| Source | Link to rubric | Lets you check requirements without searching |
Three optional fields help with larger work. Start by is the date the first work session must happen. Weight is the share of the course grade, copied from the syllabus. Estimated hours is your best guess at the total effort. As a rough starting point, Sheridan College's library suggests planning about two hours for every 5% an assignment is worth, so a 15% lab report would get about six hours, spread over several days. Adjust the estimate after the first few assignments; how long work actually takes is more useful than any rule of thumb.
| Format | Works well when | Watch out for |
|---|---|---|
| Paper planner or printable list | You have a few courses and few date changes | Rewriting changed dates; no sorting |
| Spreadsheet | You want to sort, filter, and calculate | Notes and drafts live somewhere else |
| Your school's learning platform | You need official dates and submission status | Only covers courses that use it |
| A notes workspace such as AFFiNE | Large assignments need notes, outlines, and drafts beside the deadline | More setup than a simple list |
If you want paper, the student assignment to-do list in our printable templates already has due-date and start-by columns. Whatever format you pick, the learning platform stays the official record for dates and submissions.
AFFiNE's Assignment Tracker template is a quick starting point. When we checked the template file on October 3, 2026, it contained one database with two views, a table called List and a Kanban View, and five columns: Task name, Status (TODO, In Progress, Done), Due, Priority (Low, Medium, High), and Note. Some sample rows are not schoolwork, so delete them before you start. You can also build the same structure from an empty database.
Add Course and Source columns, then rename or add Status options so each stage of your work has a name. A select column works for Course because you can pick the class instead of typing it each time. Use Source for the rubric or assignment page link. If you get feedback before submitting, add a Review option between In Progress and Done. Keep the option list short: you will only keep it accurate if updating takes a few seconds. Give each course option its own color so you can tell classes apart on the board at a glance.
AFFiNE's Date property records the day, not the time. When a deadline has a cutoff time, add it to the task name (for example, “Lab report, 11:59 PM”) or to the Note column so the exact time is visible in every view.
Go through each syllabus with the course page open and add one row per graded deliverable, then add milestone rows for any assignment that needs more than one sitting. Include quizzes, exams, presentations, and draft checkpoints, because each has its own deadline. Copy dates from the source instead of from memory, and note anything the syllabus marks as tentative.
For a lab report due Friday, the final submission is one row. Add earlier rows for the outline and full draft, each with its own date. Work backward from the deadline: leave a buffer day before it, then space the milestones across the days before that. The University of Minnesota Libraries' Assignment Calculator builds this kind of schedule for research papers, speeches, and lab reports from a start date and a due date, which is useful when you are unsure which stages a paper needs.
![]()
Illustrative example: milestones get their own rows, and two Friday deadlines are visible before the week begins.
If you would rather start from a page with more academic structure, the Academic Assignment Tracker template is an alternative.
Open the Kanban view grouped by Status so you can see what has started, what is waiting for review, and what is stuck. The board shows the same rows as the table, so you only maintain one list. Move a card when the work actually changes stage. For graded work, “Done” should mean submitted and confirmed on the course platform, not just finished on your laptop.
![]()
Illustrative example: a card that sits in one column for several days is the one to look at first.
Once a week, look at everything due in the next seven days and schedule work sessions before each deadline, not on it. Sort the List view by Due, or add a Calendar view if your version of AFFiNE has one; Calendar view for database blocks is listed in AFFiNE's v0.27.0 release notes from July 2026. Look for clusters. In the example, two assignments are due Friday, so the history reading starts on Tuesday instead of Thursday. On a crowded day, block the sessions by time in your calendar (for example, research at 9:00 and drafting at 10:30) so the plan is specific enough to follow.
![]()
Illustrative example: each deadline gets work sessions earlier in the week, plus a buffer day.
A tracker row will not alert you. AFFiNE sends notifications for mentions, comments, and workspace invitations, not for due dates, so set deadline reminders in the calendar or learning platform you already check. For fixed study blocks around these tasks, a weekly schedule template helps; for a lighter homework list, the Homework Planner template may be enough.
Give each large assignment a linked page for its rubric, sources, outline, and next action, and record an owner for every group deliverable. The tracker tells you when to act; the linked page holds what to do. Write the next action in the Note column as a concrete verb phrase, such as “compare three sources” or “revise the introduction,” rather than pasting the whole plan into a cell. If you sketch an essay structure or a project map visually, AFFiNE's Edgeless whiteboard lets you do it on a canvas linked to the same page.
For group projects, add an Owner column (a select or text property works) and one row per deliverable, each with an internal deadline a day or two before the official one. Agree on who submits the final file. In a shared cloud workspace, @mentioning a teammate on the project page sends them an AFFiNE notification, which is a convenient way to hand off a review. The Project Squad Hub group assignment tracker is a starting point built for this.
Deadline changes are where trackers usually stop matching reality. When an instructor moves a date:
If a date in the tracker disagrees with the course platform, treat the platform as correct and ask the instructor when it is unclear.
Daily, about five minutes: add any task announced in class the moment you hear it, check course announcements, correct any changed dates, pick one next action, and mark submitted work Done. Weekly, about fifteen minutes: scan every course, plan the next seven days, and book work sessions for anything that needs several. These times are suggestions; adjust them to your course load.
Use priority to break ties, not to replace dates. A practical order is: fixed deadlines first, then work that takes the longest, then anything other tasks depend on, then personal preference. A two-minute task due tomorrow can be done now; a major paper due next week needs its first session scheduled today. At the end of the term, archive or filter out finished rows so the active view stays short.
A table, board, calendar, and linked pages are more than one light course needs. Start with the six fields and add a view only when it answers a question you keep asking. If your school's learning platform already lists every assignment with reliable dates, a separate tracker earns its place mainly for planning start dates, milestones, and notes. It never replaces the platform for submissions: AFFiNE does not submit work or confirm that an upload succeeded.
If you already know you want to try AFFiNE, open the Assignment Tracker template and enter your next three real deadlines before customizing anything else.
Keep one list with the task, course, due date and time, and status, plus a link to the original instructions. Check it daily and compare every date with the syllabus or learning platform. Add priority, milestones, and other views only when you need them.
Sort by due date first so no fixed deadline is missed. Then look at how long each task will take and give large tasks an earlier start date. Priority is most useful for choosing between tasks with similar dates.
Keep the final submission as one row and add milestone rows, such as outline, first draft, and proofread, each with its own date. Work backward from the deadline and leave a buffer day. Link the rows to one page that holds the rubric, sources, and draft.
Not by itself. AFFiNE notifies you about mentions, comments, and workspace invitations, but not about due dates. Create reminders in a calendar or the course platform you already use, and update them whenever a date in the tracker changes.
Put the six fields in the first row: task, course, due, status, priority, and source. Turn Course and Status into dropdown lists with data validation so entries stay consistent, and add a conditional formatting rule that highlights rows due in the next seven days. Sort by the Due column during your weekly review. A spreadsheet will not hold your notes and drafts, so paste the link to the rubric or draft in the Source column.
Yes. Add an Area column with options such as School and Personal, then filter or group by it so a week of coursework and a week of shifts or appointments show up side by side. Keep graded work in its own rows with real due dates, so personal tasks never hide a deadline.
Yes. Add an Owner column and one row per deliverable, with internal deadlines before the official one. Agree on who submits the final version, and keep the official instructions in the course platform.
Checked on October 3, 2026, except the last two entries, checked on November 6, 2026.