Proposal Manager vs Proposal Coordinator

Proposal manager vs proposal coordinator, writer and capture: four roles, four windows of the federal procurement calendar, and which move comes next. The four titles on a federal proposal team are not four rungs. Each one owns a different window of the government's own procurement calendar, and the FAR draws the boundaries. Proposal manager vs proposal coordinator is the wrong place to start, because the four titles on a federal proposal team are not four rungs. Capture, proposal manager, proposal writer and proposal coordinator each own a different stretch of the government's own procurement calendar. Capture works before the solicitation exists. The proposal manager owns the window the solicitation opens. The writer owns one severable part inside it. The coordinator owns the moment the file reaches the government. So "which comes next" has no single answer, and two of the common moves between these jobs go sideways rather than up. The FAR draws the boundaries. Reading it tells you more about these four roles than any org chart will. Four Jobs, Not Four Ranks No FAR paragraph defines a capture manager or a proposal coordinator. Employers name these jobs, so two firms can hang one title on very different work. The windows belong to the government instead. Each one opens and closes on a date the contracting officer controls, and each role answers to a different document inside it. | Role | Window it owns | What holds it accountable | |---|---|---| | Capture | Before the synopsis posts | Market research and the draft requirement | | Proposal manager | Solicitation release to submission | Section L, amendments, the schedule | | Proposal writer | Draft to final of one volume | The evaluation factor that volume answers | | Proposal coordinator | Production to receipt | The closing time and the submission portal | Read that as a calendar rather than a hierarchy. A firm with one person covering all four columns still has four jobs. A firm with twelve people still has four windows. That is why a job title tells a candidate so little, and why the window tells them almost everything. Capture Owns The Window Before FAR Part 10 (https://www.acquisition.gov/far/part-10) tells agencies to conduct market research "Before developing new requirements documents for an acquisition by that agency", and again before soliciting offers above the simplified acquisition threshold. It also lists the techniques. One of them is "Conducting interchange meetings or holding presolicitation conferences to involve potential offerors early in the acquisition process." That clause is the capture manager's whole job description. Capture exists to be known, credible and useful while the requirement is still soft. The window has a hard edge. FAR 5.203(a) (https://www.acquisition.gov/far/subpart-5.2) says the noti

Skip to content

Proposal Manager vs Proposal Coordinator

By

Proposal manager vs proposal coordinator, writer and capture: four roles, four windows of the federal procurement calendar, and which move comes next. The four titles on a federal proposal team are not four rungs. Each one owns a different window of the government's own procurement calendar, and the FAR draws the boundaries. Proposal manager vs proposal coordinator is the wrong place to start, because the four titles on a federal proposal team are not four rungs. Capture, proposal manager, proposal writer and proposal coordinator each own a different stretch of the government's own procurement calendar. Capture works before the solicitation exists. The proposal manager owns the window the solicitation opens. The writer owns one severable part inside it. The coordinator owns the moment the file reaches the government. So "which comes next" has no single answer, and two of the common moves between these jobs go sideways rather than up. The FAR draws the boundaries. Reading it tells you more about these four roles than any org chart will. Four Jobs, Not Four Ranks No FAR paragraph defines a capture manager or a proposal coordinator. Employers name these jobs, so two firms can hang one title on very different work. The windows belong to the government instead. Each one opens and closes on a date the contracting officer controls, and each role answers to a different document inside it. | Role | Window it owns | What holds it accountable | |---|---|---| | Capture | Before the synopsis posts | Market research and the draft requirement | | Proposal manager | Solicitation release to submission | Section L, amendments, the schedule | | Proposal writer | Draft to final of one volume | The evaluation factor that volume answers | | Proposal coordinator | Production to receipt | The closing time and the submission portal | Read that as a calendar rather than a hierarchy. A firm with one person covering all four columns still has four jobs. A firm with twelve people still has four windows. That is why a job title tells a candidate so little, and why the window tells them almost everything. Capture Owns The Window Before FAR Part 10 (https://www.acquisition.gov/far/part-10) tells agencies to conduct market research "Before developing new requirements documents for an acquisition by that agency", and again before soliciting offers above the simplified acquisition threshold. It also lists the techniques. One of them is "Conducting interchange meetings or holding presolicitation conferences to involve potential offerors early in the acquisition process." That clause is the capture manager's whole job description. Capture exists to be known, credible and useful while the requirement is still soft. The window has a hard edge. FAR 5.203(a) (https://www.acquisition.gov/far/subpart-5.2) says the noti

The four titles on a federal proposal team are not four rungs. Each one owns a different window of the government's own procurement calendar, and the FAR draws the boundaries.

Proposal manager vs proposal coordinator is the wrong place to start, because the four titles on a federal proposal team are not four rungs. Capture, proposal manager, proposal writer and proposal coordinator each own a different stretch of the government's own procurement calendar. Capture works before the solicitation exists. The proposal manager owns the window the solicitation opens. The writer owns one severable part inside it. The coordinator owns the moment the file reaches the government. So "which comes next" has no single answer, and two of the common moves between these jobs go sideways rather than up. The FAR draws the boundaries. Reading it tells you more about these four roles than any org chart will. Four Jobs, Not Four Ranks No FAR paragraph defines a capture manager or a proposal coordinator. Employers name these jobs, so two firms can hang one title on very different work. The windows belong to the government instead. Each one opens and closes on a date the contracting officer controls, and each role answers to a different document inside it. | Role | Window it owns | What holds it accountable | |---|---|---| | Capture | Before the synopsis posts | Market research and the draft requirement | | Proposal manager | Solicitation release to submission | Section L, amendments, the schedule | | Proposal writer | Draft to final of one volume | The evaluation factor that volume answers | | Proposal coordinator | Production to receipt | The closing time and the submission portal | Read that as a calendar rather than a hierarchy. A firm with one person covering all four columns still has four jobs. A firm with twelve people still has four windows. That is why a job title tells a candidate so little, and why the window tells them almost everything. Capture Owns The Window Before FAR Part 10 (https://www.acquisition.gov/far/part-10) tells agencies to conduct market research "Before developing new requirements documents for an acquisition by that agency", and again before soliciting offers above the simplified acquisition threshold. It also lists the techniques. One of them is "Conducting interchange meetings or holding presolicitation conferences to involve potential offerors early in the acquisition process." That clause is the capture manager's whole job description. Capture exists to be known, credible and useful while the requirement is still soft. The window has a hard edge. FAR 5.203(a) (https://www.acquisition.gov/far/subpart-5.2) says the noti

Contact Shaavir · View services · Read the blog · Careers · Case studies · Privacy policy · Terms