Updated September 2026: in March 2020 I came back from a long vacation hoping for a fresh start with a new delivery team, and within hours was pulled back into the old request I had worked on before leaving, with the same people I had clashed with. I have rewritten it into a guide to closing requests properly so they are less likely to come back.
My leave had been restful and uninterrupted. I logged back in keen to take on a new request and prove I could deliver without escalations. Within hours, the old email thread reopened with additional services requested, and there was nobody to hand it to. It meant working again with the same people I had struggled with before.
Why do closed requests come back?
Because they were never formally closed. The deck was sent, everyone moved on, and nobody confirmed that the client was satisfied or recorded what was delivered. When the client returns with more questions, the thread reopens and the same person gets pulled back, because they are the one who knows the history.
How do you close a request properly?
- Send a closing email listing what was delivered, the final version and any open points, and ask for confirmation.
- Store the final version in a shared location with a clear name, not only in email.
- Write a short handover note on the context and decisions, so someone else can pick it up.
- Tell your manager that it is closed, and who else could handle follow-ups.
How do you avoid being the only person who can help?
The handover note is the key. If the context lives only in your head, you will be pulled back every time. If it is written down, your manager can reasonably assign follow-ups to someone else, especially if you are already committed to new work.
What if you are pulled back anyway?
Treat it as a new request with its own scope. Ask what the "additional services" are, estimate the effort, and agree with your manager how it fits alongside anything new. Being pulled back is not a reason to let the old work expand without limits.
How do you work again with people you clashed with?
Rely on structure. Confirm scope in writing, keep communication in shared channels and summarise each call. Past conflict often came from ambiguity, and clear process leaves less room for it. It also gives you a record if the same problems return.