Skip to main content

Workflow Ticket Required Fields

Ability to require certain fields are entered prior to submission

Required Inputs for Workflow Tickets

Overview

The Required Inputs feature helps ensure workflow tickets contain all necessary information before they can be submitted. Program Admins can now configure specific job inputs, recommendation fields, and custom fields that must be completed before a contractor can move a workflow ticket forward. This helps improve data quality, reduce incomplete rebate submissions, and minimize back-and-forth communication between contractors and reviewers.

Benefits

Improve Submission Quality

Require critical information before a ticket can be submitted, helping ensure rebate applications and program requirements are complete and valid.

Reduce Review Delays

Missing equipment details, serial numbers, custom fields, or other required information can be identified and corrected before submission, reducing review cycles and change requests.

Enforce Program-Specific Requirements

Admins can configure required fields that align with their program's workflow and data collection requirements, including standard Snugg Pro fields and custom fields.

Support Equipment Verification

Programs can require important equipment information, such as HVAC model and serial numbers, before contractors submit tickets for review.

Simplify Contractor Experience

Contractors can easily see what information is missing, navigate directly to the appropriate job section, and track completion progress in real time.

Who Can Configure This Feature?

Users with Program Admin permissions can configure Required Inputs within Workflow Ticket Templates. Program admins have permission to define workflow ticket templates and settings.


Configuring Required Inputs

Step 1: Open the Workflow Ticket Template

  1. Navigate to Settings.

  2. Select Your Programs.

  3. Open Workflow.

  4. Edit an existing workflow ticket template or create a new template.

  5. Scroll to the Required Inputs section.

The Required Inputs section allows administrators to define which fields must be completed before ticket submission.


Step 2: Add Required Inputs

  1. Click Add Required Inputs.

  2. The Select Required Inputs window will open.

  3. Browse the available input tree or use the search box to quickly locate specific fields.

  4. Select the fields that should be required.

Fields are organized using the same job structure users see throughout Snugg Pro, including sections such as:

  • Building

  • HVAC

  • Appliances

  • Concerns

  • Custom Fields

  • Recommendation Inputs (Refine Screen)

Administrators can search and filter the tree to quickly find specific inputs in larger programs.


Step 3: Configure Base and Improved Requirements

For applicable fields, administrators can specify whether the requirement applies to:

  • Base values only

  • Improved values only

  • Both Base and Improved values

This flexibility allows programs to enforce the exact Snugg Pro or custom field data requirements needed for a workflow stage.

Example

A program may require:

  • Improved HVAC model number

  • Improved HVAC serial number

  • Improved system efficiency

while not requiring the Base system information.

Step 4: Save Changes

  1. Click Save.

  2. Save the workflow template.

New tickets created from the template will begin enforcing the configured requirements.


Using Required Inputs in a Job's Workflow Ticket

Viewing Required Inputs

When a workflow ticket contains required inputs, users will see a Required Inputs tab within the ticket.

The tab displays:

  • Required sections

  • Individual required fields

  • Whether Base and/or Improved values are required

  • Current completion status

  • Progress indicator showing completed versus required fields

Identifying Missing Information

Missing fields are clearly highlighted so users can quickly identify what still needs to be entered before submission. The system indicates:

  • Which field is missing

  • Which section contains the field

  • Whether the requirement applies to Base or Improved values

  • Which system or recommendation the requirement belongs to

Example

A contractor may see the following required fields listed:

Field

Base

Improved

Indoor Model #

Required

Indoor Serial Number

Required

Outdoor Model #

Required

Outdoor Serial Number

Required

In this example, only the Improved equipment information is required before submission.

Navigating to Missing Inputs

To make data entry faster, users can click the link provided within the Required Inputs section to open the associated Job Input area.

This allows contractors to quickly jump to the correct section without searching through the entire job.

Real-Time Validation

As users enter required information:

  • Missing field indicators are automatically cleared.

  • Progress updates immediately.

  • Completed fields are reflected within the Required Inputs tab.

Submitting the Ticket

When all required inputs have been completed:

  1. Return to the workflow ticket.

  2. Verify the Required Inputs progress shows all requirements complete.

  3. Click Submit for Review.

If any required fields are still missing, submission is blocked until the missing information is entered. The Required Inputs tab will identify what must be completed before the ticket can move forward.


Best Practices

Require Only What Is Necessary

Focus on the information needed for program compliance, rebate processing, and quality assurance.

Use Search When Configuring Large Programs

The search feature helps locate specific inputs quickly without expanding every section.

Match Requirements to Workflow Stages

Different workflow templates can enforce different requirements depending on where the job is in the process.

Use Improved Equipment Requirements for Installation Verification

For rebate and installation workflows, requiring Improved equipment details such as model and serial numbers can help ensure completed work is properly documented.


Summary

The Required Inputs feature helps programs improve data quality, reduce submission errors, and ensure workflow tickets contain all necessary information before review. Program administrators can configure required fields from standard job inputs, recommendation inputs, and custom fields, while contractors receive clear guidance, progress tracking, and direct navigation to missing information to streamline ticket submission.

Did this answer your question?