The quiet is the normal state, not the answer
The call went well. There was real technical interest, a named pursuit, a promise to circle back. Then nothing for seven months, and the founder starts rereading the meeting notes for the sentence that killed it. There usually is no such sentence. Federal pursuits run on calendars measured in quarters, a capture lead carries a dozen at once, and the person who was enthusiastic in March is graded in October on something with a different name. What ends is not the relationship. What ends is the reason to write, and most firms treat the absence of a reason as an instruction to wait.
It helps to define what a warm relationship is in operational terms, because "warm" as a feeling cannot be managed. A partner relationship is warm when three things are true at once. Your firm sits in a file that survives the departure of the person who created it. That file is current enough that nobody has to ask you for a document before your name can be put on anything. And there is a next contact on somebody's calendar with a date on it, placed there by you rather than by an event. Everything else is sentiment, and sentiment does not survive a reorganization.
The good news in this is mechanical. The dates a federal partner works to are published, fixed, and mostly the same across every prime you will ever talk to. You can build a year of well-timed contact from public regulation without ever asking the partner what their calendar looks like.
Four reasons a partner goes quiet, and only one is about you
The pursuit moved. This is the most common cause by a wide margin. The government's own publicity rules build months of dead air into every acquisition: under FAR 5.203, a presolicitation notice is published at least 15 days before the solicitation is issued, agencies allow at least 30 days for receipt of proposals above the simplified acquisition threshold, and at least 45 days for research and development. Then evaluation runs, and evaluation is silent. A partner who told you in February that the request for proposals was imminent may be telling the truth in November.
The champion changed programs. Capture and program staff rotate. When the relationship lived in one person's head and that person moves, the memory of your delivery moves with them and nothing in the company record replaces it.
Your file went stale. Compliance and supply chain staff re-run their checks each time a teammate is added to a bid. If your registration lapsed, your cyber assessment aged out, or your insurance certificate expired, you are now a task rather than an asset. Nobody sends an email explaining this. They just choose the firm whose paperwork is already clean.
You were never in a file at all. The conversation lived in an inbox, was never entered into a supplier record, and produced no document a stranger could read. This is the failure that feels like a relationship problem and is actually a records problem.
Only the third reason is a self-inflicted wound, and it is the cheapest of the four to fix. The fourth is fixable by you as well, though it takes deliberate effort to put a durable artifact in someone else's system.
What moves a quiet partner back into a working conversation
Editorial weighting from public regulation and practitioner reading. Illustrative ranking of what earns a reply, not a measured statistic.
Read those bars as an ordering rather than as measurements. The top three are the ones that remove work from the partner's desk, which is the whole mechanism: a re-engagement lands when it makes somebody's next task easier, and it is ignored when it adds one. The bottom row is the weakest of the six and still worth doing, because appearing independently in the same public record as your partner gives them a costless reason to call you.
The partner's year is fixed, published, and not about you
A prime contractor's calendar is shaped by a small number of dates that repeat every year. None of them are secret. Knowing them turns "I should check in sometime" into a schedule.
The first is the end of the federal fiscal year. Under 31 U.S.C. 1502(a), the balance of an appropriation limited for obligation to a definite period is available only for payment of expenses properly incurred during that period, or to complete contracts properly made within it. That single sentence produces the September push that everyone in federal work has experienced from one side or the other. A firm that appears in mid-August with a scope small enough to place before the year closes is arriving at the moment when placing work is the priority.
The second set comes from subcontracting plan reporting. FAR 19.704 requires Individual Subcontract Reports semi-annually for the periods ending March 31 and September 30, submitted within 30 days of the close of each period and within 30 days of contract completion, and a Summary Subcontract Report annually by October 30 covering the twelve months ending September 30. A prime carrying a plan is therefore counting small business dollars in April and October, in writing, against goals it committed to. Those are the two months of the year when a clean one-page summary of what your firm delivered, with dollar values, is worth the most to the person receiving it.
The third is performance evaluation. FAR 42.1502 requires past performance evaluations at least annually and at the time work under a contract or order is completed, and FAR 42.1503 gives the contractor up to 14 calendar days from notification to submit comments or rebutting statements. A prime writing its annual evaluation is reconstructing a year it half remembers. Your factual summary of the piece you performed, sent before the evaluation is drafted, is genuinely useful to them and shapes the record that describes you.
The fourth is the option and recompete clock. FAR 17.204(e) holds the total of the basic and option periods to five years for services, with information technology contracts excepted and other statutes capable of tightening it further. Services vehicles therefore have bounded lives, and the follow-on conversation belongs on the calendar about a year before the end, not a month before.
| Window | What is happening on the partner's side | What lands |
|---|---|---|
| Late April | Individual Subcontract Report filed for the period ending March 31, within 30 days of close | A one-page record of what you delivered, with dollar values, easy to count |
| May to July | Pursuits qualified for the next fiscal year against published agency forecasts | A named pursuit and the gap you would close, written in the customer's language |
| August to September 30 | Funds reaching the end of their period of availability under 31 U.S.C. 1502(a) | A scope small enough to place now, already priced, with availability stated |
| By October 30 | Summary Subcontract Report filed for the year ending September 30 | A short note on what you would take next year, with current rates attached |
| Contract anniversary | Past performance evaluation prepared at least annually under FAR 42.1502 | A factual summary of your portion, sent before the evaluation is written |
| Twelve months before option end | Recompete planning inside the five-year services ceiling at FAR 17.204(e) | The follow-on conversation, opened while the approach can still change |
Keep the file current, because the file is what gets checked
The single highest-return habit in the gap has nothing to do with communication skill. It is keeping the documents a partner will re-verify in a state where nobody has to ask.
- SAM registration active and reviewed. FAR 52.204-13 requires a contractor to maintain registration during performance and through final payment, holds the contractor responsible for the currency and accuracy of the data, and requires review and update on an annual basis. A lapsed registration is read as a signal about everything else you maintain.
- A cyber assessment that has not aged out. For Department of Defense work, DFARS 252.204-7019 requires a current assessment, defined as not more than three years old unless the solicitation specifies less, with summary level scores posted in the Supplier Performance Risk System 30 days after assessment. A partner can see whether a score is posted and how old it is without asking you.
- Insurance certificates and a current W-9, dated within the year, in the same folder as everything else.
- Size representation under the codes that matter, computed the way the regulation computes it, with the basis stated rather than asserted.
- Named availability for the one or two people who would actually do the work, with the percentage and the date the statement was made.
- A one-paragraph statement of where you stand on certification, with the date you assessed and what you are doing next.
That last item deserves a note in the second half of 2026, because the ground is moving. The Department of War suspended Phase 2 assessment requirements of the Cybersecurity Maturity Model Certification program through memoranda issued on July 13, 2026, pausing a phase that had been scheduled to begin on November 10, 2026. The underlying program rule was not repealed. Self-assessment, score posting, annual affirmation, and the safeguarding and 72-hour reporting duties under DFARS 252.204-7012 continue to operate. This is a genuinely unsettled area, and the honest version is more useful to a partner than a confident one: say where you stand, give the date, and say what happens next.
Send the refreshed packet as a single dated file, unprompted, twice a year. It is the least clever thing in this article and the most reliable. A partner who has to ask you for a current document has already been reminded that you are work.
Three touches worth sending, and the one that is not
An artifact they can use without hiring you. A short technical note on a problem the partner has mentioned. A small reproducible benchmark. A one-page read of a rule change that affects their program. The test is whether the thing has standalone value if the recipient never replies. This is also the only touch that gets forwarded internally, which is how your name gets into a file you do not control.
A pursuit with the fit already argued. Not a link. A named opportunity, the evaluation criterion you would strengthen, the specific tasks you would own, and one sentence on why the customer would find that credible. The work of connecting an opportunity to a capability is the work the capture lead does not have time to do, which is exactly why doing it for them earns a reply.
A record they can cite. If your firm performed as a first-tier subcontractor on a contract that carried a subcontracting plan, you can request a written rating of your subcontractor past performance from the prime under 13 CFR 125.11, and the prime is required to provide it within 15 calendar days. The mechanics of that request and what it covers are worked through in our note on alliance management for technical firms. Asking for it is also a legitimate reason to open a conversation with someone who has gone quiet.
The touch that is not worth sending is "just checking in." It transfers the work of finding a reason to the busiest person in the exchange, and it makes the sender's need the subject of the message. It also trains the recipient to skim your name. If there is genuinely nothing to send, the correct move is to wait until the calendar produces a date, which it will within about ninety days.
Show up in the same public record, separately
Market research is a public process and it happens long before a teaming decision. FAR 10.002 lists the techniques agencies use, including contacting knowledgeable individuals in government and industry about market capabilities, publishing formal requests for information, querying government databases, and holding presolicitation conferences. Responses shape the acquisition strategy and inform whether the work can be set aside for small business.
Two things follow for a firm in the gap. First, responding to a market research notice on your own is one of the few ways to influence a requirement before it hardens, and it costs a day. Second, when your partner sees your name in the same record, the conversation restarts without either party having to manufacture a pretext. The follow-up writes itself: we both answered the same notice, here is the piece we would carry, here is our current file.
Timing is tight once a requirement surfaces, which is the argument for being early. FAR 5.203 sets the 15-day presolicitation window and the 30-day and 45-day minimum response times, and it also allows a covered acquisition's response period to be shortened to as little as 10 days when the acquisition was identified in an annual forecast. Forecasts themselves are discretionary rather than mandatory. FAR 5.404 says agencies may publicize long-range acquisition estimates as far in advance as possible to help industry plan, and many do. Reading them well is its own skill, covered in our note on parsing federal acquisition forecasts.
Build the partner's calendar from public data
You do not need the partner's cooperation to know when they will need help. Award records in the federal procurement data system and on USAspending carry period-of-performance end dates, which bound when a recompete has to happen. Read against the five-year services ceiling, those dates tell you which of a partner's vehicles are late in life.
Subaward reporting adds a second layer. Under FAR 4.1403(a), the clause at FAR 52.204-10 goes into solicitations and contracts of $40,000 or more, and the clause requires the prime to report each first-tier subcontract at or above the threshold at fsrs.gov by the end of the month following the month of award. That produces a public trace of who a prime already subcontracts to, in what size, and roughly when in the year it places work. A firm that has read this before a call knows whether it is proposing something the partner already buys elsewhere, which is a different conversation from the one most firms open with.
None of this is exotic research. It is an afternoon per partner, refreshed twice a year, and it converts an anxious relationship into a planned one.
A twelve-month cadence that never requires inventing a reason
The commercial version of the same gap
A consultancy, a systems integrator, or a software vendor partner has the same structure with different labels, and the labels are usually published. Partner programs run on tiers, and tiers are re-evaluated on a fixed date. Deal registrations expire, often after a defined number of days, and an expired registration quietly removes the protection that made the partnership economically interesting. Renewal dates for the partner's own customer contracts are the moments when scope gets re-opened.
The most useful thing to understand about a commercial partner manager is what they are measured on, because it is rarely your success. It is usually sourced pipeline, certified headcount, and joint wins in the current quarter. A firm that hands a partner manager one qualified opportunity they did not have, in the month before their quarter closes, will get more attention than a firm that sends a well-designed relationship update. The equivalent of the federal refresh packet is a current one-page partner profile: certifications and their dates, named engineers, reference customers you are permitted to name, and the two or three motions you actually want to run together.
The rhythm that works on the commercial side is a real quarterly review with an agenda and a written outcome, plus one substantive contact between reviews. Anything more frequent without content becomes noise, and anything less frequent means the joint plan is a document nobody is executing.
The re-entry note after a long silence
Assume it has been a year. The instinct is to apologize for the gap and ask for a call to reconnect. Both moves are weak: the apology makes the silence the subject, and the call request asks for thirty minutes before offering anything.
A better shape is four short paragraphs. One line on what changed at your firm that is relevant to them, expressed as capability rather than news. The artifact, attached, with a sentence on what it is and why they might care. The specific pursuit or recompete you have in mind, with the date and the piece you would carry. Then one small ask, sized so that yes costs almost nothing: forwarding the file to whoever owns that pursuit, or confirming whether that lane is still active for them.
Send it to the person who has the problem, and copy the person who owns the paperwork if you know them. Do not attach a deck. If a deck is going to be the second step, make it one that survives being forwarded and read alone, which is a different document from the one used in a meeting; the anatomy is in our note on a partner-facing capability deck. And put a date on your own calendar for the follow-up before you hit send, because the discipline that keeps relationships warm is scheduling the next contact while the current one is fresh.
When the relationship is actually over
Some of them are, and continuing to invest in a closed relationship is expensive in a way that is hard to see because the cost is time rather than money. Three signals are worth taking seriously.
Repeated non-response from more than one person. One person going dark is a workload story. Two or three people at the same organization ignoring substantive, useful messages is an organizational answer.
Your capability was absorbed. The partner hired the team, acquired the tool, or built it. This is common and is not a betrayal. It does change the arithmetic permanently, and the right response is to move the relationship to a different lane or move on.
The pursuit was lost and there is no next one. If the vehicle that justified the partnership went to a competitor and the partner has no adjacent pursuit in your lane, the relationship has no work to attach to. Keep the file current, keep the contact alive at low cost, and put your active effort where there is a scope with a date on it.
Deciding this deliberately is better than drifting. It is the same judgment as declining a teaming offer that does not fit, and the reasoning is worked through in our note on when to decline a teaming offer.
Bottom line
Partner relationships do not stay warm because people liked each other. They stay warm because a firm is inside a durable record, that record is current, and contact arrives on the dates when the partner is already thinking about the thing the contact is about. Every one of those dates is public: the fiscal year end that governs when money must be placed, the April and October subcontracting reports, the annual performance evaluation, the option and recompete clock, and the market research notices that appear before any of it. Build the calendar once, keep one dated file current, send things that would be useful even if nobody replied, and put the next contact on the calendar before the current one ends. The firms that get called back are not the most memorable ones. They are the ones that are easiest to pick up and use.
Frequently asked questions
Roughly every six to ten weeks, and only with something that has standalone value. Anchor the schedule to dates the partner already works to rather than to arbitrary intervals: the April and October subcontracting reports under FAR 19.704, the annual performance evaluation cycle under FAR 42.1502, the end of the federal fiscal year, and the option or recompete dates you can read from public award records. That produces five or six natural contacts a year without inventing a pretext for any of them.
One dated file containing the entity identifiers and registration status, size representation under the relevant codes, socioeconomic categories and whether each is certified or self-certified, current insurance certificates and a W-9, current labor rates, cyber posture with the assessment date, and named availability for the people who would do the work. FAR 52.204-13 already obliges a contractor to review and update SAM information annually, so the packet is largely a byproduct of work you owe anyway.
Yes, in a specific case. A small business that performed as a first-tier subcontractor on a contract that included a subcontracting plan can request a rating of its subcontractor past performance from the prime under 13 CFR 125.11, and the prime is required to provide it within 15 calendar days. Request it at closeout while the people who watched the work are still assigned, and file the result for later past performance volumes.
Generally no, unless you have an exclusivity commitment in writing that says otherwise. Market research responses under FAR 10.002 shape the acquisition strategy and the set-aside decision, and two independent responses describing complementary capability are useful to the contracting officer. Tell the partner you are responding and say what you are describing, so the two responses do not contradict each other on scope.
Months, and often longer than either party expects. FAR 5.203 requires a presolicitation notice at least 15 days before the solicitation is issued, at least 30 days for receipt of proposals above the simplified acquisition threshold, and at least 45 days for research and development, before evaluation even begins. Evaluation itself is silent and can run for a long time. Silence during that window carries no information about your standing.