PowerClerk Support Center

Program Design
Automations
Questions to ask yourself
Locating the Automations feature
Creating an Automation
FAQs
Communication Templates
Questions to ask yourself
Locating the Communications feature
Creating Communication templates
Smart Templates
Feature reference
FAQs
Deadlines
Questions to ask yourself
Locating the Deadlines feature
How to create Deadlines
Delaying Deadlines
Deadline Automations
Deadlines in the Admin View
Deadlines in Communication Templates
Deadlines in Reports
Deadlines in Project List Columns
Deadline Functionality Definitions
Feature reference
FAQs
Forms
Questions to ask yourself
Locating the Forms feature
How to create and edit Forms
Adding data fields
Configuring Forms
VersaForms
Sensitive Data Fields
Feature reference
FAQs
Roles
Questions to ask yourself
Locating the Roles feature
How to create and edit a Role
Feature reference
FAQs
Workflow
Questions to ask yourself
Locating the Workflow feature
How to create and edit the Workflow
Transitions
Changing a project's status
Feature reference
FAQs
Advanced Program Design
Channels
Locating the Channels feature
What are Channels?
Channels Checklist
3-Step Publishing Process
Channel Type A: Mark As Child
Channel Type B: Make Successor
Channel Type C and D: Create/Submit Related Project
Sending Signals
Connections
Questions to ask yourself
Locating the Connections feature
What are Connections
Input and Output Fields
Connecting, Testing, and Enabling
Maintenance and Alterations
Connections Message Format
FAQ
Content Library
Questions to ask yourself
Locating the Content Library feature
Uploading content to the Content Library
Use with Communication Templates
Use for Front Page content
FAQs
Curated Lists
Built-in DER lists
Global Lists
FAQ
Document Templates
Questions to ask yourself
Locating the Document Templates feature
How to define a new Template
How to define a new Merged Document
eSignatures
DocuSign template tags
Mapping eSignature tags
Smart Templates
FAQs
Formulas and Calculated Fields
Questions to ask yourself
Locating the Formulas feature
How to create a Formula
Formula Data Dictionary
FAQs
Front Page
Questions to ask yourself
Locating the Front Page feature
How to edit the Front Page
FAQs
Incentive Design
Questions to ask yourself
Locating the Incentive Design feature
How to design an Incentive
Incentive Options
FAQs
Single Sign On (SSO)
Azure AD
Okta IDP Configuration
SP Configuration
PowerClerk API
Custom API IDs
FAQ
API Documentation for Developers
Application & Process Automation
Getting Started
Common Usage Scenarios
Using Custom IDs
API Method Reference
Code Samples
Administration
Business Days
Questions to ask yourself
Locating the Business Days feature
Setting up Business Days
FAQs
Dashboards
Questions to ask yourself
Locating the Dashboards feature
How to create widgets in your Dashboard
Other Dashboard Actions
Data Import
Questions to ask yourself
Locating the Data Import feature
How to validate a Data Import
FAQs
Duplicate Check
Questions to ask yourself
Locating the Duplicate Check feature
How to use Duplicate Checks
FAQs
ePayments
Questions to ask yourself
Locating the ePayments History feature
How to add ePayments
FAQ
Import Projects
Questions to ask yourself
Locating the Import Projects feature
How to Import From V2
FAQs
Operation Status
Questions to ask yourself
Locating the Operation Status feature
How to use the Operation Status feature
FAQs
Program Info
Project Inquiry
Questions to ask yourself
Locating the Program Info feature
How to edit the Program Info menu
Notification Banners
Usage Info
FAQs
Program Statistics
Questions to ask yourself
Locating the Program Statistics feature
How to use Program Statistics
FAQs
Reports
Questions to ask yourself
Locating the Reports feature
How to setup Reports
Multi-instance reports
Sharing Reports
Integrate scheduled Reports
Cross-Program Reports
FAQs
Test Environment
Questions to ask yourself
Locating the Test Environment feature
How to setup a Test Environment
FAQs
User Administration
Questions to ask yourself
Locating the User Administration feature
How to work with User Administration
FAQs
Program Reporting
Data Fields
Questions to ask yourself
Locating the Data Fields feature
How to work with Data Fields
Custom Lists and Data Field Groups
Table form element
PV System + batteries element
FAQs
Milestones
Questions to ask yourself
Locating the Milestones feature
How to define a Milestone
FAQs
Project List Columns
Questions to ask yourself
Locating the Project List Columns feature
How to use Project List Columns
FAQs
Project Summary
Questions to ask yourself
Locating the Project Summary feature
FAQs
How to edit the Project Summary
Project Views
Questions to ask yourself
Locating the Project Views feature
How to edit Project Views
FAQs
Settings
My Account
Questions to ask yourself
Locating the My Account feature
How to use the My Account feature
Setting up Multi-Factor Authentication
MFA Recovery Guidelines
FAQs
FormSense
Questions to ask yourself
Locating the FormSense feature
How to use the FormSense feature
FAQs
Grant Access
Questions to ask yourself
Locating the Grant Access feature
How to Grant Access to users
FAQs
Integration Guides
Integration Guide 001: How to configure a Web Adapter – ArcGIS Implementation
Integration Guide 002: How to configure Electric Power Research Institute’s (EPRI) DRIVE Connect software with PowerClerk
PowerClerk Video Guides
New User Video Guide
Setting up Business Days
Dashboards
Edit Forms - Tutorial #1
Edit Forms - Tutorial #2
Configuring Forms
FormSense
Build A Formula
Automation with Formulas in Action Rules
Formulas and Advanced Visibility Rules
Calculated Fields
Milestones
Roles and User Administration
Visualize Workflows
PowerClerk User Group Sessions (UGS)
PowerClerk Responsive Admin View

