Verizel
← Back to user guide

Templates

Report templates

Understand how templates standardize controlled technical reports.

CoreProfessionalEnterprise
ReportingTemplate BuilderBasic Validation

Summary

  • Report templates define the controlled structure used when creating reports.
  • A good template reduces manual variation, improves consistency and makes review easier.

What you can do

  • Create reusable report templates.
  • Define report-level and record-level fields.
  • Add instructions and data tables.
  • Configure print layout.
  • Add basic validation rules.

Task help

Common tasks in this area

Open the task that matches what you are trying to do. The full article continues below.

Templates

Create a reusable report template

Use this when a report type will be used repeatedly across projects or work orders.

Open
  1. Create a new template.
  2. Select or define the Record Type.
  3. Add report-level fields.
  4. Add record fields, tables and instructions.
  5. Configure basic validation.
  6. Configure print layout.
  7. Test the template with a draft report.

Avoid creating duplicate templates for each job-specific tolerance. Use Work Order validation for job-specific criteria where available.

Open full guide →

What a template controls

A template can define fields, labels, tables, default values, instructions, attachments, validation rules and print layout.

The goal is to give users enough flexibility to create useful technical reports without requiring custom-coded templates for every customer or project.

Commercial value

Templates are one of the strongest parts of the portal because they allow controlled technical report configuration directly in the UI.

Instead of asking a software vendor to custom-code each report layout, authorized users can configure fields, tables, instructions and print output in a controlled way.

Good template practice

  1. Create reusable templates for repeated report types.
  2. Use clear human-readable field labels.
  3. Avoid creating duplicate templates only because job-specific tolerances differ.
  4. Use template-level validation for general rules.
  5. Use Work Order-specific validation for job-specific acceptance criteria when available.