Your plan and routine support

A development preview of upcoming tasks, received work, and requests for routine study help.

Development preview

This guide describes the newer plan and support workflow in development. Availability depends on the study and application rollout. Follow the instructions in your current app and consent materials.

One place for what happens next#

The plan brings together work needing attention, upcoming tasks, items waiting on someone else, and completed work. It uses existing questionnaire windows, confirmed visits, shipments, compensation, and released summaries. A bounded study keeps its own journey without acquiring unnecessary daily check-ins.

A local save is different from a server receipt. If a refresh fails, previously received details remain visible with a prompt to refresh the affected source.

Request routine help#

Where enabled, request help from the plan, a visit, or a shipment. Sending a request requires a connection. Receipt, team acknowledgment, responsibility, status, and the team’s response are separate steps. A closed request can be reopened if the issue remains unresolved.

A recorded replacement or appointment outcome describes work the site arranged. It does not automatically order a replacement kit or book an outside provider.

Know who is responding#

Requests enter the study team’s shared queue. Optional coverage details and response targets describe the team’s arrangements; they do not guarantee immediate monitoring or a response by a deadline. Staff email alerts depend on study setup, and an email being delivered is different from a person acknowledging your request.

Routine support is not urgent care

Use the health-concern route and contact guidance supplied by your study team for clinical concerns. For an emergency, contact local emergency services. Do not wait for a routine support request.

Read Symptoms and safety or visit Support for current contact options.