Body
Contract Basics
This article provides an overview of contract fundamentals and the full contract life cycle. Topics include what constitutes a contract, drafting and negotiating, review rounds, form and execution, contract management, record keeping, performance monitoring, amendments, ending contracts, and procurement considerations. You can click the links below to route to the various sections:
What Is a Contract?
A contract is a legally binding document between two or more parties that defines the rights and obligations of each party and establishes the ground rules for the relationship.
A valid contract includes:
- Offer: A promise to do or not do something (for example, “I will wash your car for $10”).
- Acceptance: Agreement to the offer through promise or performance (for example, “I agree to pay $10”).
- Consideration: The value exchanged between parties, such as money for services.
- Authority: The contract must be agreed to by someone with the legal authority to bind the organization. If the signer does not have authority, the contract is null.
- Eligible parties: Agreements within the same Minnesota State system (intra‑agency) are not considered contracts.
Importance of Written Contracts
Written contracts are essential for clarity, accountability, and legal compliance.
Key reasons written contracts are required:
- Services are not governed by the Uniform Commercial Code (UCC), unlike goods.
- Contracts provide clarity, completeness, and a shared understanding of expectations.
- A contract supersedes prior verbal agreements or informal practices.
- Contract changes cannot be made through emails or conversations alone. All changes must be documented in a written amendment signed by all parties.
- Amendments can only be made while a contract is active. Changes after expiration require a new contract.
Contracts must be signed before work begins. This is both good practice and required by law. Well‑written contracts help prevent disputes and are easier to manage than resolving issues after the fact.
Contracts require appropriate planning and lead time. Not all contracts can be handled as emergencies.
Documents that are still considered contracts include:
- Joint Powers Agreements
- Real estate agreements (leases, licenses, purchase agreements)
- Clinical agreements
- Click‑through agreements
- Statements of work
- Terms of use or service
- Inter‑agency agreements (with agencies outside Minnesota State)
- Letters of engagement
- Grants
- Nondisclosure agreements
- Memoranda of Understanding (MOU) and Memoranda of Agreement (MOA)
- End User License Agreements (EULA)
- Licenses and terms and conditions
- Affiliation agreements
Regardless of the title, these documents create contractual obligations.
Minnesota State contracts must comply with mandatory board policies and system procedures.
Key policies and procedures include:
- Board Policy 5.14 – Contracts and Procurement
- Procedure 5.14.2 – Consultant, Professional, or Technical Services
- Procedure 5.14.5 – Purchasing
- Board Policy 7.7 – Gifts and Grants Acceptance
Board approval is required for:
- Any procurement, lease, or professional/technical/consulting contract over $3 million.
- Any amendment that increases a contract’s total value above $3 million.
Approved templates must be used unless an alternative is approved by the Attorney General’s Office or Minnesota State General Counsel.
Entering into a contract always involves accepting risk. It is essential to identify who has authority to accept those risks.
The contract supervisor (such as a dean, administrator, or director) is responsible for evaluating whether to proceed by analyzing:
- Business risks
- Strategic risks
- Operational risks
- Reputational risks
- Compliance risks
Risk Mitigation, Decision‑Making, and Accountability
Potential risks can be mitigated through:
- Appropriate insurance coverage
- Clear and precise contract language
- Active oversight throughout the contract term
- Timely communication and documentation when issues arise
- Declining to enter contracts when risks cannot be mitigated
Accountability requires clarity around:
- Who has a complete view of all contracting activities
- Who is responsible for addressing unsatisfactory performance, breaches, or termination
- Who evaluates vendor performance and takes corrective action
Contract managers are responsible for managing vendor relationships and initiating contracts through the Marketplace Contract module.
Review rounds are a critical part of drafting and negotiation and replace informal email exchanges. They allow:
- Internal review within Minnesota State
- External review involving vendors or legal counsel
- Tracked communication and documented feedback
- Collaborative editing before formal approval
Vendors should never see a contract for the first time at signature. Meaningful review opportunities reduce errors and rework.
Once a contract enters workflow for approval, it cannot be edited unless returned to draft status.
Form ensures proper procedures were followed, including:
- Use of approved templates or legal review of non‑standard forms
- Verification that funds are encumbered
Execution ensures the document is properly signed, including:
- Verification that the signer has authority
- Confirmation that signatures are dated
Form and execution are not the same as legal review. Legal review occurs during drafting, while form and execution occur at final signature.
Authorized signers include specific designated officials, depending on the contract.
Every contract must have a designated manager responsible for oversight. Contract management includes:
- Supervising performance
- Maintaining records
- Managing amendments
- Handling disputes
- Ensuring proper contract closeout
Contracts are more than administrative paperwork—they require active management.
Record Retention and Recordkeeping
Minnesota law requires contract records to be maintained in an accessible and organized manner.
Retention requirements include:
- Non‑construction contracts: retain for six fiscal years after expiration or last payment
- Construction contracts: retain current year plus eleven fiscal years
- Litigation holds may require longer retention
Unofficial records (MGDPA still applies):
- Draft contracts
- Draft communications
- Personal notes
Official records (retention schedule applies):
- Fully executed contracts
- Invoices and purchase orders
- Contract‑related communications
- RFPs and supporting materials
There is no distinction between paper and electronic records.
Signs of contractor problems may include:
- Missed deadlines or deliverables
- Skipped or irregular invoices
- Requests for advance payment
- Outdated contact information
- Payment irregularities
- Bankruptcy filings or negative press
Disputes should be handled progressively:
- Attempt to resolve issues informally with the vendor.
- Review contract terms related to the issue.
- Involve the Office of General Counsel if informal resolution fails.
- Consider termination only as a last resort and with legal involvement.
- Litigation is handled by the Attorney General’s Office.
Contract amendments must:
- Modify an active contract (not expired or terminated)
- Be a separate document
- Reference the original contract
- Clearly state what is changing and what remains unchanged
- Be signed by all parties
Amendment templates are available in the Marketplace Contract module.
Avoiding Contract “Creep”
Contract creep occurs when a contract exceeds dollar limits or duration thresholds, triggering additional requirements.
It commonly happens through:
- Repeated amendments
- Renewing similar services year after year
To prevent it:
- Anticipate total contract value during procurement
- Plan for potential growth
- Prepare for higher approval requirements early
Ending a Contract
To properly end contracts:
- Monitor expiration and renewal dates
- Maintain organized records
- Set reminders for key milestones
- Stop payments on expired contracts
- Use the Marketplace Contract module to track status
A contract is required for:
- Services (any dollar amount, including $0)
- Intellectual property
- Real estate
- Data‑related agreements
A purchase order (PO) is used for off‑the‑shelf goods that can be returned and resold.
Purchasing authority and requirements are governed by Minnesota statutes and board policies, with thresholds that trigger additional approvals, competitive solicitations, or board review.
Purchasing Requirements by Dollar Threshold
Purchasing requirements vary based on the total dollar value of the contract or purchase. As dollar thresholds increase, additional approvals and processes are required.
The purchasing thresholds include:
Master Contracts
A master contract allows Minnesota State to purchase from existing state contracts without conducting a new Request for Proposal (RFP), making the procurement process compliant with state law and board policy. However, using a master contract does not automatically ensure that the legal terms are in Minnesota State’s best interest or that all regulatory requirements are met.
Key considerations include:
- Purchasing from a state contract satisfies procurement requirements.
- Legal terms may still require review to ensure compliance with Minnesota State obligations.
- Software purchases always require legal review, even when purchased through a master contract.
Contract and Purchasing Authority
Minnesota State derives its contracting and purchasing authority from state statute and board policy.
Authority is established through:
- Minnesota Statute 136F.581, which grants the Board authority over contracts and purchases.
- Compliance with Minn. Stat. 471.345, the Uniform Municipal Contracting Law.
- Use of contracting options available under Minn. Stat. Chapters 16A, 16B, and 16C.
Additional governing documents include:
- Board Policy 5.14.5, Part 1
- System Procedure 5.14.5, Part 4
Minnesota State Colleges and Universities is required to follow all purchasing requirements outlined in these statutes and policies.