Can the descriptor be signed electronically?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96, 2000) and by state UETA laws (adopted by most states). Ensure signer intent, consent, attribution, and reliable record retention when relying on e-signatures.

Is notarization required for submission?

Not all jurisdictions require notarization for event descriptors. Where a notarized acknowledgment or RON is specified, follow state notary rules including identity-proofing and any audio-video retention requirements per state notary commissions.

How do I correct an error after signing?

Minor corrections generally require a signed amendment or a replacement descriptor. Use a new version signed by the same parties and retain the original for auditability; note the change date and reason in the record.

Who must sign the descriptor?

Authorized signers typically include the organizer (or officer of the organizing entity), venue representative, and any contracted vendors or insurers who are party to obligations identified in the document.

Which supporting documents should be attached?

Attach current certificates of insurance, site plans, vendor contracts, and permit application forms. Missing attachments are the most common reason for permit office rejection.

How long should signed descriptors be kept?

Retain signed descriptors per applicable rules: at least 3 years for tax records (IRC §6501(a)), 6 years for HIPAA-related documents (45 CFR §164.530(j)), and longer if state law or industry rules require it.

Electronic Signature
Templates
Miscellaneous
Event Festival Descriptor

Event Festival Descriptor

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

EVENT FESTIVAL DESCRIPTOR

Organizer Name: Service Provider Name:

RECITALS

WHEREAS, Organizer desires to engage Service Provider to perform certain production, presentation, or related services in connection with the event described below (the "Event"); and

WHEREAS, Service Provider has represented that it possesses the necessary experience, personnel, equipment and licenses to perform the services described in this Event Festival Descriptor (the "Descriptor"); and

WHEREAS, the parties desire to set forth their respective duties, payment terms, and operational parameters for the Event as set forth in this Descriptor.

EVENT DETAILS

Event Name Venue / Location

Event Start Date: Event End Date: Estimated Attendance:

SCOPE OF WORK

Service Provider shall perform the services described below in accordance with the operational schedule and specifications set by Organizer. The parties acknowledge that this Scope of Work is binding and may be amended only by written agreement signed by both parties.

SITE & TECHNICAL REQUIREMENTS

Service Provider and Organizer shall comply with the site access, load‑in, load‑out, power, rigging, and technical specifications required to safely and lawfully present the Event. Unless otherwise specified below, Service Provider is responsible for maintaining a technical rider and advance plan acceptable to Organizer.

Load-in Window

PAYMENT TERMS

Compensation: Organizer shall pay Service Provider the total sum set forth below in exchange for the services described in this Descriptor. All amounts are stated in U.S. dollars and exclusive of taxes unless otherwise indicated.

Total Fee Deposit Amount

Deposit Due Date: Final Payment Due Date:

Payment Schedule / Milestones

Late Payment: Any undisputed amount not paid within days after the due date shall incur a late fee of per month on the outstanding balance, and Organizer shall be responsible for reasonable costs of collection, including attorneys' fees.

TERM AND TERMINATION

Term Commencement Date: Term Expiration Date:

Either party may terminate this Descriptor for convenience upon days' prior written notice to the other party. Either party may terminate for cause if the other party materially breaches any obligation and fails to cure the breach within days after written notice specifying the breach.

CONFIDENTIALITY

Each party (the "Recipient") shall keep confidential and not disclose to any third party any non-public information of the other party (the "Discloser") obtained in connection with this Descriptor, including technical specifications, financial terms, attendee lists, marketing plans, and production details ("Confidential Information"), except as required by law or as necessary to perform obligations under this Descriptor. Confidential Information does not include information that is or becomes publicly known through no breach by the Recipient, or which is rightfully obtained from a third party without restriction. The obligations of confidentiality shall survive for a period of three (3) years following the later of the termination or expiration of this Descriptor.

INSURANCE, PERMITS & COMPLIANCE

Responsibility for securing permits, licenses and insurance shall be allocated as follows (check applicable boxes and identify any required limits):

Organizer responsible for permits
Service Provider responsible for permits

Required Insurance

FORCE MAJEURE

Neither party shall be liable for failure or delay in performance due to causes beyond its reasonable control, including acts of God, fire, flood, earthquake, governmental acts, labor disputes, or public health emergencies. The affected party shall give prompt written notice to the other and make reasonable efforts to resume performance. If the force majeure event continues for more than sixty (60) days, either party may terminate this Descriptor without further liability except for obligations accrued prior to termination.

