Can a runsheet be signed electronically?

Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally legally binding if intent, consent, attribution, and record retention are demonstrable; exceptions apply for certain testamentary or court filing documents.

Do I need notarization for a runsheet?

Typically no. Runsheets are operational records and do not require notarization unless used as a contract exhibit or to satisfy venue or permit conditions that explicitly demand notarized attachments.

How should I handle mid‑event changes?

Record every change in the runsheet change log with timestamp, author, and reason; circulate the updated signed page and note the revision in post‑event reconciliation to avoid billing disputes.

What format should final runsheets use?

PDF/A or standard signed PDF is preferred for archival stability; include an audit trail that captures signer identity, timestamp, IP, and version history for evidentiary and compliance value.

Can I use remote notarization or digital notarization?

Remote online notarization (RON) is permitted in many states; check local RON rules for identity proofing and recording retention. If a notarized runsheet copy is required, follow the state notary commission guidelines.

How do I store signed runsheets securely?

Store signed runsheets in an access‑controlled records system with encryption at rest (AES‑256) and in transit (TLS 1.2/1.3). Maintain role‑based access controls and a retention schedule consistent with IRS, HIPAA, or other applicable rules.

Event Runsheet

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

EVENT RUNSHEET AND SERVICE AGREEMENT

Client Name: Service Provider Name:

Event Name: Event Date:

Venue / Address:

WHEREAS

1. Whereas Client engages Service Provider to coordinate, supply and operate production, technical and event management services in connection with the Event described above; and

2. Whereas Service Provider represents that it has the necessary personnel, equipment, permits and experience to provide the services in accordance with the run order and timelines set forth in this Runsheet and accompanying Scope of Work; and

3. Whereas the parties intend these Runsheet entries and the accompanying terms to constitute the operative agreement governing the provision and payment for the described services.

SCOPE OF WORK

Summary of Services

RUNSHEET SCHEDULE

The following timeline sets the order of activities, required call times and assigned leads. Times are estimates; any material changes must be approved in writing as a Change Order.

Time

Dur.

Location/Area

Activity / Cue

Lead / Crew

PAYMENT TERMS

Total Fee: Deposit (if any):

Payment Schedule / Milestones

Late Payment: In the event of late payment, Client shall pay interest at the rate of on overdue amounts, plus any collection costs and reasonable legal fees incurred by Service Provider.

TERM AND TERMINATION

Agreement Start Date: Agreement End Date:

Either party may terminate this Agreement for convenience upon written notice delivered at least days prior to the intended termination date. Termination for cause shall be permitted where a party materially breaches a substantive obligation and fails to cure such breach within fourteen (14) days after written notice.

CONFIDENTIALITY

Each party shall treat as confidential all non-public business information of the other party obtained in connection with this Agreement, and shall not disclose such information to any third party except as required to perform the services, to comply with law, or with the prior written consent of the disclosing party. This obligation survives termination for a period of two (2) years.

CHANGE ORDERS

All changes to the Scope of Work, runsheet, or material specifications shall be effected only by a written Change Order signed by authorized representatives of both parties. Client acknowledges that changes may affect fees and schedule.

Written Change Order required:

INSURANCE AND INDEMNITY

Service Provider shall maintain at its expense applicable commercial general liability and equipment insurance sufficient for the Event. Each party indemnifies and holds harmless the other against claims arising from its own negligent acts or omissions in connection with performance of this Agreement, except to the extent caused by the indemnified party's gross negligence or willful misconduct.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State or jurisdiction indicated below: . Venue for disputes shall be the applicable state or federal courts located in that jurisdiction.

ENTIRE AGREEMENT

This instrument, including the attached Runsheet, Scope of Work and any executed Change Orders, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior agreements and understandings, whether written or oral. No amendment shall be effective unless in writing and signed by authorized representatives of both parties.

CONTACTS

Client Contact Service Provider Contact

Client:

By:

Date:

Service Provider:

By:

Date:

What an Event Runsheet Is and why it matters

