This video walks through the core concepts for this module. Watch it first, then use the slides below to go deeper.
Eighteen months in, his new COR started documenting concerns about deliverable timing. James was doing the work — but not managing the relationship. His CPARS rating came back Satisfactory. When the recompete posted, a competitor with Exceptional ratings won. The work was the same quality. The score on paper was not. Think of contract administration the way a first-year employee should think about their job: you earned the position, but you're on probation. Every deliverable, every interaction, every response time is being observed and documented by someone whose written assessment will determine whether you ever get another chance. The contract is the start. What you do with it is the career.
A janitorial services company won a 3-year federal contract. Year one went well. In year two, the COR changed — the new COR had different expectations around communication frequency and documentation formats, and documented two unresolved concerns over six months. When the option year decision came, the agency declined to exercise year three. The contractor never knew the relationship had problems until it was too late to fix them. The lesson isn't that the new COR was unreasonable. The lesson is that a COR change is as important as a contract award. A new COR means your relationship score resets to zero. You have to rebuild it immediately — or discover months later that the new COR had a running list of concerns you never knew existed.
Strong contract performance requires active relationship management — not just doing the work well.
When you learn your COR is being replaced, treat it like a new contract award. Within the first week of the transition: (1) Request an introduction meeting with the new COR. Don't wait for them to reach out. (2) Come prepared with a one-page performance summary — deliverables completed, milestones hit, any open items and their status. (3) Ask directly: "Is there anything about how we communicate or deliver that you'd like to do differently?" (4) Get their preferred communication channel, reporting format, and meeting cadence — and confirm in writing. A new COR hasn't inherited the goodwill you built with the previous one. Assume the relationship starts at zero and build it the same way you did the first time.
Contract award is exciting. It's also the beginning of administrative obligations that start on day one — not when work begins, not when the first invoice is due. On the day of award. Every day you delay these steps is a day you're performing without the systems that protect you.
The COR (Contracting Officer's Representative) approves your deliverables, certifies your invoices, and writes the CPARS performance ratings that will follow you into every future proposal. They don't have the authority to modify your contract — that belongs to the Contracting Officer alone — but they have something more powerful on a daily basis: they have the documentation authority. What they write in their performance notes is what becomes your CPARS rating. Every interaction you have with the COR is either building or eroding that record.
Weekly or biweekly standing calls — even when there are no issues. Especially when there are no issues. The relationship must exist before you need it in a crisis. Come to every call with a written agenda: performance-to-date summary, upcoming milestones and their status, any risks or dependencies you want to flag, and one open question for the COR. A COR who receives organized, proactive updates from you will write organized, positive performance documentation. A COR who only hears from you when there's a problem writes a different kind of documentation.
After every verbal direction or conversation that affects scope, schedule, or deliverables: send a follow-up email. "Per our conversation today, I understand you'd like [X] by [date]. I'll proceed on that basis unless I hear otherwise." This isn't bureaucratic formality — it's protection. When scope disputes arise (and they do), the contractor who documented verbal instructions wins. The contractor who relied on memory loses. If a COR ever tells you to do something that seems outside your contract scope, document it and ask: "Should we get a modification in place before I proceed?"
Never let the COR learn about a problem from someone other than you. If something is going wrong, they hear it from you first — and they hear it with your mitigation plan already drafted. The three-part problem notification: (1) What happened — a clear, factual description of the issue with no minimization. (2) Root cause — why it happened, honestly stated. (3) Mitigation plan — what you're doing about it, with a specific timeline to resolution. A COR who learns about problems early and sees a clear plan rates you on your recovery. A COR who finds out about problems late rates you on the fact that you hid them.
CORs are government employees with their own performance metrics. Your contract performance is part of their job. When you perform well, it reflects on them. When you fail, they have to document it, escalate it, and deal with the consequences — which means paperwork, senior leadership conversations, and potential program delays they have to explain. Your success genuinely serves them. Most COR relationship problems are communication problems, not competence problems — a COR who feels informed and respected gives you the benefit of the doubt. A COR who feels surprised or managed gives you the opposite.
When your COR changes mid-contract, the relationship resets. The new COR hasn't read your file, doesn't know your history of strong performance, and may have completely different expectations from the previous COR. Don't assume continuity. Within the first week: request an introduction meeting, bring a performance summary of the contract to date, ask directly about preferred communication style and reporting format, and confirm the upcoming deliverable schedule together. Treat the COR change as a mini contract award. The contractors who lose option years often lose them in the 6 months after a COR change — not because performance declined, but because no one rebuilt the relationship.
CORs maintain a performance file throughout the contract — notes on deliverable quality, communication responsiveness, meeting behavior, and anything that deviated from what was expected. This file feeds the CPARS assessment. Here's what most contractors don't realize: the COR rarely raises minor concerns in real-time. They note them, let them accumulate, and then the CPARS assessment reflects six months of silent documentation you never knew was happening. The contractor thinks everything is fine because nobody said anything. The COR's file tells a different story. The antidote is proactive check-ins with a direct question: "Is there anything about our performance or communication that you'd like to see done differently?" Asked in a standing meeting every 6–8 weeks, this question surfaces the concerns that would otherwise end up in the CPARS file unopened.
Contractor Performance Assessment Reporting System. After each performance period on contracts over $150K, the contracting officer is required to enter a formal performance assessment within 120 days of period end. Ratings are permanently visible — every agency evaluating your past performance section on future proposals will see these ratings. There is no expiration date and no way to remove them. You can only respond to them. A single rating can shape your competitive position for years.
| Rating | What It Means | What Evaluators Infer | Target? |
|---|---|---|---|
| Exceptional | Performance significantly exceeded requirements in all or most areas; any problems were resolved with exceptional management | This contractor is a differentiator — their past performance section will score higher than competitors at the same technical level | ✅ Best possible — target this |
| Very Good | Performance exceeded requirements in some areas; minor problems were well-managed and resolved | Solid and reliable — a positive indicator that won't hurt and may help in close competitions | ✅ Strong — acceptable minimum |
| Satisfactory | Performance met the minimum contract requirements; problems were resolved but required more than expected government involvement | "They did what they were paid to do." Evaluators read Satisfactory as a warning sign, not a positive indicator. In a competitive field, this rating hurts you. | ❌ Avoid — technically acceptable but competitively weak |
| Marginal | Performance did not meet some requirements; significant government-directed corrective actions were required | Evaluators see this as a red flag and may rate the past performance section low or unacceptable regardless of other factors | ❌ Serious problem — requires rebuttal |
| Unsatisfactory | Performance did not meet contract requirements; significant harm to mission or agency operations resulted | Evaluators may automatically score the past performance volume as unacceptable — effectively disqualifying the bid | ❌ Contract-ending — always challenge |
How the CPARS timeline works: After the CO initiates the assessment, you receive a notification and have 14 calendar days to review and submit a contractor comment or rebuttal. After your review period, the CO reviews your response and finalizes the rating. Your rebuttal becomes a permanent part of the CPARS record — visible to every evaluator who sees the rating. Used well, a clear rebuttal can partially offset a lower-than-deserved rating by showing evaluators that the circumstances were disputed and documented.
What makes a rebuttal effective: (1) Fact-based and specific — cite dates, deliverable records, email confirmations, and performance metrics. "We delivered all 23 reports on schedule. See attached delivery log." (2) Professional tone — avoid defensive language, personal criticisms of the COR, or emotional framing. An evaluator reading the rebuttal should come away thinking: "This contractor is organized and professional." (3) Addresses every disputed point — if the rating cites three concerns, respond to all three with specific evidence for each.
What makes a rebuttal ineffective: Vague disagreement ("We believe our performance was excellent"), attacks on the COR's judgment, or emotional language. These make a bad rating worse.
Never let an inaccurate rating go unchallenged — even if you don't believe the rebuttal will change the final rating. The rebuttal is in the permanent record and gives future evaluators additional context.
Many contractors receive a Satisfactory CPARS rating and think "that's basically a B, good enough." In federal proposal evaluation, Satisfactory past performance typically earns a past performance confidence rating of "Satisfactory Confidence" or lower — which in most LPTA (Lowest Price Technically Acceptable) competitions is fine, but in Best Value competitions, a Satisfactory CPARS rating against a competitor's Very Good or Exceptional can cost you the award even if your technical approach and pricing are identical. The difference between Satisfactory and Very Good is often a single conversation — a formal check-in where you asked what you could do better and then actually did it.
The federal government must pay proper, clean invoices within 30 days under the Prompt Payment Act (31 U.S.C. § 3903). If payment is late, interest accrues automatically — you don't need to request it. The key word is "proper." An invoice with a single wrong field is rejected, and the 30-day clock restarts from the corrected submission date. Most small contractors experience their first payment delays because of invoice errors, not agency slowness.
Every rejection restarts the 30-day clock from the corrected submission date. One error costs you 30 days of cash flow.
If your invoice was properly submitted and 30 days pass without payment: (1) Contact the COR and confirm acceptance was certified. (2) If certified, contact the CO to flag the payment delay — cite the Prompt Payment Act and the submission date. (3) Contact the agency's payment office directly (listed in the contract or the agency's finance office). Late interest begins accruing automatically — you don't need to file a separate claim, but you do need to track the days. Texas has a similar Prompt Payment Law (Texas Government Code §2251) for state contracts — 30-day payment requirement with automatic interest.
If your monthly payroll and overhead is $50,000, you need $100,000 in available cash to bridge that 60-day gap before your first payment arrives. Most first-time contractors underestimate this by half and hit a cash crunch in month two.
Business line of credit: Apply with your bank before your first contract — banks lend based on business history, not future contracts. Get the credit line in place when you don't need it. Draw on it to bridge payroll during the 60-day gap.
Invoice factoring: You sell your government receivables to a factoring company at a discount (typically 1.5–5% of invoice value) and receive cash immediately. The factoring company collects from the agency when payment arrives. This is expensive capital — a 3% fee on a $100K invoice costs $3,000 — but it's available fast and doesn't require an established credit history. Many small federal contractors use factoring specifically for government receivables.
SBA financing: SBA 7(a) loans and the SBA's Contract Loan program can provide working capital secured against government contract receivables. Lower cost than factoring but slower to access. Apply before you have a cash need, not during one.
Your first contract delivery is also your first past performance record. Use Alex to set up the right systems before work begins.
Government contracts change — scope expands, timelines shift, requirements evolve. Every significant change requires a formal contract modification. Every option year must be actively earned. The contractors who fail at this stage are usually the ones who performed excellent work but treated the administrative side as paperwork rather than strategy.
Never perform work outside your contract without a signed modification from the Contracting Officer. The COR may ask you for additional work, genuinely believing they can authorize it — but legally, only the Contracting Officer has modification authority. If the COR asks you to do something outside your current scope: "I want to support this. Let me get a modification in place with the CO first so I can move forward properly." Unauthorized work often doesn't get paid because there's no contractual obligation to pay for it — and even when agencies try to pay for it after the fact, there are legal hurdles. The contractor who performs unauthorized work takes all the risk and has no guaranteed remedy.
A constructive change occurs when government personnel informally direct you to perform work beyond your contract scope — without a formal modification. The COR asks you to add a deliverable. The program manager says "while you're at it, can you also..." These informal directions are legally compensable changes even without a formal mod — you have the right to request an equitable adjustment from the CO for the additional costs incurred. The key: document the informal direction immediately (the "per our conversation" email), perform if the relationship requires it, and promptly notify the CO that the work constitutes a constructive change and that you'll be requesting a modification. Contractors who absorb informal scope additions silently lose money and erode the only relationship that matters. Contractors who document and address them properly get paid and protect their rates.
On a standard 5-year IDIQ contract (1-year base + 4 one-year options), each option decision is a revenue event worth the full annual contract value. A $500K/year contract has $2M in option value sitting behind the base period. Each performance period is effectively a competitive bid for the next one — except you're the incumbent, which is a significant advantage. Incumbents win recompetes at much higher rates than non-incumbents, but only when they've managed the relationship and the paperwork with the same discipline they applied to the technical work.
The language of contract administration — used every day once you're performing. These terms appear in every contract, every modification, and every compliance conversation you'll have as a performing contractor.
| Term | Definition |
|---|---|
| CO (Contracting Officer) | The government official with legal authority to enter into, administer, and terminate contracts. Only the CO can modify a contract. The CO is the legal authority — distinct from the COR, who handles day-to-day oversight. All formal contract actions (award, modification, termination) require the CO's signature. |
| COR (Contracting Officer's Representative) | The government technical authority delegated by the CO to manage day-to-day performance, receive and accept deliverables, certify invoices for payment, and document performance for CPARS assessments. The COR cannot modify the contract — only the CO can. But the COR writes the performance documentation that shapes your CPARS rating. Your most important daily relationship on every contract. |
| CPARS | Contractor Performance Assessment Reporting System — the permanent federal database of contractor performance ratings. Required for contracts over $150K. Initiated by the CO, with COR input. Ratings (Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory) are visible to every agency evaluating future proposals. Contractor has 14 calendar days to review and submit a rebuttal before ratings are finalized. |
| CLIN (Contract Line Item Number) | The numbered billing line items in your contract corresponding to specific deliverables, labor categories, or periods of performance. Your invoices must reference CLINs exactly as written in Section B — any deviation triggers rejection and restarts the 30-day payment clock. |
| Prompt Payment Act | Federal law (31 U.S.C. § 3903) requiring agencies to pay proper invoices within 30 days of receipt or acceptance. Late payments automatically accrue interest — no separate request required. Texas has a parallel Prompt Payment Law (Texas Government Code §2251) with the same 30-day requirement for state contracts. |
| Contract Modification (Mod) | A formal change to a contract signed by the CO. Bilateral mods require both parties' signatures (scope, price, or term changes requiring contractor agreement). Unilateral mods are signed by the CO alone (administrative changes, option exercises). The only legal mechanism for changing contract scope, price, or terms. Unauthorized work performed without a mod is generally not billable. |
| Constructive Change | When government personnel informally direct you to perform work beyond the contract scope — without a formal modification — you may have a compensable change. Document the informal direction immediately, notify the CO promptly, and request an equitable adjustment for the additional costs. Contractors who absorb constructive changes silently lose money and establish a precedent of free scope expansion. |
| Option Year / Base Period | Federal contracts are typically structured as a base period (e.g., 12 months) plus one or more option periods (each requiring an affirmative government decision to exercise). The government has no obligation to exercise options — each one must be earned through strong performance in the preceding period. On a base + 4 options contract, there are four separate option exercise decisions over the contract's life. |
| Cure Notice | A formal government letter notifying the contractor of a failure to make progress or a potential default, giving 10 calendar days to cure (correct) the deficiency. Failure to cure to the government's satisfaction can lead to a Show Cause Notice and potential termination for default. Receiving a Cure Notice is a serious escalation — respond in writing immediately with a specific corrective action plan. |
| Termination for Convenience vs. Termination for Default | Termination for Convenience (T4C): The government's right to end a contract at any time for its own reasons, unrelated to contractor performance. You are entitled to reimbursement for reasonable costs incurred and a negotiated profit. Termination for Default (T4D): Termination due to contractor failure to perform. You may be liable for excess re-procurement costs and lose your right to payment for unaccepted work. A T4D is extremely damaging to future proposals. If the government threatens T4D, immediately engage a contracts attorney. |
| IPP / iRAPT | IPP (Invoice Processing Platform) — the civilian federal agency invoicing system at ipp.gov. iRAPT (formerly WAWF — Wide Area Workflow) — the DoD invoicing system at piee.eb.mil. Your contract will specify which system to use. Set up your account before your first invoice is due — account approval can take 1–2 weeks. |
A scenario that plays out on hundreds of contracts every year. Before you choose, read the concept below — it explains exactly why "no news is good news" is one of the most expensive beliefs in government contracting.
CORs maintain an ongoing performance file throughout the contract. They note deliverable quality, response times, communication gaps, and anything that deviated from expectations. This file feeds directly into the CPARS assessment. Here's the behavior pattern that catches contractors off guard:
CORs rarely raise minor concerns in real-time. The response time on a deliverable was 2 days longer than expected — they note it but don't mention it. The monthly report format wasn't quite what they asked for — they note it but let it go. The quarterly review meeting felt disorganized — they note it. None of these becomes a conversation. All of them become ratings inputs.
By the time you're 2 months from contract end with no feedback, the COR's file may already contain 6 months of documented concerns you have no knowledge of. The CPARS rating that comes back Satisfactory isn't a surprise to the COR — it's the numerical expression of documentation that was accumulating the entire time.
The only way to interrupt this pattern is to proactively create the opening for those concerns to surface — before they become permanent ratings.
You've been performing a 12-month facilities management contract for a Texas state agency. The work has gone well by your standards — you've hit your deliverable dates, your team shows up, nothing has broken down. With 2 months left in the base period, you realize you haven't received any formal feedback from the COR, no mid-term assessment, and no performance concerns raised. You assume no news is good news.
Make a choice above, then continue to the knowledge check.
Three quick questions to lock in what you just learned. Click any answer — right or wrong, you'll see the full explanation. The goal is retrieval, not a grade.
Contract administration is where government contractors either build a lasting business or quietly lose it. These deliverables are operational — each one produces a system or document you'll use on your first contract from day one of award. Don't skip the ones that feel premature. Building the system before you need it is the entire point.
Track every active contract, upcoming option year date, and new opportunity in one place. BidWatchHQ's pipeline keeps your deliverable calendar, option year windows, and new bid activity visible at a glance — so your 90-day option year campaign never starts late and nothing falls through the cracks.
BidWatchHQ tracks federal and Texas procurement deadlines daily so you never miss a solicitation, Sources Sought, or option period renewal window in your target markets.
Start Free Trial →