How to Link a Bullet Journal Project Collection to Daily Task Pages

Give the project one home

Start a Collection on the next available pages and title it with the project name. Record its page number in the Index. The official Bullet Journal guidance describes Collections as a place for related notes, tasks, and events, including projects, and recommends indexing their topic and page numbers. If the Collection continues elsewhere, add the additional pages to the Index and thread the page references so you can move between sections without searching. ([Collections and Threading](https://bulletjournal.com/blogs/faq/collections); [Threading](https://bulletjournal.com/blogs/bulletjournalist/threading))

Treat the Collection as the project’s durable record: scope, milestones, decisions, and an evolving list of open or next tasks can live there. Daily pages are dated work records. This division is a practical design choice, not a special BuJo rule: it lets you see project progress in one place while keeping the daily log chronological.

Make page references do the connecting

When you copy a project task to a Daily Log, give both pages a locator. On the daily page, note the Collection page beside the task, such as “Draft outline — p. 38.” In the Collection, note the date and daily page number beside the task or its status, such as “Outline drafted — Sep 29, p. 74.” Use the actual page numbers in your notebook; these numbers are hypothetical examples.

A locator should answer, “Where is the related entry?” A reference alone does not say whether work is complete. If a daily page records an outcome, carry that outcome back to the Collection during your review. The Collection then remains useful even after the daily page is several weeks behind you.

Record outcomes, not a second checkbox

For each project item on a Daily Log, make its status unambiguous when you reconcile pages. If complete, mark the daily task complete and update the Collection with the outcome and a dated page reference. If unfinished but still relevant, leave the Collection task open and decide whether to migrate it to a future Daily Log or leave it in the Collection until you schedule it. If the task changed, revise the Collection entry and note the new wording on the current daily page.

**Hypothetical example:** The Collection on page 38 lists “Prepare exhibit labels.” On Sep 29, the Daily Log on page 74 says “Draft labels — p. 38.” You finish a first draft, not final labels. Mark the daily entry complete as written, then update page 38: “First draft prepared Sep 29 — p. 74; review wording remains.” The Collection reflects the real outcome and the remaining work; it does not retain “Draft labels” as an unchecked copy that could be mistaken for untouched work.

Choose migration or a reference deliberately

Bullet Journal’s migration guidance says to review unresolved tasks, strike out those that no longer matter, and turn the bullet into an arrow when moving a worthwhile task to a new Monthly Log’s task page or an appropriate Collection. It explains that rewriting prompts a relevance check. ([Migration 101](https://bulletjournal.com/blogs/faq/migration)) Apply that distinction across daily and project pages: migrate when you are consciously carrying an open task forward; use a reference when you are linking records or documenting an outcome.

Do not copy a completed task forward as open just to preserve its history. Keep the completed outcome in the Collection and point to the daily record. For unfinished work, avoid leaving two active-looking bullets: migrate or rewrite the task in its new home, mark the old daily entry as migrated, and link the new entry back to the Collection. A page reference is navigation; migration is a status change and decision to carry the work forward.

Use a short reconciliation routine

At the end of a work session or during a regular review, scan that day’s project entries. For each one, check the cited Collection page, update the project record with the outcome and daily page number, and confirm that open tasks have one clear current home. The review may be daily, weekly, or at month-end; choose a cadence you can sustain. The important part is not to let a copied checkbox silently become a second source of status.

This resembles a basic project tracking discipline: keep tasks and progress legible, and make updates where the project is tracked. Asana’s project planning guidance identifies tasks, milestones, and communication as components of a project plan. Here, the notebook adapts that idea into a compact handwritten record; it does not require a digital board or a separate dashboard. ([Asana, Project Management Plan](https://asana.com/resources/project-management-plan))

Hypothetical multiweek example

Suppose a project Collection starts on page 38 with three open items: gather images, draft labels, and proof the final layout. On Daily Log page 74, you write “Ask the group to choose images — p. 38.” On page 76 two days later, you write “Draft labels — p. 38.” At review, update page 38 with dated references and exact outcomes: image choices requested (p. 74), first label draft ready (p. 76), proof layout still open.

If image choices are still pending, the completed request remains complete on page 74. Record “Waiting for image choices — requested on p. 74” in the Collection. If you decide to follow up, create a separate follow-up task; do not reopen the completed request. If image gathering is complete, close it in the Collection and retain the page reference as its history. This small return step prevents a page of old daily checkboxes from competing with the Collection’s current status.

Keep exploring this topic