Skip to content

Create and Reuse a Custom Library

Define your own testing standard in the Custom Program, add reusable default findings, and select the saved Custom Library for future projects.

A Custom Library turns your team's testing method into a reusable part of voiqq. Instead of copying a spreadsheet for every engagement, you define the standard requirements once. Projects created from that library then share the same requirement identity, finding fields, workflow, and reusable default findings while keeping their own scope, evidence, assignments, comments, history, and reports.

Start with the right Program

Custom Program is the sixth parent Program in voiqq. It is intended for a method that your organization defines, such as functional testing, regression testing, exploratory testing, UAT, contract checks, privacy operations, product quality, or an internal control framework. When a recognized voiqq library already matches the engagement, use its Program instead. For example, choose the dedicated Accessibility or Web Application Security program when it matches the engagement. A Custom Library helps you organize your own method; it does not turn an internal checklist into a certification.

Prepare the standard before opening the form

  • Choose a clear library name, such as Product Regression Review or Privacy Request Handling.
  • Choose a short finding ID prefix, such as REG, FUNC, UAT, or PRIV.
  • List the stable standard requirements the team will assess. Do not use current bugs as requirements.
  • Give each requirement an ID, a short title, and a description that explains what the reviewer should check.
  • Confirm who is responsible for maintaining the method when requirements change.

Create the Custom Library in Admin

  1. Open Admin from the voiqq workspace navigation.
  2. Find Default Findings Engine, then move to the Custom Program section after the system libraries.
  3. Choose + New Custom Library.
  4. Enter the Custom Library name, finding ID prefix, and a short explanation of its purpose.
  5. Under Define the standard requirements, review the generated Standard ID for the first requirement. Edit it if your method uses another format.
  6. Enter the requirement title and description.
  7. Choose Add another requirement for each additional rule or review step.
  8. Review the highlighted field if voiqq reports an error. The message beside that field explains exactly what needs attention.
  9. Choose Create Library. The saved library now appears in the Custom Program section of the Default Findings Engine.

Add reusable default findings

  1. In Admin, locate the new Custom Library.
  2. Choose Open defaults.
  3. Open the requirement for which you want to prepare reusable issue language.
  4. Add a Summary, Description, and Remediation guidance that can serve as a starting point.
  5. Save the default. Repeat only for issue patterns that genuinely recur.
  6. Treat every generated finding as a draft. The auditor must edit it to match the behavior, evidence, affected area, impact, and remediation observed in the current project.

Create a project from the saved library

  1. Open Projects and choose New Project.
  2. Choose the team that will own the work.
  3. Under Choose a Program, select Custom Program.
  4. Under Choose a Custom Library, select the library you created in Admin.
  5. Enter the project name, description, assessment target, due date, and other project details.
  6. Choose Create Project. The project uses the saved requirements and defaults without changing the library itself.

Edit a Custom Library safely

Return to Admin and choose Edit library on its card. You can improve the name, purpose, finding prefix, requirement titles, and descriptions. Keep an existing requirement when its meaning is unchanged. Add a new requirement when the obligation is materially different. Removing a requirement stops it from being offered for new mappings, but does not rewrite historical project findings or previously generated report snapshots.

What happens after a plan downgrade

voiqq never deletes a Custom Library merely because the workspace moves to a plan with a lower library limit. Libraries are counted from oldest to newest. The oldest libraries within the current limit remain available, while newer libraries beyond the limit are shown as unavailable. Their data remains saved. Upgrade the workspace to use or edit them again.

Use the library with spreadsheet imports

When importing Excel, CSV, or a public Google Sheet, choose Custom Program and select the correct saved Custom Library during review. Confirm how the source requirement column maps to the library's Standard IDs. Confident source columns become standard voiqq fields. Unmatched columns remain in Additional Details, and the original grid remains available for comparison. A source comment column stays imported data; it does not become a project conversation comment.

Review the first project

  • Each requirement has one stable meaning and a unique ID.
  • Summary and the mapped requirement are visible in the project table.
  • Defaults are starting points, not claims that an issue exists.
  • Assignments, validation, evidence, comments, and history behave like every other voiqq project.
  • Imported data appears in the correct standard field or in Additional Details.
  • The final report is reviewed for scope, evidence, wording, and limitations before distribution.

Open Admin

Read the Custom Library model

Custom Program is voiqq's flexible parent program. Your organization creates a Custom Library inside it, defines its durable standard requirements, and then reuses that library for separate projects. A requirement describes what the team assesses; a default finding is optional reusable drafting help; an actual finding remains project-specific.