Generate and Review a Proposal

Understand the review-first model for proposals and scope documents.

Proposals & scopes2 min read

Sensra generates proposal drafts from your intake context, but the AI output is always a starting point — not a finished document. This article explains the review step and why it matters.

Why review before approving?

Review keeps you in control. An AI-generated scope can look polished while still misreading budget constraints, missing a dependency, or phrasing an assumption in a way that creates client confusion. The review step is where you catch and correct those gaps before they reach the client or become tasks.

What a proposal draft contains

A generated proposal document typically includes:

  • Scope sections: The deliverables broken down into reviewable chunks.
  • Assumptions: What the proposal assumes to be true that would change the scope or price if wrong.
  • Timeline: The project timeline and key sequencing.
  • Investment summary: Pricing or estimate tied to the scope.
  • Client responsibilities: What the client must provide for the project to move forward.

How to review a draft

  1. Open the proposal document from the project view.
  2. Read each scope section and confirm it matches what you intend to deliver.
  3. Edit any section that needs adjustment — wording, scope, pricing, or assumptions.
  4. Check the assumptions list. Add any the AI missed; remove any that do not apply.
  5. Confirm client responsibilities are accurate and complete.
  6. When the document accurately reflects the engagement, mark it Approved.

What approval unlocks

Approval is the boundary between draft and active project work. Once a proposal is approved, you can:

  • Create a client-facing proposal link to share for acceptance.
  • Draft a scope of work from the approved proposal context.

Task generation happens from an approved scope of work, not directly from the proposal. You can regenerate a draft if the first pass is too far off, but always review the new version before approving.

Editing after approval

If you need to make changes after approving, re-open the document and make edits. Significant scope changes after task generation should be reflected in the task board manually to keep the two in sync.

Need more help?

Contact support with account, billing, or project-specific questions.

Contact support