Post Submission Workflows Overview
Eproval supercharges your permit application and review process by giving you the tools and capabilities to take control of all those other processes that happen after the applicant hits the submit button. And not just the ones you might be doing today, either formally or informally, but also all those processes you've been wanting to implement because you know they'll make things faster and easier for everyone.
What Are Post-Submission Workflows?
Post-Submission Workflows are really exactly what they sound like: all those processes that happen after submission to support the review process or ensure events are safer, more organized, and better prepared. But they're also about the future: giving you the insights to implement generational improvements and adapt to trends and changes.
How It Works
Just like when you build the application, you leverage the tools and capabilities of Eproval for the Post Submission Workflows. You're using all of Eproval's form building technology in various ways to configure the workflows to meet your unique needs.
You can see our Application Form Quick Reference Guide for a complete description and examples, but the form options include:
Checkboxes
Radio Dial Buttons
Text/Narrative Fields
Yes/No Questions
Date/Time Fields
Responsive Drop Downs
Arrays
Internal Data Tracking
Anything you want to track - like a Work Order or Permit Number from a different system - can be added to Eproval as a form element, just like you do when building an application. But instead of the applicant filling it out, the Permit Manager or Reviewer completes the form. The applicant may never see it, but it's tracked right in the application.
And just like the original application, all of these form elements can be downloaded to a CSV file and reported on, providing powerful data on trends and changes over time.
Post Submission Workflow Examples
Simple, Common Post Submission Workflows
Once you start thinking about how the different form options can be used by reviewers and other stakeholders, right in the application, you begin to see what's possible.
Track Anything: Internal or external facing data such as Work Order Numbers, Permit Numbers, Council District Community Name, Police Area Command, Parks and Recreation District, Business District, and more.
Inspection Forms: An inspection form can be added to the application that, for example, the fire marshal can complete in the field on a tablet or laptop.
Review Checklists: If you have rotational or inexperienced reviewers, you can add a checklist for them to fill out during their review.
Assessment Forms: Create forms to help complete an assessment of a particular application or event element.
Post-Event Evaluations: Add evaluation forms for the Permit Manager or applicable internal stakeholders to complete after events.
More Complex Post Submission Workflows
Again, these are just using form options in different ways, but are more complex execution examples.
Requirement Lists: After reviewing the application, the Reviewer can develop and share requirements for the Applicant, like for an Emergency Action Plan or Safety Equipment List, that applicants can follow like a checklist
Equipment Notifications: A Reviewer responsible for providing onsite equipment can notify the Applicant of the type, quantity, location, delivery and pick-up times
When the Need for More Detailed or Complex Information Arises
One of the more complex workflows happens when an application is assessed and, because of certain circumstances or conditions, the reviewer determines that more information is needed beyond what's included in the standard application.
For example, the size or location of an event may dictate a more complex medical plan than what's needed for 90% of other events. Because the majority of applications don't need this, it doesn't make sense to include it by default. However, when the need arises, it can be turned on and sent to the applicant to provide that more detailed or complex information.
Implementation Flexibility
The examples shown in this document aren’t an exhaustive list of potential Post Submission Workflows. It’s really about getting to think about what’s possible within Eproval, what you might want to implement, and how you can leverage Eproval’s capabilities to manage your own Post Submission Workflows.
Your Schedule, Your Choice
It's important to stress that you only have to implement the workflows you want according to your schedule. You can use what we have, modify them, or create your own. Think of it more as a menu of options that you can select from at any time.
What's Included
All of the Post Submission Workflows we showcase are available as part of your subscription package. However, the ones you use are up to you: you don't have to use all of them, and there’s no order or timeline in which they need to be implemented. Plus you can modify the ones you’ve seen or create your own, all depending on what your Public Agency Needs. They're really just a continuation of our Eproval Permit Application Prototype.