INDEMNIFICATION & LIABILITY

Each party shall indemnify and hold harmless the other party from and against any third-party claims, damages, losses and expenses (including reasonable attorneys' fees) arising out of the indemnifying party's negligence or willful misconduct in connection with the Event. Neither party shall be liable to the other for consequential, incidental, or punitive damages except to the extent arising from gross negligence or willful misconduct.

GOVERNING LAW

This Descriptor shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of laws principles.

ENTIRE AGREEMENT

This Descriptor, together with any exhibits and schedules expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and communications, whether oral or written. Any amendment to this Descriptor must be in writing and signed by authorized representatives of both parties.

NOTICES

Organizer Notice Address Service Provider Notice Address

Organizer:

By:

Date:

Service Provider:

By:

Date:

What the Event Festival Descriptor Is and Why It Matters

An Event Festival Descriptor is a structured document that records the core details of a public event — scope, schedule, site layout, vendor lists, safety plans, insurance and permit references, and contact information for organizers and contractors. Municipal permitting offices, venue managers, insurers, and vendors use this document to review compliance, plan logistics, evaluate risk, and coordinate inspections. It is commonly required for festivals, street fairs, concerts, and similar gatherings where public safety, traffic, or neighborhood impacts must be managed and documented.

Primary Purpose and Practical Benefits

The descriptor centralizes all event-critical facts so reviewers, vendors, and emergency services see consistent information. It reduces approval delays, clarifies insurance and health-and-safety requirements, and creates an auditable record for post-event review and liability management.

Who Typically Prepares and Reviews This Document

Typical preparers and reviewers vary by role but share responsibility for safety, compliance, and logistics.

Event organizers and production managers responsible for operations, vendor coordination, and contract compliance.
Venue owners or operators who verify capacity limits, site access, and onsite services such as power or sanitation.
Local permitting staff and public-safety officials who assess traffic control, emergency access, and permit conditions.

Properly completed descriptors make permitting, insurance review, and on-site execution faster and more predictable for all parties.

Essential Sections to Include in a Professional Descriptor

A complete descriptor groups information so reviewers can verify compliance quickly and consistently.

Event Summary

Concise description of event type, purpose, dates, start/end times, estimated daily attendance, and primary organizer contact information for rapid context.

Schedule & Capacity

Detailed daily timeline, stage times, crowd capacity per zone, ingress/egress windows, and peak attendance estimates tied to site diagrams.

Site Plan

Scaled map showing vendor locations, stages, fencing, sanitation, first-aid, hydrants, electrical distribution, vehicle access, and emergency lanes.

Safety & Emergency Plan

Onsite medical staffing, fire-safety precautions, evacuation routes, radio channels, and point-of-contact information for coordinating responders.

Vendors & Contractors

List of vendors, contractors, contact names, scope of work, contract status, and proof of insurance or applicable licenses.

Insurance & Permits

Policy limits, certificate holder names, permit numbers and issuing agency, special conditions, and notice requirements for changes or cancellations.

Step-by-Step: Completing the Descriptor

Follow these four practical steps to prepare and submit a complete descriptor for review.

01

Gather Documents: Collect permits, insurance, site maps, and vendor contact info before you begin.
02

Populate Fields: Enter data into each field precisely and attach supporting files where required.
03

Review Internally: Have production, safety, and legal staff confirm entries and attachments.
04

Submit to Authority: Send completed descriptor and attachments to permitting office or insurer for approval.

How to Configure an Online Descriptor Workflow

Use a consistent workflow so submissions follow the same review and signature path every time.

Field	Configuration
Authentication Method	Email link with SMS code or stronger KBA for sensitive approvals
File Format	Submit as PDF/A to preserve layout and embedded signatures
Notifications	Automated email alerts to reviewers and vendors on each workflow step
Routing Order	Sequential routing: organizer → safety officer → insurer → permitting agency

Typical Submission Flow for eSubmission

A predictable flow reduces back-and-forth and improves tracking for all stakeholders.

Upload Descriptor: Submit the filled PDF and attach supporting permits and certificates.
Add Signers: Designate organizer, venue rep, insurer, and permitting official as signers.
Sign & Authenticate: Signers confirm identity and apply signatures using the chosen authentication method.
Receive Audit Trail: All parties get a copy and the system records timestamps, IPs, and actions.

Technical Requirements and Integrations

Ensure your platform supports required file types, signer authentication, and integration with review systems.

Integrations: Connectors for Salesforce, NetSuite, Microsoft 365, Google Workspace, Box, Procore, and AWS are common
File Formats: PDF, DOCX, and structured Excel inputs are typically supported
Authentication Options: Email link, SMS code, KBA, or advanced 2FA are used per vendor and risk level

Choosing a platform that supports these formats and integrations reduces manual rework and preserves audit trails for compliance.

Common Deadlines and Submission Windows

Timely submission aligns permits, inspections, and insurance effective dates; missing cutoffs can delay approval.

Permit Application Deadline:

Typically 30–90 days before the event depending on local rules

Insurance Submission Deadline:

Often required 14–30 days before the event start date

Vendor Contract Return:

Vendors usually must return signed contracts 14 days before load-in

Final Site Inspection:

Municipal inspections commonly scheduled within 48–72 hours of load-in

Post-Event Reports:

After-action reports may be due 7–30 days following event closeout

Key Milestones from Planning to Closeout

Use this milestone sequence to create a project plan and assign accountability across teams.

01

Planning & Budget

Define scope, budget, and preliminary schedule; identify permit needs and stakeholders

02

Permit Filing

Assemble descriptor, attach insurance and site plans, and submit to the permitting authority

03

On-Site Setup

Coordinate vendor load-in, safety briefings, and final inspections prior to opening

04

Event Closeout

Complete de‑rig, finalize incident reports, and archive signed descriptors and receipts

Common Mistakes to Avoid

Leaving key dates blank or inconsistent between schedule and permits leads to approval delays and confusion.
Failing to attach valid insurance certificates causes immediate rejection by insurers or permitting offices.
Submitting site plans without scaled measurements or access points prompts requests for clarification and rework.
Not designating an on-site safety lead or contact phone number creates operational gaps during inspections.

Consequences of Incomplete or Incorrect Descriptors

Permit Denial: Application rejected, event delayed

Administrative Fines: Local penalties or remediation orders

Insurance Lapse: Coverage gaps and claim denials

Contract Breach: Vendor or venue contractual penalties

Safety Violations: Potential citations and shutdowns

Liability Exposure: Increased legal and financial risk

Data and Security Considerations for Submissions

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Access Control: Role-based permissions and SSO where supported

Audit Trail: Time-stamped signature logs and IP addresses

HIPAA Consideration: BAA required when descriptors contain PHI

BAA Availability: Obtain BAA for healthcare workflows

Retention Policy: Preserve signed records per legal requirements

Real-World Examples of Descriptor Use

These brief examples show how organizations rely on a standardized descriptor to streamline logistics and compliance.

Optica Ventures (Brian Fitzgibbons)

Optica standardized its descriptor to centralize vendor and schedule data so planners had one source of truth.

This reduced questions from reviewers during permitting.
"The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Martin Properties (Tim Martin)

A regional venue operator used the descriptor to capture site plans and insurance certificates for each festival.

This ensured consistent inspections and cleaner closeouts.
"I can process and execute all of these documents online with 100% compliance and built-in security."

eSignature Pricing and Capability Comparison

A concise vendor comparison focused on typical purchase criteria. signNow is listed first per vendor layout requirements.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions and Troubleshooting

Answers to common questions about validity, notarization, revisions, and storage when using an Event Festival Descriptor.

Need help? Contact support

Can the descriptor be signed electronically?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96, 2000) and by state UETA laws (adopted by most states). Ensure signer intent, consent, attribution, and reliable record retention when relying on e-signatures.
Is notarization required for submission?
Not all jurisdictions require notarization for event descriptors. Where a notarized acknowledgment or RON is specified, follow state notary rules including identity-proofing and any audio-video retention requirements per state notary commissions.
How do I correct an error after signing?
Minor corrections generally require a signed amendment or a replacement descriptor. Use a new version signed by the same parties and retain the original for auditability; note the change date and reason in the record.
Who must sign the descriptor?
Authorized signers typically include the organizer (or officer of the organizing entity), venue representative, and any contracted vendors or insurers who are party to obligations identified in the document.
Which supporting documents should be attached?
Attach current certificates of insurance, site plans, vendor contracts, and permit application forms. Missing attachments are the most common reason for permit office rejection.
How long should signed descriptors be kept?
Retain signed descriptors per applicable rules: at least 3 years for tax records (IRC §6501(a)), 6 years for HIPAA-related documents (45 CFR §164.530(j)), and longer if state law or industry rules require it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now