Document Templates

Generate documents based on project data to simplify communications and contracts.

Document Templates feature


Questions to ask yourself about Document Templates:

What electronic or paper documents are required in the process?

What kind of documents should be downloadable? Will require eSignatures?
Which Data Fields should be populated within my document?
Are there requirements to keep a paper copy of certain Forms?

Do my documents currently exist in a standard text editor format (like Word)?

Locating the Document Templates feature

Anyone in a Role with the Edit Document Templates privilege can add Document Templates by opening the PROGRAM DESIGN menu and clicking on Document Templates:

 

Locating the Document Templates feature

Figure 1: PROGRAM DESIGN >> Document Templates

 

How to define a new Template

To define a new Document Template, please click on the New Template Definition button and name your new template, for instance: “Interconnection Template”. You can also enter a brief description for your new template:

 

New Template Definition

Figure 2: New Template Definition


To upload the template, expand your new template definition (by clicking the green “+” icon) and select Upload New Template. This dialog lets you browse to your document template and upload it to PowerClerk:
 

Upload New Template

Figure 3: Upload New Template


Please note: the Document Template feature allows you to define Data Field references within your template. This way you can populate project data within your template and pre-format your documents with required information. See below an example of a Word document, where the header section is populated with a range of Data Fields used within that program, inserted in with the proper Data Field curly brace tags. Within your Forms you can generate the finalized document and offer it for download to your installer or customer, keep as an internal copy and/or send for eSignature.

 

Sample template

Figure 4: Sample Document Template

 
You also have the option to append the Project Number to a generated document template. This improves the quality of life for admins who are managing multiple projects and documents and need to have a unique identifier tied to their documents:
 

Sample template

Figure 5: Append Project Number option

 

Merging Documents

Submitted Attachments, including those uploaded from Generated Documents, can be combined into a Merged Document. Attachments uploaded to Attachment Fields on the same Form containing the Generate Document element can also be merged.
 

How to define a new Merged Template

Attachments bound to be merged into one Document Template need to be marked as “Allow Document Merge” under Program Design >> Data Fields >> tab Attachments, and expanding the respective Attachment and using the Edit button offers to set option “Allow Document Merge”:
 

Allow Document Merge

Figure 6: Allow Document Merge

 
Once all attachments bound for a Merged Document have been marked as “Allow Document Merge” please navigate to Program Design >> Document Templates tab Merge Documents to start the configuration of the Merged Document and its contents:
 

Merge Documents Tab

Figure 7: Merge Documents Tab

 
Configuring a Merged Document allows Program Designers to define which other Attachments and Document Templates are to be combined, and if these items are required for the merging process to succeed. Please note that Document Templates to be merged will always be required whereas Attachments can be marked as required and are otherwise optional components of the final Merged Document:
 

 
Merge Documents Template Dialog

Figure 8: Merge Documents Template Dialog

 

