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
Feature reference
FAQs
Deadlines
Questions to ask yourself
Locating the Deadlines feature
How to create Deadlines
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
Document Templates
Questions to ask yourself
Locating the Document Templates feature
How to define a new Template
Feature reference
eSignatures
DocuSign template tags
Mapping eSignature tags
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 From V2
Questions to ask yourself
Locating the Import From V2 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
Billing 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
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
Web Adapter Factory
Questions to ask yourself
Locating the Web Adapter Factory
What are Web Adapters
Input and Output Fields
Connecting, Testing, and Enabling
Maintenance and Alterations
Web Adapter Message Format
FAQ
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
Project Summary
Roles and User Administration
Visualize Workflows
PowerClerk User Group Sessions (UGS)
PowerClerk Responsive Admin View

Deadlines

Schedule and trigger events in your application process that keep your organization streamlined.

Deadlines feature


Questions to ask yourself about Deadlines:

When should the countdown start for a Deadline?
Do I want to send out reminders? And to whom?
What should happen if the Deadline is not met?

Locating the Deadlines feature

Anyone in a Role with the Edit Deadlines privilege can navigate to the Deadlines screen by opening the PROGRAM DESIGN menu and clicking on Deadlines.

 

Locating the Deadlines feature

Figure 1: PROGRAM DESIGN >> Deadlines

 

How to create Deadlines

A common Deadline used in PowerClerk is a Deadline that requires Administrators who review applications to complete a preliminary review of every application that enters the Application in Review Status within a certain number of days. In this way, the Deadlines feature can help monitor program performance and set reasonable metrics for application processing. Deadlines can also be configured to ensure applicants (or any other user with an email collected in PowerClerk) submit certain data by a due date. In this way, Deadlines can help manage applicant expectations and provide a better applicant user experience.

To configure a Deadline, navigate to the Deadlines screen and click New Deadline:

 

New Deadline

Figure 2: New Deadline


The Deadlines screen works similarly to Actions, in that the user must configure each dropdown menu on the screen:

 

Configure Deadline

Figure 3: Configure Deadline


Due in: With this setting you can configure the countdown in days before or after a deadline shall expire. You can also dynamically calculate this date by using another Data Field to calculate the target deadline date. Please Note: If the Data Field you are trying to dynamically calculate a Deadline date with does not have a value when the deadline is started, no deadline will be set.

 

Due in

Figure 4: Due in


Allow only one instance for each project and Allow update: If another instance of this deadline is created (either manually or by an Automation’s Action Rule) and the previous instance is not satisfied, the due date will be determined using the current value of the data field reference for which the deadline relies.

 

Deadline instances

Figure 5: Deadline instances


Satisfied by status change to:

  • Require manual change: the Deadline will keep counting down until an Administrator specifically marks this Deadline as Satisfied from the project’s Admin screen.
  • Any status change: the Deadline will automatically be marked complete if the project changes to any Status but the one in which the Deadline was originally set.
  • [Specific Status]: the Deadline will automatically be marked complete if the project changes to this specific Status.

Remind with template: this setting specifies which Communication Template shall be sent as the Deadline Reminder, an email sent to the relevant group or individual for whom the Deadline due date is approaching. Within the Communication Template you can configure which recipients receive the reminder as well as the messaging such as what actions need to be taken in order to satisfy the deadline.

Reminder schedule: Choose this option, if you require different intervals for the reminder schedule to be sent out. The default schedule will send reminder notifications 60, 30, 7, and 1 day prior to the deadlines expiration. This schedule will discontinue, once the deadline has been satisfied. Alternatively, a custom schedule may be specified by a custom schedule by providing the reminder intervals separated by commas (e.g. “200, 60, 20, 5, 1”).

On expiration: This setting allows you to define what should happen if the deadline expires without being satisfied. Options for the Actions that can occur when a Deadline expires include changing the project’s status and sending out a Communication Template to inform the relevant parties that the deadline expired.
 

Delaying Deadlines

The option to delay a Deadlines expiration dates will allow you to accommodate for storm days and delays all deadlines without having to extend them individually, reset a temporary delay, or recalculate Deadline expiration (only for Deadlines configured to use Business Days):
 

Delaying Deadlines

Figure 6: Delaying Deadlines

 

Deadline Automations

Deadline Automations allow deadlines to be: Set, Paused, Resumed, and Satisfied based on certain events triggered through an Automation Action Rule.
 
A common Deadline used in PowerClerk is a Deadline that requires Administrators who review applications to complete a preliminary review of every application that enters the Application in Review Status within a certain number of days.
 
Through an Automation Action Rule a Program Designer can “Set” a deadline for Administrator Review when an application is submitted. If the application review reveals that corrections are required by the applicant, another Deadline Action Rule can be set
to “Pause” the Application Review status, and “Set” the Customer Corrections Deadline.
 
Once the customer has submitted their corrected application and the status of the project moves back to “Application Review” the Deadline for “Application Review” can “Resume” and the Customer Corrections Deadline is set as “Satisfied”.
 
Steps 1 – 3 below illustrate this example:
 
Step 1: When the project status enters “Application Review”, “Set Deadline [Application Review]”:
 

Set Deadline Action Rule

Figure 7: Set Deadline Action Rule

 

Set Deadline Action Rule

Figure 7b: Set Deadline Action Rule

 
 
Step 2: If customer corrections are required on the application, two deadline action rules are configured: “Pause Deadline [Application Review]”, and “Set Deadline [Customer Edits Required]”:
 

Pause Deadline Action Rule

Figure 8: Pause Deadline Action Rule

 
 
