A weekly task board for a small exam study group

A study group can agree to meet every Sunday and still arrive with three different ideas about what was due. A shared task board helps when each entry names a piece of work, the person preparing it and the date the group needs it. Keep the reading schedule alongside the board. The board records the work between meetings.

Choose a deliverable for the next meeting

Start with one week. Instead of assigning “revise quantitative methods,” ask one member to prepare a short explanation of a particular method, another to attempt a practice set independently and a third to collect questions for discussion. These are examples of how to divide preparation, not a recommended exam syllabus.

Write down what each person will bring. “Explain why this answer is wrong” is easier to review than “understand the topic.” Leave time for everyone to attempt the questions before comparing approaches. A completed preparation task shows that someone did the assigned work; it does not show that every group member has mastered the material.

Build a small tracker in Notion

One database is enough for a single group. Give each row a task name, an assignee, a due date and a status. Keep the agreed topic list on the same page so members can check the scope without searching through chat messages.

If the group is running several separate pieces of work, a second database can hold projects such as a four-week review cycle or a presentation. Link each task to its project with a Relation property. The guide to project management in Notion explains that two-database setup and the views that make it usable. Start with the task list if the extra project layer would add more administration than clarity.

Create a table for the full list and a board grouped by status for the weekly check-in. Both should show the same underlying tasks. Use a personal filtered view for each member’s assigned work, then return to the complete table when a task appears to be missing. A filter can hide a row that still exists.

Review the work before adding more fields

At the meeting, open the tasks due that week. Ask the owner to explain the result, let the others raise questions and record the next action. A useful follow-up might be “redo the calculation with a different assumption” or “find the step where our approaches diverge.” Assign that action to one person and choose a date while the group is together.

Avoid marking a whole topic complete because its presenter finished a summary. Keep personal practice and group preparation distinct. If a question remains unresolved, leave it visible with a note about what needs checking rather than closing it to tidy the board.

After two meetings, remove fields nobody uses. Add a separate notes area only if decisions or explanations keep disappearing. The NotionSolutions guide library offers further walkthroughs when the group needs a specific database or view. Choose the next change to solve a recurring problem, rather than rebuilding the workspace around every available feature.

Check access before sharing study material

Invite the actual group members and confirm what each can view or edit. Notion’s sharing and permissions documentation distinguishes access for invited people from access for anyone on the web with the link. A personal filtered view is an organizational aid; it should not be treated as a privacy barrier.

Link to authorized learning resources instead of copying restricted question banks into the workspace. Keep account details, private results and other people’s notes out of shared pages unless their use is permitted. Before the next meeting, ask one member to check that the board opens with the intended access and that the week’s tasks are easy to find. That small check is more useful than another dashboard.