Who must sign the declaration?

Officials who witnessed or adjudicated the incident should sign. Include a senior official or race director for authority; additional signatures (medical staff, protestors) depend on event rules.

Can the declaration be signed electronically?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.

Is notarization required?

Notarization is not universally required for event declarations but may be necessary for certain insurance claims or jurisdictional rules; check the recipient's requirements.

How do I correct an error after signing?

Create an amended declaration noting the correction, reference the original document, and obtain new signatures from the same parties to preserve an audit trail.

What attachments should accompany the declaration?

Include timing logs, photos, witness statements, ambulance or medical reports, and any protest forms to substantiate the narrative and support claims.

How long must we keep declarations?

Retain according to applicable rules: at least 3 years for financial records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)), and longer where state or contract law requires.

Electronic Signature
Templates
Miscellaneous
Post-Race Event Declaration

Post-Race Event Declaration

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

Post-Race Event Declaration

Date of Declaration:

Parties

Organizer Name Organizer Address Participant / Claimant Name Participant Contact

WHEREAS

WHEREAS, Organizer Name: organized and conducted a timed competitive race and related activities identified below; and

WHEREAS, Participant Name: participated in the race and now submits this post-race declaration regarding the event, any incidents, and any claims arising out of the event;

WHEREAS, the parties desire to record certain findings, payments, and post-race responsibilities, and to establish the terms for any post-event compensation, claims handling, and confidentiality;

Event Details

Event Name

Race Date: Location:

Number of Registered Participants

Scope of Work / Post-Race Responsibilities

Describe the post-race deliverables, verification tasks, and responsibilities

Incident and Claim Reporting

Were there any reportable incidents during or immediately after the race? Yes No

If yes, provide an incident report and any immediate remedial action taken

Any injuries requiring medical treatment reported? Yes No

Payment Terms

Total Amount Payable Payment Schedule / Milestones Late Payment Fee

Payments not received within the payment schedule shall accrue the late payment fee specified above and interest to the fullest extent permitted by law.

Term and Termination

Effective Date: Term End Date:

Notice Period for Termination

Either party may terminate this Declaration upon written notice to the other party if the other party materially breaches any obligation and fails to cure the breach within the notice period specified above. Termination does not relieve either party of obligations accrued prior to termination.

Confidentiality

All non-public information exchanged between the parties in connection with this Declaration, including incident reports, medical information, and any proprietary event data, shall be treated as confidential and may not be disclosed except as reasonably required to administer claims, comply with legal obligations, or with the prior written consent of the disclosing party.

Does this Declaration include confidential attachments?

Representations and Warranties

Each party represents and warrants that it has the authority to enter into this Declaration and that the information provided herein is true, accurate, and complete to the best of its knowledge. The Participant represents that any injuries, equipment damage, or incidents disclosed are accurately described in the incident report above.

Governing Law

This Declaration shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws rules.

Entire Agreement

This Declaration, together with any attachments and the parties' written agreement regarding post-race duties and payments, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings, whether written or oral. No modification of this Declaration will be effective unless in writing and signed by both parties.

Indemnification and Insurance

Each party shall indemnify, defend, and hold harmless the other party from and against any third-party claims arising from the indemnifying party's negligence or willful misconduct in connection with the event. Organizer shall maintain event liability insurance in amounts customary for events of similar size and scope and shall provide proof of such insurance upon reasonable request.

Insurance Carrier / Policy Summary (if applicable)

Certifications

By signing below, the undersigned certify that they have read and understood this Post-Race Event Declaration, that all information provided is true and complete, and that they have authority to bind the party for whom they sign.

Participant acknowledges receipt of final race results and any applicable awards or stipends as indicated in the Payment Terms above, unless an unresolved dispute is documented in this Declaration.

Organizer Printed Name:

By:

Date:

Participant Printed Name:

By:

Date:

What the Post-Race Event Declaration Is

A Post-Race Event Declaration records outcomes, incidents, and participant acknowledgements following an organized race or competitive event. It documents results, safety incidents, medical calls, protest outcomes, and any rule infractions the officials observed or adjudicated. Organizers use the declaration to notify sanctioning bodies, insurers, sponsors, and participants, and to create an official record for appeals or insurance claims. The document typically includes event identifiers, participant names and bib numbers, a concise incident narrative, corrective actions taken, and signatures from race officials and affected parties.

Why a Clear Declaration Matters

A clear Post-Race Event Declaration preserves an authoritative record for dispute resolution, insurance, and regulatory review while protecting organizers and participants by documenting facts, actions, and timestamps.

Who Typically Completes This Form

Several roles are commonly responsible for preparing and signing a Post-Race Event Declaration.

Race directors and event managers responsible for final results and official incident reporting.
On-course officials and marshals who witnessed incidents and provide factual statements.
Medical staff or safety officers who document injuries and treatment rendered on site.

Depending on the event's sanctioning rules, additional signatories such as sanctioning delegates, insurance representatives, or protesting parties may be required to acknowledge the record.

Step-by-Step: Completing the Declaration

Follow this order to prepare a complete and defensible Post-Race Event Declaration.

01

Prepare: Gather event identifiers, result sheets, witness statements, and medical notes.
02

Describe: Write a concise incident narrative with time, location, and participants involved.
03

Attach: Include supporting files: photos, GPS logs, timing data, and medical reports.
04

Sign: Obtain signatures from officials and any parties required under event rules.

How to Configure an Online Declaration Workflow

Key settings let you automate routing, authentication, and record retention when you complete the form digitally.

Field	Configuration
Notification	Email alerts to officials and insurer after final signature
Authentication	Email + SMS code for official signers where required
Conditional Fields	Show medical details only when injury checkbox selected
Storage	Save final PDF to event archive and insurer folder

