What to Do After You Submit a Proposal

The moment your proposal is uploaded, the work is not over — it just changes. What you do after proposal submission matters almost as much as the proposal itself: it protects your submission, teaches you how to write a stronger next one, and keeps your pipeline moving while you wait. Too many small contractors treat submission as the finish line, then sit idle for weeks wondering what happened. This guide covers the six steps to take after proposal submission — from confirming receipt to requesting a debrief, handling a win or a loss, and deciding whether a protest makes sense.

Step 1: Confirm Receipt and Keep Records

The first thing to do after proposal submission is confirm that the government actually received it. Do not assume the upload worked. Check for the confirmation email or submission receipt from the portal, save it, and verify that the files listed in the receipt match the final versions you submitted. If the portal shows a status page, take a screenshot or save a copy. If the RFP required submission by email, keep the sent message and any delivery confirmation.

Then build your submission record: a folder containing the exact proposal as submitted, the confirmation receipt, the RFP and any amendments, the compliance matrix, the pricing build, and a short note of who submitted it and when. This record is your protection if anything is disputed later — a missing file, a late-submission claim, or a question about what you actually proposed. It is also the starting point for your debrief, because months from now you will not remember the details of a proposal you wrote in a hurry. Keep the record organised and keep it for at least the life of the contract, and longer if your own record-retention policy says so. This is unglamorous work, and it is the work that saves you when something goes wrong.

Step 2: Understand What Happens During Evaluation

After proposal submission, your proposal enters evaluation — a process that is mostly invisible to you and takes longer than most new bidders expect. A typical timeline runs from a few weeks for a small, simple procurement to several months for a large or complex one, and delays are common: evaluators have other duties, clarifications take time, and protests or funding questions can pause everything. Do not read silence as bad news. Silence is the normal state of an evaluation.

What actually happens inside is straightforward in shape, even if the details vary. Evaluators — usually a team from the requiring activity and the contracting office — read each proposal against the evaluation factors stated in the RFP: technical approach, past performance, key personnel, and price. They score, compare, and document their findings. The contracting officer may send written questions, called clarifications or discussions, asking you to explain or confirm something in your proposal. Answer these promptly and precisely: a clarification is a chance to strengthen your position, not a trap, and a slow or sloppy answer can undo a strong proposal. While you wait, resist the urge to contact the evaluators directly — communication during evaluation is restricted, and an improper contact can hurt you. If you have a genuine question, route it through the contracting officer in writing, as the RFP directs.

Step 3: Request a Debrief — Win or Lose

Whether you win or lose, request a debrief. It is the single most useful thing you can do after proposal submission, and it is a right the government is generally required to honour. There are two kinds. A pre-award debrief happens when you are eliminated from the competition before award — you can ask for one, and the agency will usually provide it. A post-award debrief happens after the award is announced, and you should request it promptly: for most procurements, you should ask within a few days of learning the outcome, because there are time limits and because the details are freshest then.

Prepare for the debrief like you prepared the proposal. Before the meeting, write down what you want to learn: how your technical approach scored, how your past performance was rated, where your price stood relative to the winner, and what specific weaknesses the evaluators noted. During the debrief, listen more than you talk. Ask open questions — “What was the biggest weakness in our technical approach?” and “What would a stronger proposal have shown?” — and write down the answers. The debrief is not the place to argue or to relitigate the evaluation; it is a learning session, and the agencies that give the most useful debriefs are the ones that sense you are genuinely listening.

Afterwards, write up what you heard the same day, while it is fresh, and share it with the team that wrote the proposal. A debrief that is never written down is a debrief that is forgotten within a week. Over time, these notes become a map of what your company needs to improve — and that map is worth more than any single award.

Step 4: If You Win — Kickoff and Transition

Winning is the start of a new job, not the end of the old one. The first thing after an award is the kickoff: a meeting with the contracting officer and the government’s technical representative to confirm the scope, the schedule, the points of contact, and the deliverables. Come prepared. Bring the proposal, the pricing build, and the staffing plan, and be ready to confirm that the people you proposed are the people who will actually do the work — the government will notice if a key person named in your proposal never appears.

Then manage the transition. If you are replacing an incumbent, there is usually a transition period: learn the incumbent’s processes, take over the work without disrupting the mission, and build a working relationship with the government team. Deliver the first deliverables on time and to the standard you promised in the proposal, because the first ninety days set the tone for the whole contract. And start building your past performance record from day one: keep notes on what you delivered, when, and what the government said about it. That record is the raw material for your next proposal’s past performance section — and it is far easier to collect while the work is happening than to reconstruct a year later.

Step 5: If You Lose — Learn, Then Decide About a Protest

Losing a bid hurts, but a loss handled well is an investment in the next win. Start with the debrief — it is the main tool for learning why you lost. Then do your own honest review: was the price too high, was the technical approach weak in a specific area, was the past performance thin, or did the winner simply have a stronger offering? Compare what the debrief told you against your own reading of the proposal. The gap between what you thought you wrote and what the evaluators saw is where the real lesson lives.

Then decide whether a protest makes sense. A bid protest is a formal challenge to the award, filed with the Government Accountability Office or the agency, arguing that the evaluation was flawed — for example, that the government misapplied its own evaluation criteria or treated bidders unequally. Protests have strict deadlines, typically measured in days from when you learn the basis for the protest, so do not delay the decision. But be clear-eyed about the odds: a protest is worth pursuing when you have specific, documented evidence of an evaluation error, not merely because you are disappointed. A weak protest costs time, money, and goodwill with the agency. A strong one, grounded in the debrief and the record, can overturn an award or at least force a re-evaluation. If you are considering a protest, get legal advice before you file — the rules are technical, and a missed deadline or a poorly framed argument can end the protest before it starts.

Whatever you decide, close the loss properly: thank the contracting officer, record the lessons, and keep the relationship warm. The agency will have another requirement someday, and a gracious loser is remembered far better than a bitter one.

Step 6: Keep the Pipeline Moving

The last step after proposal submission is the one most small contractors skip: keep selling. A submitted proposal is not a won contract, and a pipeline with one opportunity in it is a pipeline that can go to zero overnight. While you wait for the evaluation, keep pursuing new opportunities: watch for new solicitations, nurture the relationships that produce them, and start the next proposal. The best time to work on the next bid is while the last one is being evaluated — your team is warm, your content library is current, and the lessons from the last proposal are fresh.

Use the waiting time productively. Update the content library with the material from the proposal you just submitted. Refresh the resumes of the staff who were proposed. Review your proposal compliance checklist and your templates against what the last bid taught you. And if the proposal was written under a short proposal deadline, note what the compressed schedule cost you and what you would do differently next time — that note is the seed of a better process. A healthy pipeline and a learning organisation are what turn one submitted proposal into a steady stream of wins, and both are built in the weeks after submission, not during the writing sprint.

Related Guides

• How to Build a Price Proposal
• How to Write a Proposal Executive Summary
• How to Write a Technical Approach