Every decision, recorded with context.

What was decided.
The outcome, the direction chosen, the priority set. Captured in clear language so anyone reading the record months later understands what was agreed without needing to interpret meeting notes or decode a Slack thread.

Who was involved.
Which team members participated in the decision, who proposed the chosen approach, and who approved it. Useful for understanding accountability and for knowing who to ask if the context behind a decision needs revisiting.

Why it was decided.
The reasoning, the alternatives considered, the trade-offs accepted. This is the context that is almost never written down but is the most valuable part of any decision record. Assembled from meeting discussions, Slack threads, and Discord conversations where the reasoning was actually debated.

Decisions connected to their outcomes.

Linked to implementation.
A technical decision is connected to the PRs that implemented it. A product decision is connected to the product docs that describe the feature it shaped. A client decision is connected to the client page it affects. Decisions do not float in isolation. They connect to the work that followed.

Decisions that evolved.
Some decisions get revisited. An approach that was chosen in March is reconsidered in June because the situation changed. Fabric tracks when a decision is superseded or modified, documenting both the original reasoning and what led to the change. The record shows the full arc, not just the latest state.

Cross-functional visibility.
Decisions made by one team affect other teams. An engineering architecture decision shapes what product can build. A sales pricing decision affects what marketing can promise. The decision log is searchable by anyone in the organization, so teams can see decisions that affect their work even if they were not in the room when it was made.

The re-debate problem.

Every team has experienced this. A question comes up in a meeting. Someone thinks they remember discussing it before. Someone else disagrees. Nobody can find a record of what was decided, so the team spends thirty minutes debating a question they already resolved three months ago. They may even arrive at a different answer this time, not because the situation changed, but because different people were in the room.

This is one of the most expensive recurring wastes of time in any organization. It is not that people are forgetful or careless. It is that decisions happen in meetings, Slack threads, and casual conversations where they are not captured as formal records. The decision was made clearly and with good reasoning. It just was not documented in a way that anyone can find later. So the team debates it again. And sometimes again after that.

A record that makes decisions stick.

Fabric captures decisions as they happen, from the sources where they are actually made. A direction agreed on in a Slack channel becomes a decision record with the context from the thread. A choice made in a meeting becomes a record citing the timestamp where it was discussed. A technical approach chosen in a PR review becomes a record linked to the code change that implemented it.

When someone raises a question that was already resolved, the answer is searchable. Your AI assistant can surface the decision record with full context. "We decided to use PostgreSQL over DynamoDB in March. The decision was made in the engineering sync on March 14th. The reasoning was around query flexibility and the team's existing expertise." The debate ends in seconds instead of consuming another meeting.

Decisions as organizational memory.

Over time, the decision log becomes one of the most valuable assets in your documentation. It is the institutional memory of how your company thinks. Which trade-offs are accepted. Which principles guide choices. How the team's approach has evolved. For startups navigating rapid growth, it captures the reasoning behind early decisions that shape everything that follows. For research teams, it documents methodological choices and their justifications. For agencies, it records per-client decisions that inform ongoing work.

New hires benefit enormously from the decision log. Understanding why things are done a certain way is as important as understanding what is done. The onboarding materials draw from the decision log so new team members get the reasoning behind current practices, not just a description of them. An engineer can trace an architectural pattern back to the decision that introduced it. A product manager can understand why a feature was scoped a certain way by reading the decision that shaped it.

Not a meeting minutes archive.

The decision log is not a dump of everything discussed in every meeting and Slack channel. It is a curated record of consequential decisions. Fabric distinguishes between casual conversation and moments where a direction was set, a trade-off was accepted, or a commitment was made. The log contains decisions, not discussions. This makes it readable, searchable, and useful as a reference rather than an overwhelming archive that nobody wants to open.

Each decision record is structured consistently. What was decided. When. Who was involved. What reasoning was discussed. What alternatives were considered. Where the decision was implemented. This structure makes the log queryable. You can search by topic, by date range, by team, or by project. The AI assistant can answer questions like "what decisions did the product team make about pricing in Q2" by drawing from the structured records.

What gets produced.

Decision records
Individual records for each consequential decision with structured fields covering the decision itself, participants, reasoning, alternatives considered, and outcome. Connected to the source conversations where the decision was made.

Topic-level decision history
Decisions grouped by topic, project, or domain. See all the decisions made about a particular system, product feature, or client relationship in chronological order.

