Changing your availability can disappoint someone who has relied on it. That reaction does not prove that your boundary is wrong, or that the other person has been exploiting you.
The useful question is what you owe, what you can continue to give, and how the change will be handled.
Distinguish a promise from a pattern
A promise creates a different responsibility from an expectation that grew without discussion. Both may matter, but they need different conversations.
Imagine a colleague who regularly asks for an evening review. If you agreed to cover a release this week, ending the arrangement tonight has consequences you need to address. If the arrangement developed by habit, you can explain a different review window and discuss urgent exceptions.
Make the boundary operational
For one recurring demand, write down the explicit agreement, the assumed availability, and the change you propose. Name the notice, handoff, or alternative you can reasonably offer.
After the change, observe whether the demand moves to a workable time or simply becomes someone else's unacknowledged burden. Reclaimed hours alone are an incomplete measure.
This is a proposal for ordinary commitments, not a rule that every relationship deserves continued access. The original concern about protecting capacity remains. The claim that disappointment proves another person's parasitism does not.
A boundary becomes clearer when it describes what you will do and how you will honor what remains.
Source note
This work develops the concern in “Resource Reclamation,” published on 2026-02-26.
Use this workExplore with AI
Explore this journal
Take this work into your preferred AI system. Choose a ready-made prompt or add your own context. Nothing you enter here is sent or saved by utpalmv.com.
Use the work as a thinking lens without adding personal context.
Optional. Add details when you want the exploration grounded in your situation. Your context remains in this page and is included only in the prompt you copy.
