Header
Unique incident identifier, submission timestamp, and submitting department to ensure the event can be tracked from intake through closure.
A formal Mayday reduces ambiguity, accelerates response, and creates an auditable record of decisions and actions during high-impact events. It helps meet internal SLAs and regulatory reporting obligations while preserving a clear timeline for post-incident review.
Team members who detect or are notified of severe operational issues should complete the Mayday to initiate response workflows.
Recipients commonly include business services, IT operations, security, facilities, compliance, and senior management depending on incident scope.
A manager in business services or operations who reviews incoming Mayday requests, confirms resource allocation, and approves escalations. They act as the central coordinator for cross-team communication and post-incident documentation.
An individual who first detects the issue—such as a call center lead or on-site technician—who completes incident details, provides initial impact assessment, and supplies attachments like error logs or photos for rapid triage.
Unique incident identifier, submission timestamp, and submitting department to ensure the event can be tracked from intake through closure.
Concise description of the problem, location or system affected, and initial symptoms to guide first-response decisions and verify reporter intent.
Scope of impact including affected customers, transactions, or internal services, plus estimated severity to prioritize resource allocation.
Specific remedial request such as 'dispatch technician', 'isolate system', or 'notify customers', including any temporary workarounds.
Predefined routing rules for approvers and escalation paths that ensure required roles are notified automatically.
Fields for signer identity, timestamps, attachments, and a summary of actions taken to support compliance and post-mortem reviews.
| Field | Configuration |
|---|---|
| Notification Method | Email | SMS for acknowledgements |
| Authentication | Email link | Optional 2FA |
| Record Retention | Audit trail stored | 7 years |
| Integration | ServiceNow | Slack routing |
Use a platform that supports secure upload, configurable routing, and an auditable signature trail for all submitted Mayday forms.
Within 15 minutes of submission
Complete within 1 hour
24 to 72 hours depending on severity
Notify senior management within 2 hours
Schedule within 7 days of closure
Form intake recorded and unique identifier assigned.
Incident severity confirmed and owner assigned.
Remediation actions are in progress and documented.
Root cause analysis completed and records archived.
| 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 free trial, no credit card required | No | No | No | No |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |