Skip to main content
After an approved Go decision, Proposal and compliance becomes the main response workspace. The goal is not to generate a long document. The goal is a traceable response that answers every requirement with evidence, uses approved pricing, and can be reviewed as a stable version.

​
Before generating a proposal

Confirm that you have the latest tender documents and addenda, a reviewed requirement list, an up-to-date company profile, evidenced similar projects, appropriate team CVs, technical and commercial assumptions, mandatory authority templates, and the required Go approval.

​
Proposal workflow

1

Build the response plan

Map each section to the requirements it covers, then assign an owner, reviewer, and internal due date.
2

Generate the first draft

Tender uses opportunity facts and company data. Missing information should remain a visible gap, never an invented claim.
3

Review each section

Edit the text or request a focused regeneration. Record the reason when a change affects a commitment, assumption, or claim.
4

Resolve comments

Use comments for questions and review feedback, then close them only after the underlying text or evidence is corrected.
5

Review compliance

Confirm that every requirement is covered or escalated and that cited evidence is current and appropriate.
6

Complete the commercial proposal

Enter price items, quantities, units, currency, taxes, and assumptions. Review line items before accepting totals.
7

Freeze the review version

Request approval for a clearly identified version. Later changes must create a visible revision and may require reapproval.

​
Review responsibilities

​
Compliance states

  • Covered: A clear response and evidence or reference exist.
  • Needs review: Text exists, but evidence or a decision is incomplete.
  • Missing information: A specific input is required before completion.
  • Exception or deviation: The response does not accept the condition and requires disclosure and escalation.
Do not turn an assumption into a contractual promise. Manually verify figures, customer names, CVs, certificates, delivery dates, and pricing before approval.

​
Commercial review

Review units and quantities, currency and exchange-rate assumptions, tax and fees, shipping and implementation, price validity, payment terms, guarantees and banking cost, consistency between price and scope, and every subtotal and total.
Approval of the technical text is not approval of the price. Tender separates proposal approval from price or financial-commitment approval according to role.

​
Versions and export

  • The active proposal displays its version.
  • Editing or regenerating a section creates a reviewable trace.
  • Do not silently change an approved proposal; return the new revision to review.
  • Open exported PDF or proposal files and inspect layout, fonts, tables, page numbering, and attachments before packaging.

Approvals and roles

Learn who can approve the decision, price, proposal, and submission.

Submission package

Run readiness checks and a sandbox simulation before any external action.