Operations
Write Your Own Procedures in the Knowledge Base
Your organization's SOPs, runbooks, and equipment notes live beside the Rivolq product help: private to your org, searchable, linkable to assets, and cited by the AI assistant.
Updated September 15, 2026
Two sets of articles
The knowledge base holds Rivolq's product help and your organization's own procedures: SOPs, isolation steps, commissioning checklists, and "how we do it here" notes. Your articles are visible only inside your organization, and you cannot edit Rivolq's help. Both appear in the same search. Open Knowledge in the sidebar, then New article.
Admins and supervisors can write; technicians and everyone else read. An SOP is a document other people follow, so it should not be quietly rewritten by whoever last had the page open. If a technician spots something wrong, the fix belongs in a note to a supervisor.
Draft, published, archived
- Draft: visible only to authors while you write.
- Published: readable by everyone in your organization and included in search.
- Archived: kept with its full history, readable by authors, but out of every reader surface, search, and the AI assistant's citations.
Archive rather than delete when a procedure is superseded. Deleting is permanent and removes the article's links, revision history, and helpfulness votes.
Revisions and change notes
Every save snapshots the previous version. The revision history panel shows what changed and when, and any earlier revision can be restored. Add a change note as you save, one line on why; "updated torque spec after the Q3 failure" is the difference between a document people trust and one they second-guess.
Linking articles to what they cover
An article can be attached to assets, work orders, PM schedules, and parts. Attach your chiller isolation procedure to the chillers and it surfaces on those records instead of waiting to be searched for. Attach it to the PM schedule that performs it and the steps reach the technician doing the job. See finding asset information and preventive maintenance basics.
Categories, tags, and review dates
Category groups articles in the browse rail; pick a handful and stick to them. Tags are comma-separated and cut across categories; facility names and equipment classes work well. Set a review due date on anything safety- or compliance-related; overdue articles are counted for you so stale procedures surface before an auditor finds them. Slugs are unique inside your organization only.
The AI assistant reads what you publish
Anything you publish is searchable by the AI assistant and cited by name when it answers from it. A wrong published article becomes a wrong answer. Draft is there for a reason.
Still need help?
Reach out for broken behavior, account-specific help, or billing questions.
