Sync Budget rebuilds the customer-facing proposal from its Project Budget. It is an explicit transfer from the budget to the proposal, rather than continuous synchronisation between the two tabs.
Consolidation methods
Option | Resulting organisation |
Multiple stages, all detail from budget | Uses multiple proposal stages and carries across the detailed budget structure. |
Single stage, converting deliverables to lines | Creates one proposal stage, with budget deliverables represented as line items. |
Multiple stages, converting deliverables to stages | Represents budget deliverables as separate proposal stages. |
Non-budgeted tasks
Include non-budgeted tasks in proposal controls whether internal-process items and deliverables without a budget are included as zero-value lines. The checkbox is separate from the consolidation method.
Replacement behaviour
Syncing overwrites the existing proposal stages and line items. This includes changes made directly on the Proposal tab. Drum warns that this action cannot be undone.
The source Project Budget and the client-facing Proposal tab remain separate working areas. Later changes in either area can leave their values different until the proposal is reviewed or rebuilt.
Document content
The selected method affects how much budget detail becomes part of the proposal. The final document also depends on the proposal’s template. Internal task descriptions can therefore reach the client-facing document when included in the proposal.