# Route a blocker request to someone who can actually answer

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Resolve the authorized route — Coordinator — The data team distinguishes retrieval responsibility from the receiving lead’s policy authority.
- Obtain a response commitment — Receiving lead — Acknowledgement names the owner and decision-return window, or explicitly declines ownership.
- Return or reroute the request — Coordinator — The answer reaches the affected task, or an unanswered/declined request has a named rerouting action.

## Workflow questions

### Should every blocker use an urgent label?

No. Explain its actual impact and useful response time; urgency alone is not an action.

### What if the recipient is not the decision owner?

Ask for the correct route instead of assuming a copied person has authority.

### Will TeamBoost send the request for me?

This page drafts text only. Put the reviewed request in your available task/comment/report workflow and use your approved communication route. No automatic notification delivery is established here.

## Job to be done

When a blocker alert reaches people who cannot decide, I want an acknowledged route to the accepting owner so a specific answer returns instead of another broadcast.

The export team broadcasts a missing cancelled-order policy to the data team. The data team can retrieve files but cannot decide the customer rule. Nobody acknowledges ownership of the requested response.

### Recognizable symptoms

- A technically relevant team is mistaken for the authorized decision owner.
- Posting the request is treated as proof someone received and owns it.
- An unanswered response window ends with another broadcast rather than a named reroute.

### Shortcut that fails

Repeating the same blocked alert to more people increases noise while leaving the decision unspecified.

### Before

Blocked on data. Can someone help urgently?

### After — invented worked answer

Routing request: the cancelled-order include/exclude rule needs the receiving lead, not the data retrieval team. Coordinator: confirm who owns this customer-rule decision and ask them to acknowledge the request. The receiving owner should return the chosen rule by the Wednesday review window, or a revised decision time. If ownership is declined or no acknowledgement arrives, the coordinator must resolve the correct receiving route; do not broadcast the same alert again. Keep export review open until an authorized rule is recorded.

### Conditional next moves

- If A policy decision is missing: Ask the accepting owner to choose. An engineer cannot resolve a business rule by guessing.
- If A file or access prerequisite is missing: Request that prerequisite from its owner. Use the actual condition rather than the policy template.
- If The recipient cannot decide: Resolve the correct route. Being mentioned does not grant authority.

### TeamBoost route — confirm account availability

- Make the blocker inspectable: Keep the affected export task and current blocking reason together. Your check: Verify that this is still the actual missing condition.
- Attach the decision request: Record the proposed receiving owner, ask for acknowledgement and agree the return window through your approved communication route. Your check: Confirm that a person accepted the response responsibility; posting a note is not proof of delivery.
- Carry the unresolved ask into reporting: Keep the task-linked ask visible until the rule is returned. Your check: The response must state the chosen rule before implementation resumes.

### Success check

A coordinator can distinguish a sent alert, acknowledged response owner and returned authorized answer, with a named rerouting action when ownership is declined.

### Editable draft facts

- Missing input or decision [input]: Cancelled orders: include or exclude? — Ask a question the recipient can settle.
- Affected outcome [impact]: Customer export review cannot proceed — Explain why the answer matters.
- Proposed owner and acknowledgement [owner]: Receiving lead; coordinator confirms acceptance of the decision request — Record who can decide and whether that responsibility has been acknowledged.
- Useful response window [when]: Wednesday review window — Offer a real checkpoint, not invented urgency.
- Return or rerouting action [fallback]: Coordinator resolves the receiving route if declined or unacknowledged; authorized rule returns to export task — Distinguish a returned answer from an unanswered broadcast.

### Draft pattern — replace every placeholder

```text
Routed decision request
Question: {input}.
Affected outcome: {impact}.
Proposed owner and acknowledgement: {owner}.
Decision-return window: {when}.
Return or rerouting action: {fallback}.
A sent or posted request is not an acknowledged response commitment; keep the affected work open until an authorized answer returns.
```

### Limits

The example is invented. Task notes do not ensure that a notification is delivered or that the recipient is authorized.

Local text preparation only; no workspace read, task creation, send or approval. Source interfaces do not establish account availability or live feature completion.