Compliance escalation — to-principal emailEasyStagecraft Module 4 · for when a compliance issue is being ignored by management or a peer · the email you write only once · structured so escalation is unambiguous but professional

What this is. Sometimes a compliance issue won't budge. A contractor refuses to provide a CoC. A director keeps pushing a real-flame request that the venue refuses. A colleague is allowing untested gear in dressing rooms. You've raised it, documented it, given grace. The next step is a formal escalation in writing to the principal. This template is that email. Once sent, it lives in your inbox forever — and so does the school's response. Don't write this email lightly; do not write it angrily; do write it when the gap between what you've raised and what's been done has reached the point where silence becomes complicity.

Send this only when:

You have raised the issue in writing at least twice with the responsible party (director / contractor / peer).
There is a tangible safety / legal / licensing exposure to the school or to students.
You have a specific ask of the principal — not "please help" but "please [action] by [date]".
You are willing to be wrong publicly if you are. Compliance escalations have a long memory; only send when the cost of NOT sending exceeds the cost of being seen to escalate.

Template — to-principal escalation

[Production] — compliance escalation · need your decision by [date]

To: Principal · CC: Business Manager / WHS Officer · BCC: none

Dear [Principal name], I'm writing to formally escalate a compliance issue I haven't been able to resolve at my level. I'd appreciate a decision from you on the path forward by [specific date — usually 48-72 hours]. The issue, in one paragraph: [2-4 sentences. Factual. No adjectives. e.g. "The lighting contractor (StageFX Hire Pty Ltd) has not provided a current Certificate of Currency for the [Production] season despite three written requests over the past 14 days (attached). Their crew is scheduled on site for bump-in on [date], which is in 5 working days. Without a current CoC the school's own insurer cannot extend cover to their crew, and our internal contractor-engagement policy is not met."] What I've already done: • [Action 1 — date] • [Action 2 — date] • [Action 3 — date] • [Action 4 — date, if relevant] The risk to the school if this remains unresolved: [2-3 specific consequences. e.g. "If we proceed with their crew on site uninsured, any incident becomes uninsured liability on the school. If we cancel their engagement at this notice, we lose the deposit ($A1,800) and face a 7-10 day delay finding an alternative supplier — which may collapse the production schedule."] The options I see, in order of preference: 1. [Option 1 — Daniel's recommendation. Be specific about action + by whom + when.] 2. [Option 2 — fallback. Same level of detail.] 3. [Option 3 — last resort. Costs noted.] What I'm asking of you: A decision on which path we take by [date], and (if Option 1 or 2) your written approval to authorise the action. I'm available [two time windows] for a 15-minute discussion if useful. Otherwise an email decision is fine. I'm sending this as an escalation rather than a query because I've genuinely exhausted what I can do at my level without your authority. I'm not flagging it because I think the situation is unrecoverable — I think it's recoverable but only with your decision. Happy to talk through any of it. Thanks for your time on this. Best, [PM name] Production Manager · [School] [Direct phone] Attachments: • [Production] approval pack (signed [date]) • Contractor correspondence — three written requests + responses • Current contractor engagement policy (school's procurement framework, section [X])

Why this works (and why each section matters)

Section	Why
Subject line w/ deadline	Principal's inbox is brutal. "I need your decision by X" jumps the queue without being passive-aggressive.
One-paragraph issue	If the principal only reads the first paragraph, they have the situation. Everything else is supporting evidence.
What I've already done	Demonstrates the escalation is the LAST step, not the first. Reduces the principal's anxiety about "should I tell PM to handle it themselves?"
Risk to the school	Frames the issue in the principal's currency: school exposure. Not your inconvenience.
Options + recommendation	Principals approve recommendations 80% of the time. Forcing a Yes/No to the PM's option is faster than asking them to invent options.
"What I'm asking of you"	Closes ambiguity. The decision is named, the deadline is named, the form (email reply / call) is named.
Closing tone	Confident but not accusatory. Not "I told them three times and they ignored me" — just "I exhausted my level".
Attachments	The email is one-page-readable. Attachments are the evidence the principal turns to if they want detail.

Three scenarios — when each variant applies

Variant A · Contractor non-compliance

Use the template above. Common issues: missing CoC, missing operator ticket on bump-in day, refusal to itemise a "compliance" line, refusal to substitute a non-licensed scope.

Variant B · Internal staff non-compliance

Same structure, softer language in the "issue" paragraph. Replace "the contractor" with "I've raised with [colleague] and they have not actioned" — but route the actual personnel matter through a separate confidential conversation with the principal, not the all-in-writing thread. The compliance email focuses on the SAFETY / LEGAL outcome, not the colleague.

Variant C · Director's safety / scope push

Use the template, but in the "Options" section be specific that you've offered alternatives: "I've offered the digital pyro alternative twice and the director has declined. The remaining options are: 1. principal speaks to director directly; 2. PM withdraws the pyro element under their veto authority; 3. licensed pyrotechnician engaged at an additional cost of A$X."

One final principle. Compliance escalations exist to make decisions visible. They are not about winning. They are about ensuring the school cannot claim later that "we didn't know". Once sent, the decision sits with the principal — and that's exactly where it should sit for the magnitude of the call being made.