Superseded decision tracking
When a decision is revisited and changed, both the original and the updated decision are documented with context about what prompted the change. The full evolution of thinking is preserved.

Engineering decision records
Architecture decisions, technology choices, and technical trade-offs documented as structured ADRs (Architecture Decision Records) with implementation links.

Product decision records
Feature decisions, prioritization choices, and roadmap changes documented with context from stakeholder discussions and user feedback.

Use cases

Stopping re-debates
When a question comes up that was already resolved, search the decision log or ask the AI assistant to surface the existing decision. The answer comes back in seconds with full context and reasoning.

New hire context
New team members read the decision log to understand why things are the way they are. The reasoning behind current practices, architectural patterns, and product decisions is documented and searchable. See how Fabric supports onboarding.

Audit and compliance
A structured record of what was decided, when, and by whom. Useful for organizations that need to demonstrate governance, justify past choices, or provide evidence of decision-making processes.

Post-mortems and retrospectives
Review the decisions that led to a particular outcome. Understand whether the reasoning was sound, whether the right information was available, and what might be decided differently next time.

Perfect for

Startups
Fast-moving teams make dozens of decisions a week. Without a log, most are forgotten within days. The decision log captures the reasoning behind early choices that shape everything that comes after. Learn more about Fabric for startups.

Product teams
Feature priorities, scope decisions, and roadmap choices are documented with the reasoning and user feedback that informed them. The product team can trace any current feature back to the decision that created it.

Engineering teams
Architecture Decision Records assembled from PRs, Slack, and meetings. Technical decisions documented with implementation context so future engineers understand why the system was built this way.

Leadership teams
Strategic decisions documented with the context and reasoning discussed in leadership meetings. Useful for board communication, investor updates, and maintaining alignment across the organization.

Works seamlessly with other features.

All source integrations
The decision log assembles decisions from Slack, Discord, meetings, GitHub, and your workspace. Decisions are captured regardless of where they happen.

All output doc types
Decisions feed into and connect with engineering docs, product docs, client trackers, onboarding materials, and the company changelog. The decision log is the connective tissue across all documentation.

AI assistant
Ask your AI assistant about any past decision. "When did we decide to deprecate the v1 API?" "Why did we choose Stripe over Adyen?" "What pricing decisions have we made this quarter?" It draws from structured decision records with citations.

Smart search
Decision records are searchable by topic, date, team, project, or keyword. Find any decision made at any point in your organization's history through a natural language query.

FAQ

What counts as a "decision" that gets logged?
Fabric identifies moments where a direction is chosen, a trade-off is accepted, a priority is set, or a commitment is made. It distinguishes between casual discussion and consequential decisions. You can review what gets logged and adjust the sensitivity.

What sources does the decision log draw from?
Decisions are captured from meetings, Slack, Discord, GitHub PR discussions, and activity in your workspace. The more sources you connect, the more complete the log.

Can I search the decision log by topic or date?
Yes. Decision records are structured and searchable. You can search by topic, project, team, date range, or keyword. The AI assistant can also answer questions about decisions in natural language.

What happens when a decision is changed or reversed?
Both the original decision and the updated one are documented. The record shows what was originally decided, what prompted the change, and what the new decision is. The full evolution is preserved so the reasoning at each point is accessible.

Can I edit decision records?
Yes. All records are full Fabric documents that your team can edit, annotate, and discuss. If a decision record is missing context or needs clarification, anyone with access can add to it.

How does this differ from meeting minutes?
Meeting minutes are a chronological record of everything discussed. The decision log extracts only the decisions and their context. It is structured, queryable, and focused on outcomes rather than the full flow of conversation.

Can different teams see each other's decisions?
That depends on your permission settings. The decision log can be shared across the full organization or scoped to specific teams. Cross-functional visibility is recommended so teams can see decisions that affect their work.

Does it work for informal decisions made in Slack?
Yes. Many important decisions happen in Slack threads without any formal process. Fabric captures these the same way it captures decisions from meetings. The informality of the medium does not diminish the importance of the decision.

How does the decision log connect to other documentation?
Decisions are linked to the documentation they affect. A technical decision links to engineering docs. A product decision links to product docs. A client decision links to the client tracker. The decision log is the connective thread across your entire documentation set.

Which plans include the decision log?
The self-writing decision log is available on Team plans. See team pricing for details.