Contract administration after award: who owns the obligations

Reference article · 5 min read

Award is a milestone, not a finish line. The procurement office runs the solicitation, resolves any protest, and gets a signed agreement in place. The work then moves to a department that has to receive the software, review invoices, accept or reject deliverables, and hold the vendor to its promises for years. That transfer is where contract administration problems usually begin, because the people who know the agreement best are rarely the people who will live with it.

Contract administration is a set of written artifacts that let a new employee, on a Monday morning, determine what the agency owes the vendor, what the vendor owes the agency, who may approve a change, and what date something expires. If those answers live only in one person's memory and inbox, the agency is one resignation away from renewing a contract it does not understand.

Run a real handoff, not an email forward

Hold a post-award session with the contract specialist who ran the procurement, the department that will use the system, and the technical lead, before anyone meets the vendor. Cover four things.

What the contract actually is. The signed agreement, the incorporated solicitation and proposal, negotiated exceptions, the order of precedence clause, and every attachment. Agencies often administer a base agreement while the binding detail sits in an exhibit nobody opened.
What changed during negotiation. Terms the vendor resisted, limits the agency accepted, and commitments made in clarifications or best and final offers.
What the agency promised. Contracts obligate the buyer too: data extracts, test environments, staff availability, timely reviews, facility access. Missed agency obligations are a common root of excusable vendor delay.
Where the money comes from. Funding source, encumbrance, whether a grant imposes terms that flow down, and what happens at fiscal year end.

Write the result down. A one or two page administration plan naming roles, meeting cadence, and escalation path is enough.

Build an obligations register

An obligations register lists every promise in the contract with the clause reference, who owes it, when it is due, the evidence required, and its current status. Read the contract once with that as the only goal, since obligations are scattered across exhibits, general terms, and the scope of work.

Pair the register with a deliverable and milestone calendar. Acceptance clauses usually give the agency a defined review window, and silence is often deemed acceptance. Track when each deliverable arrives, when the review period closes, and who signs the acceptance or rejection, so the agency never accepts defective work by letting a clock run out.

Separate the three roles and their authority

Confusion among these three jobs is how unintended contract modifications happen.

Contract administrator. Usually in procurement, or a designated department role. Owns the contract file, processes amendments, issues formal notices, and is typically the only person who may change price, scope, schedule, or terms. If it costs money or alters an obligation, it routes here and is executed in writing by whoever holds signature authority.
Project manager. Owns day to day performance: schedule, meetings, issue and risk logs, invoice review, and coordination across agency units. May direct work within the existing scope but cannot expand it.
Technical lead. Owns the substance: architecture review, integration and security requirements, test results, and the judgment behind accepting or rejecting a deliverable. Recommends acceptance rather than granting it alone, unless the contract assigns that authority.

Put those limits in writing and tell the vendor who holds them. A vendor can generally rely on direction from someone who appears authorized to give it, so a technical lead who casually approves extra work can create a claim.

Track the dates that cost money

Renewal and pricing dates need their own tickler, independent of any individual's calendar:

Term end and each renewal option, with the date by which the agency must give notice to renew or decline.
Rate adjustment dates, any index tied to them, and whether an increase requires agency consent.
Maintenance and subscription anniversaries, which often renew automatically unless the agency acts.
Insurance certificates, bonds, security attestations, and required audit or compliance reports.
Notice addresses and the required delivery method. Notice clauses are formalistic, and email to a project contact often does not satisfy them.

Set reminders far enough ahead to run a market check or a new solicitation if the agency decides not to renew.

Keep a contract file that survives turnover

The file belongs in a shared location with controlled access, not a personal drive. It holds the executed agreement and all amendments, the register, correspondence that interprets or waives anything, deliverable submissions with acceptance or rejection letters, invoices, and notices. Document decisions when they happen, including why the agency accepted a workaround or extended a date, and write performance notes contemporaneously. That record is what a future evaluation team, auditor, or successor will rely on.

How to start, and what to require

If a contract is already running and none of this exists, work backward: pull the agreement and every amendment, build the register, extract the dates, and confirm in writing who holds approval authority today. For contracts still being drafted, require the mechanics up front. Name the vendor's contract manager and notice recipients. Define an acceptance process with review periods and rejection rights. Require reporting that produces the evidence the register needs. Include transition and data export obligations that survive termination. State that only a written amendment signed by the authorized agency official changes the agreement.

Amendment thresholds, delegated signature authority, and records retention rules vary by jurisdiction and change over time, so confirm specifics with your procurement policy and counsel.

HQT works with state and local agencies on the technology side of these contracts: deliverable definition, acceptance criteria, and requirements that make performance measurable.

Frequently asked questions

Who is responsible for managing a contract after it is awarded?

Responsibility is usually shared. A contract administrator, often in the procurement office or a designated department role, owns the contract file, amendments, and formal notices. A project manager runs day to day performance and invoice review, and a technical lead evaluates the work itself and recommends acceptance or rejection. The agency should name all three in writing at handoff so the vendor knows who to contact for what.

What is an obligations register and how do we build one?

An obligations register is a single list of every commitment in the contract, including the ones the agency itself owes. Build it by reading the executed agreement and all attachments once with the sole goal of extracting promises, then record for each one the clause reference, the responsible party, the due date or trigger, the evidence that proves completion, and the current status. Review it on a set schedule rather than only when a problem appears.

Can a project manager or technical lead approve extra work on a contract?

Generally no, unless the contract or a written delegation gives them that authority. Changes to price, scope, schedule, or terms normally require a written amendment executed by the official with signature authority. Informal approvals given in status meetings can still expose the agency to a claim, because vendors may argue they relied on direction from someone who appeared authorized, so route all change requests to the contract administrator.

What should be kept in a government contract file?

Keep the executed agreement and every amendment, the solicitation and accepted proposal, the obligations register, correspondence that interprets or waives a requirement, deliverable submissions with the agency's acceptance or rejection letters, invoices and payment records, performance notes, and all formal notices. Store it in a shared location with controlled access rather than an individual's drive or mailbox. Retention periods and public records obligations vary by jurisdiction, so confirm requirements with your records officer or counsel.

When should we start preparing for a contract renewal decision?

Start well before the notice deadline stated in the contract, not before the term end date, since the two are different. Work backward from the notice date and allow time to review performance, check market pricing, and run a new solicitation if the agency decides not to renew. Track maintenance and subscription anniversaries separately, because those often renew automatically unless the agency gives timely written notice.