What changed, automatically recorded.

Engineering changes.
Merged PRs, shipped features, infrastructure updates, and technical improvements. Documented from your development workflow without anyone writing a release note.

Product and business updates.
Feature launches, roadmap shifts, new partnerships, and strategic changes captured from meetings, Slack, and product docs. The business context alongside the technical changes.

Team and organizational changes.
New hires, role changes, process updates, and tooling decisions. The operational changes that affect how the company works day to day, captured from the channels and conversations where they are announced.

One record across every function.

Cross-functional by default.
Most changelogs are engineering-only. Fabric's changelog spans the whole company because it draws from sources across every function. Engineering, product, sales, operations, and leadership activity all contribute to the same record.

Weekly cadence, no effort.
The changelog compiles itself on a weekly basis from activity across your connected tools. Nobody has to remember what happened this week or spend Friday afternoon writing a summary. The record assembles itself from work that already happened.

Searchable history.
Every week's changelog is searchable and accessible to your AI assistant. Six months from now, you can search for when a specific change happened, or ask the assistant what changed during a particular period.

The company update nobody wants to write.

Most companies have some version of a weekly update. An email from the CEO. A Slack message in #general. A standing agenda item at the all-hands meeting. Whoever is responsible for it spends time each week gathering information from across the company, writing it up, and sending it out. Some weeks it gets done thoroughly. Some weeks it is rushed. Some weeks it does not happen at all because the person responsible was busy with something more urgent.

The irony is that the information already exists. PRs were merged. Decisions were made in Slack. Updates were shared in meetings. New clients were signed. The problem is not generating the information. It is collecting and formatting it into a coherent summary. This is exactly the kind of recurring, assembly-oriented task that should not require a human to do manually each week.

A changelog assembled from real activity.

Fabric produces the company changelog by reading the activity that flowed through your connected tools during the period. PRs merged in GitHub become engineering updates. Decisions made in Slack and meetings become business updates. Client milestones from account channels become relationship updates. Sales wins from deal discussions become revenue updates. Each item is sourced from the activity itself, not from someone's recollection of what happened.

The result is a changelog that is comprehensive because it draws from every connected source, accurate because it reflects actual activity rather than memory, and consistent because it compiles itself every week regardless of whether anyone remembers to write it. For startups where the pace of change is high and no single person has visibility into everything, this is especially valuable.

A compressed history of your company.

Read individually, each week's changelog is a useful update. Read sequentially, the changelog becomes a compressed history of the company. A new hire reading the last month of changelogs gets a rapid understanding of what has been happening, what the priorities are, and how things are moving. An investor reading the last quarter sees concrete evidence of progress across engineering, product, and business development. A returning team member coming back from leave can catch up on what they missed without scheduling a dozen sync meetings.

This compressed history also serves as a reference for retrospectives and planning. When the team is reviewing what was accomplished in a quarter, the changelog provides the raw material without anyone having to reconstruct it from memory. When planning the next quarter, the recent changelog shows the actual pace and scope of work, grounding plans in reality rather than aspiration.

Connected to the detail.

Each item in the changelog links to the underlying documentation. An engineering change links to the engineering docs and the PR that introduced it. A product update links to the product docs covering the feature. A decision links to the decision record with full reasoning. The changelog is a summary layer, but anyone who wants more depth can click through to the source. This makes it useful at multiple levels of detail. Leadership reads the headlines. Individual contributors click into the items relevant to their work.

What gets produced.

Engineering updates
Features shipped, infrastructure changes, migrations completed, and technical debt addressed. Sourced from merged PRs and engineering docs.

Product updates
Feature launches, roadmap changes, user research findings, and product decisions. Sourced from product docs, meetings, and Slack.

Business and sales updates
New clients, significant deals, partnership developments, and market moves. Sourced from sales knowledge base, client trackers, and team discussions.

Operational changes
New hires, process changes, tooling updates, and organizational decisions. Sourced from Slack and meeting activity.

Key decisions
Significant decisions made during the period, summarized with links to the full decision records for anyone who wants the context.

