Roam Research Project Management: Plans and Handoffs

Roam Research project management works best when you give each project a short home page, link working notes to it, and review a clear list of next actions. Add a responsible person, an expected outcome, and a current status to every action that matters. fenbs can hold the shared tasks, decisions, and progress that connected AI assistants need beyond the linked note archive.

Use Roam to follow the thinking behind the work, then make an explicit choice about where commitments live. A meeting note can explain a task without being the task’s current record. That distinction becomes especially useful when another person or assistant takes over.

See the Roam review for a broader assessment, or other Roam options when your main question is which tool to choose.

How do you create a workable project outline?

1. Create one home page with a distinct project name. State the outcome and what would count as finished in two or three sentences.
2. Add short sections for current actions, open questions, decisions, and references. Put the current plan near the top rather than below a long meeting history.
3. Capture meeting and research notes under dated entries. Link each relevant entry to the project so you can recover its context later.
4. Write actions as observable outcomes. Give each a responsible person, a next step, and any agreed review date in plain text.
5. Review the home page at the end of a work session. Update what changed and write where the next session should start.

Roam’s official syntax documentation↗ (opens in a new tab) describes pages, nested blocks, links, and task checkboxes. Those building blocks support a simple project outline. The structure above is a suggested working convention, so explain it to collaborators instead of assuming the app will enforce it.

For a small website refresh, the outcome could be “publish the approved service pages with working inquiry forms.” Research about page structure belongs below references; the next action might be “draft the service page outline for approval.” General project management methods can guide the process without requiring a more complicated note structure.

How should you connect working notes to the plan?

Use a page link for the project and a more specific reference when an action depends on a particular passage. Under the website project, for example, connect the form task to the meeting statement that explains which information the client approved collecting. Add a sentence explaining why that passage matters.

Keep one maintained statement of an agreement. If you paste the same approval into several notes, each copy becomes another place to update when the plan changes. Links are most useful when they reduce duplicate explanations while keeping the original reasoning available.

A project home page should answer what is true now. Dated working notes answer how you arrived there. Preserve both views, but do not make a teammate reconstruct the current plan by reading every meeting. Our second-brain guides cover the broader practice of keeping reusable knowledge connected.

What makes a linked action clear enough to assign?

An action needs more than a checkbox. “Forms” could mean research, design, implementation, or testing. Write the deliverable and the acceptance check: “Confirm an inquiry reaches the agreed inbox and record the result.” Then name the person responsible for taking the next step.

Use a small, documented status vocabulary. Distinguish active work, a waiting decision, and a completed check. If a date is only a target, label it as such; do not let a date reference imply someone has agreed to deliver then. These are team agreements that need consistent review.

Roam also documents a kanban component↗ (opens in a new tab), with columns and cards built from nested blocks. A visual layout may help you scan actions, but you still need explicit ownership and a rule for keeping its contents current.

If the plan changes frequently across people, choose one shared task record rather than maintaining independent lists. That is the point where fenbs’s tasks and progress record can complement Roam’s exploratory notes. The habit matters more than whether your first view is an outline or a kanban board.

How do you keep proposals separate from decisions?

Label a proposal as a proposal until a person approves it. A discussion note might contain three possible inquiry forms, while the decision is to use one shorter version. Record who chose, the reason, the scope, and which earlier agreement it replaces. Keep unanswered questions visible.

Avoid writing “the team agreed” when only one person made a suggestion. The distinction becomes harder to recover after an assistant summarizes a long discussion. Ask for the decision evidence before promoting a summary into instructions for future work.

In fenbs, Decisions and rules hold the choices people made, and rules appear first in the context connected assistants read. Assistants can record a person’s decision, but cannot decide or sign off themselves. This keeps the starting instructions distinct from the working ideas that remain in your notes.

What should a handoff to another assistant include?

Write four things before stopping: the completed work, the checks you ran, the unresolved issue, and the next action. Add links to the exact notes or files needed for that action. “Form built; inbox delivery untested; send a sample inquiry next” is useful in a way that “nearly done” is not.

Roam offers an official MCP connection↗ (opens in a new tab), a standard connection through which an AI app can use outside tools. Its documentation covers reading pages and graph guidelines. Connecting a graph still leaves you responsible for telling the assistant which project instructions and current actions to use.

The same principle applies to Claude project work and ChatGPT project work: make the starting record explicit. With fenbs’s AI handoff workflow, the next supported assistant reads Where we left off alongside tasks and decisions. fenbs does not connect to Roam, so transfer selected information deliberately.

How to do this with fenbs

1. Create a free account and add one active project. Use the personal kanban board for your own work, or a team kanban board when colleagues need access.
2. Add the current tasks and their plans. Bring across selected findings from Roam, including enough source information to check them, and identify which record the team will maintain.
3. Record approved choices in Decisions and rules. Keep suggestions and waiting questions distinct, and include the person who made each decision.
4. Connect your supported assistant through Integrations. Ask it to read the project context at the start and save task and project progress before stopping.

fenbs is not the right fit if you only want a personal outline for thinking through a project. Keep that in Roam. Add the shared record when repeated explanations, unclear commitments, or handoffs between AI apps become the practical problem you need to solve.