How to set up eSignatures Step-by-Step

In this tutorial we are going to be requesting eSignatures from an Applicant and the Administrator of a program. We recommend that eSignatures are requested on an internal facing form after an application has been reviewed and approved.
 
Step 1: Create your eSignature document template
 
The data tags for the eSignature will be populated based on the contact details entered in a PowerClerk form (we will design this form at Step 2).
 
Commonly three DocuSign tags are placed into a Document Template: {Administrator Sign}, {Applicant Sign} and {Applicant (or Administrator) Date}. Place these tags in the respective signature spaces on the document using a white font color to completely blend into the background and become invisible to those signing this document.
 

Invisible DocuSign tags

Figure 9: Invisible DocuSign tags

 
Please note: The label in above screenshot shown as “Applicant” *must match* the signatory DocuSign tag portion as shown in the following example of specific DocuSign template tags, which will allow you to control positioning of eSignature elements:

  • {signatory Sign}: Place this tag within your Document Template to position the signatory’s signature.
  • {signatory Initial}: You can use this tag to designate where initials should be placed.
  • {signatory Date}: Use this tag to position the eSign date.

Commonly these three DocuSign tags are placed into a Document Template using a white font color to completely blend into the background and become invisible to the applicant signing this document. This also means that if you are trying to change a Document Template, you can identify potential DocuSign tags by highlighting the entire document to make them appear.
Please note: Avoid breaking these DocuSign template tags into multiple-lines as this may hinder proper placement of signatures or initials when the Document Template is parsed within DocuSign. Reducing the font size *will not* affect the actual size of the placed initials, so even though the DocuSign signatory template tags may appear very small when configuring the Document Template, the actual initials will be proper-sized and correctly placed in the respective area.
 
Besides the DocuSign signatory tags ({signatory Sign}, {signatory Initial, {signatory Date}}) you can also use the following specific DocuSign tags:

  • {signatory Text}: Adding DocuSign Text tags allow you to capture additional user input during the DocuSign, which you can further process within PowerClerk by mapping these tags with the Manage Template Tags page outlined in the next section. You can enumerate additional text tags by adding a number e.g. {signatory Text 1}, {signatory Text 2}, {signatory Text 3}, etc.
  • {signatory Sensitive}: By using DocuSign’s Sensitive tag the tag value will become obfuscated after the signer has entered the sensitive data.

 
Step 2: Upload your eSignature Document Template into PowerClerk
 
Anyone in a Role with the Edit Document Templates privilege can add Document Templates by opening the PROGRAM DESIGN menu and clicking on Document Templates:
 

PROGRAM DESIGN >> Document Templates

Figure 10: PROGRAM DESIGN >> Document Templates

 
To upload your eSignature Document Template, you will first need to make a new template definition. Click on the New Template Definition button and name your new template, for instance: “Interconnection Template”.
 

New Template Definition

Figure 11: New Template Definition

 
To upload the template, expand your new template definition (by clicking the green “+” icon) and select Upload New Template. This dialog lets you browse to your document template and upload it to PowerClerk:
 

Upload New Template

Figure 12: Upload New Template

 
Step 3: Create your eSignature Form in PowerClerk
 
Select a form (or create a new one) that you would like to request eSignatures for. Select the “Contact” field element from the “Add a Field” and drag and drop onto your form. Rename this contact field “Applicant”. Verify the “Field Name” is “Applicant”.
 
Please note: The field name “Applicant” is the data tag that we are using in the eSignature document template. {Applicant Sign}. The data tags in the document template must match the fields within PowerClerk.
 

{Applicant Sign} must match the respective Data Field

Figure 13: {Applicant Sign} must match the respective Data Field

 
Repeat these steps for the “Administrator” contact field.
 
Next, you will drag and drop the “Attachment” field onto the form. Rename your Attachment field to the specific document you are requesting eSignatures for. In this tutorial we named our attachment “Interconnection Test Form Agreement”:
 

Attachment field

Figure 14: Attachment field

 
When setting up the “Attachment” field you are given the option of “Generate/Sign Document” within the attachment field properties.
 
Select the Generate/Sign Document drop down button.
 

Generate/Sign Document

Figure 15a: Generate/Sign Document

 

Generate/Sign Document

