> ## Documentation Index
> Fetch the complete documentation index at: https://docs.carelane.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Request Orchestration

> AI-powered task automation and action management

Request orchestration uses AI to manage and automate task execution, tracking action status and coordinating complex workflows.

## What is Request Orchestration?

Request orchestration manages structured actions:

* Track action status
* Coordinate multi-step processes
* Automate routine operations
* Monitor completion

## Action Status

Actions in orchestrated workflows have statuses:

| Status                      | Code                      | Description                       |
| --------------------------- | ------------------------- | --------------------------------- |
| **In Progress**             | `in-progress`             | Action is being worked on         |
| **Complete**                | `complete`                | Action finished at site           |
| **Edited After Submission** | `edited-after-submission` | Modified after initial completion |
| **Verified**                | `verified-study-team`     | Reviewed by study team            |
| **Pending Queries**         | `pending-queries`         | Has open data queries             |

## How It Works

<Steps>
  <Step title="Action Created">
    An action is created as part of a workflow or request.
  </Step>

  <Step title="Assignment">
    Action is assigned to appropriate performer.
  </Step>

  <Step title="Execution">
    Performer completes the action.
  </Step>

  <Step title="Status Update">
    Status automatically updates based on completion.
  </Step>

  <Step title="Review">
    Actions may require review before finalization.
  </Step>
</Steps>

## Action Types

### Standard Actions

| Type              | Description           |
| ----------------- | --------------------- |
| **Questionnaire** | Data collection form  |
| **Document**      | File upload or review |
| **Signature**     | Electronic signature  |
| **Invitation**    | Member invitation     |

### Review-Required Actions

Some actions require additional review:

* Mark for approval/rejection
* Add review comments
* Track review status

## Action Review

### Review Status

| Status       | Meaning               |
| ------------ | --------------------- |
| **Approved** | Action accepted       |
| **Rejected** | Action needs revision |
| **Pending**  | Awaiting review       |

### Performing Reviews

<Steps>
  <Step title="Access Action">
    Navigate to the action requiring review.
  </Step>

  <Step title="Review Content">
    Examine the completed action.
  </Step>

  <Step title="Make Decision">
    Approve or reject the action.
  </Step>

  <Step title="Add Comments">
    Provide feedback if needed.
  </Step>
</Steps>

## Workflow Integration

Request orchestration integrates with:

### Site Onboarding

* Track onboarding task completion
* Coordinate multi-step setup
* Monitor site activation progress

### Participant Pathways

* Manage scheduled activities
* Track visit completion
* Handle conditional activities

## Automation Benefits

| Benefit            | Description                             |
| ------------------ | --------------------------------------- |
| **Consistency**    | Same process every time                 |
| **Tracking**       | Clear visibility into status            |
| **Efficiency**     | Reduced manual coordination             |
| **Accountability** | Clear assignment and completion records |

## Monitoring Orchestrated Tasks

### Dashboard View

Monitor orchestrated tasks:

* Actions by status
* Pending actions
* Overdue items
* Completion rates

### Notifications

Receive notifications for:

* New action assignments
* Status changes
* Review requests
* Overdue actions

## Configuration

### Enabling Orchestration

Orchestration features are configured at:

* Study level for participant workflows
* Organization level for operational processes

### Action Configuration

Configure actions with:

* Required vs. optional
* Review requirements
* Performer assignment
* Timing constraints

## Best Practices

<AccordionGroup>
  <Accordion title="Clear Actions">
    Define actions with clear instructions and expectations.
  </Accordion>

  <Accordion title="Appropriate Review">
    Require review only where it adds value.
  </Accordion>

  <Accordion title="Monitor Progress">
    Track action completion regularly.
  </Accordion>

  <Accordion title="Address Delays">
    Follow up on overdue or stalled actions promptly.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Workflows" icon="diagram-project" href="/data-collection/workflows">
    Operational workflows.
  </Card>

  <Card title="Participant Pathways" icon="route" href="/participants/participant-pathways">
    Participant activity management.
  </Card>
</CardGroup>