Escalating a problem with options: a specific decision, its authority and conditions
The hotel's elevator inspection has an unresolved result and the planned opening is approaching. The manager wants a decision about repair, timing and what can be communicated. The project team needs an options memo that distinguishes assessed choices from unverified possibilities rather than offering partial occupancy as if the owner's preference alone could release it.
Take the problem upward with a specific decision request and comparable options. State the observed gap, consequence, known facts and information still needed. A concise page can prepare a useful conversation, but it cannot guarantee an answer by Friday or give the recipient authority they do not have. Keep technical release, permitted use and commercial decisions with their actual responsible roles.
Make the recommendation and its conditions visible
- State the decision and actual authority. Identify the affected commitment, what answer is needed and why its date matters. Confirm who can make each part of the decision and who else must review it. Separate an owner preference, a commercial approval and a technical release instead of sending all three under one signature request.
- Compare realistic options on a common basis. Show the scope, time, cost, exposure and prerequisites for each assessed choice. Mark estimates and dates with their sources and assumptions. Identify a possibility needing feasibility review as a question, not a ready option. Include retaining the present arrangement where meaningful rather than manufacturing three choices to fill the template.
- Recommend an option with its reasoning. Explain what it addresses, the trade-offs and any conditions needed before implementation. Supply relevant supporting records without burying the request. Ask for a specific decision or direction on missing information. A preferred answer must not disguise an unresolved permission, readiness condition or purchasing authority.
- Record the received response and next handover. Capture who decided what, when and within which conditions. Name implementation receivers and further review dates. If the answer is deferred or conditional, keep that status and its consequence visible. An email acknowledging the memo is not acceptance of the recommendation, and a decision does not close every related technical question.
Common mistakes
- Offering an unverified possibility as a feasible option.
- Comparing different scope or estimate boundaries.
- Treating acknowledgement as an approved recommendation.
- Assuming a commercial decision supplies technical or use permission.
Action list
The escalation memo should show
- A specific needed decision and meaningful date.
- Actual authority and required other reviews.
- Comparable assessed options with assumptions.
- Recommendation, trade-offs and remaining conditions.
- Received response and implementation handover.
Check your understanding
The owner replies 'prepare the lower floors' to a partial-opening suggestion. Can the team treat that as occupancy release?
