The signal deciding your progress may not have a tab in a normal fitness app. Knee pain. Caffeine cutoff. Grip fatigue. Cycle symptoms. Migraine frequency. How a supplement affects your sleep. Every one of those matters to someone, and none of them fit a screen designed for sets and calories.
Custom trackers usually come in one of two bad shapes: a spreadsheet you maintain by hand, or an app that lets you name a metric and then does nothing with it. ChatRPE is a third option — describe the thing in normal language and it gets a stable structure, a place in the same Universal Logbook as your training and nutrition, and a coach that can actually analyze it later. If you have ever wanted an app where you can track anything and have it sit next to everything else, that is the whole idea.
What a custom metric costs in each workflow
| The old workflow | The ChatRPE upgrade |
|---|---|
| Build a spreadsheet column, then maintain the file forever | Say the thing once; the structure is created and reused |
| A "custom field" that only ever renders as a number on a card | A saved data type the coach can chart, average, and trend |
| Your custom metric lives apart from training and food | One logbook, so "knee pain after leg days" is a single question |
| You have to remember what units and scale you picked in March | The field names and value types you used are carried into every session |
| Reviewing means exporting and building a pivot table | Ask for the average, the direction, and the chart in one message |
Start with the decision, not the data
Tracking without a question is homework. Before adding a metric, finish this sentence: "If this changes, I will…"
If no result would change your behavior, skip it. A simple metric you log consistently beats a detailed schema you abandon.
Let ChatRPE shape the fields
Most useful custom records need a date, value, short note, and one or two pieces of context. You do not have to design that up front — describe what you want to watch and let the structure fall out of the description.
Try this: "Track my left-knee status after leg days. Use pain from 0–10, swelling yes/no, triggering exercise, and whether it changed the workout. Keep this structure for future entries."
Use one stable name for one idea. If knee_status becomes knee pain next week, ask ChatRPE to standardize it before analysis — two names for one metric is the single most common reason a custom log stops being chartable.
It remembers the structure you invented
This is the part a "custom field" in a normal tracker cannot do. ChatRPE keeps a live index of the data types you have actually saved and the field paths inside each one — that knee_status has pain as a number, swelling as a boolean, exercise as text — and that index is loaded into the coach's context before the conversation starts. It is built from a recent sample of your entries, so a metric you have not touched in a very long time may need to be named once to bring it back into view, but for anything you are actively logging the coach already knows the shape.
The practical effect is that you define a metric once and never re-explain it. Six weeks later, "log knee 3/10, no swelling, after squats" lands in the same structure as the first entry, which is exactly what makes the eventual chart readable. A spreadsheet gives you that discipline only if you supply it yourself; here it is the default.
Ask for the number, not just the chart
Once a custom metric has a few weeks behind it, ChatRPE can run real analysis on it rather than just displaying it: the average, total, minimum and maximum, the most recent value, how many entries went into it, and whether the direction over the window is increasing, decreasing, or flat, with a rough percent change. That works on any numeric field in any data type you invented, not just the built-in ones.
Try this: "What's my average knee pain score over the last month, and is it trending down since I changed my squat depth?"
Name the data type and the period you care about and the analysis answers that question precisely, which is how to interrogate a long-running metric one phase at a time. The direction it reports comes from comparing the earlier and later halves of that window, so treat it as the signal that tells you where to look closer.
Run a real experiment
"Track caffeine cutoff, sleep quality from 1–5, and morning energy for 14 days" is better than "track sleep." It has a window, a small schema, and a decision attached.
Two metrics you can plot against each other is where custom tracking pays off, because that is the question no single-purpose app can answer. ChatRPE can put two saved metrics on one chart — separate axes when their scales differ, a scatter plot when you want to see whether they move together, and a moving average over the noisy one. The sleep tracker guide walks through that two-metric pattern with sleep and training, and the same shape works for a supplement against recovery, or stress against calories.
Review noisy signals in batches. Then use small dashboards to keep only the views that help you decide.
Metrics with no number at all
Plenty of things worth tracking have no value to plot — you took the supplement, you did the mobility work, the headache happened. Those still log fine, and ChatRPE can chart them by frequency, counting entries per day, which is what turns a yes/no metric into a calendar heatmap of how often it actually occurred. That is the same machinery behind consistency tracking in the habit tracker guide, pointed at whatever you decided to watch.
Free-text belongs in the record too. A custom entry can carry a note, and notes are searchable by keyword later, so "what was I writing about my elbow in March" is a real question rather than a scroll. The workout journal guide covers the note side of the logbook in depth.
Your custom data is still yours
Anything you invent is included when you export. The download is a zip containing a CSV of your entries with their data types and fields, a Markdown file of your notes, and an index — so a metric you made up in week one comes out in the same file as your workouts and weigh-ins. See the data export guide for the full format and how often you can generate one.
Keep health claims in bounds
Pattern tracking can help you prepare better questions and notice changes. It does not diagnose an injury, condition, or deficiency, and ChatRPE is a coach and a logbook rather than a medical service. Bring concerning symptoms and medical decisions to a qualified clinician — a clean log of what you tracked and when is genuinely useful to bring to that appointment.
Frequently asked questions
Can ChatRPE track data that is not fitness-specific?
Yes. Habits, symptoms, notes, expenses, tasks, and custom scores can all become structured entries when they support your goals or routine. The category name is free-form, so the metric does not have to resemble anything a fitness app ships with.
What is the best custom fitness tracker app?
The useful test is not whether an app lets you name a metric — most do — but whether it can analyze the metric afterward and read it against everything else you log. ChatRPE keeps custom metrics in the same logbook as workouts, food, weight, and sleep, remembers the structure you defined, and can average, trend, and chart any numeric field you invented. That is what makes a custom metric worth logging rather than just worth naming.
Is there an app where I can track anything I want?
That is what this workflow is for. Describe the thing you want to watch in a sentence, agree on a simple structure, and log it in plain language from then on. There are no fixed categories to choose from and no schema to design in advance.
Do I need to define every field up front?
No. Start small and refine the structure after you see what is actually useful. Adding a field later is a sentence, and older entries simply do not carry it.
How do I avoid tracking too much?
Use one rule: if no trend in the metric would change your behavior, it is noise. Do not track it. Two or three custom metrics with a decision attached beat ten you stop filling in by week three — the daily coaching workflow is a better home for anything you only want to mention in passing.
Can I compare a custom metric against my training or weight?
Yes, and that is usually the reason to track it. Because everything lives in one logbook, you can ask for a custom metric and a standard one on the same chart — pain scores against training volume, a supplement against sleep quality, stress against daily calories — with separate axes or a scatter plot depending on what you are looking for.