Onboarding Checklist

Before leveraging COMFORT for your form implementation, consider the following points first:

Form Questions

What are the form fields you need?
For each question you want in the form, we will typically want:
- A label (for example, the question being asked)
- The Input control (is this a text field, checkbox, radio button, etc.)
- Validation rules (formatting requirements, is input optional)
- Any conditional logic (is this field dependant on another field)
Common Forms Toolkit has been successfuly used for various 'attestation'-type forms. These forms typically collect a series of contact details and yes/no answers to a list of questions. This toolkit can quickly accommodate additional instances of this form type with minimal custom coding required.

If your business area needs a completely different form structure, resources will need to be allocated to build that.

Using mobile-friendly mark-up and a modern interface component framework, you can design your form using a combination of fields and controls. (think date pickers, interactive maps, drop-downs, checkboxes, etc...)
Do you need any form fields populated with data from External BC Govt. APIs? For example,
an Address Geocoder
or OrgBook BC directory of registered companies?

Content for a landing page - Introduction text including and links to any external documents or resources related to the form
Form Title (this will get used in the website header, on form submissions and email notifications)

If your form has many questions, you may want to simplify navigation by spreading the form across multiple 'steps'. Typically, we show the user filling the form a review page where they can go back and update the data they have entered.
After submitting the data, the user could download a PDF version of their submission or send a link to their submission via email.

Notification Email: What email address should receive notifications when the form is submitted? This can be a group address or a list of individual addresses.
Confirmation Email sender: what email address should the user's confirmation notification show as being sent from?
A Form Administrator: at least one person from the business should request 'Admin' access. Once approved they can manage access for the rest of their team. We also have some Instructions for using the Administrator Panel.
Dashboard Editor: Email address of somebody who will have permissions to 'curate' a usage dashboard powered by Metabase. We already have a template you can use like this one.
Submission Status Options: The permitted sequence of status changes that can be made by an Administrator to a submission as it is processed. For example, should a submission need to be 'assigned' before it can be marked as 'completed'?

Is the web form public or does the form filler need to sign in with a password?
Does the form need to be reached via a 'vanity' URL (something more memorable than the functional URL of the COMFORT system?
On what date does the form need to go live?

Return Home