These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Wedding Planning Platform
- Features
- Review Queue
Review Queue
Record independent decisions to approve, reject or return each submitted event and vendor commitment.
OverviewReview Decision Log×
Wedding Planning Platform · Review Queue
New
Review Decision Log
Review decisions
| Parent | Source revision | Decision | Reason | Reviewer | Decided at | |
|---|---|---|---|---|---|---|
| EVN-13591 | 50 | Approve | Approve rd-167 | 12 Oct | ||
| EVN-40354 | 390 | Return | Reject rd-408 | 27 Oct | ||
| EVN-16202 | 700 | Approve | Return rd-160 | 18 Oct | ||
| EVN-70817 | 70 | Return | Approve rd-987 | 20 Oct | ||
| EVN-86453 | 330 | Approve | Reject rd-648 | 07 Oct |
6 of 6 records
Approve rd-167Review decisions · RD-11199
ApproveParentEVN-13591
Source revision50
Decided at12 Oct
What you can do
Decide the version that was submitted
Approvals in wedding planning are about specifics: this guest count, this venue, this fee. A review decision records the decision (Approve, Reject or Return), the reason, the reviewer, the time and the version number it applies to. If the event changes after submission, the decision on the earlier version no longer applies, and the new version waits for its own review.
The Planning Director works the review queue. The reviewer is independent of the person who prepared the event or commitment, so a planner does not approve their own work.
How the work is organized
- Approve. The event or commitment moves forward, and the decision is kept with its reason.
- Return. The work goes back to the preparer with a reason, for a revised version.
- Reject. The work stops, with the reason recorded for the team and the couple.
What to agree during setup
Name the Planning Director and any deputy who reviews when they are away. Agree what a reviewer checks for each event: venue rules, capacity, timing and documents. Agree what a vendor commitment review checks: client approval, fee and deadline. Decide how quickly reviews should be turned around in the weeks before a wedding.
Check the handoff on an actual case
A planner submits the reception for a June wedding with a capacity of 180 at a hotel ballroom. The Planning Director opens Events Awaiting Review, checks the venue’s eligibility note, which limits the ballroom to 160 for a seated dinner, and returns the event with that reason. The planner reduces the capacity to 160 after speaking with the couple and resubmits.
The new version appears in the queue. The director approves it, and the decision records the version number, reason and time. A week later someone tries to apply the old return decision again; it is refused because it belongs to an earlier version.
What your team sees
- Events Awaiting Review — Events submitted for review, with owner, venue, start, capacity and version.
- My Review Decisions — Decisions the signed-in reviewer has recorded.
- Review Decision Log — Every decision with its reason, reviewer and version.
Follow the work through
- Event plan to close: See where event approval sits in the lifecycle.
- Vendor commitment approval: Review a vendor booking before the vendor proceeds.
Rehearse access with a planner account before go-live.
What it keeps track of
Data model- Review decisions
- Independent review decisions recorded against event revisions
- Events
- Wedding events with capacity, lifecycle and venue
- Vendor commitments
- Vendor commitment requests and approvals for an event
- Team members
- Staff members belonging to an organization
Who uses it
Permissions- Planning Director
- , Lead Planner, Vendor Coordinator.
- The Planning Director decides.
- The Lead Planner and Vendor Coordinator prepare and resubmit work.
Set up Wedding Planning Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.