An Event Runsheet is a chronological, task‑level schedule used to coordinate every operational element of an event. It lists exact start and end times, task owners, cue points, contacts, equipment, and contingency instructions so production teams, vendors, and clients share a single authoritative source. Runsheets are used for rehearsals, load‑in logistics, show calling, vendor handovers, and post‑event reconciliation. For multi‑day or multi‑site events the runsheet can be segmented by location or role to reduce cross‑team confusion and streamline execution.

How a clear runsheet improves event execution

A concise Event Runsheet reduces ambiguity, limits last‑minute changes, and assigns clear responsibility for every item on the schedule. It simplifies vendor coordination, shortens response time for incidents, and documents deviations for billing or insurance reconciliation.

Primary users and who should keep a runsheet

Event managers, production leads, and vendor coordinators use runsheets to coordinate timing, staff assignments, and technical cues during live events.

Venue operations teams ensuring load‑in, rigging, and safety procedures align with the schedule.
Audio‑visual crews responsible for cue lists, run order, and set transitions.
Client contacts and event producers monitoring milestones, approvals, and client deliverables.

The runsheet becomes the shared operational reference for crew, vendors, and clients from rehearsals through teardown, reducing redundant communications and conflicts.

Who can approve or sign changes

Event Manager

The senior client or organizer representative who approves the final runsheet, authorizes changes to the schedule, and signs off on contingency actions. Responsible for client directives, budget tolerances, and final acceptance of event deliverables during execution.

Production Lead

The on‑site technical manager who implements the runsheet, coordinates vendors and crew, and validates timing at each cue. Authorized to direct technical substitutions, delay starts within approved windows, and record deviations for post‑event reporting.

Required runsheet fields at a glance

Event Title: Official name used on permits.

Event Date: MM/DD/YYYY format for legal clarity.

Venue Address: Street, city, state, ZIP required.

Key Contacts: Names, roles, phone numbers, email.

Run Order: Time-coded task list with owners.

Equipment List: Itemized gear with serial numbers.

Stepwise process to create a usable runsheet

Follow these sequential steps to build and approve a reliable Event Runsheet before production rehearsals begin.

01

Define Scope: List event segments, durations, and deliverables.
02

Assign Owners: Attach names, roles, and on‑site contact numbers.
03

Timecode Tasks: Set fixed start/end times for every activity.
04

Review & Approve: Circulate draft, collect signoffs, freeze final version.

Where final runsheets should be sent and stored

Use the runsheet as the authoritative operational record: distribute to staff, upload to shared project systems, and attach to final invoices and post‑event reports.

Internal Distribution: Email PDF and publish to shared drive or project folder for team access.
Vendor Circulation: Send vendor‑specific pages and arrival windows before load‑in.
Client Delivery: Provide final runsheet with post‑event reconciliation and deliverables summary.
Archive: Save signed final version in secure records management system.

Configuring a digital runsheet workflow

Configure your digital runsheet workflow to automate approvals, version control, and distribution across platforms and teams.

Field	Configuration
Version Control	Auto‑version with change log and freeze feature.
Approval Flow	Two‑step signoff: production lead then client.
Notifications	SMS/email alerts for changes and signoffs.
Storage	Save signed PDFs to cloud archive.

File types and platform requirements for runsheets

Confirm platform compatibility, authentication methods, and supported file formats before distribution to avoid access issues.

File Types: PDF, DOCX, XLSX supported.
Auth Options: Email, SMS code, KBA, SSO.
Integrations: Salesforce, NetSuite, Google Workspace.

Essential components of a professional Event Runsheet

A professional Event Runsheet combines precise timing, ownership, technical cues, contact information, contingency steps, and version control to support smooth execution and accurate post‑event accounting.

Timeline

Minute‑by‑minute schedule or time blocks with exact start and end times for every task, call, or performance to coordinate crews and vendors precisely.

Owners

Assigned responsible person for each task with mobile contact and secondary backup; clarifies escalation and prevents unilateral decisions that can disrupt the event.

Contacts

Centralized list of client, vendor, venue, emergency services, and transport contacts including roles and preferred communication channels for rapid issue resolution.

Technical Cues

Detailed lighting, audio, and stage cues with cue numbers, duration, and person responsible for execution and verification during rehearsals and live performance.

