Field note
The metric that decides your progress probably does not have a tab in a normal fitness app. Knee pain, caffeine timing, grip fatigue, cycle symptoms, screen time, how that supplement hits your sleep.
Describe it in plain language and ChatRPE saves it as structured data. The database gets shaped around what you actually track. Not the other way around.
Try this in chat
“I want to track a custom metric. Help me define the fields, save today's entry, and tell me how we should review it later.”Open ChatRPE
Best for
- People who track more than workouts and calories
- Anyone with recurring symptoms, habits, macros, or recovery variables
- Spreadsheet refugees whose apps were too rigid to keep up
Key takeaways
- Define custom metrics in normal language. No schema design required.
- ChatRPE keeps your structures consistent over time
- Tie every metric to a decision, or do not track it
Start here
4 steps- 01
Name the thing you want to track and the decision it feeds.
- 02
Ask ChatRPE to propose a simple structure with fields you will actually fill in.
- 03
Log the first entry and tell it to keep the same structure going forward.
- 04
After several entries, ask what trend would change your next move.
Copyable prompts
“Track left knee status after leg days. Fields: pain 0-10, swelling yes/no, what exercise triggered it, and whether it affected training.”
A specific structure you can later cross-examine against training.
“For the next 14 days, track caffeine cutoff time, sleep quality 1-5, and morning energy. Help me see if late caffeine is hurting sleep.”
The data has a job. It answers a question instead of feeding a curiosity.
Start with the decision, not the data
Tracking without a question is just homework. Before creating fields, name the decision the data should support.
Cannot name one? Shrink the structure. A simple metric you log every day beats a detailed one you abandon by Friday.
- What am I trying to understand?
- What would make me change behavior?
- Can I log this in under 20 seconds?
Let ChatRPE design the schema
You do not need to know database design. Say what you want to watch and ask for the fields.
A good structure is usually a date, a value, a short note, and one or two context fields. Everything past that has to earn its place.
One idea, one name
Custom data works when the same idea keeps the same name. If knee_status today becomes knee pain tomorrow, ask ChatRPE to standardize it.
Stable names make the charts, summaries, and comparisons effortless later.
Review in batches, not daily
Most custom metrics are noisy day to day. Review after a week or two and ask whether the signal is strong enough to change anything.
That keeps tracking tied to coaching instead of mutating into busywork.
Frequently asked questions
Can ChatRPE track data that is not fitness-specific?
Yes. Habits, symptoms, notes, custom scores. If it is useful context for your goals or routine, it can become structured data.
Do I need to define fields perfectly up front?
No. Start simple and refine the structure once you see what is actually useful.
How do I avoid tracking too much?
One rule: if no trend in this metric would ever change your behavior, it is noise. Skip it.