Escalation Process
Problems are normal; hidden problems are not. Renvric's escalation process gives both sides a defined route for issues that cannot be resolved within a team: who raises them, who decides, how quickly a response is expected and how the outcome is recorded.
Start your project
Why escalation needs to be designed
Without a route, a blocked issue either waits quietly or travels by hallway conversation to whoever shouts loudest. Neither is fair to the project. A defined path lets a team member say, calmly and without blame, that a matter needs a decision above their level, and be confident where it goes.
What triggers an escalation
- A decision is overdue and blocking delivery, such as an unanswered question on a core requirement.
- A risk has materialised and threatens scope, budget or a committed date.
- Two stakeholders disagree on priorities and the team cannot proceed without a ruling.
- A quality or security concern has been found that the team believes needs executive attention.
- A dependency owned by a third party or another department is not delivering.
- A disagreement about commercial terms or contract interpretation cannot be settled at delivery level.
Levels and who owns them
Level one: delivery
The delivery lead and client product owner try to resolve the issue within the project, usually within the next working cycle.
Level two: management
The Renvric engagement lead and the client sponsor review the facts and options and agree a course of action.
Level three: executive
Senior sponsors on both sides decide matters that affect strategy, contract or relationship.
Technical branch
Architectural or security disagreements go to the technical lead and the client's technical authority, with their recommendation passed up if needed.
Share the outcome you need and Renvric will recommend the smallest useful next step.
How an escalation is raised
The person raising it states the issue, what has been tried, the impact if nothing changes, the options and the decision needed by a given date. A consistent format keeps the discussion on facts. Consider a delayed access approval that has idled two engineers: the note shows the days lost, the approver, and the request to resolve or name a deputy.
Response times for each level are agreed at onboarding and recorded in the working agreement; service levels for support contracts are set separately.
Controls that make it work
- Every escalation is logged with owner, dates and outcome.
- The person who raised it is told the decision and its reasons.
- Repeated escalations on the same cause trigger a process review, not just another ruling.
- Raising an issue is never treated as a sign of failure by either side.
After resolution
The decision is recorded in the decision log, the affected backlog items or plans are updated and the risk register is revised. If the cause was structural, such as unclear ownership or slow approvals, the working agreement is changed so the same situation is less likely to recur.
Related areas to explore: Business Process Automation, Intelligent process automation and Document process automation.
Common questions
Who is the escalation process for?
Anyone involved in a project, on either side, who meets a blocker they cannot resolve at their own level. Sponsors and procurement leads also use it to understand how disputes and urgent matters would be handled before they sign.
What information is needed to escalate?
A clear description of the issue, what has already been tried, the impact on scope, cost, schedule or quality, the options, and the decision required with a date. Supporting records such as logs or correspondence help reviewers act quickly.
How fast will an escalation be handled?
Response expectations are agreed per engagement and written into the working agreement or contract. We do not publish a universal figure because urgency and support arrangements differ. What we commit to is that every escalation has a named owner and a recorded outcome.
Can the client escalate concerns about Renvric?
Yes, and we encourage it. The same route works in both directions. A client can raise concerns with the delivery lead, then the engagement lead, then senior management, and each step results in a written response.
Who can answer a related question?
Write to info@renvric.com. For a live project, start with your delivery lead; for questions about contractual routes, ask for the engagement lead. You can also ask for the escalation contacts and response expectations to be written into the working agreement before work starts, so they are visible to everyone involved.
Keep exploring
Name your level-two and level-three contacts and their deputies during onboarding, and agree what counts as urgent. Written down early, the route rarely needs to be used, and works smoothly when it is.