Before writing a proposal, identify the unknowns that could change your scope, effort, dependencies or ability to deliver. Classify each as a question to resolve, an explicit assumption or a reason to propose bounded discovery. Assign an owner and avoid hiding important gaps behind confident language or unexplained contingency.
Read the proposed work as a chain of dependencies
Walk through the engagement from first input to final handover. What must the client supply? What will you examine? Who can approve the output? Which access, permissions or specialist contributions are required? Missing information becomes easier to recognize when attached to an actual stage. A generic request for “all relevant documents” often transfers the burden without explaining what you need or why.
Create a gap register with the question, the decision it affects, the source that could answer it and the consequence of not knowing. For example, an unknown number of content variants may alter effort, while an unconfirmed publication owner may affect review timing. Different consequences require different responses. Do not treat a missing decorative preference as equivalent to an unresolved permission to use confidential source material.
Check the boundaries of your own knowledge too. If the proposal assumes an integration or a provider capability you have not verified, mark it for investigation. General familiarity with a product does not establish that it supports the client’s plan, account or environment. Explain whether verification belongs in pre-proposal preparation or a separately scoped technical activity.
Choose how each uncertainty will be handled
Some questions should be answered before you can responsibly offer the work. Others can become explicit assumptions with a process for revision. A small, bounded exploration may be appropriate when the client cannot yet provide the answers. Explain the output of that exploration and the decision it will support. Do not use an undefined discovery phase as a way to postpone all questions without accountability.
When stating an assumption, make it specific and discussable. “Estimate covers one approved language version supplied as editable text” is clearer than “client to provide materials.” Describe what happens if the assumption changes, including whether scope or schedule must be reviewed. Avoid implying that every uncertainty gives you permission to charge more; the change process should be explained and agreed in the appropriate commercial document.
Prepare a short readiness decision
Summarize which elements are ready for a proposal and which remain blocked. You may be able to offer a content inventory while a larger implementation depends on access and approvals. Keep these boundaries visible. A narrower proposal with accurate conditions is more useful than a broad commitment built on guesses. It also helps the client decide what information to prioritize next.
Before sending the proposal, compare it with the discovery notes and unresolved question list. Check that no open item has disappeared merely because the document became polished. Confirm the dates and sources of material assumptions. Where evidence conflicts, describe the conflict and the decision needed. The goal is a reviewable offer with understandable dependencies, not an appearance that uncertainty has been eliminated.
Fictional example: an unknown document collection
In this fictional case, a writer is asked to revise an organization’s “small library” of guidance. The client supplies one short document, but discovery mentions translated versions and separate regional supplements. The writer does not extrapolate a whole-library price from the single example. Her gap register identifies the file count, language coverage, ownership and review process as scope-changing questions.
The client can provide an inventory but cannot yet confirm which versions are current. The writer prepares a bounded inventory review as a possible first engagement, with a list of deliverables and unresolved implementation questions. A later rewrite proposal would use the reviewed collection. No price, commission or delivered result is invented; the example shows how missing information changes the proposed sequence of decisions.
A checklist for your next step
- Trace required inputs and approvals.
- Link each gap to a decision.
- Resolve critical permissions first.
- State assumptions precisely.
- Review proposal readiness.
Common questions
Can I quote before every question is resolved?
Sometimes, if the remaining assumptions and their consequences are explicit. Do not quote confidently where an unknown could make delivery fundamentally different.
Should a contingency replace missing scope information?
No. A contingency does not explain what the client is buying or resolve an unknown permission, dependency or acceptance process.
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.