A simple log for your symptoms from the tendons

Choose what you're using the log first

A log is a tool for a question. Do you want to know whether a practice step is appropriate, whether a working day affects the symptom or whether a treatment makes a noticeable difference? Choose one main question before registering.

Without such a question you can easily collect many numbers that give little direction. For example, a long list of pain scores does not tell whether you have become more or less active.

So start with one important goal and one associated activity. You can expand later when additional information is really needed. A small log you use has more value than a complicated file that remains after three days.

Follow activity and response together

International consensus on results in tendinopathy describes, inter alia, functioning and participation in activities as relevant domains. That supports a broader look than pain.

So write down what you've actually done. A pain score after twenty minutes of walking can be interpreted differently than the same score after two hours. The context makes a figure useful.

At Achilles's tendon symptoms, the Dutch guideline on the monitoring of symptoms and function. An own log does not replace a professional review, but can provide information for that call.

A five-column fill-in model

Use this model on paper or in a simple note:

One example is: fixed walking route, slightly longer walking, manageable nuisance, next morning similar to earlier, that day less stood at work. That gives much more context than just a loose number.

You can use words instead of numbers. Easier, more pauses or response lasted longer can be useful information when you keep recording in a similar way. Choose the shape you can hold on to.

Don't fill in any details that you don't remember afterwards. An empty space is fairer than an estimated figure that later seems exact.

How many times is enough?

The frequency depends on the question. With a fixed daily activity a short note can be useful at some agreed moments. With a specific training step, writing around that session can make more sense.

I want you to meet with your clinician... how often you discuss the overview. If no one uses the data, register loses its purpose. The logbook should support a decision, such as adjusting, building or evaluating a treatment component.

Note the load of keeping itself. If you are constantly looking for pain or interrupting movement to measure, a simpler approach is desirable. Less often registration can give better information from ordinary life.

Read trends without identifying causes too quickly

One good day doesn't prove a treatment worked. One bad day doesn't prove that recovery has stopped. Watch several similar moments and note major changes in circumstances.

When you do new exercises at the same time, work less and start an additional treatment, you cannot determine exactly which part makes a difference. The log can show if the total plan fits your goals.

Use the notes to discuss hypotheses. The long working days seem to coincide with more reaction is a useful observation. My work damages the tendon over and over again is a conclusion that the logbook cannot demonstrate independently.

Use the overview for an evaluation

Mark three things before an appointment: what is clearly improved, what remains difficult and what change do you not understand. As a result, the clinician doesn't have to go through every single note before the call gets direction.

After the discussion, ask what details are still needed. Maybe the main question has been answered and the log can stop. Maybe one other activity will become more important for the next phase.

A log isn't mandatory proof that you're doing your best. It's your tool to tell a recognizable story about load and functioning. When it gives more unrest than insight, the plan should be adjusted, just like any other part of guidance.