Marketplace Create skill Sign in

Universal Escalation Triggers (Apply to All Categories) (+2)

Sub-skill of canned-responses: Universal Escalation Triggers (Apply to All Categories) (+2).

ID: 4d80bed6-2d07-42f8-91fb-0087ad28f2f6 Version: 0.1.0 License: MIT Author: vamseeachanta Language: en Added: 2026-06-15
⬇ Download

Universal Escalation Triggers (Apply to All Categories) (+2)

Universal Escalation Triggers (Apply to All Categories)

  • The matter involves potential litigation or regulatory investigation
  • The inquiry is from a regulator, government agency, or law enforcement
  • The response could create a binding legal commitment or waiver
  • The matter involves potential criminal liability
  • Media attention is involved or likely
  • The situation is unprecedented (no prior handling by the team)
  • Multiple jurisdictions are involved with conflicting requirements
  • The matter involves executive leadership or board members

Category-Specific Escalation Triggers

Data Subject Requests:

  • Request from a minor or on behalf of a minor
  • Request involves data subject to litigation hold
  • Requester is in active litigation or dispute with the organization
  • Request is from an employee with an active HR matter
  • Request scope is so broad it appears to be a fishing expedition
  • Request involves special category data (health, biometric, genetic)

Discovery Holds:

  • Potential criminal liability
  • Unclear or disputed preservation scope
  • Hold conflicts with regulatory deletion requirements
  • Prior holds exist for related matters
  • Custodian objects to the hold scope

Vendor Questions:

  • Vendor is disputing contract terms
  • Vendor is threatening litigation or termination
  • Response could affect ongoing negotiation
  • Question involves regulatory compliance (not just contract interpretation)

Subpoena / Legal Process:

  • ALWAYS requires counsel review (templates are starting points only)
  • Privilege issues identified
  • Third-party data involved
  • Cross-border production issues
  • Unreasonable timeline

When an Escalation Trigger is Detected

  1. Stop: Do not generate a templated response
  2. Alert: Inform the user that an escalation trigger has been detected
  3. Explain: Describe which trigger was detected and why it matters
  4. Recommend: Suggest the appropriate escalation path (senior counsel, outside counsel, specific team member)
  5. Offer: Provide a draft for counsel review (clearly marked as "DRAFT - FOR COUNSEL REVIEW ONLY") rather than a final response

Comments

Loading…

Related Skills

GENERAL · data-protection

Vendor Privacy Due Diligence

Pre-contract vendor privacy due diligence per GDPR Article 28(1). Covers risk questionnaires, technical controls assessment, certification review, da…

mukul975
GENERAL · data-protection

Vendor Privacy Audit

On-site and remote vendor audit procedures per GDPR Article 28(3)(h). Covers audit planning, evidence collection methodologies, finding classificatio…

mukul975
GENERAL · data-protection

vendor-ai-review-anthropics

Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your governance positions; flag training-on-data, liability, model chang…

anthropics
GENERAL · data-protection

use-case-triage

Quickly determine whether a processing activity needs a PIA, a mandatory GDPR DPIA, or can proceed — surfaces privacy policy conflicts and routes to …

anthropics
GENERAL · data-protection

Implementing Transparent Communication

Implements GDPR Article 12 transparent information and communication requirements, covering concise, intelligible, and plain language obligations, re…

mukul975