Agiled Docs

Create a wiki page when the information should stay available after a chat or meeting ends. Good wiki pages explain a process, policy, checklist, playbook, or reference that the team will use again.

Create the Page

Open Knowledge Base or Wiki.
Select New page.
Enter a clear page title.
Select Create.

The new page appears in the wiki list. Open it to review the page, then use Edit to add or revise the content.

Choose a Useful Title

Write titles that match what a teammate would search for later.

Good examples:

New Client Onboarding Checklist
Invoice Follow-Up Process
Sales Discovery Call Notes
Support Escalation Policy
Project Handoff Checklist

Avoid vague titles like Notes, Process, or Important.

One Topic Per Page

Keep one major topic per page. If a page becomes too long, split it into smaller pages and link them from a short overview page.

Use the page title and first headings for search. Teammates should be able to find the page by the words they naturally use for the process or policy.

Use a checklist for repeatable work, a policy page for rules, a playbook for judgment-heavy work, and a reference page for stable facts. Choosing the format first keeps the page easier to scan and maintain.

If the content is temporary, use a task, project note, or chat message instead. Wiki pages should be durable enough that teammates can rely on them later.

Add the First Useful Content

A new wiki page should not stay as a blank title. Add enough context that a teammate can use the page without asking who wrote it or where the process came from.

Include:

The purpose of the page.
The owner or team responsible for keeping it current.
The steps, policy, checklist, or reference information.
Links to related records, files, forms, documents, or reports when useful.
The date-sensitive details that should be reviewed later.

Add a "last reviewed" note for policies, compliance steps, finance routines, and customer-facing processes. This helps teammates judge whether the page is still current before using it.

Open the saved page from the wiki list and read it like a teammate who has no background context. Rename vague headings, remove meeting-only notes, and link out to source records instead of copying large blocks of content that will go stale.

If the content creates work for someone, create a task instead of hiding the action inside the wiki page.

If the page documents a process controlled by a setting, workflow, template, or external provider, link to that source instead of copying details that may drift later.

After Publishing

Share the page with the team or link it from the record where the process starts. If nobody can find the page from the workflow, it will not become part of the team routine.

Maintain The Page

Assign an owner for pages that define recurring work. The owner should update the page after process changes, template changes, integration changes, or support incidents that change how the team should work.

Archive or rename pages that are no longer current. Leaving obsolete pages in search results makes it harder for teammates to trust the wiki.

Create a Wiki Page