# Understanding the Study Design Specification

The Study Design Specification (SDS) is a PDF document you can generate in Studio that details the configuration of your study. It includes the definition of the study settings, events, surveys, and logic for a specific collection version.

The SDS provides an accurate record of the study build at the time of generation. This document is not intended to be used as a requirements document for User Acceptance Testing (UAT).


## Collection Version History

This section tracks the changes associated with the collection version.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Version</strong></td>
      <td>The major version (for example, 1.0) or the minor version if the collection is in a draft state.</td>
    </tr>
    <tr>
      <td><strong>Approval Date</strong></td>
      <td>The date the major version was approved. This field is left empty for versions still in a draft state.</td>
    </tr>
    <tr>
      <td><strong>Change History</strong></td>
      <td>A summary of the change reasons included since the version was created.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912955/">Working with Collections</a>

## Study Settings

This section lists global configurations and parameters for the study.


### Resources

This table lists the resource files configured for the study.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Resource Name</strong></td>
      <td>The resource file name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Language</strong></td>
      <td>The language assigned to the resource.</td>
    </tr>
    <tr>
      <td><strong>Display Label</strong></td>
      <td>The text label displayed to the user.</td>
    </tr>
    <tr>
      <td><strong>URL</strong></td>
      <td>A clickable link that directs to the resource file.</td>
    </tr>
    <tr>
      <td><strong>Available to Participants?</strong></td>
      <td>Indicates whether the resource is visible to participants. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912935/">Managing Resource Links</a>

### Data Changes


#### Survey Data Changes

These tables define whether users can modify data after submission. We display separate tables for ePRO, eClinRO, and Composite surveys.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Survey Name</strong></td>
      <td>The name and the display label of the survey.</td>
    </tr>
    <tr>
      <td><strong>Allowed?</strong></td>
      <td>Indicates whether data changes are permitted for the survey. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
    <tr>
      <td><strong>Submission Window</strong></td>
      <td>The configured window of time after the survey submission that data changes are allowed. Displayed as <strong>N Days</strong>, for example, 7 Days.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912967/">Managing Survey Data Change Permissions</a>

#### Transcriptions

This table defines whether users can transcribe survey data on behalf of a participant. We display separate tables for ePRO, eClinRO, and Composite surveys.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Survey Name</strong></td>
      <td>The name and the display label of the survey.</td>
    </tr>
    <tr>
      <td><strong>Allowed?</strong></td>
      <td>Indicates whether transcriptions are permitted for the survey. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912967/">Managing Survey Data Change Permissions</a>

#### Remove Survey

This table defines whether users can remove a completed survey that was collected in error from reports. 

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Survey Type</strong></td>
      <td>The category of survey. Displays one of the following options: <strong>ePRO</strong>, <strong>eClinRO</strong>, or <strong>Composite</strong>.</td>
    </tr>
    <tr>
      <td><strong>Allowed?</strong></td>
      <td>Indicates whether surveys of this type can be removed. Displays <strong>Yes or No</strong>.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912967/">Managing Survey Data Change Permissions</a>

#### Requires Site Signature

This table details the requirements for Principal Investigator (PI) reviews.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Data Type</strong></td>
      <td>The category of data. The following types are included on this table: <strong>Transcriptions</strong>, <strong>Source ePRO</strong>, <strong>Source eClinRO</strong>.</td>
    </tr>
    <tr>
      <td><strong>Requires PI Review?</strong></td>
      <td>Indicates whether a review is required. Displays one of the following options: <strong>Yes, Only Surveys with Data Changes</strong>; <strong>Yes, All Surveys</strong>; or <strong>No</strong>.</td>
    </tr>
  </tbody>
</table>

* **Signature Statement Type:** Indicates which type of statement is displayed when PIs review data. Displays **Default** or **Custom**.
* **Custom Statement:** If used, the Custom Statement is displayed only in the source language.

Related Topic: <a href="/en/lr/912972/">Managing Site Signatures</a>

### Participant ID Format

