A small request can become difficult to remember once it has changed several times. Did you agree to review the document, rewrite it or send the final version? A useful boundary journal makes the agreement visible while leaving room for other people to clarify their understanding.
The aim is practical personal reflection: what was asked, what you chose and what happens next. It is not a verdict on someone’s character or a clinical assessment, and it does not replace legal advice. Favor combines personal journaling and game-style progress; this article suggests a neutral way to use that kind of tool. Valorem publishes Favor.
Use a small record with five parts
Keep enough detail to understand the commitment later, without reproducing a whole conversation. The following structure can live in your own notes; it does not assume Favor has these exact field names.
- Request: what the other person actually asked for.
- Timing: the requested deadline and when an answer is needed.
- Your choice: accepted, declined, offered a narrower scope or still considering.
- Agreed scope: the specific work you both understand is included.
- Next step: who needs to respond or act, and when you will check again.
Separate an observation from an interpretation. “Asked for three revisions after the agreed review” describes an event. “Never respects my time” turns that event into a broad judgment. If you want to record a feeling, label it as your own response rather than a fact about the other person.
A worked example: helping with a presentation
Imagine a colleague asks on Wednesday: “Could you redo these eight slides by Friday?” You have time for a limited review, but not a full rewrite. Before answering, write down the actual request and your available scope.
A possible response is: “I can spend 25 minutes on Thursday reviewing the opening two slides. I can send comments, but I cannot rewrite the full deck by Friday.” The numbers make the offer understandable; they are an example, not a recommendation about how much time to give.
Your record might say: “Requested: rewrite eight slides by Friday. Offered: review first two slides for 25 minutes on Thursday. Awaiting confirmation.” At this stage, the smaller task is only an offer. Do not mark it as a shared agreement before the colleague accepts it.
If they accept, update the scope and next step. If they send a different version with a larger request, record what changed and ask whether the original limited review is still useful. The journal should help you prepare a clear conversation, not silently settle a disagreement.
Check a suggested response before using it
Favor’s current App Store listing describes a library of boundary-setting responses, personal interaction records, game-style progression and PDF exports. A ready-made phrase can be a starting point, but it still needs to match your relationship and the actual request.
- Remove a reason that is not true for you.
- Replace vague language with the scope you can genuinely offer.
- Check that the wording does not promise a later task you have not chosen.
- Read it as the recipient might, especially when a short message could sound abrupt.
Sometimes the clearest answer is a simple decline. Sometimes it is a question about priority or timing. Offering an alternative is optional; it should not quietly create a second commitment you cannot meet.
Review unfinished agreements, not people’s scores
Once a week, look for three things: promises you still need to keep, offers awaiting an answer and requests whose scope changed. Resolve the factual status first. A request that was withdrawn should not remain in your mind as work you owe.
If you notice repeated last-minute requests, describe the pattern narrowly: which tasks, which deadlines and which changes? A useful next step might be asking for more notice on a particular recurring task. It does not require deciding that every interaction with that person has the same meaning.
Treat points, streaks and other game elements as optional engagement features. They cannot measure another person’s value or tell you whether saying yes or no was the right choice. A generous choice can be deliberate; so can declining.
Keep the journal proportionate and private
Record only the details you need. Avoid copying confidential work, sensitive information about someone else or an entire contact history into a personal journal. Consider what would be visible if the device were shared or a report were exported.
Before sharing a PDF, review every included entry and remove unrelated details. A private note reflects your perspective, and exporting it does not turn it into an independently verified account. For a workplace disagreement or a serious personal situation, a journaling app is not a substitute for appropriate professional support.
Common questions
Should I log every favor?
No. Start with requests that are unclear, changing or easy to forget. The journal should reduce administrative work, not create more of it.
What if I changed my mind?
Record the change and communicate it to anyone relying on the original agreement. Editing your private note alone does not update their expectations.
Can the app decide what I should decline?
No. Your context and commitments determine that choice. A record or suggested response can help you think it through, without making the decision for you.
For product details, review the iOS edition page. The private boundary-tracker guide covers broader selection and privacy considerations.