Verity for wedding planners
A planner’s product is coordination and a budget kept. Verity holds the vendor bookings, the payment milestones and every change to the budget against the event.
Runs alongside your existing accounting arrangement.
Verity / Events
LiveEvents booked
14
Vendor payments due
₹1.4 Cr
Budget variance
4 events
Unconfirmed vendors
18
Needs attention
Illustrative figures. Verity shows your own events in this shape.
How the business runs
Wedding planning is coordination as a product. The planner does not usually own the venue, the catering, the décor, the photography or the music — they book, sequence and pay a set of independent vendors so that everything arrives on one day that cannot move. The value is that the client does not have to hold twenty relationships and a hundred dependencies.
The commercial risk is that the planner sits between the client’s money and the vendors’ payment schedules. Vendors want advances and milestone payments on their own terms; the client pays on theirs. A planner with one point four crore of vendor milestones due in a month and client funds not fully received is carrying a timing risk that nobody has quantified.
The second is scope. Weddings change constantly, and every change is emotionally charged, verbal and rarely costed at the moment it is agreed. Nine changes across three events with no recorded cost impact is a budget conversation that will happen later, badly.
The third is confirmation. A vendor who is verbally booked and not confirmed is not booked, and eighteen unconfirmed vendors against events inside sixty days is the planner’s real risk profile.
The fourth is that the day itself is a sequence with dependencies, and the run of day exists as a document rather than as a set of owned steps.
Verity holds the event, its budget, its vendors, its payment milestones and its changes as one record.
What Verity calls these things
What gets in the way
Planning problems come from verbal agreements, unconfirmed vendors and a budget that moves without being restated.
Vendors are verbally booked and not confirmed
A vendor is discussed, agreed and assumed. Whether they are actually contracted for the date is known only when someone checks.
In Verity Vendor booking is a workflow with a confirmation state, so unconfirmed vendors against a date are visible as risk.
Scope changes are agreed emotionally and costed later
A client adds an element in a conversation, the planner accommodates it, and the cost surfaces in a budget review weeks later.
In Verity Changes are raised as change orders with cost impact at the moment they are agreed.
Vendor payments and client receipts are unsynchronised
Vendors demand milestone payments on their schedule and clients pay on theirs, and the planner absorbs the timing gap.
In Verity Both schedules sit on the event, so a funding gap is visible before it becomes the planner’s money.
The budget is agreed several times
The original budget, the revised budget and the current spend exist in different documents and different conversations.
In Verity One budget record with a change history, so what was agreed and when is unambiguous.
Run of day exists as a document
The sequence for the day is a document that everyone has a different version of, with no owners against steps.
In Verity The run of day is work with owners, times and dependencies, so a slip is visible as it happens.
Vendor performance is never recorded
Planners recommend vendors from experience, and the experience is anecdotal rather than recorded across events.
In Verity Vendors carry their delivery, punctuality and issue history across events.
The complete system
One system across events, budgets, vendors and the day itself.
Work
Each event is work with a client, date, venue, functions, budget, vendor set, timeline and state.
Why it matters here Everything the planner does hangs off the event, and it currently hangs off a folder.
In practice Fourteen events in ninety days with their vendor confirmation and budget position visible together.
Workflows
The agreed budget, changes to it, vendor payment milestones and client receipts are defined steps with recorded decisions.
Why it matters here Costing a change when it is agreed is the difference between a planner’s margin and a difficult conversation.
In practice Nine changes across three events with cost impact recorded and signed rather than absorbed.
Suppliers
Vendors are relationships with their bookings, contracts, payment terms, delivery history, punctuality and issue record.
Why it matters here The planner’s product is the vendor set, so vendor reliability is the product’s quality.
In practice Eighteen vendors unconfirmed against dates inside sixty days, four on the same day.
Relationships
Clients are records with their event, budget, preferences, decisions, communications and payment position.
Why it matters here Weddings involve several decision-makers, and what was agreed with whom matters enormously.
In practice A decision recorded against the client with who agreed it and when.
Records
Vendor contracts, design references and run sheets attach to the event they belong to with versions retained.
Why it matters here Disputes on the day are settled by what the contract and the run sheet actually said.
In practice The signed vendor contract on the event record, referenced when delivery differs.
People
The team is modelled once, and every vendor booking, change order and run-of-day step shows who owns it.
Why it matters here On the day, ownership of each step is the entire mechanism of coordination.
In practice Run-of-day steps with named owners rather than a document everyone has read differently.
Reports and analytics
Budget against actual per event, change order recovery, vendor payment against client receipts, vendor reliability and event margin come from the operational records.
Why it matters here A planner needs to know which events made money and which vendor sets worked, and both are usually impressions.
In practice Margin by event type and size, so pricing reflects what events actually cost to deliver.
Verity AI
Verity AI answers from your own event, vendor, budget and payment records, respects permissions, and can create assigned follow-ups.
Why it matters here The questions worth asking are about confirmations missing and money moving in the wrong order.
In practice "Which vendors are unconfirmed against events inside sixty days?" returns eighteen with follow-ups assigned.
Communication
Decisions, approvals and correspondence attach to the event or change they concern.
Why it matters here Wedding decisions are made in conversations across several family members, and the record is the only version.
In practice A change agreed on a call, recorded with the person who agreed it.
Control
One permission model and one audit trail, with vendor commitments and budget changes as recorded decisions.
Why it matters here Coordinators commit client money to vendors, and that authority should be explicit.
In practice A vendor booking above threshold routed to the lead planner and recorded.
Locations
Venues and sites are locations with their own constraints, contacts and history.
Why it matters here Venue constraints repeat across events, and the last event at the same venue is the best briefing for the next.
In practice Access and timing constraints from the previous event at the same venue.
Work in motion
These already happen. As records they stop depending on the planner’s memory on the day.
Quoting from what comparable events actually cost is the largest available improvement in planner margin.
A verbally agreed vendor is not a booked vendor, and the difference is only visible if confirmation is a state.
Costing at the moment of agreement is what prevents the budget being renegotiated at the end.
The planner sits between two payment schedules, and only a projection shows when that becomes their problem.
A step with an owner and a time is coordination; a document everyone has read is hope.
The next event is priced and staffed from this record rather than from memory.
Verity AI
Verity AI reads the same event, vendor, budget and payment records the business creates as it plans. It answers from your own event book, respects permissions, and can turn an answer into follow-ups.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the event and vendor records at the point the condition is met.
When
A vendor remains unconfirmed as the event approaches
When
A client requests a change
When
A vendor milestone falls due before client funds arrive
When
Event spend passes the agreed budget
When
A vendor is committed to overlapping events
When
An event completes
What you can understand
Budget, confirmation and vendor performance from the event records themselves.
All of this comes from records the planner creates while planning — bookings, changes, payments and the run of day.
One system, different ways of seeing it
Everyone works from the same records, and each opens on what they need.
Principal planner
What is at risk and what is it making?
Unconfirmed vendors, budget variance, funding gaps, margin by event type.
Event coordinator
What is unconfirmed on my events?
Vendor confirmations, change orders outstanding, payment milestones, run-of-day preparation.
Accounts
What is due and what has come in?
Client receipts against schedule, vendor milestones due, funding gaps, balances at closure.
Where it is used
Booking as a workflow with a confirmation state, so a verbally agreed vendor is visibly different from a contracted one.
Client changes costed and raised when they are agreed rather than surfacing in a budget review weeks later.
Vendor milestones and client receipts both on the event, so a funding gap is visible before it becomes the planner’s money.
The agreed budget, its revisions and current commitment on one record, so what was agreed and when is unambiguous.
The sequence as work with times, dependencies and named owners rather than a document with several versions.
Delivery, punctuality and issues recorded per vendor, so recommendations rest on history rather than impression.
Cost reconciled against budget per event, so pricing reflects what comparable events actually cost to deliver.
Plain-language questions across confirmations, budgets, payments and conflicts, with follow-ups assigned in the same step.
Getting there
Your accounting arrangement continues to run and is mapped during implementation. Clients, booked events, vendors and their terms, budgets and payment schedules are brought across, and Verity is configured around how the business already plans.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own event, vendor, budget and payment records: which vendors are unconfirmed against events inside sixty days, which events are above budget, which vendor milestones fall due before client funds arrive, which changes were agreed without a cost impact. Each answer can become a follow-up.
A caterer delivers with its own crew, stock and equipment. A planner coordinates other people’s vendors and manages a client’s budget, so the record has to be the vendor set, the confirmation state, the payment schedules on both sides and every change to the budget.
A change is recorded with who requested it, costed immediately, and raised as a change order with the revised budget for client approval — which is what prevents the whole budget being renegotiated after the event.
Vendor payment milestones and client receipt schedules both sit on the event, so the position is projected forward and a gap is visible before the planner has to bridge it out of their own funds.
Vendors carry their delivery, punctuality and issue history across every event, so recommendations and selection rest on a record rather than on the most recent memorable experience.
The sequence is work with times, dependencies and named owners, and steps are marked as they complete, so a slip is visible against the steps that depend on it rather than discovered downstream.
No. Accounting continues and is mapped during implementation. Verity holds the events, budgets, vendors, confirmations, payment schedules and the reporting across them.
A planner running fourteen events a year still coordinates hundreds of vendor commitments and payment milestones, and carries the timing risk between two payment schedules on every one.
About four weeks: discovery and mapping of how events are quoted and coordinated, configuration of budget categories and vendor terms, migration of booked events and vendors, then an ongoing operations partnership.
Verbally booked vendors on dates inside two months are the planner’s real risk. Tell us how confirmations are tracked today.