...
Scope of Work (SOW) Template shall be utilized to establish SOW. The template is located here: Commonly Used Forms SOW shall cover What, When, Where, Why, Who, and How within the scope description. This should be broad, yet clear without utilizing technical language. Member Agencies shall ensure that travel is considered and reflected within the scope and budget. Separate Scopes of Work should be used for each provider/project/fiscal year.
Scopes of Work are the contract between a member agency and a provider. Each Scope of Work should detail what deliverables the provider is expected to deliver for the member agency including fund source(s) utilized, costs per deliverable, required supporting documentation or proof of service delivery, (training sign-in sheets, receipts, etc.), as well as the time period the scope covers. Program Managers are responsible for insuring ensuring that the correct approved services are displayed in nmstar thru their read-only access to the vendor/project. For any new services or changes to the vendor/project, Program Managers should contact support@fallingcolors.com. New services require 4-6 weeks for development, testing, and deployment prior to use by the provider for billing.
A revised SOW is required to be sent to the provider when: the provider name is incorrect, the project name is incorrect, and there is a change in the deliverables that the vendor is expected to complete for the scope time period. SOWs are sent to Falling Colors via the member agency folder on SFTP. Falling Colors sends SOWs to the Signatory Authority managed by the provider in the provider profile in nmstar. Falling Colors make makes multiple attempts to follow - up with providers who have not signed their SOW within a timely manner and at times will require intervention by the member agency.
...