← Help

Product help

Reuse a reviewed budget worksheet

Product team · Reviewed

Reuse a wedding budget without copying its financial history

Open Template studio, choose Budget worksheet, and create a fixed-amount starting point for your team. A worksheet keeps row labels, amounts, assumptions, category mappings and an optional project target. Amounts are stored as integer USD cents; the editor shows dollars. These are planning estimates, not supplier quotes or committed charges.

Create, capture or load a worksheet

Start from a blank budget, choose a budget from the original starter library, or capture an owned project’s planned budget. Save a budget worksheet in the planning budget opens the exact source for review. Capturing copies planned categories and the project’s target; it excludes vendor bookings, invoices, payments, expenses and item-level paid records.

Original budget starters remain at their existing public URLs. Their distinct category labels are retained. Choose an explicit destination category for every row before applying; the system does not guess that a combined “venue and food” allowance belongs entirely to either one. Split rows when the allowance needs more than one destination. Rows mapped to the same category are added together, to the cent.

Your team or support can prepare a complete studio JSON file for an account-specific worksheet. Use Load an original worksheet or template file, inspect the complete contents, adjust amounts and assumptions, then save a private copy. Imports are limited to 80 KB and record the supplied filename and exact content fingerprint. They do not grant support or the file’s author access to the destination workspace. The file is not treated as verified advice.

Authorized copy editors can export the reviewed definition as JSON. Exported files contain what the template view shows, so remove private details before sending one elsewhere. Loaded templates start privately and use the studio’s existing named sharing and community review controls.

Apply only the changes you reviewed

Open the saved version, choose a current owned project, and select one of two modes:

  • Add only missing categories keeps every category that already has a planned amount, including an explicit zero. The preview marks those rows as skipped.
  • Replace only mapped categories changes the listed categories to the worksheet’s combined fixed amounts. Unlisted categories remain intact.

The project target stays unchanged unless you select Also apply this worksheet’s project target. A blank worksheet target explicitly clears the target only when that checkbox is selected. Before confirming, inspect every old/new amount, the planned total and target shown in the review.

If the destination changed after preview, refresh and review again. Applying the same confirmed request twice returns its existing receipt. It does not create another allocation, invoice or charge. Existing category editors also carry the amounts they displayed and reject stale saves instead of silently overwriting somebody else’s plan.

Keep versions and permission boundaries

The studio’s immutable versions, side-by-side review, restoration, exact named grants, independent copies, revocation and community moderation also apply to budgets. See Template studio for those controls. A restored or copied worksheet does not retroactively change a project where an earlier version was applied.

Budget application needs current full workspace permission and ownership of the destination project. Shared-wedding participation does not expose another business’s private budget. The current planning budget page presents category plans and its separate item ledger together; actual vendor costs, signed records, invoices, payments and recorded item commitments are preserved.

The versioned /api/v1/budget-plans interface uses the same authorized preview/apply service. Exact category edits require the expected previous amount, and all writes have request receipts and private before/after audit records. No external provider setup is needed beyond the existing workspace and database foundation.