Verizel
🇬🇧🇳🇴
← Back to user guide

Workflows

Customers, Projects and Work Orders

Use the job structure that connects reports to the correct execution context.

CoreProfessionalEnterprise
ReportingScope of WorkAdvanced Validation

Summary

  • Customers, Projects and Work Orders define where reports belong.
  • This structure keeps technical reports connected to the correct job, contract, scope and execution requirements.

What you can do

  • Create a customer.
  • Create projects under a customer.
  • Create work orders under a project.
  • Create reports in the correct Work Order context.
  • Apply scope, validation and review requirements at the Work Order level where relevant.

Recommended structure

Use Customers for the client or owning organization. Use Projects for larger work packages or contracts. Use Work Orders for specific jobs, scopes or execution packages.

Reports should normally be created under a Work Order so that the report inherits or connects to the correct job context.

Why the Work Order matters

The Work Order is where job-specific control becomes useful. It can hold planned reports, Work Order-specific validation, review requirements, asset allocations and inventory reservations depending on enabled modules.

This avoids hiding important job requirements inside free-text report fields.

Basic workflow

  1. Create or open the Customer.
  2. Create or open the Project.
  3. Create or open the Work Order.
  4. Confirm Work Order metadata and scope.
  5. Create or generate reports under the Work Order.
  6. Execute, review and approve reports.