![]() |
16.20 Client Service Contracts – Contract Award, Management, and Monitoring |
16.20.05
July 1, 2007 |
Purpose of this policy |
|
This policy serves as the basis for awarding, managing, and monitoring client service contracts. |
|
16.20.10 July 1, 2007 |
Contract negotiations |
Part of the process of awarding a client service contract under a competitive solicitation or a sole source process is to negotiate the specific contract terms. Any discussions, whether formal or informal, that are held with the apparent successful contractor to develop and finalize the contract are considered contract negotiations. Under a competitive process, negotiations may be held with the apparent successful contractor if more favorable terms are desired than were submitted in the proposal or if the proposal is not sufficiently precise or direct. Areas in the proposal that may be considered less than satisfactory include: time devoted to the project or phases of the project by the consultant, scheduling related to the items in the scope, pricing, billing terms, etc. Negotiations should not substantially change the terms of the original proposal, but should eliminate any ambiguities in the contract and clarify the terms. If the terms offered by a contract are fair and equitable, award may be made without negotiations. Under a non-competitive or sole source award, price negotiations may be necessary if the contractor costs proposed seem higher than expected. |
|
16.20.15 July 1, 2007 |
Formalizing client service contracts |
| 16.20.15.a |
Written Contract
Numerous other terms are often included in the contract documents to provide additional legal protection to the agency. A sample client service contract is provided in Additional Contract Resources at: http://www.ofm.wa.gov/contracts/resources/default.asp. |
| 16.20.15.b | Contract Format |
| 16.20.15.c | Approval as to Form |
| 16.20.15.d | Available Funding |
| 16.20.15.e |
Health Insurance Portability and Accountability Act (HIPAA) Some client service contracts may require HIPAA language in order for the contracting agency to be in compliance with HIPAA. If the service provider is a physician or other medical care provider, they may seek insertion of HIPAA language into the contract so that they are in compliance with the federal law. These provisions generally relate to “business associate” arrangements, where one of the contracting parties is a business associate of a covered entity under HIPAA or where both parties are covered entities sharing protected information. The decision about whether or not HIPAA compliance language or an addendum should be part of the contract is based on whether the parties fall under the HIPAA legal definition of a covered entity or business associate. The law provides exceptions for certain types or uses of information as well. When the issue of inserting HIPAA language into a contract is raised, the following considerations apply:
If the answer to any of these questions is “yes”, please contact your agency HIPAA compliance officer, in-house counsel, or your Assistant Attorney General to determine whether HIPAA language needs to be part of the contract. |
| 16.20.15.f | Hold Harmless and Indemnification Under a hold harmless provision, the contractor releases the state agency from any responsibility for losses to a third party arising from the acts and/or omissions of the contractor or its officers, directors, partners, employees, and agents while the contractor is performing work under the contract. For example, if a client is injured in a contractor’s facility due to the carelessness of one of the contractor’s employees, the contractor cannot seek reimbursement from the agency for the amount the contractor has to pay to the client who suffered the loss. An indemnification provision requires the contractor to reimburse the agency for losses incurred by the agency because of the contractor’s acts or omissions in performing under the contract. An example is when a state agency is sued by a client who is seriously injured when he/she falls through a rotting front step at the contractor’s place of business. If the client sues the state agency for those injuries, the contractor would have to pay costs for investigating, negotiating, defending, and settling the suit. |
| 16.20.15.g | Personal Information Privacy Notice: Safeguarding and disposition of personal information must be consistent with Executive Order 00-03 issued April 25, 2000, and chapter 42.56 RCW and other applicable statutes that protect personal information. |
|
16.20.20 July 1, 2007 |
Performance measures and outcomes |
Contract managers are encouraged to consider whether performance measures and outcomes are applicable to their contract. The purpose of performance measures is to provide a standard or measure for performance of the contracted services. Performance measures may also be used to determine if, and when, the contractor has successfully completed performance, and when and how much the contractor should be paid. Contract performance measures may:
Good performance measures are:
Contract managers should check the funding source or statutory authority to determine whether any specific outcomes are mandated. They should also consider:
|
|
16.20.25 July 1, 2007 |
Performance-based contracts |
| 16.20.25.a |
Performance-based contracts have several characteristics that distinguish them from more traditional types of service contracting. Those characteristics:
Performance contracting may be used for a variety of types of services, but it is not applicable to or appropriate for all. Its use must be carefully considered since outcomes and performance standards need to be clearly identified in the contract, so that achievement of those outcomes and standards is apparent to all. |
| 16.20.25.b | Performance-based contracts offer benefits. For example, they:
|
| 16.20.25.c | Potential issues associated with performance-based contracts include:
|
|
16.20.30 July 1, 2007 |
Fiscal considerations and payment methods |
| 16.20.30.a |
Fiscal Principles
|
| 16.20.30.b | Financial Reporting Key considerations for financial reporting provisions are to:
|
| 16.20.30.c | Payment Methods Another type of contract payment method is used with performance-based contracts. Performance-based contracts describe either what the contractor is expected to accomplish or what outcome the contractor is to achieve, but do not specify how the work will be completed. Therefore, contractors provide more strategic input into determining the best method and approach for the services in order to achieve the outcomes desired by the agency. Performance-based contracts typically tie payments to outcomes or deliverables, not just the number of hours of service provided, but they do state a maximum compensation that may be earned. |
| 16.20.30.d | Payment Documentation At a minimum, invoices submitted should include the contract number or other evidence of authorization to contract, date(s) services were provided, description of services provided or any goods received, and approval for payment. The approval for payment can be documented by the initials of the approving staff and date on the contractor’s invoice, or by an electronic approval process. For further information, refer to Subsection 85.32.30 of this manual. |
| 16.20.30.e | Contract Overpayment |
| 16.20.30.f | Federally Funded Contracts There are basic federal rules that apply to virtually all expenditures of federal awards. Each federal agency and the U.S. Office of Management and Budget (OMB) publish these rules as listed below.
Federal agency regulations including the Code of Federal Regulations (CFR) and OMB regulations (Circulars) can be accessed on the Internet at: http://www.gpoaccess.gov/cfr/, and http://www.whitehouse.gov/OMB/circulars. The federal agency regulations and the OMB Circulars are routinely updated. Contract managers of contracts involving federal funds are encouraged to stay abreast of such changes by consulting with fiscal staff or other individuals that follow federal requirement amendments. |
| 16.20.30.g | Sub-recipient or Vendor A sub-recipient is a non-federal entity that expends federal funds received from a pass-through entity to carry out a federal program, but does not include an individual that is a beneficiary of such a program. A vendor is a dealer, distributor, merchant or other seller providing goods or services that are required for the conduct of a federal program. Refer to Section 50.30 for further guidance about the sub-recipient/vendor determination and OMB Circular A-133 Audits of States, Local Governments, and Non-Profit Organizations, Subpart B-Audits, 210 Sub-recipient and vendor determinations.Contracts should be clearly written to support the determination of sub-recipient or vendor status. A sub-recipient may:
A vendor:
In some instances, a contractor could be a sub-recipient for one state agency and a vendor for another. A contractor could also be a sub-recipient for one program within an agency, and a vendor for another program within the same agency. |
| 16.20.30.h | Debarment/Suspension |
|
16.20.35 July 1, 2007 |
Liability insurance |
| 16.20.35.a |
Before contracting for client services, the agency should analyze the type of services required and evaluate the State's exposure to legal liability that may result from the contract. State agencies can be financially protected from those who seek legal recourse by requiring contractors to carry insurance. To protect the State's interests on contracts where insurance is appropriate, liability insurance requirements should be included in either the solicitation document as a condition of responsiveness or in the contract document. Injury or damage to a third party including clients may result in legal liability to the State if it occurs as a result of a contractor's negligence. Liability insurance covers legal liability of an insured. If a contractor provides liability insurance coverage and names the State as an additional insured on the policy, the State will have insurance protection for many types of tort claims that arise out of the contractor's activities. |
| 16.20.35.b | The OFM, Risk Management Division (RMD), recommends that agencies include insurance requirements in their contracts, whenever applicable. At a minimum, RMD suggests that contractors be required to purchase general liability/automobile liability and employer's liability insurance and comply with workers compensation laws. For more information on RMD's suggested insurance specifications, refer to Contracts: Transferring and Financing Risk. This manual is available in hard copy through RMD or on OFM’s RMD website at: http://www.ofm.wa.gov/rmd/default.asp. If you have further questions, you may contact the Risk Management Division at (360) 902-7301. Contract managers should contact internal agency staff, who may be knowledgeable about insurance requirements, before contacting RMD. |
|
16.20.40 July 1, 2007 |
Industrial insurance |
| 16.20.40.a | When a state agency enters into a client service contract, the contractor’s employees should be covered by industrial insurance also called workman’s compensation. This protects the State’s interest if either the contractor or someone employed by the contractor is injured while performing work under the contract. With few exceptions, Title 51 RCW, Washington State's industrial insurance law, requires that all persons performing work under contract in Washington State be covered by industrial insurance. Contractors are required to provide industrial insurance coverage either through the Department of Labor and Industries (L&I) or as self-insured employers certified by L&I. Agencies can verify a contractor's compliance by contacting L&I, Field Audit Compliance, in Olympia at (360) 902-4752 or 902-4750, or by sending an e-mail to: verifystatecontracts@lni.wa.gov. Employments excluded from mandatory coverage are listed in RCW 51.12.020 and include sole proprietors, partners, corporate officers, and others. |
| 16.20.40.b | Under RCW 51.12.050, the contracting agency is responsible for ensuring that the prime contractor and any subcontractors have industrial insurance coverage or the agency may be liable for unpaid industrial insurance premiums. As appropriate, agencies should incorporate into their client service contracts a provision stating that the contractor agrees to comply with the industrial insurance requirements of Title 51 RCW and to cover its employees with industrial insurance. |
|
16.20.45 July 1, 2007 |
Risk assessment approach to contracting |
| 16.20.45.a |
Risk Assessment Approach The risk assessment may be conducted informally or formally depending on the dollar value of the contract, complexity of the services, experience of the contractor, etc. An informal risk assessment is the analysis conducted by the contract manager to make effective contracting decisions and is not required to be in writing. A formal risk assessment is conducted in writing and documents the types of activities and factors considered. The contract manager may not know the answers to all these types of questions and may need to seek further information from the contractor, from others in the agency, from other state agencies with oversight (such as current licensure), etc. Sample risk assessment checklists are provided in Additional Contract Resources at: http://www.ofm.wa.gov/contracts/resources/default.asp. |
| 16.20.45.b | Risk Assessment Categories
Based on the results of the risk assessment, contract managers may decide whether it is advisable to contract for the services. If so, the contract manager will decide which contractor to select, and the scope, frequency, and methods of monitoring and/or auditing to use to ensure sufficient oversight, given the risks involved. Risk assessment results may also be used to devise more stringent controls and tighter contract language, when appropriate, to adequately monitor and/or audit the use of public funds. It is also important to note that contract risk is dynamic. Therefore, the risk assessment should be updated periodically to provide a current record of risk factors associated with the contract. Risk assessments, linked to a monitoring plan, should be documented. Contract managers may choose how to document this. Several examples of risk assessment tools can be found in Additional Contract Resources at: http://www.ofm.wa.gov/contracts/resources/default.asp. |
| 16.20.45.c | Transferring Risk
|
|
16.20.50 July 1, 2007 |
Contract management principles |
|
Contract managers must be mindful of the following:
|
|
16.20.55 July 1, 2007 |
Managing and monitoring contracts |
| 16.20.55.a |
Proactively Manage and Monitor |
| 16.20.55.b | Managing the Contract While the contractor has responsibility to perform under the terms of the contract, the state agency has responsibility for reasonable and necessary monitoring of the contractor’s performance to ensure compliance with the contract provisions. Many contracts name a contract manager who serves as the primary point of communication between the agency and the contractor and who provides the principal contract management and monitoring function. More than one individual can be named as having responsibility for various aspects of the contract. The chief objective of the contract manager, however, is to ensure that the contractor fulfills all contractual obligations in a quality manner within budget and schedule. To accomplish this task, the contract manager should be completely knowledgeable of the terms of the contract and maintain requisite controls throughout. |
| 16.20.55.c | Monitoring the Contract The purpose of monitoring is to ensure the contractor is:
Effective contract monitoring can assist in identifying and reducing fiscal or program risks early in the process, thus protecting public funds. Monitoring activities may include, but are not limited to, the following:
|
|
16.20.60 July 1, 2007 |
Executing amendments to existing client service contracts |
|
As work progresses, it may be necessary to make changes to the contract to enhance or improve the deliverables or services. Any written alteration to an existing contract is called a contract amendment. Amendments are executed by all parties to document the changes being agreed upon. |
|
| 16.20.60.a | Principle Terms Amended
|
| 16.20.60.b | Within the Scope of Work Changes that are within the scope of work, but which represent substantial changes in the quantity, duration, cost, or nature of the work may not be appropriate for contract amendments and may need to be addressed in a new procurement or new contract. When the agency includes in its solicitation document the option to extend the contract for additional periods or to add subsequent phases, such amendments, though they may represent substantial changes, are appropriate. They were specified in advance of contract award and all firms who competed were made aware of these potential additions to the contract. Changes that are outside the general scope of the contract are not appropriate to award through contract amendment. Such changes would have the effect of making the work performed substantially different from the work the parties bargained for at the time the original contract was awarded. If a contract has expired, it is generally not appropriate to amend it; rather it is more appropriate to award a new contract. |
| 16.20.60.c | Amendment is in the Best Interest of the State When adding funding to a contract, agencies should generally include in the amendment both the dollar amount of the additional funding and the revised contract maximum (the amendment amount added to the current contract maximum). In addition, agencies should consider specifying what additional services are being provided under the amendment and include any new deliverable dates resulting from the additional dollars being authorized. |
| 16.20.60.d | New Contract Option |
|
16.20.65 July 1, 2007 |
Corrective action |
|
Contract problems must be addressed as soon as they are discovered to prevent them from becoming recurring or serious. Corrective action is suggested when direct negotiation and other less formal means have failed. Corrective action means action initiated by the agency and taken by the contractor that corrects identified deficiencies, produces recommended improvements, or demonstrates that deficiencies or findings are either invalid or do not warrant action. Contract problems that warrant corrective action include:
A first step in corrective action would typically be to communicate in writing to the contractor describing where performance is deficient. Corrective action activities should be coordinated with the agency’s management, in-house counsel, and/or Assistant Attorney General, as applicable, to avoid waiving any rights that might be available to the State. All corrective action initiated by the agency must be documented in writing. If the corrective action is successful in resolving problems, the contractor should be notified in writing that resolution has been achieved and the documentation retained in the contract file. If corrective action is unsuccessful at first, state agency staff may continue to work with the contractor until deficiencies are resolved, or they may proceed with a dispute process or take other appropriate courses of action.
|
|
16.20.70 July 1, 2007 |
Contract disputes |
|
A contract dispute is typically the result of a serious difference of opinion between the agency and contractor about contract terms, conditions, or performance. The contract disputes process generally follows a corrective action process that has reached an impasse. The contract should contain a disputes clause setting forth the process to be followed. Invoking the disputes clause is an option available to either party, but is not required. If the dispute process is elected, the process must be followed as described in the contract. Disputes provisions may take different approaches. One approach is for the disputing party to submit a written statement of the issues to the other party at a higher level within the organization. If that does not resolve the issue(s), a neutral third party can be appointed to review the position of both parties and submit a written decision. Another approach is to convene a dispute panel with each party to the contract appointing one member and a mutually agreed upon third panel member being appointed with the majority prevailing. Other appropriate disputes approaches may also be utilized, as agreed upon. Dispute activities should be coordinated with the agency’s Assistant Attorney General. Unless otherwise directed by the Office of the Attorney General, dispute processes are to precede any court action.
|
|
16.20.75 July 1, 2007 |
Contract remedies and sanctions |
|
After efforts to resolve issues through either or both the corrective action and/or dispute processes have failed, a contractor who is deemed to be noncompliant with the terms and conditions of the contract may be determined to be subject to remedies or sanctions, such as:
|
|
16.20.80 July 1, 2007 |
Contract termination |
|
Contracts may be terminated prior to the completion date of the contract either for convenience of the parties or for cause as provided under the contract terms. |
|
| 16.20.80.a | Termination for Convenience Termination for lack of funding, referenced under the “Savings” clause of the model contract, is processed as a “Termination for Convenience.” It is intended to handle the situation when funding from federal, state or other sources is no longer available to the agency or not allocated for the purpose of meeting the agency’s contractual obligation. The Attorney General's Office may be contacted when an agency is considering invoking the termination for convenience clause. |
| 16.20.80.b | Termination for Default |
|
16.20.85 July 1, 2007 |
Review and implement contractor’s final product |
| 16.20.85.a |
When the contract is almost complete, contract managers are responsible to:
|
| 16.20.85.b | Final Written Report
Generally, the final report is submitted before final payment is made to the contractor. |
|
16.20.90 July 1, 2007 |
Evaluate contractor’s performance |
|
Upon contract completion, the agency contract manager may want to prepare a contractor evaluation. This evaluation will be useful if agency management wants an analysis of contractor performance and if other agencies inquire about the contractor. The evaluation may address the following:
Contract managers should share with other state agency staff information gained from administering the contract so that those responsible for future contracts can gain from these experiences.
|
|
16.20.95 July 1, 2007 |
Documenting the contract file |
|
Agencies are required to maintain adequate documentation regarding the contract and services provided by the contractor. Agencies may maintain contract documentation in more than one location as well as by multiple media. Contract payment documentation may be maintained in the fiscal office, while the contract manager may maintain a monitoring file in his/her location and the contract office may maintain the procurement files. The information may be available in electronic or hard copy format. |
|
| 16.20.95.a | Documentation Documentation in the contract file, at a minimum, must include the executed contract and all attachments and exhibits incorporated into the contract. Monitoring activities conducted under the contract such as meeting minutes, copies of reports submitted, fund tracking records, etc., are all examples of the types of documentation that may be part of a contract file and must be maintained somewhere in the agency. |
| 16.20.95.b | Records Retention Records retention of client service contracts must follow the requirements published by the Office of the Secretary of State in the General Records Retention Schedule for Agencies of Washington State Government at: http://www.secstate.wa.gov/archives/gs.aspx. |
|
16.20.98 July 1, 2007 |
Auditing contracts |
| 16.20.98.a |
Auditing Several types of audits are performed, including:
Audits initiated by the agency or contractor: State agencies should use a risk assessment to consider whether an audit of the contractor is needed. When an audit is deemed appropriate and necessary, the expectations for the audit scope, methodology, and due date should be included in the written contract. An audit can be designed to accomplish one or more of the following:
While an audit can be an effective monitoring tool, it carries a cost. Therefore, care should be exercised in calling for audits. Regardless of whether an audit is performed, the agency still must monitor its contracts to ensure it receives the services for which it paid. |
| 16.20.98.b | Audit Resolution Normally, if a finding exists in a published audit report, whether issued by Federal auditors (Office of Inspector General), an independent audit firm, the State Auditor’s Office, or a state agency’s internal audit staff, resolution of audit findings is warranted. |
| 16.20.98.c | Questioned Costs Methods for recovering questioned costs may include:
There may also be good reasons not to pursue recovery of the questioned costs, such as when the costs to recover a small dollar amount are more than the over-payment. Sufficient reasons, generally based on Assistant Attorney General guidance, should be documented when exercising the option not to pursue recovery. Contracts using federal funds may require different processes, as prescribed by the federal government. |
| 16.20.98.d | Performance Audits In 2005, Initiative 900 gave the Office of the State Auditor authority to conduct performance audits of state and local governments. The State Auditor developed the following definition of a performance audit: An objective and systematic assessment of the performance and management of an entity, program, activity, or function in order to:
Performance audits conducted will cover broad areas but will include those of the greatest public interest, matters that affect all agencies, and other identified recurring challenges. |