---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Create a health and safety requirement

# Create a health and safety requirement {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 min. de leitura

Create requirements to track when employees are ready to return to the workplace or visit a site. You can also create requirements that visitors must complete before entering the workplace.

## Antes de Iniciar

Role required: sn_imt_core.admin

## Por Que e Quando Desempenhar Esta Tarefa

Use health and safety requirements to define the requirements that employees must fulfill before they can return to the workplace, or that visitors must fulfill before entering the workplace. Create separate requirements for employees and visitors. A requirement must apply to either employees or visitors, not both. Employee Readiness Core provides some [pre-built
requirements](https://www.servicenow.com/docs/ufrNjoSZiaGcNyi_jJTgFg "Employee Readiness Core provides pre-built requirements."). However, you can create additional requirements using data from any of the Safe Workplace suite Safe Workplace or Emergency Response Management apps.

Health and safety
requirements are built with [Flow Designer](https://www.servicenow.com/docs/access?context=flow-designer&version=australia&pubname=australia-application-development&ft:locale=en-US). Before creating a requirement, make
sure that you're familiar with the basics of ServiceNow®
Workflow Studio.

The following steps show how to create a
requirement using the pre-built Employee Health Verification Requirement as an
example.

## Procedimento

1. In Workflow Studio, create an action to check the requirement status for an employee or visitor.
   1. Create an action.
   2. Save the action in the Employee Readiness Core application.
   3. In the Inputs section of the Action Outline, create an input for the type of record that you will use to check if the employee or visitor has fulfilled the requirement.  
      For example, to fulfill the Employee Health Verification Requirement,
      employees must have a health verification record in the Employee
      Health Verification table
      \[sn_imt_monitoring_health_verification\].
      {#create-readiness-requirement__table_up4_byt_zlb__entry__4}

      | Label | Name | Type | Mandatory |
      |-|-|-|-|
      | Employee Health Verification | health_verification | Reference.Employee Health Verification \[sn_imt_monitoring_health_verification\] | Yes |
      [Tabela 1. Inputs]

      {#create-readiness-requirement__table_up4_byt_zlb}
   4. Add a Script Step to the Action Outline.
   5. In the Required Runtime field, select Instance.
   6. Create an input variable using the input that you created for the action as the value.  
      This enables you to use the input for the action in a script.
      {#create-readiness-requirement__table_yyf_ld5_zlb__entry__2}

      | Name | Value |
      |-|-|
      | health_verification | Employee Health Verification input that you created in the Inputs section. |
      [Tabela 2. Input Variables]

      {#create-readiness-requirement__table_yyf_ld5_zlb}
   7. In the Script field, add a script to define the conditions when an employee's or visitor's requirement status is `cleared` or `not_cleared`.  
      For the Employee Health Verification Requirement, the requirement is
      `cleared` for an employee if their health
      verification response is <kbd class="ph userinput">yes</kbd>, and
      `not_cleared` for any other response.

          (function execute(inputs, outputs) {
          	outputs.requirement_status = inputs.health_verification.response == 'yes'
              	? 'cleared'
              	: 'not_cleared';
          })(inputs, outputs);

   8. Create an output variable for the requirement status.  
      This defines the <var class="keyword varname">requirement_status</var> variable that
      you used in the script.
      {#create-readiness-requirement__table_lxm_325_zlb__entry__5}

      | Label | Name | Type | Mandatory | Choice (Advanced options) |
      |-|-|-|-|-|
      | requirement_status | requirement_status | Choice | Yes | Dropdown with --None-- |
      [Tabela 3. Output Variables]

      {#create-readiness-requirement__table_lxm_325_zlb}
   9. In the Outputs section of the Action Outline, create an output for the requirement status.  
      Creating this output enables you to use the
      <var class="keyword varname">requirement_status</var> output variable from the
      script as an output returned by the action.
      {#create-readiness-requirement__table_n45_pc5_zlb__entry__5}

      | Label | Name | Type | Mandatory | Choice (Advanced options) |
      |-|-|-|-|-|
      | Requirement status | requirement_status | Choice | No | Dropdown with --None-- |
      [Tabela 4. Output Variables]

      {#create-readiness-requirement__table_n45_pc5_zlb}
   10. Assign the <var class="keyword varname">requirement_status</var> value to the output.  
       {#create-readiness-requirement__table_n2f_wc5_zlb__entry__2}

       | Label | Value |
       |-|-|
       | Requirement Status | <var class="keyword varname">requirement_status</var> output variable from the script step. |
       [Tabela 5. Output Variables]

       {#create-readiness-requirement__table_n2f_wc5_zlb}

       The action returns the value of the
       <var class="keyword varname">requirement_status</var> for the employee or visitor
       (`cleared` or `not_cleared`) as an
       output.
   11. Click Publish.
   {#create-readiness-requirement__substeps_lqn_mwt_zlb}
2. Create a health and safety requirement.
   1. Navigate to Employee Health and Safety StatusHealth and Safety Requirements.
   2. Click New.
   3. On the form, fill in the fields.  
      The Include previous applicable records section defines a set of
      records that have already been created but should still trigger the
      requirement flow. Including previous records ensures that employees
      or visitors who
      complete the requirement before it is activated have their
      requirement status set to Cleared.
      {#create-readiness-requirement__table_wxk_x2n_2mb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Unique name for the requirement. For example, <kbd class="ph userinput">Employee Health Verification Requirement</kbd>. |
      | Requirement for | Who the requirement applies to. The options are Employee and Visitor. A requirement must apply to either employees or visitors, not both. For example, the Employee Health Verification requirement only applies to employees. |
      | Requirement flow | Leave this field empty. You will return to the requirement record and fill in this field after you create the flow. |
      | Active | This field is read-only. Once you update all fields for the requirement, you can use the Activate button to activate the requirement. |
      | Default status | The default status is assigned to health and safety users who don't have any activity towards completing the requirement. The options are Cleared and Not Cleared. For example, employees who don't have a health verification record are assigned a default status of Not Cleared for the Employee Health Verification Requirement. |
      | Use duration | Option to set a time limit that the requirement status is valid for. |
      | Valid for | Time limit that the requirement status is valid for. For example, the Employee Health Verification Requirement status is valid for seven days. Employees must resubmit their health verification weekly to continue fulfilling the requirement. This field appears only when the Use duration field is selected. |
      | Actionable | Option to add a link for employees to complete the requirement on the Health and Safety Status page. |
      | Action name | The name of the action for the employee to complete the requirement. For example, Submit self-report. This name is shown on the Health and Safety Status page. This field appears only when the Actionable field is selected. |
      | Action URL | The URL of the Service Catalog item that employees use to complete the requirement. For example, the Employee Health Verification Requirement is completed by submitting the Health Verification form, which has the URL <kbd class="ph userinput">?id=sc_cat_item&amp;sys_id=9c578864ed111010fa9b395e35885545</kbd>. This field appears only when the Actionable field is selected. |
      | Action visibility | Sets when the link to complete the requirement is displayed on the Health and Safety Status page. Select Visible when false to only show the link when the employee hasn't completed the requirement, or select Always visible to always show the link. This field appears only when the Actionable field is selected. |
      | Exclude | When selected, excludes all users in the Audience field from the requirement. |
      | Audience | Select the audience to refine the number of users the requirement applies to. For example, you might want to target all users in an audience that happens to be located in California or target an audience you created specifically for a location, regardless of whether they are users who are traveling, visiting, or working in the location. No audience is selected by default and the requirement applies to users based on the rest of the form. Nota: If Exclude is checked, the requirement targets all users except those in the audience. |
      | Include previous applicable records ||
      | Table | Table to look for previously created records that will trigger the requirement flow. For example, the Employee Health Verification Requirement uses the Employee Health Verification table \[sn_imt_monitoring_health_verification\]. |
      | Condition | Add conditions to filter the records from the table that will trigger the flow. |
      [Tabela 6. Health and Safety Requirement form]

      {#create-readiness-requirement__table_wxk_x2n_2mb}
   4. Click Submit.
   {#create-readiness-requirement__substeps_qjt_mm5_zlb}
3. In Workflow Studio, create a flow to update the requirement status for an employee or visitor.
   1. Create a new flow.
   2. Save the flow in the Employee Readiness Core application.
   3. Add a trigger so that the flow runs whenever the type of record that you're using to check the requirement status is created or updated.  
      For example, for the Employee Health Verification Requirement, the
      flow runs whenever a health verification record is created or
      updated.
      {#create-readiness-requirement__table_j2h_lh5_zlb__entry__4}

      | Trigger | Table | Condition | Run Trigger |
      |-|-|-|-|
      | Created or Updated | Employee Health Verification \[sn_imt_monitoring_health_verification\] | None. | For each unique change |
      [Tabela 7. Trigger]

      {#create-readiness-requirement__table_j2h_lh5_zlb}
   4. Add the action that you created to the flow.
   5. Add the record from the trigger as the input.  
      For example, for the Employee Health Verification input, add the Employee Health Verification record that was created or updated in the trigger event.
   6. Add the Update User Requirement action provided in Employee Readiness Core to the flow.  
      {#create-readiness-requirement__table_ncn_xk5_zlb__entry__4}

      | User \[User\] | Health and safety requirement \[Health and Safety Requirement\] | Requirement status | Trigger datetime |
      |-|-|-|-|
      | Employee or User field from the trigger record. For example, the Employee field from the Employee Health Verification record. | Health and safety requirement you created. | `requirement_status` returned by the action that you created. | Created field from the trigger record. Only use this input if you set a value for the Valid for field on the requirement. |
      [Tabela 8. Update User Requirement inputs]

      {#create-readiness-requirement__table_ncn_xk5_zlb}
   7. Click Activate.
   {#create-readiness-requirement__substeps_epf_xg5_zlb}
4. Complete the health and safety requirement.
   1. Navigate to Employee Health and Safety StatusHealth and Safety Requirements.
   2. Click the requirement that you created earlier.
   3. In the Requirement flow field, add the flow that you created to update the requirement status for employees or visitors.
   4. Click Update.
   {#create-readiness-requirement__substeps_nsq_3wt_zlb}

## O que Fazer Depois

When you create the requirement, it's not active by default. You must activate the
requirement before you can track whether employees or visitors have fulfilled the
requirement. For instructions, see [Activate a health and safety requirement](https://www.servicenow.com/docs/UxrALUFzMat7wSgaBo33Dw "Activate requirements to track when employees are ready to return to the workplace or to safely travel to another site. You can also activate requirements that visitors must complete before entering the workplace.").