The post-submission follow-up is where most firms destroy the goodwill their proposal created. "Just checking in" tells the client exactly one thing: you have no new information to offer. Here's how to replace the anxiety email with follow-up that actually advances the deal.
There's a moment every architecture principal and BizDev lead knows. The proposal went out three days ago. Maybe five. The silence is building. You know you need to follow up — the pursuit can't just float indefinitely — but you also know that every generic "touching base" email chips away at the professional impression your proposal was designed to create.
So you compromise. You write some version of: "Hi Sarah — just wanted to check in on the review timeline. Happy to answer any questions as your team works through the proposals."
It's polite. It's professional. And it communicates exactly one thing: you have nothing to say.
The selection committee, meanwhile, is reviewing your proposal alongside five to seven others. They're forming impressions. They're comparing approaches. And the firm that follows up with generic status requests gets mentally categorized as "the one with nothing new to add" — which is a terrible position to hold when you're about to be compared to firms that are actively advancing their case.
The follow-up problem isn't about cadence or timing. It's about content. And the content problem is, at its root, an information problem.
Why "Just Checking In" Happens
Firms don't send generic follow-ups because they're lazy or uncreative. They send them because they have no information to act on.
When a proposal is a PDF attached to an email, the firm knows exactly one thing after submission: the email was sent. They don't know if the committee has started reviewing. They don't know which members have engaged with the proposal and which haven't opened it. They don't know whether the design approach resonated more than the fee section or vice versa. They don't know if the proposal was forwarded to stakeholders outside the original distribution.
Without this information, there's nothing substantive to say. "Just checking in" is the only available move — not because the firm lacks follow-up skills, but because the format provided no feedback to build a follow-up on.
This is the structural limitation of document-based proposals that firms rarely identify as the source of their follow-up problem. They blame themselves for awkward follow-ups when the real issue is that their submission format generates zero post-submission intelligence.
What Data-Driven Follow-Up Looks Like
When proposals are delivered as tracked, interactive experiences, the follow-up equation changes completely. Every view, section visit, and forwarding event creates a signal the firm can respond to.
Here's how the same one-week post-submission window plays out with engagement data:
Day 2: Early Signal
You see that two of the four committee members have opened the proposal. Both spent the most time on the sustainability approach and the timeline section. The fee section was viewed briefly by one and skipped by the other. One viewer spent significant time with a portfolio case study that featured a similar building type.
Action: No outreach yet. The data tells you the review has started, which means the timeline is active. You note the section-level engagement for later use.
Day 4: Forwarding Event
The proposal link was opened by a new viewer — someone who wasn't in your original distribution. Their engagement pattern focuses heavily on the budget and phasing sections.
Action: This is a stakeholder discovery event. Someone on the committee forwarded the proposal to a person who cares about budget and schedule — likely a CFO or project controls lead. You update your stakeholder map and note that financial discipline is a priority for this new audience.
Day 6: Strategic Follow-Up
All four committee members have now reviewed the proposal. The sustainability approach received the most total engagement time. One member has revisited the proposal twice, focusing on the team section.
Action: Now you follow up — not with "checking in," but with a targeted message: "We recently completed a building performance study on a comparable project that goes deeper on the long-term sustainability metrics. Would it be useful to share that with your team as you evaluate approaches?"
This message does everything a "just checking in" email doesn't. It's specific to what the committee actually cared about. It provides new value. It demonstrates that you're actively thinking about their project. And it never mentions checking in, timelines, or status.
The Five Follow-Up Types That Replace "Checking In"
Once you have engagement data — or even just structured pre-proposal intelligence — the generic status request can be replaced entirely. Here are the five follow-up approaches that advance deals instead of eroding them.
The Relevance Follow-Up
Trigger: the committee engaged heavily with a specific section of your proposal.
Share a complementary piece of content that goes deeper on that topic. A case study with more detail on the specific building system they focused on. A data point or benchmark relevant to the challenge they're evaluating. A brief perspective on a trend related to their area of interest.
The key is that the content you share must be genuinely useful — not a thinly disguised excuse to make contact. If the committee spent time on your sustainability approach, a relevant building performance case study adds value. A generic firm newsletter does not.
The Stakeholder Discovery Follow-Up
Trigger: the proposal was forwarded to someone outside your original distribution.
Adjust your stakeholder map and follow up with the original contact acknowledging the expanded audience — without revealing that you know the proposal was forwarded. "As your team evaluates proposals, we'd be happy to provide additional information for any stakeholders reviewing the financial or scheduling aspects of the project."
This positions you as responsive to the committee's process without making the tracking feel intrusive. You're offering to help the review go smoothly, which is exactly what the committee wants.
The Gap-Closing Follow-Up
Trigger: a committee member hasn't engaged with the proposal while others have.
This requires subtlety. You can't say "we noticed one of your committee members hasn't reviewed our proposal." But you can ask whether it would be helpful to provide a brief executive summary or a targeted overview for committee members who may have limited time for the full review. This provides a natural reason for re-sharing the proposal while addressing the engagement gap.
The Evolution Follow-Up
Trigger: time has passed since submission, and you have new work or thinking to share.
"Since submitting our proposal, we've reached substantial completion on the Lincoln Center renovation — a project with comparable phasing constraints to yours. We'd be happy to share updated documentation or arrange a site visit if that would be useful during your evaluation."
This follow-up adds new information to the evaluation. It demonstrates that your firm is actively producing relevant work. And it creates a reason for the committee to re-engage with your submission at a time when it might have slipped in their stack.
The Process Follow-Up
Trigger: engagement data shows the committee reviewed all proposals in a concentrated window, suggesting a decision meeting is approaching.
This is the moment to offer availability for a shortlist presentation, interview, or Q&A session. The timing is data-informed rather than arbitrary: "As your team moves toward next steps, we'd welcome the opportunity to discuss our approach in more detail. We're flexible on timing and format."
The message is brief, professional, and timed to arrive when the committee is actively making decisions — not two weeks before they've started reviewing.
Building a Follow-Up System
The shift from "just checking in" to strategic follow-up isn't about individual creativity. It's about building a system that generates the signals you need to follow up with substance.
The system has three components:
Engagement tracking on every proposal submission. This provides the real-time signals — views, section engagement, forwarding — that inform when and how to follow up.
A content library of follow-up materials organized by topic. Case studies, data points, project updates, and thought pieces that can be deployed quickly when engagement data reveals what the committee cares about. Building this library is a one-time investment that pays off across dozens of pursuits.
A follow-up cadence tied to engagement events rather than calendar dates. Instead of "follow up on day 7, then day 14," the cadence is: "follow up when engagement data reveals an actionable signal." This means some pursuits get follow-up on day 3 and others on day 10 — because the timing matches the client's actual review process, not an arbitrary schedule.
What Clients Actually Want From Follow-Up
Here's what committees don't say but consistently demonstrate through their behavior: they want firms to make the evaluation process easier, not harder.
A status request makes the process harder. It requires the committee member to stop, compose a response, and manage your expectations — all of which is friction they didn't ask for.
A follow-up that provides relevant additional information makes the process easier. It gives the committee something useful — a deeper dive on a topic they're evaluating, a reference for a concern they're weighing, a new data point they can factor into their decision. That's the kind of follow-up that gets forwarded to the full committee with a note: "Good additional info from the firm."
The difference between a firm that's perceived as persistent and a firm that's perceived as valuable is entirely about what they bring to the follow-up. Status requests are persistent. Relevant content is valuable. The choice between them determines whether your post-submission presence helps or hurts.
Frequently Asked Questions
How long should you wait before following up on an architecture proposal? Don't use a calendar. Use engagement signals. If your proposal is tracked, follow up when data reveals an actionable signal: a spike in engagement, a section revisited multiple times, or the proposal forwarded to a new stakeholder. Some pursuits warrant follow-up on day 3, others on day 10. The timing should match the client's actual review behavior, not an arbitrary schedule.
What should you say in a proposal follow-up email? Every follow-up should pass one test: does this message give the client something useful, or does it just ask them for something? Value-driven follow-ups include sharing a relevant case study that deepens a point in the proposal, forwarding data related to a challenge the client mentioned, or providing additional context on a topic the committee showed interest in. "Just checking in" fails the test because it only asks.
How many times should you follow up after submitting a proposal? There's no universal number. The right cadence depends on the signals you're receiving. A committee actively engaging with your proposal and follow-up materials is giving you permission to continue adding value. A committee that hasn't opened anything in 2 weeks is giving you a different signal. Match your persistence to the client's demonstrated interest level, not to an arbitrary follow-up count.
How do you follow up without seeming desperate? Desperation comes from asking for something ("any update?"). Confidence comes from offering something ("we have a relevant case study on the sustainability approach you asked about"). The shift is structural: if your follow-up provides value the committee can use in their evaluation, you're making their process easier. If it only requests information about their timeline, you're adding friction.
Related Reading:
About the Author
Kitae Kim
Experiential architect and co-founder of Foveate, passionate about spatial storytelling and empowering creative professionals through technology.
