Guides / EverReach
Build a weekly relationship review that takes one page
A one-page weekly relationship review: template, decision process, worked example, follow-up limits, and simple scheduling with calendar and reminders.
Consider a hypothetical Friday review: one friend is waiting for a reply, a relative is having a difficult week, and a former colleague is someone you want to contact. Write down the next action you intend to take for each person, rather than treating all three as one task called “keep in touch.”
This guide proposes a one-page weekly worksheet. Its fields, scoring categories, time limits and follow-up boundaries are chosen planning rules for this exercise, not measured predictors of relationship quality or future replies. Use the page to decide what you intend to do this week and what you intend to leave alone.
What the one-page review should do
A useful review answers five questions:
- Who needs attention from me this week?
- Why are they on my mind?
- What is the next action?
- When will I do it?
- When will I stop following up and give space?
For this method, decide whether a follow-up is appropriate before adding one. You may choose no follow-up, and any existing request for no contact takes precedence over a worksheet entry.
Use the page for current decisions. Leave out detail that does not help you choose a relevant next action.
Nielsen Norman Group’s September 1997 report describes 79% of its test users scanning new pages and 16% reading word by word. It recommends meaningful subheadings, lists and one idea per paragraph for web text (NN/g reading study). Those are findings and recommendations from that report. For this personal worksheet, use short labels and one decision per field as a proposed formatting rule.
The template: one row per person
Use a table with one row per person you have chosen to consider this week. Federal plain-language guidance emphasizes a specific audience and testing whether that audience understands the content (plain-language guidance). Here, you are the intended reader: write each entry so you can identify the proposed action when you return to it.
| Person | Relationship / context | Last meaningful contact | Current note | Next action | By when | Follow-up boundary |
|---|---|---|---|---|---|---|
| Name | Short cue | Date | One sentence | Specific action | Date | Stop point if no reply |
Here is what each column is for.
Person Use the name you would naturally search for.
Relationship / context Write a short cue, not a history. Examples: “former teammate,” “uncle recovering from surgery,” “friend with new baby.”
Last meaningful contact Use the last exchange that actually updated the relationship. For this worksheet, distinguish an exchange that gave you useful context from a quick reaction.
Current note One sentence only. Include the context that should shape your tone or timing.
Next action Make it observable. Good entries start with verbs:
- send a check-in text
- reply with the promised article
- suggest coffee next week
- mail a card
Weak entries are too abstract:
- reconnect
- be supportive
- keep in touch
By when Use a date for an action you have decided to take; mark an undecided action as deferred.
Follow-up boundary Decide in advance what “enough for now” means.
Examples:
- no follow-up needed
- one reminder after invitation
- pause after one unanswered message
A weekly decision procedure you can reuse
The real challenge is not filling out columns. It is deciding who belongs on the page at all.
Use the proposed process once a week. For individual tasks, Apple provides a guide to creating reminders on iPhone (Apple reminder guide). The worksheet below is a separate planning exercise; no product integration is assumed.
Step 1: Do a two-minute name sweep
Write down names without organizing them yet. Include people who fit any of these:
- you owe them a reply
- they are in a major life event or stressful period
- you promised something
- you want to invest in the relationship
- you do not want the connection to fade by accident
Treat two minutes as an optional prompt for this exercise, not an estimate of how long a complete review should take.
Step 2: Score each name quickly
Use a simple 0–2 scale for three factors:
- Importance: How important is this relationship right now?
- Timeliness: Is there a reason this week matters?
- Drift risk: Does the contact gap exceed a check-in interval you have chosen? This is a personal planning category, not an estimated probability.
Add the numbers.
| Total score | Meaning | Default action |
|---|---|---|
| 5–6 | High priority | Put on the page |
| 3–4 | Worth attention | Add if space allows |
| 0–2 | Lower urgency this week | Leave off |
This is a focusing tool, not a moral ranking.
Step 3: Limit each person to one next action
For this one-action version, choose one step for the row and keep other ideas separately.
Choose the smallest useful move.
- not “repair friendship,” but “send an honest check-in message”
- not “network,” but “reply with the promised introduction”
- not “support them,” but “mail a card”
Step 4: Add a respectful boundary
Before you send anything, decide what you will do if there is no reply.
Examples:
- one invitation, then one reminder, then pause
- one supportive message, no follow-up
- one check-in, then wait for them to reopen
Use the chosen boundary as a limit on your planned action rather than a scheduled chase sequence.
Step 5: Review outcomes at the end of the week
Use one of four labels:
- Done
- Waiting
- Deferred
- Dropped
Use those labels to record what you actually did and what remains unresolved.
Fully worked example
The following example is hypothetical. Names, dates, and situations are synthetic and only demonstrate the method.
Assume the weekly review happens on Friday, November 6, 2026, with the outcome review one week later.
Step A: Initial name sweep
- Maya
- Devin
- Aunt Rosa
- Lena
- Jordan
- Priya
Step B: Quick scoring
| Person | Importance (0–2) | Timeliness (0–2) | Drift risk (0–2) | Total |
|---|---|---|---|---|
| Maya | 2 | 2 | 1 | 5 |
| Devin | 1 | 1 | 2 | 4 |
| Aunt Rosa | 2 | 2 | 0 | 4 |
| Lena | 2 | 0 | 2 | 4 |
| Jordan | 1 | 0 | 1 | 2 |
| Priya | 2 | 1 | 1 | 4 |
If your one-page review has room for five active names, Jordan stays off this week because Jordan is the only score-2 entry.
Step C: Build the page
| Person | Relationship / context | Last meaningful contact | Current note | Next action | By when | Follow-up boundary |
|---|---|---|---|---|---|---|
| Maya | Close friend; interviewing | Oct 28 | Final interview is this week | Send a brief good-luck message | Nov 6 | No follow-up |
| Devin | Former colleague | Sep 14 | Mentioned reconnecting after the move | Suggest 20-minute coffee next week | Nov 8 | One reminder max |
| Aunt Rosa | Family; recovering from surgery | Oct 30 | Home from hospital and likely tired | Mail a short card instead of calling | Nov 7 | No follow-up |
| Lena | College friend in another city | Aug 9 | Long gap, no known tension | Send check-in with one personal update and one question | Nov 9 | One follow-up max |
| Priya | Mentor | Oct 12 | Owe her the article I mentioned | Email article with two-line thank-you | Nov 6 | No follow-up |
Step D: Turn rows into real outputs
The review page is not the final work. The message or action is.
Maya “Thinking of you today. Hope the interview goes smoothly. No need to reply.”
Intent: refer to the known interview and make a reply optional.
Devin “You mentioned reconnecting after the move. Want to grab coffee for 20 minutes next week if your schedule allows?”
Intent: state the context, ask for a specific meeting and leave the choice with Devin.
Aunt Rosa Action: mail a short card instead of calling.
Intent: choose a format consistent with the fictional context note; an actual recipient’s preferences may call for another choice.
Lena “Thinking of you this week. I finally finished the class I told you about. How have things been on your side?”
Intent: include one personal update and one question without claiming to know why contact lapsed.
Priya “Here is the article I mentioned on onboarding. Thank you again for your advice last month.”
Intent: send the promised item and acknowledge the earlier help.
Step E: Check the result at week’s end
| Person | Outcome | What to check |
|---|---|---|
| Maya | Done | Message sent by date |
| Devin | Waiting | Invitation sent; no extra nudge yet |
| Aunt Rosa | Done | Card mailed |
| Lena | Deferred | Intentionally moved, not forgotten |
| Priya | Done | Promise completed |
For this example, completion means recording the planned actions and their status. A reply is a separate observation, not a required outcome or proof of relationship quality.
How to schedule it with simple tools
You do not need a specialized system for this habit.
Use a recurring calendar block for the review
If you choose a standing review time, create a recurring event. Google Calendar allows you to create a repeating event, choose the frequency, and set when the repeating series ends; it also lets you edit repeating events and choose which events in the series changes should apply to (Google Calendar Help).
A practical pattern is:
- Friday: review names and choose actions
- Monday: send anything that needs more energy or thought
That split is optional. The point is to separate planning from execution if doing both at once makes the task feel heavier.
Use reminders for individual actions
After the review, create reminders for the actual tasks. Apple provides guidance for creating reminders on iPhone (Apple Support).
Name reminders with a verb and a person:
- Text Maya
- Mail card to Aunt Rosa
- Send Priya article
Avoid vague reminder names like “relationships” or “keep in touch.” A reminder should tell you exactly what to do when it appears.
Assumptions, limits, and common mistakes
This proposed method uses a small set of entries. Decide whether that scope fits your current situation.
Assumptions
This article assumes:
- you want a lightweight personal practice
- you are comfortable keeping short written notes
- you can focus on a handful of active relationships per week
- you want a prompt for action, not a complete record of every interaction
Limits
This method is not enough for:
- ongoing conflict that needs a direct conversation
- situations where contact may be unwelcome
- privacy-sensitive details you should not store casually
- relationships that are persistently one-sided and need a harder boundary decision
It is a planning habit, not a substitute for judgment.
Common mistakes
Writing too much context If every row becomes a paragraph, the page stops being a review and starts being an archive.
Choosing abstract actions Replace “reconnect” with the specific action you have chosen.
Skipping the follow-up boundary Record the contact limit you chose and check it before another message.
Treating silence as a failure A good review measures whether you took a respectful step, not whether you got a response.
Keeping everyone on the page forever The page should reflect this week, not every relationship you have ever had.
Reusable checklist
Copy this checklist into the bottom of your page:
- [ ] I listed names for two minutes without organizing
- [ ] I scored each name for importance, timeliness, and drift risk
- [ ] I chose who belongs on this week’s page
- [ ] Each row has one short context note
- [ ] Each row has one specific next action
- [ ] Each action has a date
- [ ] Each row has a follow-up boundary
- [ ] I created calendar time or reminders where needed
- [ ] At week’s end, I marked each row done, waiting, deferred, or dropped
At week’s end, record what you actually did, what remains open and which contact you decided to pause. Bring only unresolved, still-appropriate actions into the next review.