Most reloading logs fail the same way: they get filled in carefully for a few weeks and then turn out to be missing the one field you need. Deciding what to record in a reloading log is mostly a matter of working backwards. Ask what you will want to know in a year, when a load has drifted, a canister of powder has run out, or a rifle has started printing differently, and write down the things that would answer it. A log is not a diary of what you did. It is a trace you can follow when something changes, and when safety depends on knowing exactly what is in a case.
What to record in a reloading log: start with traceability
The first job of any record is to let you reconstruct a round. If a box of ammunition behaves oddly, you should be able to say what went into it without guessing. A tidy log that cannot tell you which batch a round came from is decoration, and a messy one that can is doing its job.
Components and lot numbers
Write down the maker and product name of every component, and its lot number. Powder, primers, bullets and brass all vary from lot to lot, and a velocity shift that appears the day you open a new canister is only explicable if you recorded the old lot. Lot numbers cost ten seconds at the bench and are impossible to reconstruct later.
The load, exactly as you loaded it
Record the charge you actually weighed, the powder it was measured for, and where it came from. The source should be a current published manual or manufacturer page, and the log should name it, so that when published data is revised you can see which of your loads were built from the older figure. Never record a load you cannot source. The log documents what is in your cases; it does not replace the manual.
Brass history
For brass, what to record in a reloading log comes down to history, because it is the most re-used component. Record the headstamp, the lot if you know it, how many times the batch has been fired, whether and when you annealed it, and your trimmed length.
Measurements that describe the loaded round
Cartridge base to ogive, or CBTO, is the number most people log, and it only means something next to the measurement it came from. Record the jam length you measured in your own rifle, the jump you wanted and the CBTO you set. Take several jam readings and average them, and note the bullet, because a different bullet jams at a different length. See seating depth, jump and CBTO.
Shoulder bump and neck tension belong in the same record. Both are easy to change without noticing and both can move velocity spread, so log them or you cannot tell whether a good session came from the load or from a quiet change in sizing.
The rifle and its round count
Log which rifle and barrel the data came from, and its rounds fired at the time. A barrel at 200 rounds and the same barrel at 2,000 are different instruments. Record the setup too: optic, rest, any suppressor or muzzle device. When a group changes, the first question is always what changed, and a setup note is the fastest way to find out.
Conditions on the day
Record the date, range, distance, temperature and altitude, with wind in rough terms. Temperature moves velocity for some powders more than others, and altitude with temperature and pressure sets air density, which changes drop. The numbers are easier to handle with the explanation in density altitude for shooters. You only need enough to explain a bad day later.
Velocities, shot by shot
For velocities, what to record in a reloading log is simple: every shot, not just the average. An average hides the spread. With every shot stored you can recompute standard deviation and extreme spread later, exclude a bad reading with a note explaining why, and combine sessions. Be clear which kind of SD you quote; what a good SD looks like explains the convention and why short strings mislead.
Groups and where they landed
Record group size, mean radius (which uses every shot) and the point of impact relative to your aim point. A load can group tightly in the wrong place, and that offset says something about zero and conditions. Keep the target photo too, since you can re-measure it later. Measuring them the same way every time matters more than the method you pick.
Notes, and what to leave out
A free text note catches what structured fields miss: a feeding hiccup, a cleaning before the session, a pulled shot, a change of scope. If you take one rule on what to record in a reloading log, make it this: write what you would need to repeat or investigate the session, and skip opinions you cannot test.
Paper, spreadsheet or app
The format matters less than the discipline, but it decides what you can do with the data. Paper is robust and slow to search, a spreadsheet is flexible and easy to break, and an app can compute as you log. The answer to what to record in a reloading log stays the same in any format. There is a roundup in the best reloading log apps and a direct comparison in LoadNode versus a spreadsheet. Whatever you pick, back it up: a log you lose is a log you never had, and reloading data backup covers how. Handloading has always rewarded people who keep records, because the whole hobby rests on repeating something you did before.
How LoadNode handles it
The list of what to record in a reloading log is long, so LoadNode builds it into the workflow. A recipe holds your components with their lots and your brass prep, with neck tension and shoulder bump tracking in Pro. The load job wizard records your jam as several averaged readings, takes the jump you want and computes the loaded CBTO from your own jam. A session captures range, brass firings, distance, date, notes and optional weather autofill, with shots logged live and SD and ES updating. Groups are measured from a photo, and rounds fired at a step still count if the chronograph missed one. In Pro, the parts and setup list is copied into each session. Encrypted backup is free, and CSV export is Pro.
Handloading is an adult activity done at your own risk. LoadNode is a logbook and analysis tool: it never provides load data. Always develop loads from current published manufacturer data and work up safely.