A proposal handover should preserve the enquiry’s purpose, confirmed facts, scope questions and decision owners. Separate the prospective client’s request from work you are prepared to offer. Identify missing inputs and assumptions before estimating, then prepare a reviewable proposal whose status and dependencies are clear.
Create a reliable bridge from message to offer
An enquiry often arrives as a mixture of problem, proposed solution, urgency and background. Before writing a proposal, extract the parts that affect the offer. Record the requested task, intended audience, desired output and reason for the timing. Attribute reported facts and retain the source message privately where appropriate. Do not let a polished proposal transform an informal statement into an independently confirmed requirement.
Add the decisions needed to proceed: who can commission, who approves the work and what budget or procurement conditions apply. An enthusiastic contact may be exploring possibilities rather than holding authority to appoint a provider. Clarify this without making assumptions about their job title. The proposal should address the actual decision process, including any review that must happen before work can be authorized.
Keep the client’s request distinct from your recommended scope. If they ask for a whole-site rewrite and you suggest an inventory first, state both. Explain why the narrower step is proposed and what it would produce. This allows the client to assess your recommendation rather than discovering later that the offer does not match what they originally requested.
Resolve the questions that change the estimate
Identify unknowns that alter effort or feasibility: volume, languages, access, source quality, review rounds and specialist involvement. Ask focused questions instead of requesting an entire archive. If answers are unavailable, decide whether to state an explicit assumption, offer bounded discovery or postpone the proposal. Avoid hiding major uncertainty inside an unexplained buffer that gives the client little understanding of the work.
For each assumption, describe its effect. An estimate based on one approved source document differs from one that includes reconciling conflicting versions. A review schedule based on consolidated feedback differs from collecting independent comments from several departments. The handover note should make these conditions visible before they become price or schedule claims. Keep sensitive information limited to the people who need it for preparing the offer.
Prepare for an informed review
Build the proposal around deliverables, boundaries, responsibilities and the process for acceptance. State what the client must provide and when timing can be confirmed. Identify anything excluded or dependent on another specialist. If a commercial arrangement needs specific terms or advice, handle that through an appropriate process; a general article cannot establish the legal effect of a proposal in every jurisdiction.
Check the draft against the original enquiry and discovery summary. Every material question should be answered, marked as a condition or explicitly excluded with an explanation. Use accurate status language such as proposed scope or estimate for discussion. Sending a proposal, receiving it and commissioning the work are distinct events. Keep a record of revisions so an older version does not remain an accidental basis for conflicting expectations.
Fictional example: from “new website copy” to a bounded offer
A fictional content specialist receives an enquiry for “new website copy” before a product announcement. A short discussion reveals that the public site has two audiences, incomplete product information and an approval route still being decided. The specialist prepares a handover note that separates the announcement deadline from the unconfirmed scope of the whole website.
The proposed first output is a page inventory and message outline based on approved product facts. A later writing estimate would depend on the agreed page list and review owner. The handover records those conditions instead of implying that a complete rewrite can already be scheduled. This invented example shows a proposal preparation artifact; it does not report a contract, a client approval or a deployed website.
A checklist for your next step
- Preserve the original request.
- Confirm decision authority.
- List scope-changing unknowns.
- Make assumptions explicit.
- Check the offer against discovery.
Common questions
Should I forward the entire enquiry to a collaborator?
Only if the collaborator needs it and sharing is appropriate. A purpose-specific handover may provide the necessary context with less sensitive detail.
Can the proposal recommend a different first step?
Yes. Explain the reason and resulting output clearly, and distinguish the recommendation from what the prospective client initially requested.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.