How should a proposal separate deliverables, assumptions and exclusions?

Give each part of the proposal a distinct purpose

Deliverables describe what the supplier will provide. Assumptions describe the conditions on which the offer is based. Exclusions identify related work that is not included. Separating these ideas helps both parties understand the offer before they commit resources.

Use ordinary language suited to the customer. A short, specific description is often more useful than a broad phrase such as end-to-end support. Define the work closely enough that someone can later compare the result with the offer and determine whether the agreed scope has been completed.

This is a practical drafting method, not a substitute for the customer's procurement instructions or the final contract. If a tender prescribes schedules or prohibits qualifications, follow that process and seek clarification through the permitted channel. Do not assume a proposal can override mandatory terms merely by adding an exclusions page.

Write deliverables that can be reviewed

Describe each output, its purpose and the relevant boundary. For a document assignment, identify the document, subject, period or entity covered and the format required. For an ongoing service, describe the activities and reporting expected during the agreed period.

State what completion means in a way that fits the work. This might involve delivery of a reviewed draft, correction of agreed comments or completion of specified administrative steps. Avoid promising a third-party approval as though it is entirely within the supplier's control.

Identify the evidence of delivery. An email confirming that a file was sent is different from the customer accepting it or an authority approving an application. Where those stages matter, name them separately and assign responsibility for the next action. This makes progress reports more useful and reduces confusion about what remains outstanding.

Make the planning assumptions visible

Record conditions that materially affect effort, price or timing. Examples include the number of entities involved, the period of records, the availability of customer information and the number of review rounds included. Use assumptions because they explain the offer, not because they provide a place to conceal uncertainty.

Distinguish an assumption from a fact already known to be false. If the customer has told you records are incomplete, do not price on the assumption that all records are complete without addressing the mismatch. Describe the known condition and agree how the missing material will be handled.

For each important assumption, explain the consequence if it changes. Additional entities may require more work; delayed information may move the delivery schedule. The proposal should identify the review process rather than inventing an automatic additional charge that the customer has not understood or agreed.

Set boundaries without contradicting the offer

An exclusion should identify a plausible related service that is outside the agreed scope. It should be specific enough to prevent misunderstanding. A generic statement excluding everything not expressly mentioned may still leave the customer unable to understand a broad promise elsewhere in the document.

Check exclusions against the headline, deliverables, price description and sales discussions. If the proposal says complete application support, clarify which application steps are included and whether ongoing compliance after the application is outside the engagement. Do not bury a major limit in small print while keeping an unrestricted headline.

Explain whether excluded work can be discussed separately. This is an invitation to agree a new scope, not a claim that the customer must buy an additional service. Keep the customer's ability to make an informed decision central to the presentation.

Use one example to test all three categories

Consider an illustrative assignment to prepare a company profile. The business can use a simple scope table to see whether the offer is internally consistent. The example is a drafting illustration and does not state Vatco's fees, turnaround or standard package terms.

If the proposed profile includes project photographs but photography is excluded, the proposal must explain who supplies suitable images. A dependency should not disappear between the deliverables and exclusions sections.

Assign customer and supplier responsibilities

Identify who provides source information, who reviews drafts and who has authority to approve changes. Where several customer departments are involved, ask for a coordinated response rather than assuming every comment has equal approval status.

State any necessary access or permissions. The supplier may need documents or authorised access to perform the work, but that does not justify requesting personal passwords or unrestricted access by default. Specify the task and appropriate arrangement, and collect only information needed for the engagement.

Make responsibilities workable. A requirement for the customer to approve every minor step can delay delivery, while giving the supplier unrestricted discretion can create unwanted commitments. Agree meaningful review points and identify what can proceed between them. Record unanswered questions before work begins rather than leaving them to be resolved during a dispute.

Connect scope to the price and schedule

The price should correspond to the deliverables and assumptions. Explain the charging basis and material items included or separately chargeable. If third-party fees are relevant, distinguish them from the supplier's fee and verify how they will be handled.

Describe timing in relation to the information and decisions needed. An estimated working period may begin only after specified documents are available. A regulator's processing period should not be presented as a guaranteed supplier delivery time. Identify the dependency and keep the estimate appropriately qualified.

Review the proposal for contradictory numbers or dates. A cover email, pricing table and detailed scope should describe the same offer. If the customer changes the brief, update the price and schedule where needed rather than leaving an old quotation attached to a new scope.

Agree how changes will be considered

A useful change process starts with a description of the requested change and its reason. The supplier then assesses the effect on work, price and timing, and the authorised parties decide whether to proceed. Keep the record with the current proposal or contract.

Separate correction of an agreed deliverable from genuinely additional work. A supplier should not automatically label every customer comment a scope change. Compare the request with the original description and acceptance criteria, and explain the distinction with reference to the actual offer.

For formal procurement, changes may be constrained by the bid rules and applicable process. National Treasury's evaluation guidance is useful context, but the issued documents govern the particular response. Do not promise an informal workaround to a mandatory requirement.

Review the proposal as a single offer

Read the proposal from the customer's perspective. Ask what they reasonably expect to receive, what they must supply and what would require a further decision. Resolve conflicts between sections before sending the document for acceptance.

Use a final checklist covering deliverables, assumptions, exclusions, responsibilities, price, timing and change approval. Keep the approved version and the supporting brief. Ask the person who will deliver the work to confirm that the stated output is achievable with the resources and dependencies described. Their review can reveal a commitment that a document-only check would miss. When discussing the offer, refer to the same version so that verbal clarification does not create a different understanding from the written document.

Proposal-writing assistance can help make these boundaries clear. The result should be an offer the customer can assess and the delivery team can perform, with uncertainty addressed openly and changes handled through an agreed process.