How to respond to an urgent last-minute request

When to use: Use when you need to stay helpful but cannot commit to the implied speed.

Risk: If the reply stays too soft, the client may still assume the original rushed timeline is possible.

Example wording: I understand this is urgent. Before I commit, I want to be clear about what is realistically possible in this window so I do not overpromise.

When to use: Use when a faster path exists only if the work becomes smaller.

Risk: If the reduced version is not concrete, the client may still expect the full result on the rushed schedule.

Example wording: If this needs to move faster, the cleanest path is usually to reduce the immediate scope rather than try to force the full version through at the same speed.

When to use: Use when urgency changes effort, sequencing, or availability materially.

Risk: If the condition sounds like punishment, the client may resist instead of choosing.

Example wording: Because this is both last-minute and urgent, I would want to treat it as a rush request rather than fold it into the normal timeline assumptions.