The Custom Libraries Default Findings Engine is a requirement-aware template layer for organization-defined assessment requirements. It helps a team define consistent starting language for recurring findings while the normal project remains the source of truth for scope, evidence, ownership, remediation progress, validation, and reports.
Library and standards scope
A Custom Library represents requirements authored by the organization rather than a voiqq system standard. It can support internal policy reviews, quality assurance, vendor assessments, contractual checklists, educational exercises, and proprietary consulting methods while using the same project, finding, evidence, assignment, validation, and export foundations.
Global, local, and project layers
- Global defaults are standards-based templates published by voiqq platform owners for a system Library.
- Local defaults belong to the signed-in workspace administrator and can override editable wording without changing the global source.
- A project finding receives copied template values and then becomes an independent record.
- Later global changes do not silently rewrite a local override or a finding already created in a project.
- Status is Open and validation is Pending when the reusable default is applied, unless an authorized project workflow later changes them.
Fields and canonical mapping
Each template is owned by a canonical organization requirement in the Custom Libraries Library. The reusable record contains a stable identifier, summary, description, remediation guidance, severity key, mapped values, source Library, and display order. The visible wording can be edited locally, while the background requirement identity continues to support filters, reports, imports, and New Finding suggestions.
Create or customize a default
- Define the purpose, audience, decisions, and stable requirements of the Custom Library.
- Use clear requirement identifiers and descriptions before creating defaults.
- Write reusable summaries, descriptions, and remediation without old project evidence.
- Choose severity and workflow options that have one documented meaning.
- Pilot each default in a small project and ask another reviewer to apply it.
- Revise the library deliberately rather than copying an old project as the new standard.
Writing rules for reusable findings
Write the summary as a concise statement of the recurring failure. Use the description to explain the expected behavior, likely impact, or control concern in neutral language. Use remediation to describe the desired outcome rather than a patch tied to one framework or customer. Store actual results, reproduction steps, affected assets, evidence, people, dates, measurements, samples, and environment details in the project finding.
Suitable template subjects
- A required approval is not recorded before a defined business action.
- A required quality review step is not completed or evidenced for the reviewed item.
- A vendor requirement is not implemented, tested, or supported by current evidence.
- An internal policy control has no assigned owner or repeatable review procedure.
- A training exercise needs a reusable example finding without copying a previous learner record.
Use a default in a project
Open New Finding inside a project configured with Custom Libraries. Choose Template mode or select a prepared template after choosing the applicable organization requirement. voiqq prefills the reusable values. Review every field, add the real evidence and context, and save the finding. Comments, attachments, assignments, history, validation, sharing, exports, and reports then use the same normal project workflow.
Accuracy and safety checks
- Keep requirement identity separate from the visible project field label.
- Do not copy client names, findings, or evidence into reusable defaults.
- Define which fields are required for a valid project record.
- Test imports and exports before organization-wide rollout.
- Review the library when policy or methodology changes.
Open the Custom Libraries engine
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.