Comparison
Brief vs a knowledge base
A wiki tells a new hire how the company works. It rarely tells them where their accounts stand this week.
Why not just use our knowledge base?
Scope. A knowledge base is organisation-wide, permanent, and maintained by many people, which is why it drifts. A Brief is scoped to one project, engagement or transition, built from that context's own sources, and shareable with someone outside your company who will never have a wiki account.
Why wikis drift
- Everyone can edit, so nobody owns currency.
- Pages describe process, not the state of a specific engagement.
- External counterparties cannot be given access.
- Search returns the page that matched, not the answer.
How they coexist
- Step 1
Wiki for durable process
How we run a launch, how expenses work, what our standards are.
- Step 2
Brief for a specific context
Where this project, account or transition stands right now.
- Step 3
Brief for external audiences
Recipients open a link; no account, no seat.
- Step 4
Retire the Brief
When the engagement ends, revoke it. The wiki stays.
Side by side
Knowledge base
- Organisation-wide
- Permanent
- Internal audience
- Process and policy
Brief
- One project or engagement
- Time-bounded
- Internal or external
- Current state and evidence
Overlap to avoid
- Do not put policy in a Brief
- Do not put live deal status in a wiki
Common objections
The ones worth answering directly.
- Is this another place to maintain? No — the Brief reads your existing sources rather than asking you to rewrite them.
- Can external people read our wiki? Usually not. That is the main reason handoffs leave it.
- Does a Brief replace documentation? No.
- What happens when the project ends? Revoke the link.
Currency
- A Brief's answers come from the sources you added, so staleness is visible rather than assumed.
- Update dates reflect real change, not edits made to look active.
- Unknowns are stated rather than filled in.
Where does this content belong?
- Does it apply to the whole company, indefinitely? Wiki.
- Is it the current state of one engagement? Brief.
- Does someone outside the company need it? Brief.
- Is it policy? Wiki.
Common questions
- How is Brieflin different from a knowledge base?
- A knowledge base is maintained for an ongoing audience and decays when nobody curates it. A Brief is scoped to one project or engagement and one transfer moment. It is built from the material that already exists rather than written from scratch, and it is meant to be handed over rather than maintained forever.
- Does Brieflin replace project documentation?
- No. Brieflin connects source material into a transferable context layer. The original files remain evidence, while the Brief helps recipients understand what happened, what matters, and what remains open.A Brief summarizes and cites the sources it was given. It is not a system of record.
- Can recipients view a Brief without an account?
- Yes. A recipient opens the share link and can read and ask questions immediately, with no account and no software to install. The creator keeps control: links can be revoked at any time, can carry an expiry, and stop working the moment they are revoked.
Scope one context
Build a Brief for a single project and compare it with the wiki page.