Skip to main content
Templates give you a pre-structured page so you do not have to start from a blank editor every time. Orizon QA includes four built-in templates that cover the most common QA document types. Each template opens with placeholder headings and content blocks already in place — fill in the details and save.

​
Built-in templates

Test Plan

A structured template for documenting the scope, approach, and test cases for a release or feature.

Bug Report

A standard format for capturing a defect with steps to reproduce, expected and actual results.

Feature Spec

A specification template for defining a feature’s problem statement, proposed solution, user stories, and acceptance criteria.

Meeting Notes

A quick-capture template for meeting date, attendees, agenda, discussion notes, and action items.

​
How to use a template

1

Open the Knowledge Hub home screen

Navigate to the Knowledge Hub. The home screen shows a Quick Start Templates section listing all four templates.
2

Click the template you want

Click any template name in the list. The new page editor opens with the template’s title, icon, and block structure already populated.
3

Fill in your content

Replace the placeholder text in each section with your actual content. You can add, remove, or reorder blocks just like on any other page.
4

Save the page

Click Save or press ⌘S to create the page in your Knowledge Hub.
You can also start a template from the Templates quick action on the Knowledge Hub home screen, which takes you to the full template gallery.

​
What each template includes

​
Test Plan

The Test Plan template gives you a structured document for planning a testing effort. It opens with the following sections:
  • Overview — a brief description of what is being tested and why
  • Scope — what is included in this test effort and what is explicitly excluded
  • Test Cases — a checklist block where you list each test case as a to-do item you can check off as testing progresses
This template is well-suited for sprint-level test planning, release sign-off checklists, and feature regression planning.

​
Bug Report

The Bug Report template structures a defect report so that any team member can reproduce and understand the issue. It includes:
  • Summary — a one-line description of the bug
  • Steps to Reproduce — a numbered list of the exact steps that trigger the bug
  • Expected Result — what the correct behavior should be
  • Actual Result — what actually happens when the steps are followed
Use this template to document any bug you find during exploratory testing, automated test failures, or production incidents.

​
Feature Spec

The Feature Spec template helps you define a new feature before implementation begins. It structures the discussion around:
  • Problem Statement — the user or business problem the feature addresses
  • Proposed Solution — a high-level description of how the feature will work
  • User Stories — a bullet list of user stories in the format “As a user, I want to…”
  • Acceptance Criteria — a checklist of conditions that must be true for the feature to be considered complete
This template is useful for capturing requirements that will feed into test case generation in Orizon QA’s codebase analysis tools.

​
Meeting Notes

The Meeting Notes template is designed for quick capture before and during a meeting. It includes:
  • Date — pre-filled with today’s date
  • Attendees — a field to list who was present
  • Agenda — a bullet list of topics to cover
  • Discussion — free-form notes from the meeting
  • Action Items — a checklist of tasks assigned during the meeting, with a placeholder for the assignee
After the meeting, share the page link with attendees so everyone has access to the agreed action items.

​
Customizing templates for your team

Built-in templates are a starting point. You can adapt any template-based page freely — add blocks, remove sections, or restructure the outline to match your team’s conventions.
If your team always adds the same custom sections to a Bug Report or Test Plan, create a page with your preferred structure and duplicate it whenever you need a new document of that type. Use the … menu on any page and select Duplicate to copy both the structure and content.