# How to Build an Open Decision List for a Project Review

> Build an open decision list from discussions. Preserve accepted choices, separate implementation checks, and flag missing outcomes without assuming indecision.

- URL: https://www.hemory.com/blog/searchable-memory/open-decision-list/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-04
- Last updated: 2026-11-04
- Summary: Build a project review list that distinguishes explicitly open choices from accepted decisions awaiting conditions and outcomes missing from the available sources. A fictional pilot example contains one confirmed open date choice and two different checks. Hemory can help retrieve available history and draft the list without reopening settled work.
- Tags: open decisions, project reviews, decision follow-up

You are preparing a project update and keep seeing the same choices discussed across meetings. One looks settled, another depends on training, and a third ends with “let's come back to this.” Which decisions still need attention?

Build the list around the choices that matter to the next piece of work. Recover the latest relevant outcome for each, separate a pending choice from a pending task, and keep missing evidence distinct from a decision that is genuinely still open.

## TL;DR

- Start with the decision blocking current work, rather than cataloging every question ever raised.
- A proposal suggests a choice; an accepted decision establishes one. Conditions can limit an accepted choice without undoing it.
- A postponed decision is still open. An accepted decision awaiting implementation is a different kind of follow-up.
- If no outcome appears in the sources reviewed, say the status needs confirmation. Do not assume nobody decided.
- For discussions captured in Hemory, use organized Memory or a supported connected agent to recover outcomes and draft a focused list of what remains open.

## Define the choice you need to settle

Write the question in terms that would change the work: “Which onboarding format will we use for the pilot?” is more useful than “What's happening with onboarding?”

You may discover several separate choices inside a broad topic. The format can be accepted while the start date remains open. Keeping those separate avoids reopening settled work or reporting an entire project as undecided.

You only need enough detail to find the relevant material. A project name, remembered proposal, or approximate meeting can be a starting point; a complete timeline is not a prerequisite.

## Find the outcome and any later change

Check an existing decision note, project document, or meeting summary first. It may already establish the choice. If the outcome is missing or ambiguous, return to the exchange where people discussed it.

If those exchanges were captured in Hemory, use its organized Memory to locate the discussion. Within a known conversation, ask what was proposed, what was accepted, and what remained open. Look for the response to a proposal as well as the proposal itself.

Then follow any relevant later clarification or accepted replacement. The most recent mention is not necessarily the current decision: someone can ask about a settled choice without reopening it. A later suggestion can also leave an earlier instruction unchanged.

Treat authority according to the actual process. Acceptance might come from a designated lead, an authorized committee, or another agreed method. It need not require unanimous enthusiasm or a particular phrase such as “final decision.”

## Separate the states that lead to different next steps

| What the record establishes | How to describe it | Useful next step |
|---|---|---|
| An idea is suggested but no choice is established | Proposal; outcome needs confirmation | Find the decision or ask whether the proposal was accepted |
| The authorized process accepts a choice | Accepted decision | Use it within its scope |
| A choice is accepted subject to a condition | Accepted with conditions | Establish whether the condition is satisfied before acting |
| The group explicitly postpones the choice | Deferred decision | Return at the agreed trigger, or clarify follow-up if none was set |
| One part is decided and another remains open | Accepted part plus unresolved choice | Preserve the settled part and resolve the remaining question |
| Available records do not show the outcome | Status not established in the sources reviewed | Check another relevant source or seek confirmation |

“We agreed to review the options” is an agreement about a task, not a selection of an option. “We chose the portal, but setup is unfinished” is a decision with outstanding implementation work. These should not occupy the same place on an unresolved-decisions list.

## Example: one confirmed open choice, two different checks

This fictional example illustrates the review list; it is not an actual project record or Hemory output. The available records establish:

- At the October 21 review, the authorized lead accepts group onboarding for the pilot. The invitation date is left open until Support confirms its available dates.
- At the October 28 review, the lead approves the pilot launch once staff training is complete. The choice is accepted; the records reviewed do not establish training completion.
- A message says the reporting format was discussed separately, but the decision from that discussion is not in the available material.

The working list should distinguish the remaining work:

| Item | Established position | What still needs attention |
|---|---|---|
| Pilot onboarding | Group format accepted | Invitation date remains undecided; obtain Support's availability to inform the choice |
| Pilot launch | Approved after staff training | Confirm training completion before proceeding; do not relabel the approval as undecided |
| Reporting format | A separate discussion is referenced | Locate its outcome or confirm the status; do not claim that no format was selected |

The next review can focus on the invitation date. Training needs a completion check; the reporting format needs a source check before it can be counted as open. The accepted group format and conditional pilot approval remain intact.

## Ask an agent to draft the list from captured discussions

If the relevant Hemory material is available through a compatible AI agent connection, you can ask the agent to retrieve and organize it before manually assembling a history.

```text
Review the Hemory discussions you can access about the pilot.
Identify choices that are explicitly still open or deferred, and
separate them from accepted decisions with outstanding conditions
or implementation tasks.

For each item, give the established position, source, and precise
remaining question or action. Preserve partial decisions and later
accepted changes. If the available material does not establish an
outcome, mark the status as needing confirmation.
Draft an open-decision list for the next project review, with separate
implementation checks and requests to confirm missing status.
```

Add current task information or approvals held outside the connection when they affect the list. For example, a training-completion update can resolve the launch condition without changing the original approval.

Hemory reduces the work of remembering which meeting contained each choice and relaying those discussions to AI. Your review can focus on the differences that matter: what is settled, what is still a choice, and what is simply waiting to be done.

## Prepare the confirmed open choices for review

For each genuinely open choice, state the question, why it matters now, and the input needed to decide. Include the decision-maker or process and timing only where established. If these are missing and necessary, list them as details to clarify.

```text
Open choice:
Established decisions to preserve:
Why this needs attention now:
Missing input or options to discuss:
Decision-maker / process, if known:
Agreed timing or trigger, if any:
Source reference:
```

Keep implementation checks and status-confirmation requests nearby but separate. They may belong in the same meeting agenda, yet they do not need the same discussion.

For organizing the whole meeting around decisions, discussions, and coordination, see [building a recurring project meeting agenda](/blog/searchable-memory/recurring-project-meeting-agenda/).

Stop searching when the available outcome is sufficient for the task or the remaining gap can be stated precisely. A focused confirmation request is often better than another broad archive search.

For future discussions, [Hemory](/features/) can preserve the choices and their conditions while you participate. The next review can start with a clearer account of what is settled and what still needs a decision.

## FAQ

### Is a decision unresolved until every condition is complete?

No. A choice can be accepted with conditions on when or how it may be carried out. Keep the approval and the outstanding condition visible. A condition that explicitly postpones the choice itself is different.

### What if the last meeting ends with another question?

Read what the question concerns. It may ask how to implement an accepted decision, request clarification, or propose reconsideration. It does not automatically cancel the earlier choice.

### Can a meeting summary establish a decision?

Yes, when it clearly records the outcome and relevant authority or process. Return to fuller material when an important condition or interpretation needs clarification, rather than treating every summary as insufficient.

### What if the decision happened outside the records I can access?

Identify the missing source or ask for confirmation. Keep the status unconfirmed in your working list until you have the answer; missing access is not evidence that the decision never happened.