Make today’s session clear when you read it tomorrow
You finish training, open your phone’s notes and jot down a few things before you forget. When you come back to them, “3 × 10” still makes sense, but the “12” on the next line is less clear. Minutes? Repetitions? A useful diary doesn’t need to look impressive: you need to be able to tell what you actually did.
You can ask an AI to arrange those notes in a table. You provide the facts; the AI suggests how to present them. We’ll use a fictional session created solely to explain the recordkeeping process. The exercises and quantities in this example are neither a recommended workout nor a customer’s results.
Start with a note you can check
Imagine you wrote this: “10 November 2026. Biceps curl: 3 sets of 10 repetitions each. Treadmill: 8 minutes. Bike: 12 minutes. I didn’t record the dumbbell weight or how the session felt”.
That gives us enough information for three rows. It doesn’t tell us how many calories you burned, how much you should lift next time or whether you’ve improved. We don’t know the full session length either: the time spent on curls, rest periods and any other breaks are missing.
If your notes only say “curl 3 × 10”, clarify what you meant before turning it into a recorded fact. A likely interpretation is still an interpretation. When you can’t remember something, leave it unresolved; filling a cell with a guess makes the record less reliable.
Give each number its own place and unit
For this example, these columns will work: date, exercise, sets, repetitions per set, minutes, load and notes. Remove any you don’t need. What matters is that “10 repetitions” doesn’t end up in the minutes column, and that any load you record includes its unit.
The curl row would show 3 sets and 10 repetitions per set. The load would read “Not recorded”. The treadmill row would show 8 minutes; the bike row, 12. The note contains no sets or repetitions for those last two activities, so there’s no reason to enter zeros.
“Not recorded” means we don’t have that information. “Not applicable” means the column doesn’t apply to what you’re recording. They are different things. Keep your original note beside the table, too: it lets you resolve a question without relying on the chat’s interpretation.
A simple prompt for organising the session
A prompt is the instruction you give an AI. OpenAI’s and Google’s guides recommend explaining the task, providing context and specifying the format you want. For this task, you can try the following original example in the chat you already use, then paste in your notes.
“Help me organise these notes from a session I have already completed. Create a table with date, exercise, sets, repetitions per set, minutes, load and notes. Use only the information I provide and keep its units. If a detail is missing, write “Not recorded”; don’t replace it with zero or guess it. If something could mean more than one thing, ask me before placing it in a column. Don’t suggest a workout, changes in load, calories or conclusions about my progress. Keep any calculations separate from the original data and explain how you calculated them. List any unanswered questions at the end. Here are my notes: [paste what you recorded here]”.
This is an instruction for organising information, not a guarantee of a correct answer. If the table is confusing, you can ask for a simpler version or point out the specific mistake. Check the revised answer just as you checked the first one.
Two correct calculations that can still mislead
In our fictional example, 3 sets of 10 make 30 curl repetitions. That total is calculated from the note; it doesn’t replace the breakdown into sets. Keeping only “30” would lose a detail we already had.
We can also add 8 minutes on the treadmill and 12 on the bike: that’s 20 minutes across those two activities. If the answer says “Total workout duration: 20 minutes”, correct it. The sum is right, but the label is wrong. The full session length is still unknown.
Before saving, compare names, dates, quantities and units with the original. Remove any invented weight or progress claim without supporting data. Microsoft’s documentation reminds readers that Copilot’s responses can contain errors and should be checked; a neatly formatted table needs the same scrutiny.
Once you have several sessions, compare like with like
Save the checked table wherever suits you: in a note or a spreadsheet. When you want to compare two sessions, provide both and ask the AI to identify differences in the recorded data, with dates and units. Don’t assume the chat has your complete history.
More minutes or repetitions aren’t enough on their own for this record to prove improvement. The exercise, machine or way you recorded it may have changed. If one session has no load recorded, comparing loads remains an open question. The diary helps you remember and prepare questions for your trainer.
Also distinguish each day’s actual notes from reminders you reuse. A description of how you felt last week shouldn’t be copied as though it happened today. To organise this example, you don’t need to share your name, medical reports or information about other people.
If you’re looking for the RavenPrompts listing
The “Create a training diary” prompt relates to this task and is paid; its public description is available at the link below. This article’s original example is separate, and you can try it yourself. Keep your own checked records: viewing a RavenPrompts listing doesn’t automatically create a history of your sessions.
Start with one note. If you can read it tomorrow and tell what you did, what’s missing and where each total came from, you have a useful starting point for keeping records. What detail do you usually find missing when you review a session?

