Spoke 3 - The Yellow Flag

Escalation Standards | Indisputable Delivery

In racing, a yellow flag does not mean the race is over. It means something needs attention before it becomes a red flag. An SA who raises a yellow flag early is doing their job well. An SA who waits for smoke before pulling in is managing risk poorly.

THE CULTURE EXPECTATION

Escalating early reflects professional judgment, not weakness. A senior SA escalates often on small things because they understand that catching something at a two on the problem scale costs far less than catching it at an eight.

This is the explicit standard at Zipcio:

• Raising a small escalation you could handle yourself is always the right process
• If it is something you can own, your Pod Leader will tell you and support you in owning it
• You will never be penalized for raising something - you will only be penalized for sitting on it
• The Pod Leader's job is to have an accurate picture of every engagement - not just the ones that are on fire

TWO-TIER ESCALATION MODEL

Tier 1 - The Heads-Up

A Slack message to your Pod Leader. Three fields, no ticket required. Use this for anything you want your Pod Leader to know about before it potentially grows.

Most escalations should be Tier 1. Fast, low friction, keeps the Pod Leader informed.

Tier 2 - Formal Escalation Ticket

Used when the situation requires leadership involvement, a client-facing response that needs review, or a decision that affects scope, timeline, or commercial terms. This is the existing escalation ticket process.

• Any client-facing complaint or expressed dissatisfaction
• Any scope or timeline decision that requires a change order
• Any situation where the Pod Leader needs to be on a client call
• Any commercial conversation about pricing, contract terms, or retainer
• Any situation escalated from Tier 1 that grew

EXHAUSTIVE ESCALATION TRIGGER LIST

If any of the following occur, escalate. Use Tier 1 unless the situation matches the Tier 2 criteria above.

Timeline and Delivery

• Client requests any compression of a scoped milestone
• SA realizes a deliverable will be late before the client has noticed
• A client dependency - content, access, data, or decisions - is more than three business days overdue with no response to follow-up
• A delivered item has not been reviewed or responded to in more than five business days
• An internal capacity constraint will impact a committed client deadline
• A sprint dependency on another team member is at risk
• The engagement timeline needs to shift by more than one week for any reason

Scope and Change

• Client makes any request the SA believes may be out of scope
• Client references a feature or deliverable the SA does not see in the SOW
• SA realizes something in the SOW is technically not feasible as described
• A third-party integration or data issue is discovered that changes the build approach
• HubSpot portal requires cleanup or remediation before scoped work can proceed
• Client's existing HubSpot setup conflicts with what was scoped

Client Relationship and Health

• Client expresses any dissatisfaction with a deliverable, process, or communication
• Client misses two or more consecutive meetings without rescheduling
• Decision-maker stops attending or goes silent
• SA senses a shift in client tone, engagement, or enthusiasm without a clear reason
• Client mentions budget pressure, leadership change, or internal restructuring
• Client references a competitor or questions the value of the engagement
• Client makes a complaint about Zipcio or any team member directly or indirectly
• SA receives negative feedback in a survey or informal channel
• Client is using Zipcio work as leverage in an internal political situation

Communication

• A client message has gone unanswered for more than 24 hours for any reason including SA illness or OOO
• Client has asked the same question more than once without a satisfactory answer
• SA is unsure how to respond to a client message and has been holding it for more than a few hours
• SA receives a message from someone at the client organization they have not been introduced to

HubSpot and Technical

• A delivered workflow, sequence, or automation is not functioning as expected after sign-off
• Client reports a HubSpot issue impacting their business operations
• SA discovers a data integrity issue in the portal not disclosed at intake
• A HubSpot platform change or outage is affecting the engagement
• SA is unsure whether a technical approach is right and needs a second opinion

Retainer and Commercial

• Client gives any signal - positive or negative - about whether they intend to continue
• Client asks about pricing, contract terms, or what comes after the engagement
• Client references a conversation from the sales process the SA does not have full context on
• A potential upsell opportunity arises that the SA is not positioned to pitch alone
• Client expresses interest in referring Zipcio to another company

Internal

• SA is unclear on ownership of a deliverable between themselves and another team member
• A handoff from another SA or team member is incomplete
• SA has a personal situation that will affect their availability for a client in the next two weeks
• SA is carrying more active client load than they can sustain at standard quality

WEEKLY CHECK-IN QUESTIONS

Two questions for your Pod Leader check-in each week: