Enter each event's date and location, the standards that apply to all of them, what changes from event to event, the delivery milestones and who holds the contract. The organiser builds a master request with an individual brief for each event and lists the dependencies still open. It assumes nothing about crew, availability or package pricing.
What this organiser does
It brings several events under one request. You write the shared standards once, then add a short brief for each event covering date, place and anything that differs. The result is a master request that a photography team can read in one sitting.
Typical uses are a conference series, a company roadshow, a school programme across terms or a set of related celebrations.
How to use it
- Add each event with its date and location. Mark any detail not yet decided.
- Write the shared standards, such as style, formats, captions, image-use limits and approvers.
- For each event, note what varies: venue rules, priority people, scope and delivery milestones.
- Name the contracting owner for the whole commission and for each event if they differ.
- Read the list of unresolved dependencies and settle what you can.
Reading the result
The master request is the cover page; the individual briefs sit beneath it. The dependency list shows items such as an undecided venue, a missing approver or a date that clashes with another event.
Our guide on photography for a recurring event series helps you decide what to standardise, and booking photography across several related events under one agreement explains how agreements usually work. For cost structure, see pricing a multi-day photography commission.
Assumptions and limits
The organiser does not assume availability, a package discount or the same crew for every date. Each of those is confirmed in writing in the quotation. When events are in different cities, photography coverage and outstation planning in Malaysia covers travel questions.
If your events repeat on a schedule, our recurring event photography enquiries page is the right place to start. Your entries stay in your browser unless you save them on this device.
Checklist
- List each event with its date and location.
- Write the standards that apply to every event.
- Mark what differs between events.
- Set delivery milestones for each event.
- Name the contracting owner and the approver.
- Note any date or location still undecided.
- Leave crew and availability open until confirmed.
Send us the master request and the event briefs, and we will say in writing which dates and locations we can plan for and how the quotation separates each event.
Request a proposal for our eventsCommon questions
Will one crew cover every event?
Do not assume so. Dates, locations and travel decide who can attend each event. We confirm the crew assigned to each event in writing, and the master request leaves that open until then.
Is there a package discount for several events?
The organiser does not assume one. Ask us whether anything applies to your commission, and read how the quotation lists each event, so you can compare it fairly with other offers.
What belongs in the shared standards?
Things that stay the same: image style, file formats, naming, caption rules, image-use limits and who approves. Keep event-specific items, such as venue rules and priority people, in each individual brief.
Who should hold the contract for a series?
The person or organisation that will approve and pay. Name them early, since agency, department and sponsor roles often differ between events and this affects the quotation and invoices.
Request a proposal for our events
Send us the master request and the event briefs, and we will say in writing which dates and locations we can plan for and how the quotation separates each event.
What happens next: You send your event details on WhatsApp. Our team reads the brief, asks what is missing, then confirms in writing whether the date, venue and coverage can be booked, with a quotation. Opening WhatsApp does not send anything, and a message is not a booking until both sides confirm.
Last reviewed: