Application Onboarding Screen Guide

This guide explains the main parts of the Application Onboarding screen and how teams use it to move applications toward readiness and go-live.

**Suggested screenshot title:** Application Onboarding Overview

Screen sections

1. Application onboarding header

The header identifies the application and shows that you are viewing its onboarding workflow.

2. Current stage indicator

This section shows the application's current onboarding stage. It helps teams understand where the application is in the readiness process.

3. Stage progression

This area shows the onboarding stages, either as a sequence, checklist, or structured set of steps. It helps users understand what has been completed and what still needs attention.

4. Validation checks

Validation checks are used to confirm whether the application is ready to move forward. These may include support readiness, knowledge readiness, pilot readiness, and go-live readiness.

5. Workflow or state information

Some onboarding screens also show workflow states, approval signals, or readiness-related statuses that help explain current posture.

6. Related comments, activity, or attachments

Where supported, onboarding screens may include activity, comments, or attachments that capture decisions, blockers, and supporting information.

7. Go-live or readiness signals

Some versions of the page may include a go-live or readiness section to show whether the app is close to completion.

How to use this screen

A common onboarding workflow is:

1. review the current stage 2. check incomplete validation items 3. review activity and attachments for blockers 4. update supporting workflows as needed 5. progress the app toward pilot or go-live readiness

Best practice

Do not treat onboarding as only a checklist. Use readiness signals, comments, and validation to make better handoff and go-live decisions.