Use Case
Project Experience Sheets for AEC Proposals
Generate pursuit-specific project sheets from one project database. Highlight different scope, staff, and details for every submittal — export to DOCX in your firm's template.
Why project sheets eat up proposal time
Every AEC proposal needs project experience sheets — one-page summaries proving your firm has done similar work. A typical submittal includes 5-10 project sheets, each customized to emphasize the scope most relevant to the pursuit.
The standard workflow: find a project sheet from a past submittal, copy it into the new proposal, adjust the scope description to match the current RFP's evaluation criteria, update the staff names if the team has changed, verify the contract value and completion date are still accurate, and fix the formatting that broke during copy-paste. That is 15-30 minutes per sheet, multiplied by 5-10 projects per pursuit.
The deeper problem is consistency. The same project appears in dozens of past proposals, each with slightly different scope descriptions, different staff listed, and sometimes different contract values. There is no single source of truth — just a trail of Word documents with conflicting information.
How RFPM.ai handles project experience sheets
One project record, every version
Each project lives as a single structured record in RFPM — scope of services, contract value, completion date, client contact, location, and the staff who worked on it. This is your source of truth. When you need a project sheet for a pursuit, you generate it from this record, choosing which details to feature. The record itself never changes — only what you highlight.
Pursuit-specific tailoring
The same project can look different for different pursuits. A highway widening project might emphasize traffic management for one RFP and drainage design for another. RFPM lets you select which scope elements, staff members, and project details to feature — without editing the master record. Each pursuit gets a tailored sheet. The underlying data stays clean.
Staff and project linkage
Staff profiles and project records are linked bidirectionally. The project sheet shows which staff worked on the project and their roles. Staff resumes reference the project with matching details. The SF330 Section G matrix maps both together. Change a project detail once — every connected document reflects the update.
Export to DOCX in your template
RFPM exports project sheets to DOCX using your firm's branded template. The layout, fonts, and structure match what your firm already uses — no reformatting after export. For federal submittals, generate in SF330 Section F format directly.
Project sheet workflow: before and after
| Task | Manual Process | With RFPM.ai |
|---|---|---|
| Find the right project | Search shared drive folders, check old proposals, ask colleagues who remember | Ask RFPM Agent: "Which projects had stormwater scope over $2M?" |
| Tailor for the pursuit | Copy old sheet, rewrite scope description, swap staff names, update figures | Select which scope elements and staff to feature, generate |
| Verify accuracy | Cross-check contract value, dates, and client contact against original records | Data pulls from the verified master record automatically |
| Format and export | Fix layout breaks, match template, convert to PDF — 10-20 min per sheet | Export to DOCX in firm template or SF330 Section F format |
| Time per project sheet | 15-30 minutes | 3-5 minutes |
What goes on a project experience sheet
A standard project experience sheet for AEC proposals includes:
- Project name and location — official project title and geographic location
- Client and contact information — agency or owner name with a reference contact for verification
- Contract value and completion date — demonstrates the scale and recency of the work
- Scope of services narrative — what the firm actually did, tailored to highlight relevance to the current pursuit
- Key staff and their roles — which proposed team members worked on this project and in what capacity
- Relevance to the current pursuit — why this project demonstrates the firm's qualifications for the work being procured
Who this is for
- ✓AEC firms that include project experience sheets in every proposal — SF330 Section F, SOQ submittals, or shortlist interview packages
- ✓Firms with 50+ completed projects where finding the right one for a pursuit takes longer than writing the description
- ✓Multi-discipline firms that need to present the same project differently for different service areas (transportation vs. water vs. environmental)
- ✓Proposal teams tired of conflicting project data across old submittals — different contract values, outdated staff lists, inconsistent scope descriptions
Learn more about project experience sheets
Project Experience Sheets: What They Are and How to Create Them
A practical guide to building effective project sheets for AEC proposals.
SF330 Guide: What It Is, How to Fill It Out, and Common Mistakes
Section F of the SF330 is where project experience sheets live in federal submittals.
Use Case: SF330 Proposal Preparation
See how project sheets fit into the full SF330 preparation workflow.
Stop copying project sheets from old proposals
Build your project database once. Generate tailored project sheets for every pursuit — accurate, consistent, and in your firm's template.
Frequently asked questions
What is a project experience sheet?
A project experience sheet is a one-page summary of a completed project used in AEC proposals. It typically includes the project name, client, location, contract value, completion date, scope of services, staff who worked on it, and a brief narrative describing the firm's role. In SF330 submittals, project experience sheets correspond to Section F (Example Projects). Most agencies use them to evaluate whether a firm has relevant past performance for the work being procured.
How does RFPM.ai generate project experience sheets?
RFPM.ai stores project data as structured records — scope, contract value, client, completion date, staff involvement, and project descriptions. When you start a pursuit, you select which projects to include and choose which details to emphasize. RFPM generates the sheet in your firm's template format and exports to DOCX. Because the data is structured, you can tailor the same project for different pursuits without editing the source record.
Can I highlight different aspects of a project for different pursuits?
Yes. A single project record can produce multiple versions of a project sheet. Pursuing a water treatment contract? Emphasize the water infrastructure scope and the staff with water experience. Pursuing a general civil project? Lead with the site design and permitting scope from the same project. The underlying record stays the same — you select which details to feature each time.
How do project experience sheets connect to staff resumes in RFPM.ai?
Staff profiles and project records are linked in RFPM. When a staff member is listed on a project, that relationship exists in both directions — the project sheet shows which staff contributed, and the staff resume can reference that project. This also powers the SF330 Section G matrix, which maps key personnel to example projects. Update a project record once and every connected resume and sheet stays in sync.
What format does RFPM.ai export project sheets in?
RFPM.ai exports project experience sheets to DOCX format using your firm's template. The export includes all selected project details — scope narrative, key staff, contract value, client information, and completion dates — formatted to match your firm's branded layout. You can also generate sheets in SF330 Section F format for federal submittals.