How Event Change / Exception Requests Are Handled

How Event Change / Exception Requests Are Handled

Use Event Change / Exception category for:

  • Date or time changes
  • Participant count changes
  • Offering scope changes
  • Budget-impacting requests

Key points:

  • Changes are assessed for impact on cost, SLA, and delivery
  • Budget Impact field must be filled
  • Changes are not confirmed until formally approved by the PMO team.

    • Related Articles

    • Event-Day Live Support: What to Expect

      For Event-Day issues: Raise a support request under Event-Day Live Support Select correct severity (P1/P2) Mention number of participants impacted SE&O Americas Field-led Events Support provides: Immediate acknowledgment Live troubleshooting or ...

    • Catalog & New Offering Requests – What to Know

      Catalog-related tickets are not tied to live events. Use this category for: New catalog item requests Enhancements to existing offerings Status of MSFT / GTM review Development progress tracking These requests are evaluated, approved, and funded ...

    • Post-Event Feedback, RCA, and Closure

      After event completion: Automated feedback is collected P1/P2 issues require a Root Cause Analysis (RCA) Budget reconciliation is completed by offering owners Final closure confirmation may be shared via support request Use Post-Event Closure & ...

    • What is SE&O Americas Field-led Events Support?

      SE&O Americas Field-led Events Support is the official support channel for SE&O Americas Field-led Events for Enterprise. It is used to manage: Event readiness and delivery issues Labs, platforms, and instructor support Event-day live issues Approved ...

    • Severity Levels Explained (P1–P4)

      Use severity correctly to ensure appropriate response: P1 – Critical (Event Blocker) Event cannot proceed, large participant impact P2 – High (Major Impact) Event running with significant issues P3 – Medium Partial impact, workaround available P4 – ...