For clinicians

What your client did between sessions, written down.

Meloa is a self-monitoring app your client owns. It attaches distress ratings to the real events on their calendar, before and after, so what you talk about on Tuesday isn’t rebuilt from memory a week later. If they want you to see it, they export a PDF and bring it.

What the client is actually collecting

SUDS either side of the event

0–100 SUDS logged before an event (T−1) and after it (T+1), anchored to a real, dated thing on the client's calendar rather than a daily prompt. The pair is the point: a prediction and its own outcome, so the gap is measured, not recalled.

A four-part breakdown

Each check-in optionally splits into somatic, cognitive, anticipatory, and autonomic subscores (0–25 each), so a flat 70 can be read as a body-led 70 or a rumination-led 70.

Context, not just numbers

Every log carries the event's category, whether it happened at home, and whether it fell in a prep or recovery window. A score arrives with its situation attached.

Periodic baseline assessments

Short self-report check-ins: general anxiety and depression adapted from the GAD-7 and PHQ-9, plus a social-anxiety check-in written for Meloa. Four items each, scored 0–100, not full administrations, and each can be skipped. A skipped scale is recorded as not taken, never as a zero, so it can't enter the series as a floor score.

Try the loop yourself

No account, and nothing leaves this page. Drag the rating and watch the held hours resize. That’s the same math a real event uses.

Try it right hereNo account. Nothing you do here is saved or sent anywhere.

Pick a thing. Say how bad it’ll be. Watch the room appear.

50/100 — Building

FineUnbearable

Meloa would set aside 25 minutes to get ready and 25 to land afterwards — 50 minutes nothing else can be booked into. These are the real defaults the app uses.

Afterwards, Meloa asks for one more number: how it actually went. The gap between the two is what you’re here to find out.

Add it for real — freeTakes about a minute. No card.

The report

Your client makes a PDF and picks which sections go in it. Nothing goes in that they didn’t choose.

  • Baseline assessment scores over time (adapted from the GAD-7 and PHQ-9, plus a social-anxiety check-in written for Meloa)
  • Daily baseline check-ins, independent of any event
  • SUDS logs, with how far and how often outcomes came in under the prediction
  • Event history for anything they rated 7+ for anticipated distress

One pattern comes up often enough to name: clients who log both scores often find the anticipation ran hotter than the event. Meloa doesn’t interpret that for anyone. It just makes the pair of numbers exist, dated, so the two of you can look at them together.

See a sample report

Opens a real PDF, made by the same code your client’s export uses. Every figure in it is invented. No user’s data appears anywhere on this site.

What this asks of you: nothing

Meloa creates no duty to monitor, and it’s built so it can’t. There’s no clinician account to make, and no version of this where data lands on your desk that you didn’t agree to receive.

  • You have no login, and there is no clinician dashboard to check.
  • Nothing notifies you. Not a high score, not a missed check-in, not a crisis.
  • You see nothing unless your client hands you a PDF themselves.
  • You are not a party to the account, and Meloa never contacts you about a client.

If a client brings you an export, it’s a document they chose to give you, like a mood diary or a worksheet. Whether it becomes part of your record, and what that obliges you to, is a matter for your own practice and jurisdiction. Meloa isn’t a party to that and doesn’t presume to advise on it.

In an emergency the app tells clients to call or text 988 in the US, or 911. It doesn’t escalate to anyone on their behalf, and it never will.

What it’s built on

Meloa didn’t invent any of these. It just puts them on a calendar.

Prospective forecast vs. outcome

The app asks for a predicted distress rating before an event and an actual one after, and keeps the running record. LaFreniere and Newman's RCT found that logging worries with their predicted and actual outcomes over ten days reduced trait worry in GAD. The mechanism is repeated disconfirmation of one's own predictions, not reassurance from anyone else.

Affective forecasting / impact bias

People reliably over-predict how bad they'll feel and for how long, and anxiety amplifies that. That's why the before/after pair is stored and shown as a record: the gap is the point, and it only works as the client's own dated data, not a therapist's reassurance.

Affect labeling

Check-ins ask for a number and, optionally, a four-part split of what the distress was made of. Lieberman et al. (2007) found that putting affect into words dampens amygdala response and recruits right ventrolateral prefrontal cortex. Naming does something. It isn't just recording.

Ecological momentary assessment

Ratings are captured in the moment and in context, not rebuilt in session a week later. That's the whole rationale for EMA: recalled distress skews toward the peak and the most recent experience.

Psychological detachment and recovery

The recovery window after a hard event is the recovery literature expressed as scheduling: Sonnentag and Fritz on detachment as a distinct recovery experience, and boundary theory on transitions between roles. Meloa's contribution is making the transition a held block rather than something a person has to remember to take.

