Templates that start with the right shape — and learn from your work.

Decision log. Meeting. PRD. Retro. Knovya picks the right scaffold from a 50+ library, auto-attaches type and status, and follows the note from draft to precedent. If you want AI-summarized meetings instead of an empty meeting template, see AI Meeting Notes. All 50+ built-in templates are free on every plan — harvested patterns and AI auto-fill arrive on Pro.

Built-in templates
50+
Lifecycle stages
5
Step from scaffold to precedent
1
Templates
Experiment 02 · The Forge

Pick a template. Watch it grow up.

Eight scaffolds — six built-in, two harvested from a workspace's own patterns. Drag the lifecycle dot and the note's metadata, banner, and standing follow.

Q3 Planning Meeting — Sept 18 meeting
Lifecycle Drag the dot — the metadata, banner, and rank follow. Stage: Seed

Just started. Knovya has noticed the type and offered the right scaffold — nothing else is graded yet. Take your time.

Free includes all 50+ built-in templates — every one, every plan. Pro unlocks harvested patterns, AI auto-fill, custom templates, team sharing → See Pro
Anatomy · what's inside one

Ten attributes, four families.

A Notion or Word template is a layout. A Knovya template carries metadata, watches for completion, and feeds your knowledge graph — so the note becomes findable and reusable on day one.

Family I Scaffold
3 attributes
01
Block layout Pre-built structure of headings, paragraphs, callouts, code, math, tables — every block type the Knovya editor supports. Not a copy of a page; a real composition the editor reads natively.
02
Checklist scaffolding The "agenda" of meeting templates, the "acceptance criteria" of PRD templates, the "what worked / what didn't" of retros — every checklist becomes a completion signal.
03
Variable placeholders Date, author, project, channel — slotted in at creation. Standup template inherits today's date; meeting template inherits the calendar event title.
Family II Auto-Metadata
3 attributes
04
Type inheritance Choose the Decision template, get type: decision on the note. NoteRank weights it accordingly. Experience Envelope finds it when you draft another decision.
05
Status start-state New notes from a template begin status: draft — automatically. The note knows it's not finished, even before you fill it in.
06
Suggested tags Templates carry a tag suggestion bundle — q3, standup, customer-research — that the AI tag suggester pre-fills, ready for you to accept or strike.
Family III Lifecycle hooks
2 attributes
07
Completion detection When every checklist box on a template-derived note is checked, Knovya offers to mark the note complete and stamp the timestamp. Status moves itself.
08
Outcome prompt When a templated note is archived, the archive flow asks "What was the outcome — success, partial, cancelled?" Templates know which notes deserve the question.
Family IV Source & provenance
2 attributes
09
Library — 50+ built-in Cornell, PARA weekly review, Decision log, PRD, Daily, Knowledge base article, Customer interview, Retro, Project plan — a curated set with the methodology baked in.
10
Harvested from your work Knovya watches for repeated note shapes — three weekly standups in a row, two customer-call recaps with the same headings — and offers to save the pattern as a personal template. Your patterns become your tools.

Static templates are glorified file headers
and your knowledge deserves better.

Microsoft Word has had templates since 1990. Notion ships 30,000 of them. Obsidian's Templater plugin lets you write programmable ones. And every single one of them is dead on arrival.

You pick a template. You fill it in. The system forgets why. It does not know the note is a meeting. It does not know when you are done. It does not connect a finished retro to the next retro you draft six weeks later.

The cost
Templates that don't know what kind of note this is can't help you find it again, can't rank it, and can't surface it as precedent.
The fix
Bind templates to the note's lifecycle — type, status, completion, outcome. Then templates stop being decoration and start being plumbing.
The lineage

From Cornell paper to auto-attached metadata.

Templates aren't new. What's new is the binding to lifecycle. Five forerunners taught us how a scaffold becomes a system.

  1. 1950s
    Walter Pauk — Cornell Notes A two-column note layout that turned the page itself into a recall protocol — proof that structure can do cognitive work. Cornell University · pedagogy
  2. 1990s
    Microsoft Word — *.dot files The first mass-market template format — open, save-as, fill-in. Set the convention that templates are decoration, not data. Microsoft · productivity software
  3. 2017
    Tiago Forte — Building a Second Brain PARA, Progressive Summarization — methodology turned into reusable note shapes. The first widely-adopted argument that templates are knowledge architecture. Forte Labs · PKM movement
  4. 2020
    Obsidian Templater — programmable templates YAML frontmatter + JavaScript blocks. Templates that read the calendar, query the vault, write the date. The community plugin that made templates active, not passive. Obsidian · community plugin
  5. 2026
    Knovya Templates Templates bound to lifecycle. Type, status, completion, outcome — auto-attached. Patterns harvested from your own work. Scaffolds that follow the note from Seed to Precedent. ★ Knovya · production
