Pre-Launch Checklist

Launching a program in FORWARD Direct is a major milestone. Before switching your program to Active, it’s critical to confirm that all portal, program, workflow, and communication settings are fully configured and tested.

This Pre-Launch Checklist answers the most common questions program teams ask before going live and helps you avoid applicant confusion, workflow issues, or reporting gaps once applications open.

What is the FORWARD Pre-Launch Checklist?

The Pre-Launch Checklist is a final readiness review to confirm that your Portal and Program are fully configured, tested, and approved before accepting real applications.

It ensures that:

• Applicants see a complete, accurate experience

• Staff roles and permissions are correctly assigned

• Workflows, notifications, and reports function as expected

• Your program launches smoothly without operational disruptions

This checklist applies to all FORWARD Direct programs, regardless of program type or template. 

When should I complete the Pre-Launch Checklist?

You should complete the Pre-Launch Checklist before changing a program’s status to Active.

Best practice is to complete the checklist while your program is in TEST status so you can safely submit test applications and validate workflows without exposing the program to the public. 

Portal Readiness FAQs

Is my portal branding complete?

Confirm that:

• Organization name, portal title, and welcome message are filled out

• Large logo, small logo, and background image are uploaded and display correctly

• Brand colors are selected and readable across pages

• Login, sign-up, and portal selection pages have been previewed

Incomplete branding can create confusion or reduce applicant trust. 

Are portal-level notifications set up?

Verify that default portal notifications are created and reviewed, including:

• Account creation emails

• Password reset emails

These notifications apply across the portal and are separate from program-specific notifications. 

Are the right portal admins assigned?

Confirm that:

• At least one Portal Admin is assigned

• Portal Admins can manage portal settings, branding, notifications, and program recovery

• Additional team members are added only if they need portal-level access

This helps prevent accidental changes or deletions. 

Program Configuration FAQs

Is the program using the correct template?

Program templates cannot be changed after creation.

Before launch, confirm that the correct template was selected:

• Individual / Household

• Business

• Case Management

• Case Management with Referrals

• 3rd Party

If the wrong template was selected, a new program must be created. 

Are Basic Settings complete?

Check that the following fields are finalized:

• Program name and description

• Funding source and budget (if applicable)

• Program type

• Two-Factor Authentication settings

• Self sign-up and multiple application rules

These settings control applicant access and security. 

Is the application form complete and published?

Before launch:

• All required sections and fields must be configured

• Eligibility logic must be reviewed

• Internal-only sections must be properly grouped

• The form must be published, not just saved

Launching with an incomplete form may expose unfinished sections to applicants. 

Workflow & Review FAQs

Are workflow stages reviewed and validated?

Confirm that:

• All workflow stages reflect your program’s real process

• Roles can move applications through assigned stages

• Denial, appeal, and finance paths are correct (if applicable)

Workflow issues can block applications once the program is live. 

Are workflow state labels applicant-friendly?

If you’ve customized workflow state labels:

• Confirm public-facing labels are clear and appropriate

• Ensure sensitive internal terms (such as fraud-related states) are hidden from applicants

Applicant-facing labels appear in notifications and dashboards. 

Are denial reasons configured?

Before launch:

• All possible denial reasons should be created

• Messaging should be clear, compliant, and approved

• Languages should match program requirements

Denial reasons feed directly into notifications and reporting. 

Notifications & Communications FAQs

Are program notifications created and active?

Confirm that:

• Notifications exist for key workflow stages

• Correct recipient types are selected

• Email, SMS, or voice messages are reviewed

• Tokens populate correctly with application data

• Notifications are set to Active, not Paused

Notifications are essential for applicant communication once the program is live. 

Is contact information configured?

Verify that:

• Program email address is set

• Phone number and area code are generated

• Support phone number is assigned if needed

These contact details power automated and manual communications. 

Team & Permissions FAQs

Are program team roles assigned correctly?

Before launch, ensure:

• At least one Process-Admin is assigned

• Review, QA/QC, Finance, Customer Success, and PII Viewer roles are correctly mapped

• No users are missing required access

• Program-Manager role is not manually assigned

Incorrect permissions can block reviews or reporting. 

Are partner organizations added (if applicable)?

If your program involves partner organizations:

• Organizations are added at the program level

• Permissions are reviewed and approved

• Users are assigned under the correct organization

This prevents unauthorized access to applications or data. 

Testing & Final Checks FAQs

Has the program been tested end-to-end?

Before going live:

• Submit multiple test applications

• Verify eligibility logic and workflow movement

• Confirm notifications send correctly

• Review dashboards and reports

• Test applicant and staff experiences separately

Testing should always occur while the program is in TEST status. 

What status should my program be in before launch?

Your program should move through these stages:

1. Draft – Configuration

2. Test – Internal testing

3. Active – Public launch

Only switch to Active after completing the Pre-Launch Checklist. 

What happens if I skip the Pre-Launch Checklist?

Skipping the checklist may result in:

• Incomplete applications

• Broken workflows

• Missing notifications

• Incorrect reporting

• Increased applicant support requests

Completing the checklist helps protect both your team and your applicants from avoidable issues.