Section 2 | Guest Intake Profile (fka Application Form)

[sanya301]

The Problem:

Currently, Guests have no means to provide information about themselves to the homeless youth matching organization as well as Hosts online.

User Story:

As a Guest, I should be able to see the questions in the Profile (formerly application form) and fill it to the best of my knowledge for the matching process.

High-Level Approach:

Profile (formerly application form) page with multiple questions and a place to enter the answers to those questions. The page should also contain options like save and have the ability to move to any section of the profile.

Additional note: Guest will see all communication in their process as "Profile", but we will internally refer to the form that the Guests fill out as "Intake Profile" in future stories for the purposes of distinguishing this from the "Matching Profile" that gets generated once the "Intake Profile" is approved. In this user story, "Profile" and "Intake Profile" are synonymous.

Solution Alignment

Considerations

• Anticipate that users will be using desktop, tablet, mobile devices --> use responsive design
• In the future, the plan is for the guest onboarding experience for multiple organizations (SPY and beyond), where different organizations might want to modify the profile (application) questions needed for Guests.

Goals & Success

Success is if a guest can successfully complete the intake profile (formerly application form), as well as edit it based on the instructions received from the coordinator.

Metrics

• Number of intake profiles completed vs the number of intake profiles (formerly applications) started.
• Average time taken to complete each intake profile (formerly application)

Key Features:

