Define workflow from moving collected info to Hellosign
As initially discussed, we plan on sending completed form data to membership.coordination where the team will be responsible for reviewing the data before manually creating/sending Legals documents via Hellosign.
The next stage is building on top of what we created in order to simplify our process and our workflows.
Here's my initial vision for this. Please note that this is still open for discussion:
We first need to create a "Report" section that would allow our membership team to review form submissions regardless of their state. The default should be to filter them by "completed/submitted" forms.
The landing page of this report page would be a list of form submissions. Each row would have a link to view more information. This view more page would display all our captured information about the request. I would also include actions buttons on this page such as "Send Legal Document".
The "Send Legal Document" button would lead to a new page with a history of the legal documents sent from this system. This page would also include a dynamic form that would allow staff to send a legal document based on the information captured in our enrollment form.
The first question of this form would be "Document Type": A dropdown with various options (Membership Agreement, MCCA, WGPA IoT...)
and then based on the chosen document, we would display a mapping of all the data that we wish to send to Hellosign. To make it easier, we could allow staff members to make changes before the document is sent.
Signing Authority: Mike Milinkovich (edit) Membership Class: Associate: NGO (edit) Key Contacts: (edit) Paul White Denis Roy ..etc
I think the first step is documenting each legal document and their respective fields in a google doc. For example:
Membership Agreement:
- Signing Authority: pre-populated from form submission
- Signing Authority Signature: Empty when the document is sent but required by the client