A government marketing RFP should make proposals comparable before anyone starts scoring them. If one agency includes media spend inside its fee and another excludes it, evaluators may be comparing different purchases.
Use the copy-ready scope below to define the work, separate costs, set acceptance standards, and evaluate agencies on the same evidence. Adapt the language to your procurement process rather than treating a marketing template as a complete solicitation.
What is a government marketing RFP?
A government marketing RFP is a request for proposals inviting agencies to explain how they would deliver specified marketing or communications services, at what price, and under what terms. It connects the government’s requirements with proposal instructions and evaluation criteria. The statement of work defines the services being purchased.
Copy-ready government marketing RFP scope of work
Start with the work, but do not stop there. For federal negotiated acquisitions, FAR 15.203 identifies minimum RFP content covering government requirements, anticipated contract terms and conditions, information required in proposals, and evaluation factors and significant subfactors with their relative importance.
Use the outline below as the service-requirements portion of your solicitation. Add the applicable submission instructions, contractual provisions, pricing forms, and procurement procedures separately. Requirements vary by agency and jurisdiction; this guide is not legal advice.
Bracketed fields are intended for replacement. Remove workstreams you are not buying, and define optional work separately from the base requirement.
1. Background and operating context
The agency seeks marketing and communications support for [program or service]. Describe the public need, current communications channels, available research, geographic coverage, existing contracts, and known constraints. Identify what the selected contractor may change and what remains outside its authority.
2. Objectives and intended public outcomes
The engagement will support [specific public outcome], such as completed service applications or attendance at an eligible program. Identify the baseline, target population, measurement period, and agency-controlled dependencies. Separate the intended public outcome from contractor-controlled obligations; do not make an agency promise results it cannot independently deliver.
3. Target audiences and access needs
Priority audiences are [audience groups], including [language, disability, connectivity, or other access considerations]. Require the proposal to explain audience research, channel selection, message adaptation, and how underserved groups will be reached without relying exclusively on paid digital targeting.
4. Scope boundaries and integration
The contractor will coordinate [selected channels] around one approved communications plan. State whether strategy, production, buying, publishing, website changes, and community management are included. Percepture's omnichannel marketing services offer a reference point for organizing an integrated scope; the solicitation should describe required functions, not prescribe a particular agency's operating model.
5. Deliverables and acceptance
For each deliverable, specify the format, quantity or ordering mechanism, due date, reviewer, acceptance criteria, and included revision rounds. For example: “Provide an editable campaign plan containing audience priorities, channel roles, budget allocation, measurement definitions, dependencies, and an approval schedule.” Define how rejected work will be corrected and resubmitted.
6. Channel workstreams
Require separate descriptions for each included workstream:
- SEO: Technical recommendations, content discoverability, search-intent mapping, implementation responsibilities, and change documentation.
- Content: Research, writing, editing, translation, fact verification, publishing, and maintenance.
- Public relations: Message development, media materials, outreach, spokesperson preparation, and coverage reporting.
- Social media: Channel plans, publishing, moderation, response boundaries, and account administration.
- Email: List permissions, segmentation, production, testing, delivery reporting, and unsubscribe handling.
- Paid media: Planning, buying, trafficking, creative testing, pacing, and financial reconciliation.
- AI search: Public-information accuracy, source discoverability, and an agreed method for observing relevant answers and citations.
If AI search is included, define its relationship to conventional SEO. Percepture's GEO services provide a separate service reference for that workstream; do not substitute a service label for a deliverable specification.
7. Paid media budget and agency fee separation
Require separate line items for working media, agency labor or management fees, production, technology, research, subcontractors, and other reimbursable costs. Ask bidders to disclose markups, commissions, rebates, credits, cancellation charges, and minimum commitments. Identify who contracts with media vendors and how unused funds and billing discrepancies will be handled.
8. Analytics and measurement
The contractor will submit a measurement plan identifying each metric's definition, source, owner, reporting frequency, and limitations. Specify approved analytics environments, tracking permissions, baseline establishment, attribution assumptions, and data exports. Use the distinction between activity and outcomes when defining attribution and analytics requirements: a click is not a completed public-service transaction.
9. Optional AI-answer observation
If purchased, the contractor will document the questions observed, answer surfaces, collection dates, source citations, sampling approach, and interpretation limits. Request an initial baseline and a repeatable comparison method. Keep this an optional, separately priced measurement deliverable unless the program has a defined need for it; do not require a named platform or promise control over third-party answers.
10. Accessibility and quality assurance
Identify the accessibility requirements applicable to each deliverable and the evidence required for acceptance. Assign responsibility for documents, webpages, video captions, transcripts, email, and third-party components. Specify automated and manual testing, remediation, and retesting. For federal procurement planning, consult the Section 508 pre-solicitation accessibility guidance alongside your agency's requirements.
11. Privacy, security, and information handling
Identify permitted data, prohibited data, approved systems, access roles, retention periods, incident contacts, and deletion or return procedures. Require bidders to describe subcontractor access and proposed external tools. State which approvals must precede tracking changes, data transfers, or use of agency information in AI systems.
12. Stakeholder approvals and crisis escalation
Name the agency's decision owner, subject-matter reviewers, accessibility reviewers, and authorized publishing contacts. Define review windows and how delayed approvals affect schedules. Establish escalation triggers, emergency contacts, response authority, and approval boundaries. Treat crisis communications as a defined responsibility rather than an implied round-the-clock obligation.
13. AI-generated content and factual controls
Require disclosure of proposed AI-assisted activities, tools, data inputs, human review, and retained records. Identify prohibited uses and content requiring subject-matter review. Require factual statements to be traceable to appropriate sources, with a correction process for errors. Do not accept a general promise of “human oversight” without named responsibilities and review steps.
14. Intellectual property, accounts, and data rights
Identify the rights sought for final deliverables, editable source files, campaign data, and custom work. Separate pre-existing contractor materials and third-party licenses from newly created assets. Specify account administration, access continuity, export formats, and any restrictions on reuse. Put the agreed rights and license terms into the contract rather than relying on a proposal slogan about ownership.
15. Transition and offboarding
Require an inventory of accounts, assets, licenses, credentials-transfer procedures, open commitments, scheduled activity, and unresolved issues. Specify handover formats, training, transition assistance, access revocation, and data disposition. Include transition pricing and responsibilities for both normal completion and early termination.
16. Schedule and dependencies
Define the period of performance, kickoff requirements, discovery milestones, approval dates, launch conditions, and recurring delivery dates. Identify agency inputs and external dependencies. Require bidders to distinguish committed dates from assumptions and describe how changes will be documented and authorized.
17. Performance standards
For each service, state the required result, measurable standard, assessment method, reviewer, and correction procedure. Use FAR 37.602 as the federal reference for results-oriented performance work statements and measurable standards. Preserve room for bidders to explain their methods rather than specifying every production task.
18. Reporting and decision support
Require a reporting package covering progress against objectives, deliverable status, spend reconciliation, measurement limitations, risks, decisions required, and next actions. Include access to underlying data where permitted. Define the reporting cadence and accountable owner; a dashboard alone is not a complete management report.
19. Proposal response and evaluation factors
Provide a response structure that maps directly to the published evaluation factors. Request the proposed approach, staffing, relevant examples, measurement design, quality controls, pricing, assumptions, and exceptions. State how optional services will be evaluated and how price relates to non-price factors under the selected procurement method.
Turn broad promises into assessable performance standards
A government marketing RFP can describe ambitious outcomes without treating every outcome as a contractor guarantee. Assign standards to work the contractor controls, then measure broader program outcomes with their dependencies visible.
“Improve awareness” is an objective, not an acceptance test. “Deliver an approved research plan and report results using the agreed audience and method” gives the reviewer something concrete to assess.
Sample acceptance standards to adapt
| Deliverable | Example standard | Acceptance evidence |
|---|---|---|
| Monthly report | Submit by the fifth business day, with every agreed metric populated or its absence explained. | Report, source exports, limitations, and assigned actions. |
| Media reconciliation | Reconcile billed media against approved purchases; identify every variance and credit. | Placement records, invoices, and reconciliation log. |
| Public content | Complete the agreed factual and accessibility checks before release. | Source references, review record, test findings, and resolved defects. |
| Account handover | Transfer the agreed accounts, editable assets, and permitted exports by the contractual transition deadline. | Inventory, access checks, export files, and handover record. |
For each standard, also decide who reviews the evidence, how often review occurs, and what happens when work fails acceptance. Keep this quality-assurance responsibility separate from the contractor's own quality-control process.
A 100-point agency evaluation matrix
Use this sample to design a scoring model, not to bypass your procurement rules. Adjust the weights and criteria before issuing the solicitation. Keep any applicable eligibility checks separate from scored distinctions, and disclose the factors used to make the award.
Adjustable agency evaluation weights
| Evaluation factor | Maximum points | Evidence to request |
|---|---|---|
| Understanding of objectives and audiences | 20 | A program-specific approach, audience priorities, assumptions, and dependencies. |
| Integrated delivery approach | 20 | Channel responsibilities, coordination, sequencing, and a deliverable-to-owner map. |
| Measurement and reporting | 15 | Metric definitions, source access, attribution limits, and decision-oriented reporting. |
| Accessibility and content quality | 10 | Testing methods, reviewer responsibilities, sample evidence, and remediation procedures. |
| Privacy, security, and AI controls | 10 | Information-handling procedures, tool disclosures, access controls, and escalation plans. |
| Proposed team and delivery management | 10 | Named roles, availability, subcontractor responsibilities, and continuity arrangements. |
| Relevant past performance | 5 | Comparable work identifying the bidder’s actual role, scope, and reference contacts. |
| Price and evaluated value | 10 | Comparable cost schedules, fee transparency, assumptions, and transition costs. |
| Total | 100 | Adjust weights to the acquisition’s priorities before release. |
For a simple technical-factor worksheet, rate each response from 0 to 5: no usable evidence, major gaps, partial response, meets the requirement, strong supported response, or exceptional supported value relevant to the stated criterion. Weighted points equal the rating divided by five, multiplied by the factor's maximum points. A rating of 4 on a 20-point factor earns 16 points.
Define the price-evaluation method separately; do not assume the same qualitative scale is suitable for price. Compare offers using the same media-spend assumptions, service quantities, contract period, options, and cost categories.
Give evaluators a space to record the proposal passage supporting each judgment. A polished presentation should not receive extra credit for an unstated factor, and an integrated agency should not win simply because it offers more services than the government requested.
Questions evaluators should ask
Use these questions to clarify the published criteria through the communications process authorized for your procurement. Apply the same standards to every bidder.
- AI-generated content: Which activities would use AI, which tools would be involved, and what agency information would enter those tools? Who is accountable for the final output?
- Fact verification: Show how a reviewer would trace a factual statement to its source, resolve conflicting information, and correct an error after publication.
- Accessibility: Which deliverables receive manual testing, who performs it, and what evidence accompanies remediation and retesting?
- Source transparency: Can the agency provide the underlying data, reporting definitions, research references, and permitted exports behind its recommendations?
- Media economics: What does the quoted fee exclude? How are commissions, credits, unused media funds, and third-party charges handled?
- Delivery ownership: Who resolves a conflict between paid media, public relations, website content, and analytics? Which subcontractors or agency teams control each dependency?
- Continuity: What remains usable if the contract ends tomorrow, and what would require another license, migration, or payment?
Ask for relevant work samples where appropriate, but distinguish existing evidence from new speculative work requested during evaluation. Do not request a live product demonstration unless it serves a stated evaluation need.
An integrated response architecture for Percepture
For an agency such as Percepture, organize the response around the government's outcomes rather than a tour of departments. The brief's integrated scope—strategy, media, PR, SEO, AI search, and measurement—can be expressed through five connected proposal components:
- Outcome and audience map: Connect each public objective to its audience, channel role, and measurement approach.
- Delivery responsibility map: Assign an accountable lead and supporting specialists to each required workstream, including agency-side dependencies.
- Evidence and acceptance map: Pair every deliverable with its proposed quality checks, sources, reviewer, and acceptance evidence.
- Commercial schedule: Separate labor, media, production, technology, optional work, and transition costs using the required pricing format.
- Continuity plan: Explain approvals, escalation, account access, rights, documentation, and handover.
Score those components against the same matrix used for every bidder. The question is whether the proposed team can deliver the purchased scope with clear accountability—not whether its service menu is the longest.
Separate SOW checklist before solicitation release
- Scope: Base services, options, exclusions, audiences, and deliverable quantities are distinguishable.
- Costs: Media, fees, production, technology, reimbursables, and transition work have comparable pricing fields.
- Acceptance: Deliverables have measurable standards, assessment evidence, reviewers, and correction procedures.
- Controls: Accessibility, privacy, security, AI use, factual review, approvals, and crisis escalation have assigned responsibilities.
- Continuity: Rights, licenses, account access, source files, permitted data exports, and offboarding are addressed.
- Evaluation: Response instructions align with published factors, weights, and the price-evaluation method.
- Feasibility: Schedule, budget assumptions, agency inputs, and external dependencies describe the same purchase.
Before releasing the government marketing RFP, trace one requirement all the way through: scope, deliverable, price line, acceptance evidence, and evaluation factor. If the chain breaks, fix the solicitation language. That is a more useful final test than adding another page of agency credentials.
Compare service scope before setting the budget
For early market research, compare engagement structures with the workstreams and ownership terms above. Use the published solicitation—not a commercial pricing page—as the basis for bid pricing.
About Bob Generale
Bob Generale is President of Percepture.
