AEC RFP Compliance Checklist

Most losing AEC proposals aren't beaten on capability - they're disqualified on compliance. Use this checklist on every pursuit to make sure a strong response actually makes it into evaluation.

1. Solicitation intake

1. Download the full solicitation package, including attachments and any posted Q&A.
2. Confirm the due date, time zone, and delivery method (portal, email, hard copy).
3. List every amendment and acknowledge each one if required.
4. Note page limits, font rules, file naming, and packaging instructions.
5. Identify whether this is QBS (qualifications first) or a priced RFP.

2. Mandatory vs scored requirements

1. Build a compliance matrix: every shall/must/required item mapped to a response location.
2. Separate pass/fail items from scored evaluation factors.
3. Assign an owner and status for each row (not started / draft / complete).
4. Flag forms, certifications, insurance, licenses, and registrations with expiration dates.
5. Confirm SAM.gov or state vendor registration is current when the owner requires it.

3. Content alignment

1. Map key personnel and past projects to the published evaluation criteria - not to a generic firm brochure.
2. Verify resumes and project sheets match the solicitation's format and limits.
3. Check that teaming partners appear where required and that letters of commitment are signed.
4. Remove orphan claims that aren't backed by a named person, project, or document.
5. Score your own draft against Section M / evaluation criteria before the final polish pass.

4. Final packaging

1. Re-read submission instructions one last time against the assembled PDF or package.
2. Confirm file size, format, and naming match the portal rules.
3. Verify every mandatory form is signed and included.
4. Submit with margin for portal outages and clock skew - late is usually dead.
5. Archive the exact package submitted plus the compliance matrix for debrief and reuse.

5. Build and own a compliance matrix

The checklist tells you what to verify. A compliance matrix is where you prove you did it, requirement by requirement, in a form your whole team can see. On lean AEC pursuits, the matrix is often the difference between catching a missing form on day two and discovering it an hour before submission.

Treat the matrix as a living document owned by one person, usually the proposal coordinator or capture lead. Ownership matters because a matrix that belongs to everyone belongs to no one. The owner does not have to write every response, but they are accountable for the status of every row.

Set a cadence rather than checking the matrix only at the end. A short standup two or three times a week, keyed to the status column, keeps red rows visible while there is still time to fix them. The last matrix review should happen the day before submission, not the morning of.

6. Handle amendments and Q&A mid-cycle

Almost every AEC solicitation changes after it drops. Agencies issue amendments, extend deadlines, swap out attachments, and answer submitted questions in ways that quietly rewrite the requirements. A proposal built against the original document can be fully compliant with a version that no longer governs the award.

Assign one person to monitor the portal for the life of the pursuit. When an amendment lands, the workflow should be deliberate:

1. Download the amendment and read it in full, not just the summary line.
2. Diff it against the current requirements and flag every change that touches page limits, formats, due dates, or evaluation factors.
3. Update affected rows in the compliance matrix and reassign owners if scope shifted.
4. Confirm and, where required, formally acknowledge receipt of the amendment - a missing acknowledgment is itself a common disqualifier.
5. Tell the whole team what changed, even the parts you think are minor.

7. Run a color-team review, scaled for a lean AEC team

Large capture organizations run formal color-team reviews - pink team for early drafts, red team for a mock evaluation, gold team for the final polish. You do not need that overhead to get the benefit. The value is not the color; it is putting fresh eyes on the proposal against the actual criteria before the client does.

A workable version for a small firm collapses this into two focused passes:

• Compliance pass: a reviewer who did not write the content checks every mandatory row in the matrix against the draft. This pass ignores quality entirely and asks one question - is the requirement met, yes or no.
• Score pass: a reviewer reads as an evaluator would, using the published scoring factors, and marks where the response is thin, generic, or off-target on the criteria that carry weight.

Keep the reviewer separate from the author wherever possible. Writers lose the ability to see gaps in their own work, and a compliance miss is exactly the kind of gap that hides from the person who created it. For the score pass, it helps to have the evaluation criteria open side by side with the draft so feedback maps to points, not taste.

8. Keep a single source of truth

Version sprawl kills compliance quietly. When three people are editing three copies of the same volume, the wrong file gets submitted, an old page limit survives a purge, or a corrected resume reverts to a stale one. None of these are capability problems. All of them lose.

• Name one authoritative location for the working proposal and forbid parallel copies floating in email.
• Use clear, dated file names or real version control so anyone can identify the current draft at a glance.
• Lock the requirements source - the assembled RFP plus all amendments - so no one edits the thing you are being measured against.
• Reconcile the compliance matrix to the single source of truth, not to someone's local copy.

9. Do a pre-submission dry run of the actual delivery

Compliance does not end when the content is done. How a proposal is delivered is itself a requirement, and it is a common late-stage failure point. Federal late-proposal rules are strict, and a portal that rejects an oversized file at 4:58 p.m. does not care that the writing was excellent.

Give yourself a buffer and rehearse the submission itself:

1. Confirm the exact delivery method - portal, email, physical copies, or a combination - and the precise deadline, including time zone.
2. Check file specifications: format, file-size limits, naming conventions, and whether volumes must be separate files.
3. Generate the final PDFs and open them fresh to confirm fonts, page breaks, and required forms survived export.
4. If the portal allows a test upload or draft submission, use it well before the deadline.
5. Verify every required signature, acknowledgment, and attachment is present in the package that actually uploads - not the one on your desktop.

10. Close the loop: debrief and reuse

The compliance work you do on one pursuit is worth more if it survives the submission. After every proposal - won or lost - capture what happened while it is fresh. Request a debrief when one is offered; agencies will often tell you exactly where a response fell short on the factors that mattered.

Feed the lessons back into reusable assets: a cleaned-up requirements template, a corrected boilerplate section, an updated project sheet, a note on a portal quirk that nearly cost you. Over a year of pursuits, this loop turns scattered effort into a compliance system your team trusts.

If most of your work is public-sector, pair this checklist with the government AEC RFP playbook and, for federal qualifications, the guide on writing an SF330 that wins.

Flodoc extracts requirements from an uploaded RFP/RFQ, tracks each one to closure, and matches staff and past projects to scored criteria so your team spends the last hours strengthening weak spots instead of hunting for gaps. It assembles SOQ and SF330-style documents in its editor; it does not auto-fill the official federal SF330 PDF.