Figure 15b: Generate/Sign Document

 
Follow Steps 1 – 7 below to configure the attachment for eSignatures.

  1. Within the “Generate/Sign Document” drop down you will select the Document Template that you just uploaded with the eSignature fields.
  2. You will also be able to configure if an eSignature is required, or optional. Selecting “Optional” will allow the user to upload a wet signed copy of the document or request eSignatures.
  3. Next you will select the green + sign “Add signatory”. Under label type “Applicant”
  4. For “First Name” choose the Applicant First Name from the contact field element.
  5. For “Last Name” choose the Applicant Last Name from the contact field element.
  6. For “Email Address” choose the Applicant Email from the contact field element.
  7. Select “Add” to commit the first signatory.

If another signatory is required, such as the “Administrator” select the Add Signatory button once more and populate the data fields with the required information.
 

Add Signatory

Figure 16a: Add Signatory

 

Add Signatory

Figure 16b: Add Signatory

 
The last step to configuring eSignatures on your PowerClerk form is by dragging and dropping the “Signature Request” field onto the form. Save your form:
 

Signature Request

Figure 17a: Signature Request

 

Signature Request

Figure 17b: Signature Request

 
Step 4: Demo your eSignature Form in PowerClerk
 
Configure your eSignature form so that it is available for the Administrator to fill out. Select a demo project to enter in demo data and select your own email address to send to. This way you will be able to demo the full functionality of the eSignature process:
 

Demo eSignature Form

Figure 18: Demo eSignature Form

 
Select the Sign and Upload button. This will open an attachment field that will allow you to upload the customer’s wet signed application if they did not opt to eSign.
 

Sign and Upload

Figure 19: Sign and Upload

 
Select “Change Signature Type” to switch back to “eSign”.
Select the “eSign” button.
Select “Preview Document”. This will allow you to view the pre-populated data in the document template to ensure accuracy before sending it to the Applicant for eSignature.
 

eSign

Figure 20: eSign

 
Once the document has been previewed you are now able to select the “Request Signatures” button. This will send the eSignature request to both the Applicant and the Administrator.
 

Request Signatures

Figure 21: Request Signatures

 
Select the Request Signatures button. PowerClerk will update the status of the eSignatures with “Out for Signing”. Once completed PowerClerk will automatically update this status
 

Out for Signing

Figure 22: Out for Signing

 
Step 5: Check your email for eSignature request
PowerClerk will send both the Applicant and Administrator an email. Select “Review Document” to eSign:
 

Review Document

Figure 23: Review Document

 
Once both parties have eSigned PowerClerk will update the eSignature status to “Completed”.
 

Completed

Figure 24: Completed

 
Step 6: Create your eSignature Form Automation
Now that your eSignature form is completed you can set up eSignature automations. There are three dedicated eSignature triggers for Automations when selecting a Form as the triggering element:

  • All Form eSignatures are complete – this will trigger once all parties have signed the document
  • One Form eSignature has failed – this will trigger when any eSignature fails (e.g., email delivery issue)
  • Any signatory has eSigned an envelope, waiting for others – this will trigger every time one of the signatory signs unless they are the last, in which case the scenario would be “All Form eSignatures are complete”

 

eSignature Automation Triggers

Figure 25: eSignature Automation Triggers

 

Cancelling eSignatures

To cancel an eSignature that has already been sent go to that project’s admin page. Scroll to the middle of the admin page and select the eSignature form from the forms drop down. Select Cancel Pending Signatures and type in the reason for cancellation.
 

Cancel Pending Signatures

Figure 26: Cancel Pending Signatures

 
Each email associated with the eSignatures will receive an email informing them the eSignature request was voided. Additionally, you can re-request eSignatures from here by selecting “Preview Document” >> “Request Signatures”.
 

eSignature Troubleshooting

There are two places to verify that the customer has received the DocuSign notification: from the eSignature Status and the eSignature request. The eSignature Statuses is a new drop down within the Project’s admin page. If an eSignature request fails it will send a bounce back email. This is reflected as “Auto Responded” in the eSignature Status drop down.

 

Auto Responded

Figure 27: Auto Responded

 
Additionally, on the form the eSignatures were requested an “Invalid email address” notification will appear if the eSignature was unable to deliver to the recipient. In cases of invalid email addresses you can cancel the pending signature request, fix the email address within the form, and re-request the eSignature.
 

Re-request eSignature

