Make each request specific.
Request individual résumés, forms, project examples, and technical inputs. Record the responsible firm, due date, and whether each item is required.
PURSUIT COORDINATION FOR AEC TEAMS
Every contribution.
A clear owner.
A ready handoff.
Bring résumés, project examples, required forms, and technical inputs into one coordinated pursuit. Know what is missing, review the right version, and give your proposal team the accepted files.
Built for pursuit specialists, proposal coordinators, and the teams they bring together.
PURSUIT / CONTRIBUTIONSILLUSTRATIVE EXAMPLE
RFQ · NORTHLINE CIVIC CAMPUS
One team. A clear next step.
Required materials for proposal handoff
06 / 08required items ready
2 need attention
-
Key staff résumésStructures partner · v03Accepted
-
Relevant project examplesCivil partner · v02Accepted
-
Required teaming formSurvey partner · due Nov 12Requested
-
Technical inputGeotechnical partner · v02In review
Accepted-file handoffCurrent versions + indexes + clear exceptions
Fictional project, firms, and statuses. No customer information is shown.
FROM REQUEST TO ACCEPTED USE
Pursuit specialists · Marketing teams · Technical reviewers · Teaming partners
01 / THE COORDINATION BEHIND THE PROPOSAL
Less chasing.
A clearer path to ready.
Your proposal depends on contributions from across the team. AEC Workroom gives each request, revision, and review a place, so you can see what still stands between the team and handoff.
Give every firm a next step.
Invite the people responsible for the material. Contributors upload and revise their firm’s requested items within their assigned access.
Accept the version you mean.
Distinguish received material, requested changes, and accepted contributions. Keep submission history so a replacement does not silently become an approved file.
Know what is ready to use.
Export current accepted contributions in a ZIP with indexes. See missing required items and unresolved addendum impacts before declaring the handoff complete.
02 / FOLLOW ONE PURSUIT
From the first request
to the accepted files.
A focused workflow for the collection work behind your proposal. Explore this fictional pursuit, one step at a time.
REQUIREMENTS / ASSIGNED01 / 04
Start with what the proposal team needs.
Create the pursuit, invite your internal team and contributing firms, and record individual requests. Give each required résumé, form, project example, or technical input a responsible firm and an internal due date.
NORTHLINE CIVIC CAMPUS / FICTIONAL PURSUITEight requested items. Every item has an owner.
A specific request is easier to act on than a general request for qualifications. Required and optional materials stay distinguishable.
Interactive illustration · No files are uploaded and no invitations are sent.
03 / ONE PURSUIT, DISTINCT RESPONSIBILITIES
The right people.
A shared understanding.
Pursuit specialists
Keep the requirements, owners, and deadlines in view. Follow up on missing inputs and resolve outstanding work before handoff.
Marketing & technical teams
Supply accurate qualifications, project information, and technical inputs. Revise requested material and help reviewers establish what is ready for this pursuit.
Reviewers & proposal managers
Review the current contribution, request corrections, and record acceptance. Give the proposal team a traceable set of accepted materials.
SHARED WORK. DELIBERATE ACCESS.
Invite people into
their part of the pursuit.
Internal coordinators and reviewers need the wider picture. External contributors need their firm’s requests and files. AEC Workroom keeps those responsibilities distinct.
A focused place to respond.
Contributors access their firm’s authorized requests and submissions, plus the shared solicitation and official addenda.
Keep the review within your team.
Internal SOQ drafts and review comments stay with explicitly authorized internal participants. A pursuit invitation grants no access to unrelated exchanges or agreements.
WHEN YOUR WORKFLOW GOES FURTHER
A pursuit is the starting point.
AEC Workroom also supports private commercial RFP exchanges, agreement records, and project delivery. Explore these separately when they fit your process.
Work through each firm’s offer.
Review scope, schedule, fee, constraints, and assumptions in separate sender–recipient exchanges. Keep revisions and the accepted commercial proposal.
Carry the agreed work forward.
Review agreement packages, retain externally signed copies, and track milestones, changes, costs, and invoices. Payments remain in your existing process.
Accepting a pursuit contribution records a file decision. Commercial acceptance, agreement approval, and signing are separate decisions.
04 / START WITH A DEFINED PURSUIT
Bring your next pursuit.
See where the work gets stuck.
Walk through your collection and review process in a guided demo. Then discuss a paid pilot with agreed participants, support, fee, and review date.
- Explore the fit. Show us how your team requests and reviews contributions today.
- Agree the pilot. Define the pursuit, contributing firms, workflow, and commercial terms.
- Review the results. Compare coordination effort, missing materials, correction turnaround, and handoff accuracy.
A focused start.
A measurable outcome.
Contact us for pricing
Tell us about your next deadline, the firms involved, and the materials you need to collect. We’ll discuss availability and scope before enrollment.
- Individual contribution requests and due dates
- Firm contributors with assigned access
- Version review, corrections, and acceptance
- Addendum follow-up and material readiness
- Accepted-file ZIP handoff with indexes
A FEW DETAILS BEFORE WE TALK
Questions about AEC Workroom.
Who is AEC Workroom for?
Pursuit specialists and proposal coordinators who bring together marketing teams, technical reviewers, and partner firms. Keep requested qualifications, contributions, review decisions, and accepted-file handoff in view for a defined pursuit.
Does AEC Workroom write or submit our proposal?
Your team owns the strategy, technical claims, proposal authorship, and final submission. The initial pursuit workflow coordinates requested materials, revisions, review, and accepted-file handoff to the people preparing your proposal.
How do you handle addenda and replacement files?
The pursuit owner reviews and acknowledges official addenda and identifies affected material requests. Affected items require explicit resolution. A replacement contribution has its own review; historical acceptance alone does not make the current material ready for a complete handoff.
What does AI help with?
Where enabled, AI can suggest RFQ details with source-page references and check internal SOQ drafts against selected requirements and prior comments. Findings need human verification, especially for scanned pages and visual requirements. Your team accepts contributions and authorizes final release. AI-assisted review is separate from the focused collection pilot and is included only when agreed in its scope.
Can we keep using our proposal tools and Bluebeam?
Yes. Export accepted contributions in a ZIP with indexes for your proposal team. Where internal SOQ review is enabled, review the exact PDF in Bluebeam Revu and import its Markups Summary CSV into the matching review round. These are file handoffs; live Bluebeam Studio synchronization and automatic owner-portal submission are not included.
Which files can we bring into a pursuit?
Firm materials support PDF, DOCX, XLSX, and TXT, up to 3 MiB per file. Source RFQ PDFs support up to 3 MiB; internal SOQ PDFs support up to 10 MiB. We’ll review your package sizes and the applicable limits when scoping a pilot.
FROM REQUIRED TO READY
Bring the contributions together.
Request a demo
Tell us about your next pursuit.
Civiltronics will review your
request and follow up.