Name the page for the task
Use a title that describes the job. Colleagues often arrive from a search or a link, not from the index, so the title does most of the work of helping them choose the right page.
General BusinessContent Creator
Internal wiki page: one task, an owner and a review date
An internal wiki page explains one task or topic that colleagues need, such as a process, a tool or a team's responsibilities, and it names the person who keeps it current. The key judgement is scope: a page that covers one job, shows its owner and records when it was last checked stays useful, while a page that tries to hold a whole department's knowledge goes stale quickly.
Section outline
What each page should contain
Title that names the job
A title such as Book the large-format printer rather than Printing. Readers find pages by searching for what they need to do, so the title should use the words they would type.
40 wordsOwner and last checked
The role responsible for the page, the date someone last followed the steps and the date of the next check. Use a role rather than a person's name, so the page survives a change of staff.
30 wordsWho this is for
One or two sentences on who needs the page and in which situation. A reader should be able to tell in five seconds whether it applies to them.
60 wordsSteps or facts
Numbered steps for a process, each with one action, or a short table of facts for reference material. Put any warning before the step it concerns.
300 wordsExceptions and escalation
What to do when the standard path fails, the role to contact, the channel to use and the hours when that role answers.
120 wordsSources and related pages
Links to the system or policy that holds the authoritative version, and to the pages a reader needs next. Link instead of copying, so there is one version to keep current.
60 words
Total: 610 words
Example excerpt
A sample page for a print studio
Sample section
Sample page for a fictional print studio, Oakmere Print Studio. Details are invented for illustration. Book the large-format printer Owner: studio operations lead. Last checked: October 2, 2026. Next check: January 2027. Who this is for: anyone who needs a print larger than A3. Steps 1. Check the printer calendar for an open block of at least two hours. Allow for one proof run before the final print. 2. Add the job to the calendar with your name, the paper size and the number of prints. 3. Load the paper stock named on the calendar entry. Do not reuse paper from another job. 4. Print one proof on scrap before the full run, and attach the proof to the calendar entry. Exceptions If the printer shows an error code, stop and do not clear the paper path yourself. Message the operations lead with the code and the job name. If a deadline falls before any open block, ask the studio manager, who can release a block held for a client proof.
Format notes
Keep the page short, dated and linked
Link to the source of truth
If a rule lives in a policy system or a contract, link to it and summarise only what a person needs to act on. Two copies of the same rule drift apart, and the out-of-date one can be the one people follow.
One action per numbered step
A step that contains three actions gets partly done. Split it, keep the numbers in order, and put a warning above the step it concerns rather than at the end of the page.
Show the owner and the check date at the top
A page with no date is hard to trust. Show the owner role and the last-checked date near the title, so a reader can decide whether to ask before they follow the steps.
Mistakes to avoid
How wiki pages go stale
Covering a whole department on one page
A page that explains every process becomes a long index that nobody reads to the end. Write one page per job, and link them from a short index that has no steps of its own.
Writing from memory and never checking
Procedures change when tools and suppliers change. Follow the steps yourself at least once, then record the date you did so.
Leaving out who to ask
A procedure with no escalation path stops at the first unusual case. Name the role, the channel and the hours when someone answers.
Putting personal details on the page
Many people can read a shared wiki. Refer to roles rather than individuals, and leave out contact numbers, account details and passwords.
Frequently asked questions
What is the difference between an internal wiki and a knowledge base?
A wiki is a set of editable pages that a team builds up over time. A knowledge base is usually a larger, organised collection of articles, often for staff who answer questions or for customers. For a single internal page, the useful question is who maintains it and how colleagues will find it.
Does Content Creator give me an editable wiki?
No. The output is one HTML page, which can be sent by link or saved as a download. It is not a multi-page editable wiki and does not keep an edit history, so keep the living wiki in the tool your team already uses and publish single pages from it when you need a shareable copy.
Is there a free internal wiki page template?
A template can give you the headings: purpose, owner, steps, exceptions and sources. It cannot give you the steps for your job. Work through the process yourself, write the steps from what you observed, and check the page against the headings before you publish it.
How long should an internal wiki page be?
Long enough for someone to finish the task without asking a colleague, and no longer. If a page needs several screens of background, move the background to a linked page and keep the steps at the top.
Should our onboarding guide be one wiki page?
Usually not. An onboarding guide works better as a short index with one page per task a new hire must complete, and a first-week page that lists only the tasks due before the end of the week. That keeps each page short enough to follow on the day.
Browse by category
More references in General Business
References
FAQ Page
Reports
Decision Log
Reports
Investor Update
Decks
Board Deck
Documents
Digital Document
Documents
Strategic Plan
How to build it
Follow the eight-step wizard: type, assets and description, images, branding, contact and call to action, Atty Suggestions, blueprint, and generate. Atty generates one HTML page in the background. Review it, then publish and share the page link or download the HTML file.
