Skip to main content
Administrator Guide
Last Updated: 2026-10-30
Add New Checklists

Add New Checklists

Have the
checklists.settings
permission.
Checklists are optional, rule-based actions that you can configure for contractors, work orders, and vendors. You can create checklists to required users to take action at specific timeframes, such as pre-onboarding or post-offboarding.
You can apply checklists to jobs you create based on the rules you select on the
Checklists
page. When you edit an existing checklist, it doesn't impact existing checklist actions.
You can also bulk upload checklists by downloading the provided template when you click
Bulk Upload
from the
Checklists
page. For more information, see the
Checklist Items
section of the Workday VNDLY File Import Specifications page in Community.
  1. From the header, select
    More
    Company Settings
    .
  2. Under
    Jobs & Work Orders
    , click
    Checklists
    .
  3. Click
    Create New Checklist
    . As you create the checklist, consider:
    Option Description
    Title
    Name the checklist.
    Checklist Type
    Categorizes the requirement as one of these:
    • Compliance
      : Defines legal, regulatory, organizational, and contractual standards across contingent workers, work orders, and contractors.
    • Credentials
      : Defines professional qualifications, certifications, licenses, and technical information required for a worker to perform a job role.
    Must Complete
    Specifies the scope and frequency of completion:
    • Per Work Order
      : The checklist must be completed for every job.
    • Per Contractor
      : The checklist must be completed 1 time by each contractor.
    • Per Vendor
      : The checklist must be completed 1 time by each vendor.
    Add Criteria
    (Optional) This option is only available when
    Per Worker
    or
    Per Contractor
    is selected for
    Must Complete
    .
    Select 1 or more criteria for VNDLY to apply the corresponding checklist items to the job or Statement of Work (SOW) role. Adding criteria rules enables you to create different checklists for various geographic areas, job categories, job templates, organization unit, module, and hire types. If you don't select any criteria, VNDLY applies this checklist to every job you create.
    Criteria are grouped into families and you can select only 1 criteria from each criteria family. After selecting your criteria, select 1 or more of the appropriate options. When selecting a job category, organization unit, or region criteria, Workday VNDLY applies the checklist to both the parent and the children categories.
    Example: You can create a checklist using these criteria:
    • Subdivision
      :
      Alabama
      ,
      Arkansas
    • Hire Type
      :
      Contractor
    • Job Category
      :
      Engineering
    The checklist only displays for candidates applying to Engineering contractor jobs in those 2 states. Be aware that the checklist will also display for matching jobs that are in sub-org units within the Engineering parent job category.
    Timing
    Determines when this checklist action is due.
    • Pre-Onboarding
      : Blocks the onboarding workflow when you don't complete or waive the checklist.
    • Post-Onboarding
      : Enables you to specify the number of days for when the checklist is due after onboarding the contractor.
    • Post-Offboarding
      : Enables you to specify the number of days for when the checklist is due after offboarding the contractor.
    Action Required From
    Select the roles responsible for satisfying the action in VNDLY. You can select more than 1 role.
    Roles include:
    • Vendor
      : For
      Per Work Order
      and
      Per Contractor
      checklists, VNDLY sends a notification to the vendor users associated with the work order or contractor. Vendor users can take action on the checklist, as long as they have the
      checklist.admin
      or the
      checklist.update
      permission.
      For
      Per Vendor
      checklists, VNDLY sends a notification to vendor users if they have been added to VNDLY. Note that you can’t manually apply a checklist action to a vendor for
      Per Vendor
      checklists. Vendor users can take action on the checklist if they have the
      checklist.admin
      , the
      checklist.update
      , or the
      vendor_company.activate
      permission.
    • Users with Program Team role tag in the Organization Unit
      : For
      Per Work Order
      and
      Per Contractor
      checklists, VNDLY sends a notification to users who have the
      Program Team
      role tag on the security role attached to their organization unit. If these users have the
      checklist.admin
      or the
      checklist.update
      permission, they can take action on the checklist.
      For
      Per Vendor
      checklists, these users need the
      checklist.admin
      , the
      checklist.update
      , or the
      vendor_company.activate
      permission to take action.
    • Resource Manager
      : This option is only available for
      Per Work Order
      and
      Per Contractor
      checklists. For
      Per Work Order
      checklists, VNDLY sends a notification to the resource manager associated with the work order. For
      Per Contractor
      checklists, VNDLY sends a notification to the resource manager associated with any of the work orders the contractor is assigned to, including inactive work orders.
      Resource managers are able to take action on the checklist, as long as they're listed as the resource manager on the work order and they have the
      checklist.admin
      or the
      checklist.update
      permission.
    • Admin
      : For all checklist types, VNDLY sends a notification to all client admin roles. For
      Per Worker
      and
      Per Contractor
      checklists, these admin users can take action if they have the
      checklist.admin
      or the
      checklist.update
      permission.
      For
      Per Vendor
      checklists, any client admin users with the
      checklist.admin
      or the
      checklist.update
      permission can take action.
    • Contractor
      : This option is only available for
      Per Work Order
      and
      Per Contractor
      checklists with the
      Timing
      field set to
      Post-Onboarding
      . VNDLY sends a notification to the contractor.
      Contractors will be able to take action on the checklist, as long as they have the
      checklist.admin
      or the
      checklist.update
      permission. You also must enable the
      Allow Contractors to Manage Checklist Actions
      setting on the
      Configuration
      tab to ensure that contractors can access the
      Manage Checklist Actions
      page and view the
      Checklist
      tab on the work order.
    • Program Team Users
      : For
      Per Work Order
      and
      Per Contractor
      checklists, VNDLY sends a notification to users listed in the
      Program Team Users
      field on the job or work order. These users can take action on the checklist if they have the
      checklist.admin
      or the
      checklist.update
      permission.
      For
      Per Vendor
      checklists, VNDLY sends a notification to the users specified on the job. These users can take action on the checklist if they have the
      checklist.admin
      , the
      checklist.update
      , or the
      vendor_company.activate
      permission.
    Select when checklist actions are generated
    Select the work order status at which the checklist action should be generated.
    • Pre-Onboarding
      :
      Apply
      ,
      Offer Release
      , or
      Offer Accept
      .
    • Post-Onboarding
      :
      Apply
      ,
      Offer Release
      ,
      Offer Accept
      , or
      Onboard
    • Post-Offboarding
      :
      Apply
      ,
      Offer Release
      ,
      Offer Accept
      ,
      Onboard
      , or
      Ended
      .
    Must Complete Within # Days Post-Offboarding
    Only displays when a
    Timing
    of
    Post-Offboarding
    is selected.
    Sets the completion deadline relative to when offboarding begins.
    Must Complete Within # Days Post-Onboarding
    Only displays when a
    Timing
    of
    Post-Onboarding
    is selected.
    Sets the completion deadline relative to when onboarding begins.
    Force Select when Criteria Matches
    When checked, if a work order or candidate matches the criteria rules, VNDLY forces the selection of that checklist requirement.
    Attachment Required
    When checked, the assigned user must upload at least 1 document or file attachment to submit and complete the checklist action.
    Hide Attachment Section
    When checked, the
    File Upload
    section is hidden from the checklist action interface. Example: Check this box for an acknowledgement-only checklist item that doesn't require an attachment.
    Required Attachment Expiration Date
    When checked, a document expiration date must be entered when an attachment is uploaded. This ensures the system tracks expiration windows and sends renewal notifications. Examples: Time-sensitive compliance documentation such as medical licenses, certifications, or work visas.
    Pass/Fail
    When checked, VNDLY adds a
    Pass
    or
    Fail
    selection control to the checklist action. Examples: Assessment outcomes such as a background checks or drug screenings.
    Approval Required
    When checked, the checklist action must undergo formal review and approval before it is finalized.
    Hide From
    Select to hide the checklist actions from vendors or clients. You can select both check boxes, if required. Program team members, Administrators, and MSP users are able to view all checklist actions and aren't blocked by the
    Client
    selection.
    Custom Field Setup
    (Optional) Enables you to add custom fields to per-work order, per-contractor, and per-vendor checklists. The custom fields display on checklist actions for users who are prompted to complete them. See: Add Custom Fields to Checklist Actions.
    Expiration
    Determines how long a checklist action is valid before you must update it. Select the appropriate option for the checklist action:
    • Never:
      Item never expires. Examples: One-time onboarding items such as NDA signing or an initial background check.
    • Specific date of the year:
      Item expires on a specific date every year. The renewal date for the related actions is based on the next occurrence of this date after the last completed date of action. Example: Annual program-wide compliance verification every December 31.
    • Expiration Duration Unit
      : Item expires based on a standardized, duration-based expiration window measured relative to when the action was completed. Example: Time-bound certifications with fixed validity windows, such as a 1 year certification.
    • User-entered Expiration Date on Action
      : Item forces the Action owner to enter an expiration date. The expiration date isn’t calculated and relies on the user-entered value. Example: Documents with unique, variable expiration dates such as a work visa, CPR card, or state license.
    Notify When Nearing Expiration
    (Optional) Select to configure single or multiple notifications that remind users when a checklist item is nearing expiration. You can configure reminder notifications by the number of days before expiration and the roles to notify. See: Set Up Multiple Checklist Expiration Notifications.
    Allow Auto-Escalation
    (Optional) When checked, you can configure the escalation process.
    Days to Notify In
    : Enter the number of days after which the escalation process should begin and the selected users should be notified.
    Check the box for each user type that should be notified.
    Additional Details
    (Optional) Enter information to help users select the correct checklist. This text displays on each checklist action in the
    Checklist Actions
    list pages and each job checklist
    Requirements
    tab.
  4. Click
    Save Checklist
    .
When dealing with different regional requirements, you can create different checklists for specific work locations and job categories.
This example demonstrates how to create a compliance checklist required for each contractor for engineering jobs in California and Oregon. Selecting the
Per Contractor
option requires contractors in these work areas to only complete this checklist once.
Field
Value
Checklist Type
Compliance
Must Complete
Per Contractor
Criteria
Subdivisions
:
California
and
Oregon
Criteria
Job Categories
:
Engineering
If your statement of work stipulates that contractors must supply a specific valid credential for a specified job title in specific work regions, you can set the credentials as:
Field
Value
Checklist Type
Credentials
Must Complete
Per Contractor
Criteria
Subdivisions
:
Florida
,
Louisiana
, and Texas
Criteria
Job Template
: Engineer
Criteria
Module
:
Statement of Work
Criteria
Hire Type
:
Contractor