Training diary

What you actually did, session by session, set against what you said a block of weeks was for. Six months of it answers the question a diary exists for: have you been working on what you meant to work on?

Saved on this device, sent nowhere.Nothing logged yet.My progress holds what you have learned; this holds what you have been doing.

Log a session

Date and what kind of session it was are the whole requirement. The rest helps the reviews below say more.

Optional, and a couple of entries is plenty. This is what lets the reviews below say which material a block of weeks actually went on.

    This week

    Nothing logged this week yet.

    Phases

    A phase is a block of weeks and what you wanted from it: a name, the dates, how many sessions a week you are aiming for, and the material it is for. Everything below measures what you logged against what you said.

    Phases may overlap, because real plans do: a conditioning block can run underneath a technical one, and each is scored on its own terms.

    Add a phase

    What the scorecard checks you actually trained. Leave it empty and the phase is scored on volume alone.

      No phases yet. Without one the diary still records what you did; a phase is what turns that into whether you did what you meant to.

      The last six months

      Everything logged in the last 26 weeks, whatever phase it fell in.

      Nothing logged in the last six months.

      Your sessions

      Nothing logged yet.

        Keep a copy

        A diary is worth more the longer it runs, and a browser can clear this storage. The JSON file carries everything, sessions and phases together, and is what to import on a new device. The CSV carries the sessions alone, for your own spreadsheet, and imports back just as well.

        Importing adds sessions rather than replacing them, and a session already here is recognised and skipped, so importing your own file twice changes nothing. What this site stores is listed on the privacy page.