Salag
SALAGWork With Structure.
LoginStart Free

Risk Escalation Framework

Handling high-risk situations professionally.

alert-circle

When Situations Become High-Risk

Common escalation triggers: Late or missing payment, expanding scope without agreement, contract terms being ignored, or communication that breaks down suddenly.

Most freelance disputes escalate because neither party has a clear process for handling them. A calm, structured approach protects your professional reputation while creating the paper trail you need.

Escalation is not confrontation. It is a structured sequence of communications that gives the other party multiple opportunities to resolve the issue before more formal actions become necessary.

shield

The Four-Stage Escalation Sequence

Stage 1: Friendly Follow-Up (Day 1-3)Assume good faith. Reach out with a brief, neutral message. Most issues at this stage are caused by oversight, not intent. A soft check-in often resolves the situation immediately.
Stage 2: Formal Notice (Day 4-7)Reference the original agreement explicitly. State what is overdue or violated. Give a specific resolution deadline. Keep tone calm and professional. This message creates the documented record.
Stage 3: Work Pause Notice (Day 8-14)If the issue remains unresolved, pause work and notify the client. State clearly that work will resume once the matter is resolved. This is not a threat. It is a professional boundary.
Stage 4: Exit or Escalation (Day 15+)If still unresolved, assess whether to formally end the contract or escalate through the platform, legal, or financial channels available to you. Document everything before taking this step.
guide-script

Escalation Scripts

Stage 1: Friendly Payment Follow-Up

Use this when an invoice is 1-3 days overdue.

"Hi [name], just a quick note to check on the invoice I sent on [date] for [amount]. Sometimes these get buried. Let me know if you need me to resend it or if there is anything else needed on my end to process it."

Stage 2: Formal Payment Notice

Use this when payment is 4-7 days overdue.

"I'm following up on the invoice for [project] dated [date] for [amount], which was due on [due date]. Per our agreement, payment was due within [X] days of delivery. Could you confirm when this will be processed? I want to resolve this without disrupting our working relationship."

Stage 3: Work Pause Notice

Use this when a boundary violation is unresolved and you need to pause work.

"To protect both of us and the integrity of the project, I will be pausing work on [project] starting [date] until we have resolved [specific issue]. I remain committed to completing this project and am happy to continue as soon as this is addressed. Please reach out so we can align on next steps."

Scope Escalation Notice

When a client continues to push scope beyond agreement.

"I want to flag that the recent requests for [specific additions] are outside the scope we agreed on at the start of the project. I have been accommodating where I can, but at this point it is affecting the timeline and my capacity on other commitments. I would like to either formalize these additions with adjusted pricing or confirm we return to the original scope. Which works better for you?"

Communication Breakdown Notice

When a client has gone silent for an extended period.

"I have not heard from you since [last contact date] and want to check in. There are [X items] awaiting your feedback or approval before I can proceed. If I do not hear from you by [specific date], I will need to pause work to avoid missing the deadline. I am easy to reach at [contact info]."
alert-circle

What to Document During an Escalation

If an escalation moves past Stage 2, documentation becomes critical. Compile the following before taking further action.

Original agreement or scope summaryDate, terms, deliverables, payment amount, and any written confirmation from the client.
All communication related to the issueScreenshots, emails, and message threads that document the timeline of events from start to escalation.
Evidence of work completedDeliverables, file submissions, and any client confirmation that work was received or approved.
Record of escalation attemptsCopies of all follow-up messages with timestamps to show that you attempted resolution in good faith.

Use Salag tools to analyze red flags before a situation escalates.

Explore Protection Tools