Use cases

Weekly company updates
Replace the manually written weekly email or Slack post with a changelog that assembles itself. More comprehensive, more consistent, and requires zero time from whoever used to write it.

New hire orientation
New team members read the recent changelog to understand what has been happening. A month of changelogs gives them a rapid overview of current priorities, recent changes, and the pace of work. See how Fabric supports onboarding.

Investor and board communication
Share a quarter's worth of changelogs as evidence of progress. Concrete, sourced from actual activity, and covering every function in the company. More credible than a slide deck assembled the night before a board meeting. See how Fabric supports data rooms.

Return from leave
Someone coming back after a week or a month reads the changelogs they missed. Faster and more thorough than asking colleagues "what did I miss" and piecing together the answer from incomplete responses.

Quarterly retrospectives
The changelog provides the material for quarterly reviews. What was shipped, what decisions were made, what changed operationally. The team can discuss outcomes rather than spending time reconstructing what happened. See how Fabric supports project docs.

Perfect for

Startups
Things change fast and no single person has full visibility. The changelog gives the entire team a shared understanding of what is happening across the company each week. Learn more about Fabric for startups.

Remote and distributed teams
When the team is spread across locations and time zones, a weekly changelog keeps everyone informed without relying on synchronous meetings. Learn more about Fabric for teams.

Founders
Founders juggling product, engineering, sales, and operations get a compiled view of what happened across every function. Useful for their own awareness and for sharing progress with investors and advisors.

Growing companies
As the team gets larger, it becomes harder for anyone to know what is happening outside their own function. The cross-functional changelog maintains organizational awareness as headcount grows.

Works seamlessly with other features.

All source integrations
The changelog draws from GitHub, Slack, Discord, meetings, and your workspace. The more sources connected, the more complete the record.

All output doc types
The changelog summarizes activity that is documented in detail elsewhere. Engineering docs, product docs, decision records, client updates, and sales activity all feed into the changelog. Each item links back to the full documentation for anyone who wants depth.

AI assistant
Ask your AI assistant what changed during any period. "What did the engineering team ship last month?" "What decisions were made in January?" "When did we start using the new deployment process?" It draws from the changelog and underlying documentation.

Publishing
Publish the changelog as an internal page or share it externally with investors and stakeholders. Add password protection for controlled access.

FAQ

Does someone need to write the changelog?
No. The changelog assembles itself from activity across your connected tools. Nobody needs to collect updates from different teams or write a summary. It compiles automatically on a weekly basis.

What sources does the changelog draw from?
Everything. GitHub for engineering changes, Slack and Discord for business updates and decisions, meetings for verbal updates and commitments, and your workspace for content and project activity.

Is the changelog only for engineering changes?
No. Unlike most product changelogs, Fabric's company changelog covers every function. Engineering, product, sales, operations, and organizational changes are all included. It is a company-wide record, not a release log.

Can I customize what appears in the changelog?
Yes. You can configure which sources and activity types feed into the changelog. If certain channels or repositories are not relevant, you can exclude them.

How often is the changelog produced?
The default is weekly, but you can configure the cadence to match your team's rhythm. Some teams prefer daily summaries. Others prefer bi-weekly or monthly compilations.

Can I share the changelog with external stakeholders?
Yes. The changelog is a Fabric document that can be shared, published, or distributed via link with analytics. You can add password protection for controlled access. Useful for investor updates and board communication.

Can I search past changelogs?
Yes. Every changelog is searchable alongside all your other documentation. You can search for when a specific change happened or ask the AI assistant to summarize activity during a particular period.

Can new hires use the changelog for onboarding?
Yes. Reading the last few weeks or months of changelogs gives new hires a compressed view of what has been happening. The changelog is one of the materials that feeds into onboarding docs.

How does this differ from a product changelog?
A product changelog records feature releases for customers. Fabric's company changelog records everything that changed across the company for internal consumption. Engineering changes, business updates, organizational shifts, and key decisions are all captured. The audience is your team, not your users.

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