First of its kind

Nobody else binds templates to lifecycle.

Notion has the biggest gallery — 30,000 templates, all static. Obsidian has the most flexible — programmable, but every plugin author defines their own metadata. Apple Notes has the cleanest — and the fewest. None of them know the note is a meeting after you've filled it in.

  • Notion 30,000+ marketplace · static layouts
  • Obsidian Templater plugin · manual frontmatter
  • Apple Notes built-in formats · no metadata
  • Mem.ai no template system
  • Tana supertag · structure-only
  • Roam Research SmartBlocks · static hierarchy
  • ★ Knovya 50+ built-in · auto-metadata · harvest your patterns · lifecycle-aware
Surfaces

Templates show up where you start a note.

Four entry points. Same gallery underneath. Each one already knows what kind of note you are about to write.

Slash menu in editor

Inside any note, type / and the template gallery is two characters away. Filter as you type. The note inherits structure mid-stride.

Conversation → Note AI-detected

When the AI assistant notices you are recapping a meeting or writing a decision, it suggests the matching template — and pre-fills it from what you've already said.

New note button smart suggest

Click "New note" and Knovya offers your most-used templates first — including the patterns it has harvested from your work. Frictionless start, every time.

Settings → Templates workspace library

Browse, edit, share, version. Built-in templates sit alongside your harvested patterns and your team's customs — one library, three sources.

Frequently asked

A few honest answers.

What is a Knovya template?
A Knovya template is a structured note scaffold — blocks, headings, checklists, and metadata — that a note inherits when you start it from the template. Unlike static templates in Notion or Word, Knovya templates participate in the note's lifecycle: type and status auto-attach, completion is detected from checkbox state, and matured notes can become precedents in your Experience Envelope.
How are Knovya templates different from Notion templates?
Notion gives you 30,000+ static templates that copy a page layout. Knovya gives you 50+ built-in templates that auto-attach metadata (type, status, suggested tags), watch for completion, and feed downstream systems — NoteRank, Experience Envelope, Smart Archive. The template is not where you start; it is how the note becomes findable, rankable, and reusable.
Can AI fill in a template for me?
Yes. Conversation→Note watches the chat, detects when you are describing a meeting, decision, or PRD, and offers the matching template — pre-filled with the structure and the content you have already discussed. You confirm, the note is saved with the right metadata, and you keep going. (Pro plan.)
Can templates be harvested from my own notes?
Yes. When Knovya notices you write the same kind of note repeatedly — a weekly standup, a customer call recap, a 1:1 prep — it offers to save that pattern as a personal template. Your patterns become reusable scaffolds, with no manual extraction step. (Pro plan.)
Does Knovya support Cornell, PARA, GTD, Zettelkasten?
All four methodologies have built-in templates. Cornell (split-page note layout for study), PARA (project / area / resource / archive — used in Second Brain), GTD weekly review, and Zettelkasten atomic-note scaffolds. Each one auto-attaches the right metadata so the methodology survives across your library.
Can I share templates with my team?
Yes — workspace templates appear in every member's gallery. When the workspace owner updates a template, every existing note from that template gets a diff hint so you can pull the update if you want to. No silent overwrites. (Pro and Team plans.)
Are templates free?
All 50+ built-in templates are free on every plan, including Knovya Free. Pro adds custom-template authoring, harvested-pattern detection, AI auto-fill via Conversation → Note, and team-shared templates with workspace diff hints.
Is this template-only — or does it also run an AI meeting note taker?
This page is the template primitive: empty scaffolds you fill in by hand (meeting, standup, 1:1, retro, decision log, PRD, board, kickoff). If you want the AI workflow — bring a transcript from Otter, Granola, Fireflies, ChatGPT, voice or paste, and Knovya structures it into a linked, MCP-readable note — see AI Meeting Notes. The two are complementary: bring an empty template to a planned meeting, run the AI workflow on the resulting transcript.

Try the Forge in your own notes.

All 50+ built-in templates on day one — free for everyone. Your patterns become your templates as you work.

★   element 21 · Group III — Editor