SUDS in graded exposure

The 0–100 scale is Wolpe's, unchanged, and remains the standard unit for pacing exposure work. Meloa holds the numbers between sessions; you decide what they mean and what happens next.

Where the evidence stops. These mechanisms are established. Meloa is not. It hasn’t been trialed, and whether EMA works as a mental-health intervention is still unsettled: some randomized trials show symptom improvement and others don’t. There’s also a documented risk worth weighing for particular clients. Self-monitoring without an acceptance or mindfulness component can increase emotional reactivity in some people, and for a client who checks or seeks reassurance, one more thing to log may feed the compulsion rather than loosen it. Meloa has schedule-locking safeguards meant to reduce that, but you’re better placed than we are to judge whether tracking helps a given person.

What Meloa is not

  • Not a medical device. Meloa has no FDA clearance and makes no treatment claim. It records self-report; it does not assess, diagnose, or treat anything.
  • Not a validated instrument in itself. SUDS, the GAD-7 and the PHQ-9 are established measures, but Meloa’s assessments are four-item versions scored 0–100 (the social-anxiety one is written for Meloa rather than adapted), have not been separately validated, and should not be read as equivalent to administering the instruments in session.
  • Not a monitoring service. Nobody is watching the data in real time. Meloa does not alert you, page anyone, or escalate. It is not appropriate for risk monitoring, and it does not replace emergency services.
  • Not a clinician portal. There is no therapist login and no dashboard of your caseload. You see a client’s data only when that client hands you a file.
  • Not structured ERP. Meloa can hold the record around exposure work you direct. It does not build hierarchies, set exposures, or pace anyone through them.

Full terms in our clinical disclaimer.

Whose data it is

The client’s, entirely. Every record is sealed to the account that created it, enforced by the database itself rather than by the app remembering to ask. No other account can read their calendar or health data: not ours in ordinary operation, and not whoever pays for their plan. Meloa’s group plan is a billing bundle only: five people, five separate private accounts, no shared visibility of any kind.

Sharing is deliberate. The client chooses the sections, makes the PDF, and decides who gets it. Nothing syncs to a clinician in the background, because there’s no clinician account to sync to.

AI features stay off until a client separately turns them on, which is separate from paying for any plan. See our privacy policy and consumer health data notice.

Free while you’re in practice

Clinicians get the paid tier at no cost, so you can see the record and the export properly before deciding whether to mention it to anyone. You’ll also get a code to hand to clients that gives them 30 days — long enough for the anxiety and mood assessments to be taken twice, which is what makes the second reading mean anything.

I check these by hand, which is why it asks for a license number. No card, and nothing renews.

Who made this

Meloa is built by Andrew. It is a small independent product, not a venture-backed platform, and there is no sales team behind this page — if you write in, you get the person who wrote the code.

Criticism is more useful here than endorsement. If something on this page overstates what the app does, or the report is missing the one thing you would actually want in it, that is worth more to me than a recommendation.

Tell me what’s wrong with it

Pointing a client to it

Send them to meloa.io. The parts that matter clinically, the before-and-after check-ins, the held time around events, and the calendar itself, are free with no time limit. A client can start without a card and keep using them for as long as they like. The paid tier adds the long-term charts, the assessments, and the full PDF export.

Worth saying when you do: on iPhone it’s on the App Store; on Android it’s on Google Play. It also runs in any browser, for a client who’d rather not install anything. It’s the same account and data every way in, so a client who starts in the browser loses nothing by installing the app later.

Worth knowing before you recommend it: a client who starts on the web gets 14 days of the paid tier automatically, starting from their first before-and-after rating, with no card and nothing to cancel. An account created inside the iPhone app does not — Apple requires a free period to be offered through the App Store, so someone who installs from there first starts on the free plan. If those days matter for a client, send them to meloa.io and let them install the app afterwards; the account keeps them. That covers intake and a first pass at the baseline check-ins. It is not long enough for a second. The GAD-7 and PHQ-9 items they’re adapted from both ask about the past two weeks, so a real series takes longer than the introductory period, and a client who wants one will need the paid tier. We’d rather you knew that up front. After it ends the account goes back to the free plan, and those check-ins and the long-term charts sit behind the paid tier unless they subscribe. The before-and-after ratings, the held time and the calendar are unaffected, and nothing they’ve logged is ever removed: older entries are kept, and the free plan shows the recent ones.

The export itself is free. A free account can always make a report covering the last 30 days, enough for one administration and a repeat, so a client you asked to bring something can always bring something. The paid tier adds reach: a report going back months rather than weeks.

One page, no jargon, safe to leave in a waiting room. Print it or save it as a PDF.

Questions about what it collects, or something you need it to do? support@meloa.io. A person reads these.