The RFQ for a county's construction management services on a school bond program posts on a Tuesday. Proposals are due in 23 days. The PDF is 140 pages, plus three exhibits, a sample agreement, and a fee form that has to be sealed separately.
By Friday, the proposal manager has read it twice. The principal has skimmed the scope and the evaluation section. The marketing coordinator has a page of notes on fonts, tabs, and page limits. Nobody has written a word of the actual proposal yet.
Then Addendum 1 comes out. It moves the due date, answers 41 questions, and in answer 27 quietly adds a requirement that the resident engineer hold a state PE license.
From the outside, it looks like the proposal team is slow. They are not. They are doing the most important part of the pursuit, understanding exactly what the owner asked for, with the worst possible tool: reading every page by hand, under a deadline, while two other pursuits are also due.
Where the first week actually goes
Reading an RFP is not one task. It is several kinds of reading, usually done at the same time and by the same tired person.
Reading for requirements
Every "shall," "must," and "proposer will provide" is a potential pass/fail item. Some sit in the Instructions to Proposers where you would expect them. Others hide in the scope narrative, the insurance exhibit, or the sample agreement. Minimum qualifications for key staff are a common trap: years of experience, licenses, certifications, and "similar projects" defined in a very specific way.
Reading for scoring
The evaluation criteria tell you what the owner actually values. Thirty points for key personnel and ten for approach is a different proposal than the reverse. The best teams map every section of the response to a scored criterion. That only works if someone has pulled the criteria, the weights, and the scoring language out of the document and put them where the writers can see them.
Reading for dates and logistics
Questions deadline. Mandatory pre-proposal meeting, and whether attendance is required to submit. Due date and time, delivery method, number of copies, portal registration. Interview window. Miss one of these and the quality of the proposal does not matter.
Reading for the fine print
Page limits, and what counts toward them. Font size and margins. Required forms, signatures, and notarization. Small or disadvantaged business participation goals. Conflict of interest language that might rule out a teaming partner. Insurance limits your firm may or may not carry today.
Then reading it all again
Each addendum can change any of the above. Q&A responses are often where the real clarifications live, and they are rarely written in the same structure as the original document. So the team re-reads, re-checks, and hopes nothing slipped.
The real cost is what the reading crowds out
The hours matter. What they are taken from matters more.
Strategy starts late. Win themes, staffing decisions, and teaming conversations should begin in the first few days. Instead, they start after the document is fully understood, which on a 23-day turnaround means the last two weeks.
Go/no-go gets made on a skim. When reading takes days, the decision to pursue is often made before anyone has found the requirement that should have stopped it. That is how a firm spends a week on a proposal it was never going to qualify for.
Mistakes cluster in the details. Firms rarely lose a pursuit because they misunderstood the scope. They get marked down, or disqualified, for a missing form, an unsigned addendum acknowledgment, or a resume that does not show the required license.
The team caps out. If every pursuit costs several days of reading before writing begins, a small BD team can only take on so many. Good opportunities get passed over, not because they are a poor fit, but because nobody had time to read them.
A better first pass, with or without tools
You do not need new software to improve this. You need to separate understanding the RFP from responding to it, and make the first part fast, complete, and shared.
Build a one-page pursuit brief
Before anyone writes, produce a short document that answers:
- Who is the owner, what is the project, and what is the contract type?
- What are the minimum qualifications, for the firm and for each key position?
- What are the evaluation criteria and their weights?
- What are the dates: questions, pre-proposal meeting, due date, interviews?
- What are the submission rules: format, page limits, copies, portal, sealed fee?
- Which forms, signatures, and acknowledgments are required?
- What participation goals, insurance limits, or conflict rules could affect the team?
- What is unclear and should go in as a question before the deadline?
Same brief, same format, every pursuit. That alone turns an open-ended read into a checklist.
Cite the page for every item
Each line in the brief should point back to the page or section it came from. When a writer asks "are resumes excluded from the page limit?" the answer should take ten seconds to verify, not ten minutes.
Treat addenda as changes to the brief
When an addendum lands, the question is not "what does this say?" It is "what in our brief does this change?" Update the brief, flag what moved, and tell the team.
Keep extraction separate from judgment
Pulling requirements and dates out of the document is mechanical. Deciding whether to pursue, who to propose, and how to win is not. Mixing the two is what makes the first week feel endless. Do the mechanical part fast, then give your best people the time for the rest.
Before and after
Before: The RFP posts. One person reads it end to end, builds notes in a format only they understand, and shares highlights in a kickoff meeting. Addenda get read and mentally merged. Questions about the document get answered by searching the PDF. Writing starts in week two.
After: The RFP posts. Within a day, the team has a cited pursuit brief, a list of pass/fail requirements, the scoring criteria mapped to proposal sections, and a draft list of questions for the owner. The go/no-go conversation happens with the full picture. Addenda update the brief instead of starting a new read. Writing starts in week one.
The proposal manager still owns the response. They just stop being the only person who knows what is in the document.
Where AI helps, and where it does not
This is a good fit for AI because the first pass is structured reading: find the requirements, dates, criteria, and rules, and organize them.
Where it helps:
- Pulling requirements, minimum qualifications, deadlines, and submission rules from a long RFP into a consistent brief
- Linking each item back to its source page so people can check it
- Comparing an addendum against the original and listing what changed
- Answering plain-language questions about the document, like "is there a DBE goal?" or "what counts toward the page limit?"
Where people still decide:
- Whether the pursuit is worth chasing at all
- How to read the owner's priorities between the lines
- Which staff to propose and how to position them
What to watch:
- Scanned and messy documents. Poor-quality scans and tables split across pages make extraction harder. A person should check anything pass/fail.
- Over-trust. A missed requirement is still a missed requirement. Use the brief as a starting point, not a signed checklist.
- Confidential material. Your past proposals, fee schedules, and staff data are sensitive. Know where they go.
How we approach it
At InstinctIQ, we work as a forward-deployed team. Before we change anything, we sit with your BD and proposal staff through a live pursuit and watch where the hours go: how the RFP gets read, how notes get shared, how addenda get tracked, and where the late-night fixes happen.
From there, IQ-Pursuit supports the workflow your team already runs. It finds opportunities across agency portals and scores them against your firm's experience. It lets your team search RFPs and past proposals in plain language, checks drafts for compliance with the owner's requirements, and starts first drafts from your most relevant past proposals in your firm's voice. The point is not to replace your proposal manager. It is to give them back the first week.
If you take one thing from this post, make it the pursuit brief. It works on paper too.
A useful next step
Pull the last RFP your team responded to. Ask the proposal manager how long it took before the team had a clear picture of the requirements, the scoring, and the dates. Then ask what got pushed back because of it.
If the answer is "most of the first week," we are happy to walk through that RFP with you and show what the same first pass looks like when the reading is already done.
Ready to win more pursuits?
Join hundreds of AEC teams already saving hours every week.