Where to Send the Completed Declaration

Routing depends on event rules, insurance requirements, and whether the event is sanctioned.

Sanctioning Body: Submit the official copy to the governing organization per its reporting rules.
Insurance Provider: Send insurer the incident report and supporting documentation for claims.
Event Archive: Store a signed copy in the organizer's secure records.
Participants: Provide affected participants a copy for their records and appeals.

Technical Distribution and Integration Options

Choose a platform that supports secure signing, conditional fields, and automated delivery to downstream systems.

Integrations: Connectors include Salesforce, NetSuite, Google Workspace, and Microsoft 365
File Formats: Accepts PDF, Word DOCX, and stores final PDF/A for archives
Authentication: Email, SMS code, or advanced multi-factor options

Ensure the chosen platform provides a tamper-evident audit trail, secure storage, and the ability to export signed records for audits and insurance reviews.

Security and Compliance Considerations

Transport Encryption: TLS 1.2/1.3 protects data in transit

Data at Rest: AES-256 encryption secures stored documents

Audit Trail: Detailed logs capture signer attribution and timestamps

Certifications: SOC 2 Type II and ISO 27001 available

Regulatory Support: HIPAA compliance available with a BAA

FDA / Records: 21 CFR Part 11 controls supported where required

Typical Timelines and Deadlines to Observe

Timely completion and delivery of the declaration reduce risk and support prompt insurance and sanctioning responses.

Immediate Recording:

Document incidents on race day while details are fresh

Official Submission Window:

Submit to sanctioning body within required period, often 7–30 days

Insurance Notice:

Notify insurer promptly; many policies require immediate notice for claims

Participant Copies:

Provide affected participants copies within two weeks if requested

Evidence Retention:

Retain supporting materials at least as long as the declaration itself

Consequences of an Incorrect or Late Declaration

Insurance Denial: Incomplete reports can lead to denied claims

Disqualification: Errors in results may trigger protests or disqualification

Civil Liability: Inaccurate facts may increase organizer exposure to suits

Sanction Penalties: Governing bodies may assess fines or sanctions

Appeal Limitations: Late reports can forfeit appeal or protest rights

Criminal Exposure: Deliberate false statements could raise perjury concerns

Common Preparation Pitfalls to Avoid

Delayed documentation that omits critical timestamps or witness statements, making later verification difficult.
Incomplete supporting evidence such as missing photos, timing logs, or medical incident reports that insurers require.
Mismatched participant identities between the declaration and entry records, causing administrative disputes or rejected claims.
Using ambiguous language or subjective conclusions rather than concise factual descriptions of what occurred and who observed it.

Real-World Usage Examples

The following short case summaries show how organizers and operators document events and secure signatures for records.

Optica Ventures — Operational Efficiency

Organizers digitized post-event reports to reduce processing time and centralize records

Used conditional fields to capture incident-specific data efficiently
The result reduced back-office reconciliation and made incident review faster for sanctioning officials and insurers while keeping a clear audit trail.

Martin Properties — Compliance and Mobility

A mobile-first organizer needed forms that work on phones and tablets

Implemented electronic signatures to capture officials' attestations onsite
This allowed immediate completion and distribution of declarations to stakeholders and supported insurance reporting without paper handling delays.

Practical Tips for Accurate and Efficient Declarations

Apply these practices to reduce errors, improve clarity, and accelerate downstream processing.

Use Structured Fields

Design the declaration with predefined fields for time, location, and participant identifiers to avoid inconsistent entries and simplify data extraction.

Attach Verifiable Evidence

Include photos, GPS traces, official timing exports, and medical logs as attachments to support narratives and expedite insurer reviews.

Require Official Authentication

Have at least one senior official sign and date the declaration; use multi-factor authentication for electronic signers when possible.

Archive and Index

Store signed declarations in a searchable archive with metadata (event, date, participants) to support future audits and appeals.

Key Processing Milestones After Race Finish

Track these sequential milestones from immediate recording to final distribution to ensure timely and auditable handling.

01

Event End

Officials record initial incident notes and timing data on race day

02

Initial Report

Draft and circulate the declaration to officials within 48–72 hours

03

Review & Sign

Obtain required official and medical signatures and finalize attachments

04

Distribution

Submit the finalized declaration to sanctioning body, insurer, and archive

eSignature Pricing & Feature Snapshot for Completing Declarations

Vendor pricing and feature availability influence operational cost and the ability to support notarization, bulk send, and regulatory controls for official declarations.

	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	Yes, limited	Yes, limited
Bulk Send	Yes (available in Premium)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About Post-Race Event Declarations

Answers to common questions about completion, signatures, and storage for Post-Race Event Declarations.

Need help? Contact support

Who must sign the declaration?
Officials who witnessed or adjudicated the incident should sign. Include a senior official or race director for authority; additional signatures (medical staff, protestors) depend on event rules.
Can the declaration be signed electronically?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.
Is notarization required?
Notarization is not universally required for event declarations but may be necessary for certain insurance claims or jurisdictional rules; check the recipient's requirements.
How do I correct an error after signing?
Create an amended declaration noting the correction, reference the original document, and obtain new signatures from the same parties to preserve an audit trail.
What attachments should accompany the declaration?
Include timing logs, photos, witness statements, ambulance or medical reports, and any protest forms to substantiate the narrative and support claims.
How long must we keep declarations?
Retain according to applicable rules: at least 3 years for financial records (IRC §6501(a)), 6 years for HIPAA-related records (45 CFR §164.530(j)), and longer where state or contract law requires.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now