Figure 28: Re-request eSignature

 

 

Mapping eSignature tags

Configure eSignature Document Templates via the Manage Template Tags page to pull data entered during the eSignature process into the chosen PowerClerk data fields:
 

Manage Template Tags

Figure 27a: Manage Template Tags

 
When new Document Templates are uploaded to your program, PowerClerk will detect signatory tags.
 
The Manage Template Tags page provides you the ability to map signatory tags to PowerClerk data fields. Once the eSignature process is complete, all data entered by signers into signatory tags that are mapped to a PowerClerk data field will be copied to the configured fields.
 
Optionally, select a required format for data that the signer will be asked to enter during the signature process, e.g. to capture Social Security Numbers in Sensitive Data Fields within PowerClerk:
 

Manage Template Tags

Figure 27b: Manage Template Tags

 
DocuSign Date, Text, and Sensitive tags are mappable while the Sign and Initial tags cannot be mapped to a PowerClerk Data Field.
 
PLEASE NOTE: The Manage Template Tags page will only show signatory tags after you re-upload a Template Document for an existing Template Definition or upload a template for a new Template Definition.
 

Automation triggers for eSignatures

There are three dedicated eSignature triggers for Automations when selecting a Form as the triggering element:

  • All Form eSignatures are complete – this will trigger once all parties have signed the document
  • One Form eSignature has failed – this will trigger when any eSignature fails (e.g., email delivery issue)
  • Any signatory has eSigned an envelope, waiting for others – this will trigger every time one of the signatory signs unless they are the last, in which case the scenario would be “All Form eSignatures are complete”

 

eSignature Trigger

Figure 28: eSignature Trigger

 

Smart Templates

With the introduction of Smart Templates, PowerClerk has made it easier for Program Designers to create and maintain Document Templates and Communication Templates. Once you upgrade your templates to Smart Templates, PowerClerk will track all the Data Fields, Data Field Groups, and Attachments that your templates reference via Template Tags. Smart Templates will behave the same as the current templates when used, so the change will be invisible to your users.
 
Upgrading to Smart Templates will simplify the Program Designer’s job in the following ways:

  1. Early Error Detection:
    • PowerClerk will alert you to common errors in your templates as soon as you upload a new Document Template or save a Communication Template.
  2. Automatically Update Templates when Renaming Fields:
    • If you change the name of a Data Field referenced by a Smart Template, the Smart Template will automatically update to reflect the new name.
  3. Improved Data Field Reference Tracking:
    • Once all your templates are upgraded, the Data Field List Page will display new columns showing the Communication Templates and Document Templates referencing each Data Field, Data Field Group, or Attachment.
    • These new columns will appear once all templates of the respective type have been upgraded.
    • PowerClerk will block you from archiving fields that are referenced by a Smart Template.

 

Upgrading to Smart Templates

In order to take advantage of Smart Templates, you need to upgrade your existing Document Templates and Communication Templates. You will start the process by going to either the Document Templates page or Communications page under the Program Design menu. You can choose to have PowerClerk try to upgrade all your templates automatically by clicking the “Upgrade All Templates” button, or you can upgrade templates one-at-a-time by clicking any un-upgraded template in the table and clicking the new “Upgrade” button. You must upgrade your Communication Templates and your Document Templates separately.
 
You must upgrade all templates of a given type to see which templates of that type reference a given Data Field on the Data Field List Page. Once you begin upgrading templates, it is recommended to finish upgrading all templates as quickly as possible to avoid confusion that could arise when some templates are upgraded but others are not. For instance, if you rename a field, the upgraded templates that reference the field will automatically update to reflect the new field name, but the un-upgraded ones will not. If you have old templates that are no longer in use, you can choose to delete them rather than upgrade them.
 

Upgrading when a Test Environment Exists

If your program has an active Test Environment, it is recommended that you upgrade your templates to Smart Templates in the Test Environment. When you commit the Test Environment, the upgraded templates will be transferred to your production program. You do not need to upgrade every template in the Test Environment in order to commit it. If you expect to keep your Test Environment active for a long time, you can upgrade your templates in your production program, but you will need to repeat the same upgrades in the Test Environment before committing it.
 

Broken Template Tags

