Compliance Tracking – Step 1: Prepare

This entry is part 13 of 24 in the series Setup Guide - Compliance

Before establishing compliance tracking in sfPMS, you’ll need to gather the following information:

  • What Compliance types does your company track?
  • Which of these Compliance types are required and which are optional?
  • Which of these Compliance types are tracked at the vendor level and which are tracked at the commitment level? Do you want to track lien waivers on Pay Request documents?
  • Will all vendors require the same Compliance types? sfPMS allows you to assign Compliance types by Vendor subtype, so before assigning Compliance types to Vendors, you’ll need to determine if you will create two or more Vendor subtypes and then build Compliance types for each Vendor type.
  • Will all commitments require the same Compliance types? sfPMS also allows you to assign Compliance types by Commitment subtype, so before assigning Compliance types to Commitments, you’ll need to determine if you will create two or more Commitment subtypes and then build Compliance types for each Commitment subtype.
    Note: Pay Requests inherit subtypes from their corresponding Commitments.
  • Will you want to track certain requirements on Pay Requests (eg: Lien Waivers) or Change Orders (eg: Executed Contract Returned)?
  • What text do you want in your Compliance Notification document?
  • What persons or roles will receive the Compliance Notification document?
  • Will you route the Compliance Notification via e-mail, fax, or hard copy, and will you need an Attachment template for Compliance Notification?
  • Who will be given the newly created “Compliance Staff” role?

 

 

Series Navigation<< Setup of Compliance Tracking and NotificationCompliance Tracking – Step 2: Code Maintenance >>