Establishing secure connection…Loading editor…Preparing document…

Event 36th

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

EVENT 36TH GENERAL BUSINESS AGREEMENT

This General Business Agreement ("Agreement") is made and entered into as of by and between Client Name: and Contractor Name: .

WHEREAS

WHEREAS, Client desires to engage Contractor to provide services and deliverables in connection with the Event known as (the "Event"), including planning, production and on-site management as detailed below; and

WHEREAS, Contractor represents that it has the experience, personnel, equipment and expertise to perform the required services and is willing to perform such services under the terms and conditions set forth in this Agreement.

SCOPE OF WORK

Event Date:   Location:

PAYMENT TERMS

Deposit required upon execution:   Balance due by:

Any amount not paid when due shall accrue interest at the lesser of (i) a rate equal to or (ii) the maximum rate permitted by applicable law. In addition, the non-paying party shall be responsible for all reasonable collection costs, including attorneys' fees.

TERM AND TERMINATION

Term Commencement Date:   Termination Date:

Either party may terminate this Agreement for convenience upon days' written notice to the other party. Either party may terminate immediately upon written notice if the other party materially breaches any obligation under this Agreement and fails to cure such breach within thirty (30) days after receipt of written notice specifying the breach.

CONFIDENTIALITY

For the purposes of this Agreement, "Confidential Information" shall mean all non-public information disclosed by either party to the other in connection with the Event, whether disclosed orally, in writing, electronically, or by inspection, that a reasonable person would understand to be confidential. Each party shall: (a) hold the other party's Confidential Information in strict confidence; (b) use Confidential Information solely to perform its obligations under this Agreement; and (c) not disclose Confidential Information to any third party except as reasonably necessary to perform the services and subject to appropriate confidentiality protections.

The foregoing obligations shall not apply to information that: (i) is or becomes generally known to the public other than by breach of this Agreement; (ii) was lawfully known to the receiving party prior to disclosure; (iii) is rightfully received from a third party without restriction; or (iv) is independently developed by the receiving party without use of the disclosing party's Confidential Information.

INSURANCE AND INDEMNIFICATION

