Review and launch
Read the ten Setup steps, clear anything that blocks launch, then launch; launch creates the rounds and sends no invitation.
Who can open this: Principal investigator, Steering committee (full access), Biostatistics, Coordinator
Who this is for
Review & launch is the last Setup screen. Its own line is "Verify the study configuration and manage launch status." It is the destination. It is not one of the ten steps that can be ready.
Anyone who can read Setup can open the page. The launch control is shown only to someone who can edit Setup, which is the Principal investigator. A launch from anyone else is refused with "You do not have permission to do that." Steering committee (full access), Coordinator, and Biostatistics can read the page. Coder, Adjudicator, and Steering confirmer do not get Setup.
Steps
The crumb is "Setup / Review & launch". The title is "Review & launch". While the study is still a draft, the card heading is "Not launched yet". After launch it is "Study launched", and the line under it is "This study is active."
The draft line is the count. When every counted step is ready it is "All 10 steps are ready." Otherwise it names how many of the 10 are not ready. The reason under the button is separate: it starts "Launch is unavailable until all 10 Setup steps are ready", then how many are not, then "Still to do:" and each step with its status in lowercase.
The ten steps are Identity, Method, Eligibility, Size & mix, Profile & integrity, Item bank, Rating & consensus, Rounds & feedback, Consent & comms, and Analysis plan. They sit in Study design, Panel design, Round design, and Governance. The status words, the same ones as the sidebar, are "Ready", "Needs attention", "Blocks launch", "Required later", and "Not started".
A step whose only issues are warnings counts toward the ten and still says "Needs attention". "Blocks launch", "Required later", and "Not started" do not count, and launch stays unavailable. The button then shows the reason, starting from "Launch is unavailable until all 10 Setup steps are ready".
Table: which status counts toward the ten. The same words are on the sidebar and on Review & launch.
| Status | Counts toward the ten |
|---|---|
| Ready | Yes |
| Needs attention | Yes. Launch stays available. |
| Blocks launch | No |
| Required later | No |
| Not started | No |
Study team sits beside the ten steps and is not one of them. When it blocks, the summary adds "Study team blocks launch." and the reason is "Launch is unavailable until Study team is ready." A Study team warning does not stop launch. Open Study team to clear a block.
"Consent contact does not match the study reply-to" is listed on its own as "Blocks launch", linked to the Contact section of the consent form. Fix it on Governance.
Ready to send is "Not one of the ten steps, so it never changes their count."
Table: the Ready to send checks. Before launch each one that is not done is "Warning", and none of them stops launch.
| Check | Before launch |
|---|---|
| Protocol label | Warning until it is set. Does not stop launch. |
| Send mode | Warning when sending is off, not fully configured, or pointed at a local test inbox. The test inbox does not block invitations. Does not stop launch. |
| Maintenance job | Warning when it is not scheduled or has not run. Does not stop launch. It holds the first invitation only on a production deployment. |
The three checks are "Protocol label", "Send mode", and "Maintenance job". A done check is "Ready". One that is open is "Warning". After launch, and until the first invitation, a check that would stop a real send is "Blocks first invitation". Before launch, none of them stops launch. The page also shows "Automatic send checks". That check does not stop launch and does not block the first invitation. The line says "None of these stops launch, but the first invitation waits for each one that would stop a real send." The refusal is "No invitation can be queued yet: {checks} is not ready. Review & launch, under Ready to send, says what to do." "Protocol label" links to "Open Study identity". "Send mode" and "Maintenance job" link to "Open Email & operations", and the note says "A workspace administrator sets this under Settings, Email & operations." A local test inbox does not block invitations. The maintenance job holds the first invitation only on a production deployment.
Messages that will not send. When every optional message has saved wording, the line is "Every optional message has saved wording, so each one is sent when its event happens." Otherwise: "Optional messages are sent only once this study saves their wording. Open one to use the default wording or write your own." Each gap is badged "Will not send", with "Open {name}". A round-open message that will not send says "{name} will not send: {reason}, so a panelist's first round link reaches them only with a reminder or when the team resends it."
Thresholds is a read-only table: "Thresholds: value, where each is set, whether it is enforced or only reported, and what it applies to." Change a number on the Setup step the row names. The inventory is Thresholds.
Launch this study, for the Principal investigator, on a study that is not a sample. The line is "Launching creates the rounds of your plan and locks the parts of Setup that cannot change once a study is running. No invitation is sent."
The list under "What launching locks" is the screen's list. The server list has one home, the governed study record. This guide does not copy either list.
The button is "Launch study". While Setup is still saving it says "Setup is still saving. Wait for “Saved to this study”, then launch." The confirmation is "Launch this study?", confirmed with "Launch": "The rounds are created from your saved plan and the locked parts of Setup stop being editable without a controlled amendment. This cannot be undone." When counted groups cannot meet the Round 1 group check at their targets, the dialog lists them and asks you to tick "I understand this group check cannot be met at these targets and choose to launch anyway. This acknowledgement is recorded." Without that tick the server says "Some counted groups cannot meet the Round 1 group check at their target. Review the current targets and explicitly acknowledge them before launch."
A launch the server rejects starts "Setup is not ready to launch." and names "Setup step N is not ready." A Study team error is prefixed "Study team: ". An empty plan is "The round plan has no rounds." A second launch is "This study has already launched."
Success is "Launched. 1 round was created and Round 1 is being prepared." or "Launched. 2 rounds were created and Round 1 is being prepared." The page then offers "Go to Overview" and, for someone who can open the panel, "Invite panelists". Inviting still waits on a published consent form and on Ready to send. See Invitations and Round 1 questionnaire.
What the app will not do
Review & launch does not count toward the ten. "n of 10 ready" counts steps 1 to 10 only.
A warnings-only step, labeled "Needs attention", does not keep Launch unavailable. "Blocks launch", "Required later", and "Not started" do.
Launch sends no invitation. It creates the rounds from the saved plan. What cannot change is named on the governed study record.
Ready to send does not change the count of ten and does not stop launch. It can refuse the first invitation.
Optional messages with no saved wording are not sent. The list says "Will not send".
Someone who cannot edit Setup cannot launch. The server answers "You do not have permission to do that."
Launch cannot be undone. "This study has already launched."
Related
- Study design
- Panel design
- Round design
- Governance
- Thresholds
- Study team
- Round 1 questionnaire
- Roles and access
Checked against the app on 2026-10-31.