1. Trackers
  2. Relationships
  3. Argument & repair log Tracker
Argument & repair log Tracker
Relationships

Do you repair faster than you think?

Log arguments and their outcomes — and let AI reveal whether your relationship bounces back quicker when certain patterns shift.

Be first when Argument & repair log launches

No spam. One email when it's live.

2 minutes after the dust settlesAI insight at 30 daysFree to startComing soon
Your argument & repair log
7.2/ 10 avg
Last 30 days
W1W2W3W4
+0.4 vs last month
This week
M
T
W
T
F
S
S
Your streak
9days
AI insight preview

In the last 8 arguments, when intensity was above 6 and harsh_startup was true, time_to_resolve_hours averaged 18.3. When intensity was similar but harsh_startu…

Based on 31 entries · free at 30 days · only you see this
Only you see your data
No one else — not even the team — can read your entries
Export or delete anytime
One click. Full CSV export. Account deletion is instant.
AES-256 encrypted at rest
Your entries are encrypted before they're stored. Always.
Why track this

Arguments feel chaotic in the moment, but they leave patterns behind. By logging the setup (who started it, how it began, what you were both dealing with) and the outcome (how long repair took, what actually resolved it), you build a private dataset of your relationship's conflict cycle. Over time, AI can show whether certain conditions — like poor sleep, harsh opening lines, or high background stress — reliably predict longer repair times or sharper intensity. You're not diagnosing your relationship; you're just seeing what actually happens when things go sideways.

What it tracks

6 fields. Done in 2 minutes after the dust settles.

Fast enough to fit into any routine, specific enough to generate real patterns after 30 days.

Argument today?
boolean
Argument intensity (1 = mild, 10 = severe)
scale
Topic(s) of the argument
multi select
Who initiated
single select
Harsh startup? (first words sharp, accusatory, sarcastic)
boolean
Time from start to resolution (hours)
number
How it works

Log, build, learn.

01

Log after the repair

Once things have cooled down, open the tracker and answer the fields — intensity, topic, who started it, how long it took to resolve.

02

Build a conflict dataset

After a handful of arguments, you'll have enough logged data for the AI to start comparing outcomes — which setups led to quick repairs, which dragged on.

03

Get your first pattern

The AI will surface correlations — like whether harsh_startup predicts longer time_to_resolve_hours, or if certain topics always resolve faster than others.

Benefits

Why people stick with it.

See whether harsh opening lines actually make repair slower in your relationship
Spot which argument topics resolve fastest — and which spiral
Understand if poor sleep or high stress reliably makes conflicts sharper
Track whether you're getting quicker at bouncing back over time
Stop relying on memory and start seeing your real conflict cycle
What you'll learn

4 things Argument & repair log reveals about you.

  • Whether harsh opening lines predict longer repair times in your relationship
  • Which topics resolve quickest — and which linger
  • If poor sleep or background stress makes arguments sharper or slower to heal
  • Your relationship's actual repair speed, not what you assume it is
Sample AI insight

Here's what arrives at 30 days.

Illustrative — your analysis uses your own data.

What AI analysis reveals
Your argument & repair log pattern

The AI looks at how fields like harsh_startup, intensity, and stress_either correlate with time_to_resolve_hours and resolution outcomes. It might show that arguments about certain topics (topic_kind) always resolve faster, or that when sleep_poor_either is true, intensity tends to spike. Over weeks, it can surface whether your repair speed is actually improving — or if certain setups reliably predict longer, messier conflicts. These are illustrative examples of the kind of patterns the AI spots, not guaranteed results.

Your averages
7.2/10
vs 8.4 on your best days

In the last 8 arguments, when intensity was above 6 and harsh_startup was true, time_to_resolve_hours averaged 18.3. Whe

Your best runs
May 4–6 · avg 8.4
Consistent routine · early start
May 13–16 · avg 8.1
Low stress · good preparation
May 23–25 · avg 7.9
Same pattern · 3 times
Pattern confirmed
Who's tracking Argument & repair log

People watching their own patterns.

This tracker is for anyone in a relationship who wants to understand their own conflict patterns — not fix their partner, just see what actually happens after a row.

FAQs

Common questions

Will my partner see what I log?

No. This is your solo tracker. Your partner never sees your entries, and you never share access unless you actively choose to export and send something yourself.

What if we argue but never actually resolve it?

You can still log the argument and mark the outcome as 'unresolved' or 'swept under the rug'. The AI can still spot patterns in what leads to those outcomes versus quicker repairs.

Do I log every single disagreement?

That's up to you. Most people log anything that felt tense or required repair — not every tiny difference of opinion. The tracker works best when you're consistent about what counts as an 'argument' for you.

What if I can't remember exactly how long it took to resolve?

Rough estimates are fine. The AI looks for patterns across multiple entries, so one imperfect number won't skew the bigger picture.

Will this help us argue less?

It won't stop arguments, but it might show you what makes them sharper or longer — and what helps you both bounce back faster. What you do with that is up to you.

Can I add context without naming names or quoting what was said?

Yes. The notes field is for themes only — no direct quotes, no partner's name. You're tracking the shape of the conflict, not building evidence.

Free forever · Plus £7.99/mo · Pro £17.99/mo

Coming Soon

Be first when Argument & repair log launches

We'll email you as soon as this tracker goes live.

Be first when Argument & repair log launches

No spam. One email when it's live.