In most cases, your templates can be upgraded automatically with no manual intervention once you initiate the upgrade. However, during the upgrade process, PowerClerk may detect broken template tags. Any tags detected in this way are currently being ignored by PowerClerk when using the template, so this will alert you to existing errors in your templates. A tag can be identified as broken for any of the following reasons:

  1. Invalid Tags:
    • The tag contains a typo and PowerClerk cannot read it.
    • This may arise if there is a typo in the prefix of a template tag (ie. before the “:”), or if there is another typo or formatting error.
    • This can also arise in Communication Templates if there is HTML formatting applied to a portion of the tag but not the entire thing.
  2. Tags whose Reference cannot be found:
    • The tag attempts to reference a field or group that does not exist.
    • This situation may arise from a typo in the field name.
    • It may also arise if the field was renamed after the template was created.
  3. Tags whose Reference is archived:
    • The tag attempts to reference a field that has been archived.

You will need to manually correct any errors in a template to finish upgrading it. Once all the errors have been corrected, PowerClerk will automatically upgrade the template to a Smart Template.
 

Examples of Broken Tags
  1. {data: Customer Naame First}:
    • Assume a field called “Customer Name First” exists.
    • This template tag is broken because it contains a simple typo in the name of the Data Field it is trying to reference.
    • This can be resolved by fixing the typo in the field name
  2. {data: Payment Amt}:
    • This tag does not contain an obvious typo, but it may still be invalid if there is no field named “Payment Amt.” This could arise if the field has been renamed or archived. For example, perhaps a designer later renamed the field “Payment Amount.”
    • This can be resolved by ensuring the tag text matches the current field name or unarchiving the “Payment Amt” field if applicable.
  3. {Project Number}:
    • This is a template tag for the built-in ProjectNumber field, but it contains a subtle typo. The correct tag is {ProjectNumber} (no space). You can view all supported template tags for built-in fields in the Built-In Fields Tab of the Data Field List Page.
    • This can be resolved by fixing the typo (removing the space).
  4. {fullname: Customer}:
    • Assume a contact Data Field Group called “Customer” exists.
    • This tag is invalid because of a typo in the tag prefix. The correct prefix is “full_name” (underscore, not hyphen), so the correct tag is {full_name: Customer}.
    • This can be resolved by correcting the typo in the tag prefix.
  5. {{data: <b>Applicant Email</b>}:
    • Assume a field called “Applicant Email” exists.
    • This may arise in Communication Templates due to HTML formatting interfering with PowerClerk’s ability to read a template. This is tricky to understand because it may appear correct when the template is inspected visually. The issue is that the <b> pieces are invisible when the template is viewed in the browser because they convey the information that the text “Applicant Email” appears in bold. In this case, the tag will appear as the following to the user: {data: Applicant Email}. However, when PowerClerk processes the template, the <b> text gets in the way of finding the correct “Applicant Email” field. This kind of error may look different depending on the specific text formatting in the template, but any case where you see text enclosed in angle brackets (“<”, “>”) showing up in the template errors but not visible in the template is probably an example of this.
    • This can be resolved by clearing existing text formatting from the template tags in your Communication Template and ensuring that any formatting applies to the entire tag, including the outer brackets.

To remedy Template Tag formatting errors, there are several ways to alleviate these issues:

  1. With the whole tag selected, click the “Clear formatting” button as sometimes tag formatting is completely invisible to the viewer:
     

    Clear Formatting

    Figure 28: Clear Formatting

     

  2. Alternatively, delete the tag and re-type it from scratch. That will also remove any invisible formatting.

Video Guides

Would a video guide help to better explain Document Templates? Contact us and let us know.
 
A full list of all Video Guides can also be found here.

FAQs

Q: For leased systems we have the lessor sign an interconnection agreement. Can we use the eSignature feature to email the agreement to the lessor without them having to create an account with PowerClerk?
A: PowerClerk's DocuSign integration (see the eSignatures section above) does not require the lessor to have a PowerClerk account. The designated signatory data field configured to capture the lessor's email address serves to send out the eSignature request from PowerClerk, prompts the lessor to sign via DocuSign, and updates the eSignature status accordingly within PowerClerk upon completion.

Have additional questions? Contact us to nominate your FAQ and help others find answers to your own questions concerning this feature.

Create A Support Ticket

Not finding your answer here?  Submit a question to our support team at the PowerClerk Ticket System and leverage the PowerClerk team’s expertise.