Step 3: When the customer corrections are finished and the project re-enters the Application Review status, two action rules are configured: “Satisfy Deadline [Customer Edits Required]”, and “Resume Deadline [Application Review]”. Please note: In these examples a formula condition was used to express the scenario of customer corrections being required:
 

Resume Deadline Action Rule

Figure 9: Resume Deadline Action Rule

 

Deadlines in the Admin View

Deadlines in the Admin View Project Page now show “Status, (Paused, Pending or Satisfied), Due Date, Due in day(s), length the deadline has been paused, and the End Date.” The End Date represents the date the deadline was Satisfied.
 

Deadlines in the Admin View Project Page

Figure 10: Deadlines in the Admin View Project Page

 
 

“Deadline Active” Template Tag

Template tags for deadlines are now available. This template tag shows how long the deadline was active in the “Pending” status. This template tag disregards all time that the deadline was “Paused”.
 
This template tag can be helpful when reporting on how long a deadline was actively being processed during a specific status:
 

Deadline template tags

Figure 11: Deadline template tags

 
To illustrate the Deadline Automations Template Tag, the communication template below is configured to send a utility customer an email informing them how long the utility took to process their application:
 

Deadline template tags

Figure 12: Deadline template tags

 

Allowing a deadline to continue running after due date

A new deadline feature is now available within the “Edit Deadline” page. The feature, “Allow deadline to continue running after due date” can be selected if you wish the deadline to be used like a timer.
 
If this box is checked, the deadline counter will continue to run until satisfied (the counter will continue to run even when expired), and you can report on how long the deadline has been active. This feature can help utilities uncover bottlenecks in their workflow, understand how long deadlines run before being satisfied, and the number of days a deadline may run before it is considered due in the definition of that deadline.:
 

Allowing a deadline to continue running after due date

Figure 13: Allowing a deadline to continue running after due date

 
 

Deadlines in Reports
Deadline in Reports

Figure 14: Deadlines in Reports

 
Deadlines can also be reported upon by using the Deadlines column within your Report to retrieve the due dates for a set deadline. You can also use the Nearest Deadline column within your Report to fetch the next, upcoming Deadline per project and output this information in your Report:

    Within the Multi- Instance Report you can now report on Deadline History. The deadline fields being reported are:

  • Deadline Name: Name of deadline
  • Creation Timestamp: The date the deadline was originally created (set) on a project deadline.
  • Due Date: Deadline due date that includes any extension such as Delay Deadline or Admin Change Due Date.
  • Original Due Date: Original due date, prior to a Delay Deadline or Admin Change Due Date being triggered.
  • Deadline Status: Pending (active), Paused, Satisfied, Expired
  • End Date: The date the Deadline was marked as “Satisfied”
  • Calendar Days Running: The difference (in calendar days) between the creation date and the time the deadline was stopped by the Automation, minus the time it was paused (explicit to the Deadline Automations).
  • Calendar Days Left on Paused Deadline: The calculation of days remaining in calendar days (explicit to the Deadline Automations).
  • Calendar Days Paused: Number of calendar days the deadline has been paused (Explicit to the Deadline Automations).
  • Business Days Running: The difference (in business days) between the creation date and the time the deadline was stopped by the Automation, minus the time it was paused (explicit to the Deadline Automations).
  • Business Days Left on Paused Deadline: the calculation of days remaining in business days (explicit to the Deadline Automations).
  • Business Days Paused: Number of business days the deadline has been paused (explicit to the Deadline Automations).

Please note: The deadline automations “Days Running, Days Left, and Days Paused” is calculated by the difference between the Creation Timestamp, and the time the deadline was stopped (i.e., paused), minus the total time paused.
 

Days Running, Days Left, and Days Paused

Figure 15: Days Running, Days Left, and Days Paused

 

Deadlines in Project List Columns

With the ability to add column headers Nearest Deadline Name and Nearest Deadline Due Date in your Project List Columns, you can easily add an overview of which Deadline will expire next for each project in your program:
 

Deadlines in Project List Columns

Figure 16: Deadlines in Project List Columns

 
 

Satisfying Deadlines with a Data Import

Please follow this link to learn more about how to satisfy Deadlines in bulk via Data Imports.
 

Deadline Functionality Definitions
  • Deadline Automations: to pause/resume deadlines with the purpose of obtaining a tally of the total number of days a deadline was running or “active” (useful for reporting purposes).
  • Delay Deadline: to modify the due dates of all active deadlines for a particular Deadline Definition (useful in scenarios where all instances of a deadline need to collectively be extended e.g., during storm duty events)
  • Change Deadline: Admin page functionality allowing an Admin to change the Due Date for that project’s active Deadline(s).

Feature Reference

Deadlines

Deadlines enable administrators to keep stakeholders abreast of the timing requirements for any application. PowerClerk can automatically send reminder communications prior to expiration of a deadline and can also send additional communications and/or change the status of a particular application when a deadline expires.


As shown in Figure 8 below, a Deadline can be configured to automatically send reminder emails. A Deadline can be configured to be satisfied once the application is moved into a new status.

 

Reminder Schedule

Figure 8: Reminder Schedule

Video Guides

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

FAQs

Q: In the ‘View/Edit’ page for a project I see a ‘Deadlines’ section, but I don't see the same deadline exposed that I can see on the ‘Admin’ page. Why is that?
A: As the majority of deadlines are mostly utility internal, and most utilities would not want to expose such deadlines, you will have to mark a deadline on the Edit Deadline page as Show on Project View/Edit page to display this deadline also on the View/Edit Page: Show on Project/view page

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.