Logistics

Load‑in and load‑out windows, storage locations, parking allocations, and vendor access instructions to mitigate delays and comply with venue rules.

Contingency

Predefined alternatives for common failures (mic problems, power loss, speaker no‑shows) with decision makers and time thresholds for implementing backups.

Key scheduling deadlines to manage before the event

Establish and communicate calendar deadlines so permits, vendor confirmations, and rehearsals happen with sufficient lead time to reduce operational risk.

Initial Draft Deadline:

Draft runsheet circulated at least 21 days before the event.

Vendor Confirmation Deadline:

All vendors confirm arrival times 10–14 days prior.

Tech Rehearsal Window:

Full technical dress rehearsal occurs 1–3 days before event.

Final Freeze Time:

Final signed runsheet issued 24–48 hours before load‑in.

Post‑Event Report Due:

Submit reconciliation and incident log within 7–14 days.

Common mistakes to avoid when preparing a runsheet

Using relative times (for example, '30 minutes before') rather than fixed clock times causes confusion across vendors and can generate cascading delays.
Failing to confirm vendor arrival windows and load‑in access often results in late setups and may incur extra fees or denied access at the venue.
Omitting contact details for key roles such as production manager and stagehand prevents fast issue resolution during technical or safety incidents.
Locking the runsheet without documenting revisions makes it hard to reconcile discrepancies and assign responsibility after the event concludes.

Risks and consequences of an incorrect or missing runsheet

Permit Violations: Municipal fines or event shutdown risk.

Safety Incidents: Liability claims, OSHA citations possible.

Breach of Contract: Vendor penalties and indemnity exposure.

Insurance Denial: Incorrect runsheet may void claim.

Reputational Harm: Client loss and future bookings impacted.

Financial Overruns: Unplanned costs for overtime and remakes.

Real examples showing runsheet value

These brief cases illustrate how organized runsheets reduce reconciliation time and support compliance in real operations.

Martin Properties

Martin Properties used a centralized digital runsheet to coordinate multi‑site open houses and contractor schedules with on‑site crews across properties.

Improved turnaround and compliance.
By attaching signed runsheets to invoices and maintaining versioned records, the team reduced reconciliation time, eliminated duplicate requests, and preserved audit trails useful for insurance and client dispute resolution.

Optica Ventures LLC

Optica Ventures streamlined vendor handoffs by publishing role‑specific pages from a master runsheet, reducing on‑site confusion during high‑volume events.

Clear owner assignments reduced escalations.
The approach provided a single point of truth for crew shifts, sped up incident response, and simplified post‑event billing reconciliation with auditable signoffs.

Typical eSignature pricing and capability comparison

Compare common vendor starting prices and core capabilities relevant to runsheet signing and distribution; signNow is listed first per composition guidance.

	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 by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about Event Runsheets and eSigning

Answers to common questions on signing, revisions, storage, and legal validity designed for production teams and administrative staff.

Need help? Contact support

Can a runsheet be signed electronically?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally legally binding if intent, consent, attribution, and record retention are demonstrable; exceptions apply for certain testamentary or court filing documents.
Do I need notarization for a runsheet?
Typically no. Runsheets are operational records and do not require notarization unless used as a contract exhibit or to satisfy venue or permit conditions that explicitly demand notarized attachments.
How should I handle mid‑event changes?
Record every change in the runsheet change log with timestamp, author, and reason; circulate the updated signed page and note the revision in post‑event reconciliation to avoid billing disputes.
What format should final runsheets use?
PDF/A or standard signed PDF is preferred for archival stability; include an audit trail that captures signer identity, timestamp, IP, and version history for evidentiary and compliance value.
Can I use remote notarization or digital notarization?
Remote online notarization (RON) is permitted in many states; check local RON rules for identity proofing and recording retention. If a notarized runsheet copy is required, follow the state notary commission guidelines.
How do I store signed runsheets securely?
Store signed runsheets in an access‑controlled records system with encryption at rest (AES‑256) and in transit (TLS 1.2/1.3). Maintain role‑based access controls and a retention schedule consistent with IRS, HIPAA, or other applicable rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now