What Is a Call for Proposals? Meaning, Parts and How to Respond

A call for proposals (often shortened to CFP, and sometimes written "call for proposal") is a published invitation to send in a plan for a project. The issuer says what it wants to achieve, who may apply, what to submit, how submissions will be scored and when they're due. Everyone who responds is judged against those same rules, which is the point: the issuer gets competing ideas and a fair way to compare them.

The phrase turns up in three different worlds, and knowing which one you're in tells you what you're competing for.

Three places a call for proposals shows up

Grants: you propose the project

In funding, the applicant designs the work. The European Commission puts it plainly on its funding and tenders page: applicants submit proposals for projects in response to a call for proposals, and successful ones receive financial support. Its grants and procurement page adds the rules that make a grant a grant: the beneficiary usually shares the costs, may not make a profit from the grant, and keeps ownership of the results.

In the United States, federal agencies publish these calls as a notice of funding opportunity (NOFO). Under the federal grant rules, 2 CFR 200.204, agencies should generally keep a funding opportunity open for at least 60 calendar days, and for no less than 30 except in urgent ("exigent") circumstances, and the notice should name who is eligible.

Procurement: you propose how to meet their need

When an organization is buying, it writes the requirement and you propose how to fill it. The Commission keeps this separate from grants: it uses calls for tenders when it needs to buy goods, services or works. In US federal buying, the document is a request for proposals. The Federal Acquisition Regulation (FAR), the rulebook for government purchasing, sets its contents: FAR 15.203 says an RFP must at least describe what the government needs, the expected contract terms, what each proposal must contain, and the evaluation factors with their relative importance.

There is a middle case. A broad agency announcement under FAR 35.016 asks for research proposals on a broad area of interest, where different technical approaches are expected. Because the proposals don't answer one common work statement, they don't have to be ranked against each other; each goes through its own scientific review.

Conferences: you propose a session

For events, a CFP collects talk ideas. PyCon US 2026's talk page is a typical example: proposals had a title, description and outline, each person could submit up to three, and reviewers in the first round didn't see who wrote each proposal.

What a call for proposals usually contains

The wording varies, but a well-written call answers these questions before anyone has to ask:

• The goal or requirement. The problem to solve, or the topics the program will fund.
• Eligibility. Who may apply: organization type, location, size, prior funding.
• What to submit. Sections, page limits, budget forms, letters, file formats.
• How it's scored. The evaluation criteria and how much each one counts.
• Dates. The deadline, any question period, and when decisions go out.
• Terms. Funding amounts or contract terms, reporting duties, who owns the results.

Some calls run in two stages. A short pre-proposal comes first, and only shortlisted applicants write the full version. The University of New Hampshire's research office describes this as a way for a sponsor to limit how much effort applicants put in before it decides a full proposal is warranted.

How to respond to one, step by step

1. Check eligibility first. If you don't qualify, nothing else in the call matters, however good your idea.
2. Decide whether to bid at all. Compare the scoring criteria with what you can honestly show. A call that weights past performance heavily is hard to win without it.
3. Turn the criteria into your outline. One section per scored factor, in the order the call lists them, using its own headings. Reviewers score against the listed criteria, so make each one easy to find.
4. Ask questions in the question window. When a call shares its answers with every bidder, your question also shapes what competitors write, so word it with that in mind.
5. Build the budget or price alongside the plan, not after it. A plan the budget can't pay for loses points on both.
6. Leave time for sign-offs. At a university, for example, a solicited proposal goes through internal routing before it can be submitted.
7. Submit early and confirm receipt. A day of margin covers a failed upload or a missing form.

An example worked through

Suppose a state agency posts a call for proposals for a two-year staff training program, and you run a training company. The call scores submissions out of 100: technical approach 50 points, relevant experience 30, price 20. It allows 15 pages, opens questions for two weeks and closes in six. These numbers are made up to show the method.

The scoring tells you where to spend your pages. Half the points sit in the technical approach, so roughly half the document should explain exactly how the training will run: the curriculum, the schedule, how you'll measure whether staff improved. Experience gets its own section with two or three past programs that look like this one. Price gets a clear table, but trimming it heavily can only win you some of 20 points, while a vague plan can lose you most of 50.

During the question window you notice the call doesn't say whether sessions can be online. You ask. The published answer says in-person only for the first year, which changes your costs, and every other bidder now knows it too.

Call for proposals vs. RFP, RFQ and RFI

These terms overlap, and organizations don't use them consistently. One agency's "call for proposals" is another's RFP. As a rough guide:

The RFI and RFQ descriptions follow the Wikipedia article on RFPs. The most useful split is the one the European Commission draws: in a call for proposals, you propose the project and receive support for it; in a tender, the buyer pays for goods, services or works it needs.

Common mistakes

• Writing your own structure. A proposal organized your way makes reviewers hunt for the scored items, and points they can't find aren't awarded.
• Answering a different question. Reusing an old proposal word for word usually shows. Each call has its own goal and its own criteria.
• Ignoring format rules. Page limits, fonts and required forms are part of the rules everyone is judged by, and a proposal can be set aside for breaking them before its content is read.
• Treating the deadline as approximate. Assume a late submission won't be read unless the call says otherwise.

A call is rarely worth answering when it seems written around another organization's exact credentials, or when the award is small next to the writing time. Saying no to a poor fit leaves time for the calls you can win, and in sales, for the deals you can close.