This table defines the structure of participant identifiers.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Format</strong></td>
      <td>The required character format for the ID. For example, [@@]-[##]-[###].</td>
    </tr>
    <tr>
      <td><strong>Example Value</strong></td>
      <td>A sample ID that matches the configured format.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918811/">Managing the Participant ID Format</a>

### In-Person Access

This table details the configuration for in-clinic participant access.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Enabled</strong></td>
      <td>Indicates whether the participants can complete surveys while in clinic. Displays <strong>Yes or No</strong>.</td>
    </tr>
    <tr>
      <td><strong>Access Type</strong></td>
      <td>The method used to access the device. Displays one of the following options: <strong>Streamlined</strong>, <strong>Password authenticated</strong>, or empty.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918790/">Managing In-Person Survey Access</a>

## Study Details

This section provides general study information and participant grouping structures.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Description</strong></td>
      <td>The description that was added for the study.</td>
    </tr>
    <tr>
      <td><strong>Image URL</strong></td>
      <td>A clickable link to the image that is displayed for the study in MyVeeva for Patients. Typically a company or study logo.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912955/">Working with Collections</a>

### Included Supported Languages

This table lists all languages active in the collection.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Language</strong></td>
      <td>The name of the language in English.</td>
    </tr>
    <tr>
      <td><strong>Patient</strong></td>
      <td>Indicates whether the language is supported for MyVeeva users. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
    <tr>
      <td><strong>Site</strong></td>
      <td>Indicates whether the language is supported for eCOA site users. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912940/">Managing Study Languages and Translations</a>

### Groups

This table outlines the group types and specific groups defined in the study.


<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Group Type</strong></td>
      <td>The configured type used for the group.</td>
    </tr>
    <tr>
      <td><strong>Groups</strong></td>
      <td>A list of the specific groups that have been configured within this row’s group type.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/914851/">Managing Groups</a>

## Events

This section lists all events configured in the study sequence.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Event Name</strong></td>
      <td>The event name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Event Label</strong></td>
      <td>The name of the event displayed to users.</td>
    </tr>
    <tr>
      <td><strong>Type</strong></td>
      <td>The type of this event, such as <strong>Scheduled Event</strong>, <strong>Unscheduled Event</strong>, or <strong>Criteria Check</strong>.</td>
    </tr>
    <tr>
      <td><strong>Sequence</strong></td>
      <td>The sequence number of the event.</td>
    </tr>
    <tr>
      <td><strong>Available When</strong></td>
      <td>The logic that determines when the event becomes available. Displays one of the following options: <strong>Always</strong>, <strong>When Criteria Check is Passed</strong>, or <strong>After Previous Event</strong>.</td>
    </tr>
    <tr>
      <td><strong>Populated By</strong></td>
      <td>The source that triggers the event date. Displays one of the following options: <strong>Sites</strong>, <strong>Rule</strong>, or <strong>API</strong>.</td>
    </tr>
    <tr>
      <td><strong>Protocol Expected Date</strong></td>
      <td>Details the following setting information if an anchor event is used:
        <ul>
          <li><strong>Anchor Event:</strong> The event label of the anchored event.</li>
          <li><strong>Offset Days:</strong> The number of days after the Anchor Event that the event will occur.</li>
          <li><strong>Default Event Time:</strong> Not shown when an event is populated by a rule.</li>
          <li><strong>Automatic Datetime Population:</strong> Not shown when an event is populated by a rule.</li>
          <li><strong>Visit Window:</strong> The preferred timeframe that was configured for the event. Displayed as the number of days before and after the default event time.</li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><strong>Groups</strong></td>
      <td>A list of groups the event applies to. Includes the group type and group name. If the event applies to all groups, displays <strong>All Groups</strong>.</td>
    </tr>
    <tr>
      <td><strong>Event-Triggered Group Assignment</strong></td>
      <td>Indicates whether the group is event-triggered. Displays <strong>Yes</strong> or <strong>No</strong>.
        <p>On the next line, lists any new group types that need to be assigned during this event.</p>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912959/">Managing Events</a>

## Schedule Visualization

Includes a link to the study schedule preview.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If a collection in draft state is updated after you generate the SDS, the study schedule preview URL may have different information than the contents on the previously generated SDS. The URL is dynamically updated and unique for each minor version.</p>
    </div>
  </div>
</div>



Related Topic: <a href="/en/lr/918795/">Previewing the Study Schedule and Surveys</a>

## Surveys

This section details every survey in the collection. It begins with an overview table that provides a high-level summary of all surveys, and is followed by detailed breakdowns for each survey.


<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Survey Name</strong></td>
      <td>The name of the survey that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Display Label</strong></td>
      <td>The name of the survey displayed to users.</td>
    </tr>
    <tr>
      <td><strong>Type</strong></td>
      <td>The type of survey. Displays one of the following options: <strong>ePRO</strong>, <strong>eClinRO</strong>, <strong>Composite</strong>.</td>
    </tr>
    <tr>
      <td><strong>Respondents</strong></td>
      <td>The user type who completes the survey. For composite surveys, multiple user types are listed.</td>
    </tr>
    <tr>
      <td><strong>Sequence</strong></td>
      <td>The sequence number of the survey.</td>
    </tr>
    <tr>
      <td><strong>Restricted Data</strong></td>
      <td>Indicates whether the survey includes restricted data. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
    <tr>
      <td><strong>Source</strong></td>
      <td>The origin of the survey. Displays one of the following options: <strong>Study Specific</strong>, <strong>Library</strong>, <strong>Veeva Library</strong>.</td>
    </tr>
  </tbody>
</table>

### [Survey Display Label] 

The following survey overview information is displayed:

* **Preview:** A clickable link that takes you to the survey preview.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If a collection in draft state is updated after you generate the SDS, this URL will become out of sync on the previously generated SDS. The URL is dynamically updated and unique for each minor version.</p>
    </div>
  </div>
</div>

 

* **Domain:** The domain the survey is configured in. Displays one of the following options: **QS**,  **FT**, **RS**, or **MK**.
* **As Needed Display Label:** The As-Needed Display label if the survey has an As-Needed schedule associated with it.
* **Respondent:** The type of respondent who is responsible for answering the survey. For a composite survey, the respondents are included in a comma separated list.
* **Reviewed:** Indicates whether the survey has been reviewed. Displays one of the following options: **Yes**, **No**, or **N/A**
* **Licensed:** Indicates whether the survey has been licensed. Displays one of the following options: **Yes**, **No**, or **N/A**
* **Respondent Burden:** Indicates the anticipated difficulty level of the survey for the respondent. Displays one of the following options: **Very Easy**, **Easy**, **Moderate**, **Hard**, or **Very Hard**.

Related Topic: <a href="/en/lr/912957/">Configuring Surveys</a>

#### Survey-Level Parameters

* **Survey Type:** Indicates the type of survey. Displays one of the following options: **ePRO**, **eClinRO**, **Composite**
* **Survey Sub Type:** Indicates the survey subtype. Displays one of the following options: **Standard**, **Training**, **Diary**
* **Language Override:** Indicates whether the default language settings should be overridden to allow a site to view the survey in a participant language. Displays **Site** or **Patient**.
* **Label:** The participant-viewable label of the survey. 
* **Description:** The participant-viewable description of the survey. 
* **License Text:** The license and copyright information.
* **License Image:** A clickable link to the license image.
* **License Image Description:** The description of the license image that can be read by screen readers.
* **Review Prompt:** Indicates whether a prompt is displayed at the end of a survey instructing the respondent to view their responses before submitting. Displays **true** or **false**.
* **Additional Details:** Any additional details or licensing information for the survey.
* **Overt Navigation:** Indicates whether navigation buttons are included as part of the survey experience. Displays **true** or **false**.

Related Topic: The <a href="/en/lr/912970/#universal-survey-parameters">Universal Survey Parameters</a> section of the Understanding Survey Parameters page

##### Diary Settings

The following information is displayed when the survey has a subtype of Diary:

* **Diary Label:** The label that is displayed with the diary item on the To Do page.
* **Action Label:** The additional text that is displayed with the diary item on the To Do page.
* **Description:** The diary description that is displayed on the diary page.
* **Show Responses:** Indicates whether a participant can open and view responses to diaries they already submitted. Displays **true** or **false**.
* **Summary Blocks:** The block in this survey that is used to summarize the instance when it is referenced in other questions or previews to help users identify which survey it is.

Related Topic: The <a href="/en/lr/912970/#universal-survey-parameters">Universal Survey Parameters</a> section of the Understanding Survey Parameters page

#### Questions

The following information is displayed for multi-part surveys:

* **Part Name:** The survey part name that is referenced throughout Studio.
* **Part Label:** The label of the part that is viewable by MyVeeva Users.
* **Respondent:** The type of respondent who is responsible for answering this part of the survey.
* **Survey Type:** The type of survey for this survey part. Displays **ePRO** or **eClinRO**

Related Topic: The <a href="/en/lr/912957/#configuring-composite-mp-surveys">Configuring Composite and Multi-Part Surveys</a> section of the Understanding Survey Parameters page

##### All Section Parameters

The following information is displayed for all sections:

* **Section Name:** The section name that is referenced throughout Studio.
* **Type:** Indicates the section type. Displays one of the following options: **serial**, **table**, **repeat**
* **Condition:** The condition that causes the section to be displayed for the respondent when it evaluates to true.
* **Heading:** The participant-viewable heading that is displayed at the top of the section.
* **Sticky Heading:** Indicates whether the section heading will stay visible when the users scroll down the survey page. Displays **true** or **false**.

Related Topic: The <a href="/en/lr/912970/#universal-section-parameters">Universal Section Parameters</a> section of the Understanding Survey Parameters page

##### Repeat Settings

The following information is displayed for repeat section types:

* **Question Number:** The number that is displayed before the heading.
* **Heading:** The text that provides instructions for the set of repeating questions.
* **Summary Block:** The block in this section that is used to summarize the set of repeating questions when the user answers them.
* **Minimum Entry:** The minimum number of times a respondent must answer the set of repeating questions (entries).
* **Maximum Entry:** The maximum number of times a respondent can answer the set of repeating questions (entries).

Related Topic: The <a href="/en/lr/912970/#universal-section-parameters">Universal Section Parameters</a> section of the Understanding Survey Parameters page

##### Table Columns

The following information is displayed for table section types (one pair per table column):

* **Heading:** The participant-viewable heading that is displayed at the top of the table.
* **Width:** The width of the column. The sum of the widths across all columns has to be 1.

Related Topic: The <a href="/en/lr/912970/#universal-section-parameters">Universal Section Parameters</a> section of the Understanding Survey Parameters page

##### Question Block Information

This table details the configuration of every question block in a survey.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Question Number</strong></td>
      <td>The number assigned to the question.</td>
    </tr>
    <tr>
      <td><strong>Question Name</strong></td>
      <td>The question name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Question Type</strong></td>
      <td>The type of question. Displays one of the following options: <strong>Text</strong>, <strong>Single Choice</strong>, <strong>Multiple Choice</strong>, <strong>Number Scale</strong>, <strong>Visual Scale</strong>, <strong>Number Entry</strong>, <strong>Text Entry</strong>, <strong>Date Entry</strong>, <strong>Time Entry</strong>, <strong>Datetime Entry</strong>, <strong>Interactive Image: Pain Detect</strong>, <strong>Interactive Image: Joint Count</strong>, <strong>Link</strong>, <strong>Site Media</strong>.</td>
    </tr>
    <tr>
      <td><strong>Table Position</strong></td>
      <td>The position of the question if it is used in a table section. This column is hidden if no table sections are included in the survey or survey part.</td>
    </tr>
    <tr>
      <td><strong>Question Text</strong></td>
      <td>The heading or prompt text displayed to the respondent.</td>
    </tr>
    <tr>
      <td><strong>Response Configuration</strong></td>
      <td>Detailed settings for the answer format, such as codes, scores, and ranges. See the Related Topics below the table for more information on what responses can be configured for each question type.</td>
    </tr>
    <tr>
      <td><strong>Optional Answers</strong></td>
      <td>Lists choices like "Don't Know" and their associated scores.</td>
    </tr>
    <tr>
      <td><strong>Condition</strong></td>
      <td>The condition that has to evaluate to true before the question is displayed. This column is hidden if no conditions are included in the survey or survey part.</td>
    </tr>
    <tr>
      <td><strong>Validation</strong></td>
      <td>Checks applied to the answer to ensure validity. This column is hidden if no validations are included in the survey or survey part.</td>
    </tr>
  </tbody>
</table>

Related Topics:
* <a href="/en/lr/912970/#configuring-a-single-choice-vrs-question">Configuring a Single Choice Question Type</a>
* <a href="/en/lr/912970/#configuring-a-multiple-choice-question">Configuring a Multiple Choice Question Type</a>
* <a href="/en/lr/912970/#configuring-a-nrs-question">Configuring a Number Scale Question Type</a>
* <a href="/en/lr/912970/#configuring-vas-scale-question">Configuring a Visual Scale Question Type</a>
* <a href="/en/lr/912970/#configuring-number-entry-question">Configuring a Number Entry Question Type</a>
* <a href="/en/lr/912970/#configuring-text-entry-question">Configuring a Text Entry Question Type</a>
* <a href="/en/lr/912970/#configuring-date-question">Configuring a Date Entry Question Type</a>
* <a href="/en/lr/912970/#configuring-time-question">Configuring a Time Entry Question Type</a>
* <a href="/en/lr/912970/#configuring-datetime-question">Configuring a Datetime Entry Question Type</a>
* <a href="/en/lr/912970/#configuring-interactive-images">Configuring an Interactive Image Question Type</a>
* <a href="/en/lr/912970/#configuring-attachments">Configuring an Attachment Upload Question Type</a>
* <a href="/en/lr/912970/#linkedsurvey">Configuring a Linked Survey Question Type</a>

#### Export Mappings

This table shows survey data that has been mapped for export. A row is populated for each block in the survey that has at least one value mapped.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Question Name</strong></td>
      <td>Displays the <strong>Original</strong> name used throughout Studio and the <strong>Mapped</strong> export name.</td>
    </tr>
    <tr>
      <td><strong>Question Text (Heading)</strong></td>
      <td>Displays the <strong>Original</strong> question text and the <strong>Mapped</strong> export text.</td>
    </tr>
    <tr>
      <td><strong>Answer Name</strong></td>
      <td>Displays the <strong>Original</strong> answer name used throughout Studio and the <strong>Mapped</strong> export name.</td>
    </tr>
    <tr>
      <td><strong>Answer Text</strong></td>
      <td>Displays the <strong>Original</strong> answer text and the <strong>Mapped</strong> export text.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/911840/">Configuring Export Mapping</a>

#### Conditions

This table lists the logical conditions configured for the survey.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Condition Name</strong></td>
      <td>The condition name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Type</strong></td>
      <td>The type of condition. Displays <strong>Single</strong> or <strong>Compound</strong>.</td>
    </tr>
    <tr>
      <td><strong>Condition</strong></td>
      <td>The information used to build the logic statement. For example:
        <ul>
          <li><strong>Block:</strong> Q1</li>
          <li><strong>Operation:</strong> ==</li>
          <li><strong>Answer Type:</strong> Number</li>
          <li><strong>Answer number:</strong> 20</li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topics: <a href="/en/lr/912958/">Configuring Conditions</a>

#### Validations

This table lists the cross-question validation functions used in the survey.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Validation Name</strong></td>
      <td>The validation name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Function</strong></td>
      <td>The formula used to validate the answer.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912964/">Configuring Survey Cross-Question Validations</a>

#### Scores

This table details any scoring logic applied to the survey.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Score Name</strong></td>
      <td>The score name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Label</strong></td>
      <td>The participant-viewable label for the score.</td>
    </tr>
    <tr>
      <td><strong>Display</strong></td>
      <td>Indicates whether the score is displayed to the respondent. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
    <tr>
      <td><strong>Function</strong></td>
      <td>The formula used to calculate the score.</td>
    </tr>
    <tr>
      <td><strong>Result</strong></td>
      <td>The condition and output value or text based on the result.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/916459/">Configuring Scores</a>

#### Schedules

This table outlines when the survey is available to respondents.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Schedule Name</strong></td>
      <td>The schedule name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Description</strong></td>
      <td>Text describing the purpose of the schedule.</td>
    </tr>
    <tr>
      <td><strong>Groups</strong></td>
      <td>The participant groups this schedule applies to.</td>
    </tr>
    <tr>
      <td><strong>Location</strong></td>
      <td>The location where the survey is taken. Displays <strong>Home</strong> or <strong>Clinic</strong>.</td>
    </tr>
    <tr>
      <td><strong>Events</strong></td>
      <td>The <strong>Start Events</strong> and <strong>End Events</strong> that trigger the schedule.</td>
    </tr>
    <tr>
      <td><strong>Configuration</strong></td>
      <td>The following configuration details:
        <ul>
          <li><strong>Timepoint Label:</strong> The label used to differentiate between survey submissions for surveys that are included in multiple schedules.</li>
          <li><strong>Export Details:</strong> The additional schedule details that are included in adherence and survey data reports.</li>
          <li><strong>Delay:</strong> The amount of time that the schedule is offset from the Start Event by.</li>
          <li><strong>Available:</strong> The availability type of the schedule. Displays one of the following options: <strong>For</strong>, <strong>Between</strong>, <strong>As Needed</strong>, <strong>Open-Ended</strong>. Also displays availability time or duration if configured.</li>
          <li><strong>Partial Window:</strong> For As Needed and Between Schedules, defines whether or not the schedule will start when within a partial window. Displays <strong>true</strong> or <strong>false</strong>.</li>
          <li><strong>Recurrence:</strong> The interval, frequency, and number of times the schedule is set to recur before it ends. For example, a survey that should be available for a MyVeeva user once a week for six weeks looks like this: INTERVAL=1;FREQ=WEEKLY;COUNT=6</li>
          <li><strong>Start Multiple:</strong> Indicates whether respondents can have multiple instances of a diary answer in progress at one time.</li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912960/">Configuring Schedules and Notifications</a>

#### Notifications

This table lists the alerts sent based on the survey schedule.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Schedule Name</strong></td>
      <td>The schedule name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Notification Name</strong></td>
      <td>The notification name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Template</strong></td>
      <td>The message template used.</td>
    </tr>
    <tr>
      <td><strong>Type</strong></td>
      <td>The notification type. Displays one of the following options: <strong>Available</strong>, <strong>Due</strong>, <strong>Complete</strong>, <strong>Missed</strong>.</td>
    </tr>
    <tr>
      <td><strong>Recurrence</strong></td>
      <td>The following information that indicates how often the notification will repeat before the schedule ends:
        <ul>
          <li><strong>Interval:</strong> The number associated with the frequency.</li>
          <li><strong>Frequency:</strong> The unit of time associated with the interval. Displays <strong>Daily</strong>, <strong>Weekly</strong>, or <strong>Monthly</strong>.</li>
          <li><strong>Count:</strong> The number of times the notification should be sent.</li>
          <li><strong>Default Delivery Time:</strong> The time of day for the participant when the recurring notification should be delivered, in 24-hr format.</li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><strong>Additional Configuration</strong></td>
      <td>The following information is included:
        <ul>
          <li><strong>Survey Part:</strong> For composite surveys, the survey part the notification is sent for.</li>
          <li><strong>Offset:</strong> How far before the due date and time the notification should be sent.</li>
          <li><strong>Number Missed:</strong> For notifications with a type of missed, the number of surveys that must be missed before the notification is sent.</li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/912960/">Configuring Schedules and Notifications</a>

## Rules

This section details the automation rules configured for the study. The document displays expressions with line breaks to match the view in the Studio editor.


### Survey-Based Notification Rules

These rules allow you to configure notifications to be sent when specific conditions are met.

#### [Rule Name]

These rules trigger notifications based on survey responses. The section includes a **Variable Definitions** table and a **Notifications** table.

* **Description:** The description of what the rule is for. 
* **Survey Reference:** The reference for the survey that triggers the rule evaluation.

##### Variable Definitions Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Variable Name</strong></td>
      <td>The name of the variable used in the rule expression.</td>
    </tr>
    <tr>
      <td><strong>Definition</strong></td>
      <td>The source data defining the variable.</td>
    </tr>
  </tbody>
</table>

* **Preconditions:** The preconditions that must be met before the system will evaluate the rule expression.
* **Expression:** The definitions of how the data in a rule should be evaluated. When an expression evaluates to True, the rule evaluation is triggered.

##### Notifications Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Notification Name</strong></td>
      <td>The notification name that is referenced throughout Studio for this rule-based notification.</td>
    </tr>
    <tr>
      <td><strong>Recipients</strong></td>
      <td>The roles or email addresses that receive the message.</td>
    </tr>
    <tr>
      <td><strong>Title</strong></td>
      <td>The subject line of the notification.</td>
    </tr>
    <tr>
      <td><strong>Body</strong></td>
      <td>The body text of the message.</td>
    </tr>
    <tr>
      <td><strong>Restricted Data</strong></td>
      <td>Indicates whether the notification contains restricted data. Displays <strong>Yes</strong> or <strong>No</strong>.</td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918793/">Creating a Survey-Based Notification Rule Template</a>

### Criteria Check Rules

These rules evaluate participant data against defined criteria.

#### [Criterial Check Rule Name]

* **Description:** The description of what the rule is for. 
* **Criteria Check Event:** The name of the event that triggers the check.
* **Restricted Data:** Indicates whether restricted data is included in the check. Displays **Yes** or **No**.

##### Variable Definitions Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Variable Name</strong></td>
      <td>The name of the variable used in the rule expression.</td>
    </tr>
    <tr>
      <td><strong>Definition</strong></td>
      <td>The source data defining the variable.</td>
    </tr>
  </tbody>
</table>

* **Preconditions:** The preconditions that must be met before the criteria check can be run.
* **Missing Preconditions Message:** The message the system displays when the preconditions are not met.


##### Actions

* **Section:** The name of the criteria section, if applicable
* **Hide from Site Users:** Indicates whether the section is hidden from site users. Displays **Yes** or **No**.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Criteria Configuration</strong></td>
      <td>Displays the following information:
        <ul>
          <li><strong>Criteria Name:</strong> The name of the criteria that is used throughout Studio.</li>
          <li><strong>Hide from Site Users:</strong> Indicates whether the criteria is hidden from site users. Displays <strong>Yes</strong> or <strong>No</strong>.</li>
          <li><strong>Display Label:</strong> The user-understandable description of what the topic the criteria evaluation is answering.</li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><strong>Expression</strong></td>
      <td>The logic used to evaluate the criteria.</td>
    </tr>
  </tbody>
</table>

##### Conditional Actions

* **Action Expression:** Another expression that is run after the criteria check.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Action</strong></td>
      <td>The action that is taken when a conditional action expression evaluates to True. Displays one of the following options: <strong>Make Events Available</strong>, <strong>Trigger FTP Export</strong>, or <strong>API Call</strong>.</td>
    </tr>
    <tr>
      <td><strong>Action Details</strong></td>
      <td>
        <ul>
          <li><strong>Make Events Available:</strong> A list of events that become available.</li>
          <li><strong>Trigger FTP Export:</strong> The names of the export jobs this rule is connected to.</li>
          <li><strong>API Call:</strong> The following information is included:
            <ul>
              <li><strong>Call Name:</strong> The API Call Name</li>
              <li><strong>Credentials:</strong> The connected credential label</li>
              <li><strong>Field Mapping:</strong> The .JSON mapping information.</li>
              <li><strong>Call Mapping:</strong> The API call mapping details below.</li>
              <li><strong>Event Group Name:</strong> The event group name.</li>
              <li><strong>Event Name:</strong> The event name.</li>
              <li><strong>Form Name:</strong> The form name.</li>
              <li><strong>Study Name (if populated):</strong> The study name.</li>
              <li><strong>UAT Study Name (if populated):</strong> The related UAT study name.</li>
            </ul>
          </li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918792/">Creating a Criterial Check Rule Template</a>

### Populate Event Rules

These rules automatically set the date and time for an event.

##### Populate Event Rules Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Rule Name</strong></td>
      <td>The rule name that is referenced throughout Studio.</td>
    </tr>
    <tr>
      <td><strong>Description</strong></td>
      <td>Text describing the rule.</td>
    </tr>
    <tr>
      <td><strong>Variable Definitions</strong></td>
      <td>Includes the following information:
        <ul>
          <li><strong>Variable Name:</strong> The name of the variable used in the rule expression.</li>
          <li><strong>Variable Definition:</strong> The source data defining the variable.</li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><strong>Survey Reference</strong></td>
      <td>The survey that triggers the rule.</td>
    </tr>
    <tr>
      <td><strong>Actions</strong></td>
      <td>Includes the following information:
        <ul>
          <li><strong>Selected Event:</strong> The event that is selected.</li>
          <li><strong>Populate With:</strong> What time information the event is populated with. Displays one of the following options: <strong>Datetime</strong>, <strong>Date and Time</strong>, or <strong>Date</strong>.</li>
          <li>Depending on the populate option, the related following information is included:
            <ul>
              <li>Datetime
                <ul>
                  <li><strong>Datetime Reference:</strong> The datetime reference that the event is populated based on.</li>
                  <li><strong>Override Time:</strong> Included if rule is configured to override the time provided with survey data.</li>
                </ul>
              </li>
              <li>Date and Time
                <ul>
                  <li><strong>Date Reference:</strong> The date the event is populated based on, and the time in 24-hr format.</li>
                  <li><strong>Time Reference:</strong> The time reference the event is populated based on.</li>
                </ul>
              </li>
              <li>Date
                <ul>
                  <li><strong>Date Reference:</strong> The date the event is populated based on.</li>
                  <li><strong>Time:</strong> The time in 24-hour format.</li>
                </ul>
              </li>
            </ul>
          </li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918796/">Creating a Populate Events Rule Template</a>

#### [Rule Name]

**Description:** The description of what the rule is for.

**Survey Reference:** The survey that triggers the rule.

##### Variable Definitions Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Variable Name</strong></td>
      <td>The name of the variable used in the rule expression.</td>
    </tr>
    <tr>
      <td><strong>Definition</strong></td>
      <td>The source data defining the variable.</td>
    </tr>
  </tbody>
</table>

* **Preconditions:** The preconditions that must be met before system will evaluate the rule expression.
* **Expression:** The definitions of how the data in a rule should be evaluated. When an expression evaluates to **True**, the rule evaluation is triggered.

##### Actions Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Start With</strong></td>
      <td>The trigger condition. Displays one of the following options: <strong>Survey Completion Datetime</strong>, <strong>Question Answer</strong>, <strong>Start Event Datetime</strong>.</td>
    </tr>
    <tr>
      <td><strong>Populate With</strong></td>
      <td>
        <ul>
          <li>If it starts with a Question Answer, includes what time information the event is populated with. Displays one of the following options: <strong>Datetime</strong>, <strong>Date and Time</strong>, or <strong>Date</strong>.</li>
          <li>Depending on the populate option, the related following information is included:
            <ul>
              <li>Datetime
                <ul>
                  <li><strong>Datetime Reference:</strong> The datetime reference that the event is populated based on.</li>
                  <li><strong>Override Time:</strong> Included if rule is configured to override the time provided with survey data.</li>
                </ul>
              </li>
              <li>Date and Time
                <ul>
                  <li><strong>Date Reference:</strong> The date the event is populated based on, and the time in 24-hr format.</li>
                  <li><strong>Time Reference:</strong> The time reference the event is populated based on.</li>
                </ul>
              </li>
              <li>Date
                <ul>
                  <li><strong>Date Reference:</strong> The date the event is populated based on.</li>
                  <li><strong>Time:</strong> The time in 24-hour format.</li>
                </ul>
              </li>
            </ul>
          </li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

Related Topic: <a href="/en/lr/918794/">Creating a Schedule Trigger Rule Template</a>

### Send Survey Data Rules

These rules trigger the API to send survey data to another system.

#### [Rule Name]

**Description:** The description of what the rule is for.

**Survey Reference:** The survey that triggers the rule.

##### Variable Definitions Table

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Variable Name</strong></td>
      <td>The name of the variable used in the rule expression.</td>
    </tr>
    <tr>
      <td><strong>Definition</strong></td>
      <td>The source data defining the variable.</td>
    </tr>
  </tbody>
</table>


* **Preconditions:** The preconditions that must be met before the system will evaluate the rule expression.
* **Expression:** The definitions of how the data in a rule should be evaluated. When an expression evaluates to True, the rule evaluation is triggered.


##### Actions

**Send Missed Surveys:** Indicates whether missed surveys should also be sent. Displays **Yes** or **No**.

<table>
  <thead>
    <tr>
      <th>Column</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Action</strong></td>
      <td>The type of action that is taken when the expression evaluates to True. Displays <strong>API Call</strong>.</td>
    </tr>
    <tr>
      <td><strong>Action Details</strong></td>
      <td>The following information is included:
        <ul>
          <li><strong>Call Name:</strong> The API Call Name</li>
          <li><strong>Credentials:</strong> The connected credential label</li>
          <li><strong>Field Mapping:</strong> The .JSON mapping information.</li>
          <li><strong>Call Mapping:</strong> The API call mapping details below.</li>
          <li><strong>Event Group Name:</strong> The event group name.</li>
          <li><strong>Event Name:</strong> The event name.</li>
          <li><strong>Form Name:</strong> The form name.</li>
          <li><strong>Study Name (if Populated):</strong> The study name.</li>
          <li><strong>UAT Study Name (if Populated):</strong> The related UAT study name.</li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

  Related Topic: <a href="/en/lr/918799/#anchor">Creating a Send Survey Rule Template</a>