Recording a reading
How to record a counter value, why the day matters, and what happens when a reading reaches a limit
What a reading is
A reading is the value of a counter on a piece of equipment on a day.
Record the whole number, not the change since last time. If a wing read 408 before today and flew four times, record 412.
KitNDocs calls the thing being counted a tracking parameter. Flights, jumps, cycles and airtime hours are examples.
The newest reading is the current value. KitNDocs does not estimate missing readings.
The Logbook tab shows current values. The History tab shows every reading recorded.
Record one reading
Open the form
Open the equipment record. Open the Logbook tab and press Record a reading.
Choose the counter
Choose what this counts.
Enter the reading
Type the reading and check Taken on.
Save it
Press Record reading.
Choose Something else… if the counter is not listed.
Use the day the reading was taken. A reading from March dated today makes limits look further away than they are.
You cannot use a future date.
Record a day across equipment
Use Record readings when one day's use reached more than one piece of equipment.
Open the bulk form
Open Equipment and press Record readings.
Enter the day's use
Choose what this counts. Type how many on the day and check Taken on.
Choose the equipment
Tick the equipment the day reached. Check each new total.
Save the readings
Press Record readings.
KitNDocs writes one reading to each ticked piece of equipment. If one cannot be written, none are written.
Ticking a rig can also tick installed equipment that counts the same word. Untick anything the day did not reach.
Equipment that does not count the chosen word cannot be ticked. Record its first reading from its own Logbook tab.
From a rig's Logbook tab, Record across what is installed opens the same screen with the rig and matching installed equipment ticked.
When a reading reaches a limit
A deferred defect can use a reading as its limit. For example, the equipment can stay in service until 1,250 jumps.
When the reading reaches that number, the equipment goes out of service. KitNDocs tells you beside the field before you save.
The warning does not stop you saving. A reading records what happened, so saving it is still correct.
If the defect has an early-warning margin, KitNDocs can also tell you how many units are left.
The bulk readings screen does not show these warnings. It still writes the readings, and equipment that reaches a limit still goes out of service.
A reading dated before the newest reading does not change the current value. It does not trigger a limit warning.
Date limits are different. They reach the morning briefing, not the reading form.
Correct a reading
Record the correct value as a new reading. Add a note that explains the mistake.
Nothing is edited or deleted. The old reading stays in History.
What a reading does not do
A reading does not say what caused the count. KitNDocs holds no per-flight or per-jump ledger.
A reading does not reach other equipment on its own. A count on a container is not a count on the reserve inside it, unless you record both.
A reading does not estimate a rate. KitNDocs does not turn 48 jumps left into a date.
A reading does not put equipment back into service. It is an observation, not a certificate.
Updated 30 Aug 2026.