Feature Guide

Compatibility

How Matchdiary scores a pair against partner preferences — and where that score turns up.

In a nutshell

  • Compatibility is scored in both directions: does B fit A's stated preferences, and does A fit B's?
  • Each preference is weighted — must-have counts most. The pair is then labelled bidirectional, one-way, no match, or no preferences.

Two directions, one pair

A good match usually goes both ways. Matchdiary checks each side's partner preferences against the other person.

Source profile

score each direction
→

Candidate profile

Both people's partner preferences are evaluated; a missing set of preferences on one side makes that direction score zero.

A → B and B → A

The score is not a single vibe — it's two preference checks, one per person, combined.

  • Direction A→B: does the candidate satisfy the source's preferences?
  • Direction B→A: does the source satisfy the candidate's preferences?
  • Each direction produces a percentage; a direction "matches" at 50% or above
  • The two directions together give the pair its match type

How much each preference counts

When you set a partner preference you also set how strongly it matters. That level is the score weight.

Must-have
20 points — a hard requirement
Preferred
10 points — clearly wanted
Acceptable
5 points — fine either way
Will consider
2 points — open to it
Match threshold
A direction counts as a match at 50% of its possible points or higher
The percentage is that direction's earned points divided by the maximum it could have earned from the preferences that person actually set.

The five outcomes

The two directional results combine into one label you see on the pair.

Match typeA → B matchesB → A matches
BidirectionalBoth people's preferences are satisfied — the strongest signal
One-way (A→B)The source's preferences are met, the candidate's are not (or unset)
One-way (B→A)The candidate's preferences are met, the source's are not (or unset)
No matchNeither direction reaches the threshold
No preferencesNeither profile has partner preferences set — nothing to score——

Where the score appears

The same engine feeds several surfaces.

Pool & roster candidate lists — sorted by score A profile's compatible-matches panel The seeker's browse view — as a match percentage Suggestion-building — to help you pick

Kept fresh automatically

Scores are cached so lists load fast, but never go stale silently.

Cache, invalidation, refresh

A pair's score is cached the first time it's needed. Saving either profile's partner preferences clears that cached score, so the next view recomputes it. You can also force a fresh recompute on demand.
Cached
Per pair, per matchmaker — first computed on demand.
Cleared when
Either profile's partner preferences are saved.
Force refresh
Available on the compatibility view to bypass the cache.
No preferences set
The pair is labelled "no preferences" — not zero, just unscored.

Related features

SuggestionsAuto-ConnectPartner preferences
Network Pool