• Text-based questions for most questions (Questions where the answer would be in paragraph type). (As of now application form is same as safe place for youth. The link is in the PDF below)
• Date, phone number, email, checkbox and signature question types/validations
• Navigation on all profile (application form) pages to enable the users to modify their answers and move to any section of the profile (application)
• Save button on each page to save the profile (formerly application) and exit
• Autosave feature every time Guest tries to exit the page they are currently on with a message that informs them that the page's progress will be saved
• Ability to see the same saved profile (formerly application) after logging in
• Ability to edit the answers multiple times before completing the profile.
• Required field validations and indications that required fields have not been filled out
• Ability to see a final overall preview before submitting the profile
• Ability to sign the profile before each submission
• Button to submit the final profile
• Ability to get a PDF version of the signed profile (formerly application) on submission (download button or email whichever is easier; quick feedback from eng is that render + download pdf shouldn't be a major effort, will need input on what the pdf should look like). Update:
  • Email should be auto generated on submission
  • Ability to get PDF version at any given time from the Guest dashboard
• Ability to edit the answers if requested by the coordinator after a profile (application) is submitted.
• Ability to see the last version of the submitted profile (need to work out the design for accessing/displaying profiles)

Acceptance Criteria:

• Once a guest is logged in, they should be able to start the profile from the dashboard page under the Profile section.
• On the first page of the profile (formerly application form), a guest should be able to see the minimum expectations from a guest (Just like we see terms and conditions)
• A guest should be able to type/modify the answers to questions until the profile is submitted.
• Guest should see an error if a question type is filled incorrectly (Date, phone number, email and signature)
• Guest should be able to fill the profile (formerly application form) in multiple sessions by saving the profile using the autosave functionality (The autosaving functionality will add all the filled questions into the database for this particular guest)
• Given the guest is trying to close the tab, move to a different section of the profile or click any navigation item that would take them away from the current page they are on, they should see a pop up confirming if they want to leave and inform them that changes would be autosaved
• Guest should be able to see pre-filled answers for any answers that were saved at any point.
• Guest should see a (*) for mandatory questions and they should not be allowed to submit the profile if a mandatory question is not completed. They should see an error describing that a mandatory question is not completed and highlight the missing question (easier to identify) when they try to navigate away from a page
• Guest should be able to see a preview of all answers before the final submission.
• If a guest is logged in and has exited before submitting the profile (formerly application form), they should be able to continue the profile from the dashboard page under the application section and they should be redirected towards the first page that has an unfilled required field.
• Guest should be able to self-sign the profile (formerly application form) at the end by either uploading the signature from the computer or entering the name at the end. See considerations here
• Guest should have a submit profile (formerly application) button at the end of the application form which will lock the profile and send the profile for review to the coordinator.
• Guest should have the ability to get a PDF version of the signed profile on submission (download button or email whichever is easier)
• Once the guest has completed the profile (formerly application form), they should see the profile status as Pending Review on the dashboard page.
• If a coordinator finds any question incomplete and requests more info (to be discussed):
  • The guest should see a Needs more info status on the application tab of the dashboard and would receive an email/call from the coordinator on what needs to be edited
  • Profile should be unlocked for the Guest to edit all fields
  • Guests should be required to sign the edited version of the profile before they click submit.
• Guest should be able to navigate to any section of the profile (formerly application) without completing previous sections

Future Consideration:

• If a coordinator finds any question incomplete and requests more info (to be discussed)::
  • The guest should see a Needs more info status on the profile tab of the dashboard
  • On clicking the profile, the guest should be navigated to the first question that has a request for an edit
  • After the first requested edit question is modified, they should be directed to the next requested edit question and so forth (to be discussed with engineering)
  • Any questions that did not require changes should be locked.
  • Guests should be required to make changes to all requested edits field before they resubmit the profile
  • Guests should be required to sign the edited version of the profile before they click submit.

Guest physical application form (intake profile):

Guest application form Link - Guest profile for us

Design

• Review existing designs on Figma
• Edit existing designs as needed
• Designs are edited and ready for engineering. Link to the Figma: Guest Prototype Mobile , Guest Desktop Prototype

Team Reviews:

• Product - Sanya
• Design - Jiehong
• Engineering - Erik

Engineering

• Implement Forms API #636

Open Questions:

• What are the options for signature? Ideal is low effort legally binding signature capability. Need research on this
• Customer open question: should paragraph answers have a minimum character count?

[sanya301]

To be discussed: Whether we want email notifications after each step of an application

[erikguntner]

@sanya301 Thanks for the write up! This looks great. Are we still planning to keep it to one question per page or multiple?

[sanya301]

@erikguntner Great question, let's discuss this with design. We could group a few related questions into one page or do one per page (likely what we will need to do for mobile anyways)

[edela0015]

hi sanya, quick question: if a user enters their birthdate and it does not fall within the 18-25 range, will the system block them from completing the application or will they still go through the entire app and the coordinator will still have a final say.

[sanya301]

We might need an additional user story for filling out the guest about me info (which in the physical copy is after the guest signature)

[sanya301]

@edela0015 we realized that the Guest profile question (on page 10) that we originally thought we might include in the Guest application needs to be a separate action item that unlocks after the first submission of the Guest application. I'll be creating a new story for this

Edit: Created story here #589

[sanya301]

As discussed in the last sync, here is a follow up user story for signatures #611 @erikguntner

[jiehongc]

Updated user story with mobile and desktop figma file links

[erikguntner]

@sanya301 @jiehongc

Given the guest is trying to close the tab, move to a different section of the profile or click any navigation item that would take them away from the current page they are on, they should see a pop up confirming if they want to leave and inform them that changes would be autosaved

I have a few questions about edge cases regarding this functionality:

1. If the user provides some invalid information, such as an invalid email, phone number, etc. and the user navigates away are we okay with saving this data? Are we okay not validating data that is saved using the autosave feature?
2. If we aren't validating information through the autosave feature does that mean a section can only be marked complete by pressing the continue button? For example, if the user fills out a section completely with valid information and navigates away using the sidebar do we mark this as a completed section?

It may simplify things to make it so we only validate and mark a section as complete by pressing the continue button if we don't mind saving invalid information to the database.

Let me know if this makes sense or needs more clarification.

[erikguntner]

Also, consider checking out read.cv and their profile editor. I think the functionality is similar to what we are going for.

[edela0015]

@erikguntner

1a. No. 1b. Yes.

2. We are validating with autosave. To your example, yes.

[erikguntner]

@edela0015 thanks for clearing that up. One follow-up question: if we're validating during autosave, what is the expected functionality when the data is invalid?

[edela0015]

if we are validating for format (for example mm/dd/yyyy) is wrong and we autosave - this should be deleted next time the user logs in.
if we are doing a short answer where the minimum count is not met, for example, then we should still save this data.

let me know if this makes sense :) @erikguntner