Contractor shall maintain insurance customary for the industry adequate to cover liabilities arising from the performance of the services. Contractor agrees to indemnify, defend and hold harmless Client and its officers, directors and employees from and against any claims, liabilities, losses or expenses (including reasonable attorneys' fees) arising out of Contractor's negligence or willful misconduct in connection with the Event.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles. The parties submit to the exclusive jurisdiction of the courts located within that State for any action arising out of or relating to this Agreement.

ENTIRE AGREEMENT

This Agreement, together with any schedules or attachments executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. No amendment or modification shall be binding unless in writing and signed by both parties.

NOTICES

Client:

By:

Date:

Contractor:

By:

Date:

Enter text✕

What the Event 36th form is and when it’s used

The Event 36th is a structured event registration and authorization form used to record organizer details, event dates, venue information, participant lists, insurance and safety attestations, and fee payment authorizations. It standardizes event-related information for permit review, venue approval, vendor contracts, and insurance verification. The form supports digital completion and eSignature to speed processing while preserving an auditable record of consent, dates, and signatory attribution. When used for public events it often accompanies liability insurance certificates and site plans required by local permitting authorities.

Why a consistent Event 36th form matters

A standardized Event 36th collects all required details in a single document, reducing review cycles, ensuring consistent data for liability and permitting checks, and making electronic submission and recordkeeping straightforward for organizers and municipal reviewers.

Why a consistent Event 36th form matters

Who typically completes the Event 36th and who reviews it

Stakeholders use the same form to maintain a single record of decisions, approvals, and signed acknowledgments for audit and insurance purposes.

  • Event organizers and promoters responsible for logistics and compliance, completing all event-specific fields and attaching required documentation.
  • Venue and facility managers who confirm site availability, capacity limits, and safety measures and who may add venue endorsements.
  • Local permitting or municipal staff who review submissions for regulatory compliance and either approve, request changes, or deny the application.

Core elements that a professional Event 36th should include

A complete Event 36th captures event identity, schedule, organizer and venue contact information, safety and insurance confirmations, vendor and performer details, and explicit signature blocks for responsible parties.

Event Identity

Name, brief description, and intended attendance numbers; used to determine scale and permit category for municipal review and insurance assessment.

Schedule

Start and end dates/times including setup and breakdown windows, plus contingency timing for weather or delays so reviewers can assess noise and traffic impacts.

Organizer Details

Legal entity name, contact person, daytime phone, email, and mailing address used for notifications and liability assignment.

Venue Information

Venue name, physical address, site contact, capacity, emergency egress description, and proof of venue consent or lease authorization.

Safety & Insurance

Insurance carrier, policy number, coverage limits, and required endorsements; list of security, medical, and fire‑safety plans attached as exhibits.

Signatures

Signature blocks for organizer, venue owner, and any third‑party vendors with printed name, title, date, and eSignature field to capture intent and attribution.

Required information fields at a glance

Event Name: Official event title
Event Date(s): MM/DD/YYYY range
Organizer: Legal entity name
Venue Address: Street, city, state, ZIP
Insurance: Carrier and limits
Primary Contact: Name, phone, email

Step-by-step: filling and submitting the Event 36th

Follow these sequential steps to complete the Event 36th accurately and submit it for review.

  • 01
    Prepare attachments: Collect insurance, site plan, and vendor agreements before starting.
  • 02
    Complete fields: Fill event, organizer, venue, and schedule details precisely.
  • 03
    Add signatures: Apply required eSignatures and dates where indicated.
  • 04
    Submit and monitor: Send to reviewer and retain confirmation or submission ID.

Where the completed Event 36th goes and how it is processed

After submission the document follows a predictable routing path: permit intake, technical review, approvals or requests for revision, and final authorization or denial.

  • Intake: Local permitting office or designated reviewer receives the submission.
  • Technical Review: Staff verify safety, insurance, and zoning compliance.
  • Correction Loop: Reviewer requests clarifications or additional documents if needed.
  • Final Decision: Approval, conditional approval, or denial is issued and recorded.

Delivery options and technical considerations

For automated workflows and integrations use systems that support PDF, DOCX, and audit trails; many eSignature platforms integrate with municipal systems and CRMs.

  • eSubmission: PDF or signed PDF
  • Email: Attach PDF and reference permit ID
  • In-Person: Bring printed copies and attachments

Suggested digital workflow settings for online completion

Configure the online form to enforce required fields, apply conditional sections, and capture a complete audit trail for every signer.

Field Configuration
Required Fields Make organizer, venue, date, and insurance required
Conditional Sections Show vendor fields only when vendor list populated
Signer Authentication Email + optional SMS code for added verification
Audit Trail Capture timestamp, IP, and action log

Typical submission windows and timing expectations

Municipalities and venues set different lead times; plan and submit early to allow for review, corrections, and any required inspections.

Standard Lead Time:

Submit 30–90 days before the event for routine permits

Large Events:

Submit 120+ days before for citywide or multi‑venue events

Insurance Proof:

Provide certificate at least 14 days before event

Late Submissions:

Expect expedited fees or denial for last‑minute filings

Permit Expiration:

Permits typically expire on the approved end date

Key milestones from application to final authorization

Track these stages to understand processing lead times and where delays commonly occur.

01

Application Submitted

Document enters intake queue and receives a tracking identifier.

02

Initial Completeness Check

Reviewer confirms required fields and attachments are present.

03

Technical Review

Staff evaluate safety plans, insurance, and zoning compliance.

04

Final Approval Issued

Permit or conditional approval is posted and communicated to applicant.

Common mistakes when preparing the Event 36th

  • Incomplete insurance details or missing endorsements that delay verification and can trigger requests for updated certificates.
  • Using colloquial or abbreviated names for legal entities which causes mismatch with insurance or vendor contracts and slows approval.
  • Failing to include setup and breakdown times, leading reviewers to underestimate site occupancy and impose additional conditions.
  • Uploading scanned images with unreadable text or missing pages that force re-submission and extend processing time.

Penalties and risks of incorrect or late Event 36th submissions

Permit Denial: Event may be prohibited
Fines: Local fines or administrative penalties
Insurance Gaps: Claims may be denied
Vendor Liability: Contract disputes may arise
Operational Delays: Setup and schedule disruptions
Recordkeeping Risk: Missing audit trail weakens attribution

Representative eSignature vendor pricing and compliance snapshot

Below is a concise comparison of common pricing and compliance dimensions across leading eSignature providers with signNow listed first for reference.

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 Yes, 7‑day Yes Yes Yes Yes
Bulk Send Yes Yes Yes Yes Yes
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently asked questions about completing and submitting the Event 36th

Answers to common questions about eSigning, notarization, submission, revisions, and recordkeeping for the Event 36th.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users