1. Wedding Planning Platform
  2. Features
  3. Activity and Evidence
Feature · Activity and Evidence

Activity and Evidence

Attach contracts and plans to each event and keep a receipt of every guarded action and its outcome.

OverviewOperation Exceptions
Wedding Planning Platform · Activity and Evidence

Operation Exceptions

Operation receipts

New
ParentActionOperation keyResult stateOccurred atFailure reason
EVN-93858ACT-746OK-532Pending21 OctCut to length
EVN-32609ACT-670OK-852Failed17 OctWeld frame
EVN-64116ACT-776OK-458Needs review23 OctDrill and tap
EVN-72840ACT-107OK-375Pending18 OctDeburr
EVN-14095ACT-780OK-214Failed15 OctAssemble
6 of 6 records
ACT-746Operation receipts · OR-99095
Pending
ParentEVN-93858
Operation keyOK-532
Occurred at21 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Keep the paper trail with the event

Wedding planning runs on documents: venue contracts, floor plans, run sheets, vendor quotes and the couple’s signed proposals. Each document is attached to its event with a title, an evidence type, the uploader and the upload time. Visibility is Internal for the planning team or Shared for documents the team may pass to vendors and the couple.

Alongside the documents, every guarded action on an event leaves an operation receipt: the action taken, a unique operation key, the version it expected, the outcome and the time. Outcomes are Pending, Completed, Failed or needs review, with a failure reason and any external reference.

How the work is organized

  • Documents by type. Evidence types such as contract, floor plan or run sheet let the team find the right file quickly.
  • Receipts for every action. Approvals, reservations, admissions, closures and cancellations each leave a receipt. A repeated action returns the original receipt.
  • Exceptions reviewed by finance. Receipts that are Pending, Failed or needs review are compared with the provider’s evidence and resolved.

What to agree during setup

Agree the evidence types you use and which documents may be shared. Decide who reviews operation exceptions and how quickly. Agree how a receipt marked needs review is resolved and who signs off the correction.

Check the handoff on an actual case

On the morning of a wedding, the venue’s door tablet loses signal while a guest is being admitted. The admission is attempted twice. The first attempt leaves a receipt marked Pending; the second, with the same operation key, returns the same receipt and does not admit the party twice.

That afternoon the Finance Coordinator opens Operation Exceptions, sees the Pending receipt and compares it with the admission record. The party’s admission time is present, so the receipt is marked Completed. Another receipt, for a refund the provider has not yet confirmed, is marked needs review with the reason recorded until the provider’s refund evidence arrives.

What your team sees

  • Operation Exceptions — Receipts waiting for review, with action, outcome and failure reason.
  • Shared Documents — Files the team may share with vendors and the couple, by event and type.

Follow the work through

Map the source records before importing documents.

What it keeps track of

Data model
Record attachments
Supporting documents and evidence attached to events
Operation receipts
Durable receipts for guarded operations executed on events
Events
Wedding events with capacity, lifecycle and venue
Team members
Staff members belonging to an organization

Who uses it

Permissions
Finance Coordinator
, Lead Planner, Planning Director, Admin.
The Lead Planner attaches documents.
The Finance Coordinator reviews operation exceptions.
The Planning Director and Admin read the trail when a question arises.

Set up Wedding Planning Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started