Solutions
One platform. Different pathways. One coordinated event picture.
Pick your role to see the problem, how you use Event101, what you gain, and the outcome.
Choose your pathway
Choose the role that fits you, then go straight to that section.
- OrganisersPlan and deliver events with full control and visibility.Access Event101
- Funeral directorsFast, consistent funeral notifications without festival-scale overhead.Access Event101
- Protest organisersStructured routes, safety detail and submissions authorities can review.Access Event101
- Suppliers and contractorsGet discovered and stay aligned with live event requirements.Access Event101
- Local authoritiesReview events with clear evidence and less rework.Access Event101
- Emergency and statutory stakeholdersOperational awareness tied to the live event record.Access Event101
- Public and businessesUnderstand event activity and plan around it.View event activity
Event organisers
Review-ready plans without rebuilding the same information across tools.
You work in one event record: information is entered once, rules evaluate the event, and timelines, risk, budgets, documents and submissions stay aligned from that same source.
The problem
Planning splits across spreadsheets, email and documents. Risks, timelines, roles and submissions drift apart.
How they use Event101
- Create workspaces and capture event detail in one structured record.
- Build timelines, EMPs and submissions from that same record.
- Link risk assessments to real activities and locations.
- Assign responsibilities and track permits and notifications.
- Invite suppliers and stakeholders into the coordinated record.
What this gives them
- Details, timelines, risks, budgets, documents and submissions stay tied to one record.
- Capture once; reuse across planning outputs without duplicate entry.
- Requirements surface when activities, scale or locations change.
Outcome
Structured planning from draft through delivery and review.
Funeral directors
High-frequency notifications with a focused, respectful workflow.
Each notification sits on one structured record so route and timing updates reuse the same fields and keep outputs aligned for authorities and partners.
The problem
Notifications must be fast and consistent without forcing full-scale festival planning for every procession.
How they use Event101
- Capture route, timing and location in a dedicated pathway.
- Reuse notification patterns across many events.
- Coordinate access and operational detail in one place.
What this gives them
- Structured records replace ad hoc emails and attachments.
- Same fields feed repeatable notifications and audit trails.
- Less manual repetition between similar events.
Outcome
Faster, clearer notifications with less administrative load.
Protest and civic assembly organisers
Routes, stewarding and safety detail in a coherent submission.
Assembly detail lives in one record, rules structure what reviewers need, and submission outputs stay aligned when routes or stewarding change.
The problem
Assemblies move quickly. Routes, crowd risks and communications must be explicit for reviewers.
How they use Event101
- Define assembly points, routes and timings.
- Record stewarding, safety and communications.
- Submit structured material authorities can review in context.
What this gives them
- One record holds route and safety detail reviewers can trace.
- Updates stay linked instead of scattered across messages.
- Fewer gaps between what happened on paper and what is planned.
Outcome
Accountable planning for assemblies and marches.
Suppliers and contractors
Visible to organisers and aligned to live event requests.
Your profile and responses attach to the organiser event record, so requests, documents and quotes reuse the same live data instead of a separate thread.
The problem
Coordination often runs through email: repeated uploads, unclear scopes and mismatched documents.
How they use Event101
- Maintain a profile and service categories.
- Respond to invitations inside the event context.
- Upload documents against explicit requirements.
What this gives them
- Profiles and documents stay tied to the directory and assigned events.
- Organisers pull from one source instead of chasing attachments.
- Less duplicated asks for the same evidence.
Outcome
Clearer expectations and less repeated administration.
Local authorities
Review linked evidence instead of fragmented packs.
You review the same structured record organisers maintain, so submissions, risks, timelines and documents stay aligned with what was evaluated under the rules.
The problem
Incomplete or out-of-sequence submissions drive follow-up, slow decisions and weak oversight.
How they use Event101
- Open one structured record per event.
- See timelines, permits, risks and documents together.
- Track gaps and support inspections from the same picture.
What this gives them
- Submissions draw from live data instead of stitched documents.
- Risk, timelines and budgets stay traceable to event inputs.
- Review trails reflect what organisers actually hold in the record.
Outcome
Faster review with clearer evidence and fewer loops.
Emergency and statutory stakeholders
Awareness grounded in the authoritative event record.
Granted views read from the same live record, so when organisers update detail your operational picture and published context stay aligned.
The problem
Informal updates and attachments make it hard to trust what is current for resource and safety planning.
How they use Event101
- Access operational detail granted for your role.
- See public activity in context where published.
- Align notes with the organiser record instead of side channels.
What this gives them
- Visibility tracks the same structured data organisers maintain.
- Fewer conflicting versions across agencies.
- Readiness decisions reference current event inputs.
Outcome
Stronger readiness and multi-agency alignment.
Public and local businesses
Published activity from the same record organisers operate.
Published dates and notices surface from the event record, so what you read stays aligned when organisers update what they choose to publish.
The problem
Notices and informal updates often disagree about dates, routes and impacts.
How they use Event101
- Read published activity for dates, locations and notices.
- Use alerts when your site offers them.
- Reach organisers only where contact is enabled.
What this gives them
- Public-facing views can reflect approved fields from the live record.
- Fewer conflicting posters and ad hoc messages.
- Local impacts are easier to see in one place.
Outcome
People can plan around activity with clearer information.
One record. Clear reuse.
Information is captured once and reused across planning, risk assessment, timelines, budgets, documents and submissions.
- Single authoritative event record per event.
- Triggered requirements when activities, scale or locations change.
- Linked data across risk, timelines, budgets, documents and review packs.
- Role views read from the same structured source.