ASO Policies and Procedures

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

ASO shall manage contracts between the Member Agencies and Vendor. Member Agencies shall refer to and utilize the most current award of the BHC’s Services Agreement and the ASO. ASO will manage agreements, however, it is the responsibility of each Member Agency to enforce documentation and policies to the vendor.

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 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 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 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, there is a change in the deliverables that 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 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.

Agencies direct Falling Colors to contract with providers that they want to hire to deliver services and submit billing. Falling Colors needs the below information from a member agency in order to contact the provider for onboarding:

  • Legal Name of Provider as listed on W-9

  • Address of Provider

  • Provider Vendor Administrator-to give nmstar permissions to complete the registration

    • Name:

    • Email Address:

    • Phone:

  •  Provider Signatory Authority- to send Contract and Business Associates Agreement

    • Name:

    • Email Address:

    • Phone: 

  • Scope of Work-we are unable to register new vendors without an approved Scope of Work

 Once we have this information, Falling Colors will get the nmstar registration in place and send the required FC (non client or client services based on SOW) Contracts and SOW to the Provider's Signatory Authority via SignEasy for signature along with the annual Attestation from nmstar. We will then inform the member agency when the provider has completed their registration in nmstar, signed all documents, and is ready for the member agency to send Falling Colors a Budgetary Letter of Direction (BLOD) or Change Request Form (CRF) to allocate funding to the provider for billing.

Falling Colors will not allocate funding to providers unless there is a signed SOW for the provider/project and a signed Attestation for the provider.

New Providers are provided training on the nmstar application to assist them prior to billing.

*Please refer to the How-To section for details on How to submit BLODs and CRFs.

 

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.