Did the Date Actually Happen? Chem IRL Is the Best Dating App That Bothers to Ask.

You proposed Wednesday night at seven. They said yes. You walked to the bar, took a stool at the corner, and waited. Forty-five minutes later you walked home in the same coat you'd just put on. A week later, the match you'd never confirmed-confirmed slid quietly out of your inbox when it expired. The only person who knew that meeting had failed to happen was you.

This is the part of dating-app design most apps decline to fix because fixing it would require admitting the meeting was supposed to happen at all. The app is built to deliver matches, not meetings, and a meeting that didn't happen is, structurally, none of its business. Chem IRL is built to deliver meetings. That makes it, by extension, our business.

Which dating app actually confirms whether dates happened?

Chem IRL, as a built-in mechanic on every scheduled date. After the proposed meeting time, both people get a separate two-tap prompt — did this happen? The yeses count toward the Seriousness Score and toward the public reputation badges. The noes are cross-checked, soft-reviewed, and logged. It is the rare moment in a dating app where the offline event gets fed back into the online system, and it changes how the rest of the app is allowed to work.

How does the confirmation actually work?

The prompts go out shortly after the scheduled end of the date — long enough that the meeting is genuinely over, short enough that it's still fresh. The form is two taps: a yes/no answer, an optional one-line note. Honest feedback is rewarded (it lifts the score regardless of the answer); silence is just silence.

The two answers are then cross-referenced.

Both yes. The cleanest case. Date counts; both Seriousness Scores move up; reputation badges accrue against the cumulative count.

Both no. Match closes. Neither score takes a hit, since both parties confirmed the meeting didn't happen — that's just life. The match's expiry is honored, and both users move on.

Yes / no mismatch. Goes to soft review. We don't punish either party automatically; we flag the case, look at surrounding context (the chat history, prior reports, prior pattern), and add it to the reportee's history if the pattern persists. A single mismatch is rarely conclusive. Three mismatches against the same user, across three different matches, are.

Silence. Logged as unconfirmed. Repeated non-response across many dates does affect the Seriousness Score, slowly. A single missed prompt doesn't.

The system is designed to be expensive to game and cheap to use honestly.

Why doesn't every dating app confirm dates?

Building the prompt is trivial. Building a system that does something with the answers is harder, and most apps don't have a reason to do the work. If the business model rewards time-on-app and matches-per-user, the question of whether matches turned into meetings is — bluntly — bad for the dashboard. A "yes, it happened" prompt is interesting; a "no, it didn't" prompt is a metric the company would have to do something about, and most companies prefer not to.

We chose to know. Read more about why outcomes are our north star in the post on counting dates. The short version: an app that doesn't measure whether matches become meetings is an app that can't honestly claim to be helping you meet anyone. We measure, on every date, both ways.

What does this make possible?

Three downstream things, all visible to users.

Reputation badges that mean something. Counts of completed dates and on-time arrivals on a profile aren't gamified streaks; they're earned through real, two-sided confirmed events. Other users can read them before swiping. (See reputation badges in the flaking post.)

A Seriousness Score with ground truth. Most behavioral scores are inferred from in-app activity alone. Ours is anchored to the actual outcome variable — meetings — which makes it less gameable and more meaningful.

Pattern-based detection of bad actors. Multiple no-show reports against the same user, even from matches months apart, build a pattern that the moderation system can act on. (Read more in the post on human moderators.) Without confirmation, that signal doesn't exist.

What we give up to do this

The honest tradeoff: every dating app is built to look maximally healthy on its dashboard. Asking users to tell us when dates didn't happen guarantees we'll see, on a daily basis, the rate at which our matches are failing to convert. That's an uncomfortable number for any product team. We made it a primary KPI on purpose; the alternative is shipping a product that's allowed to ignore its own outcomes.

We also add a little post-date friction — two taps a couple of hours after a meeting. Some users will skip it; that's fine, and the system handles silence gracefully. We chose two taps over zero on the bet that most users actually want the system to know whether the meeting worked.

What this looks like for you

After your next date, the app will ask. Two taps. If it went well, say so; the system rewards you accordingly. If it didn't happen, say that too; the system protects future users by remembering. Either answer is a small honest move that compounds across the user base into a more reliable product for everyone.

That's the design. The meeting is the point; we built the app to know whether the point was reached.

Common questions

How does Chem IRL confirm a date happened?

After the scheduled meeting time, both people get a separate two-tap prompt: did the date happen? Yes lifts the count and the Seriousness Score; no asks a single follow-up. The two answers are cross-checked. Matching answers count cleanly. A mismatch (one yes, one no) triggers a soft review that doesn't immediately punish either party — it flags the pattern.

Why doesn't every dating app confirm dates?

Because most apps deliberately don't measure offline outcomes. Building the prompt is technically trivial; building the system that does something with the answers — feeding them into matching, into reputation, into business decisions — is hard. And measuring real-world outcomes risks proving that the app's matching isn't producing them. Most apps prefer not to know.

What if only one person confirms the date?

It's logged as unconfirmed. We do not penalize the user who didn't respond to the prompt; people get busy, miss notifications, forget. Repeat patterns of non-response do reduce the Seriousness Score over time. The asymmetry is intentional — it's expensive to falsely punish a real user, and cheap to under-count a real meeting.

What happens if you mark a date as a no-show?

If both people agree it didn't happen, the match closes. If one says yes and the other says no, the case goes into a soft-review queue rather than triggering an automatic strike. Repeated no-show reports against the same user, especially from different matches over time, build a pattern that does affect their visibility and account status.