An AFT total can look plausible even when one entry is wrong. Before exporting a scorecard, work back from the raw results and the Soldier’s details. A short review is easier than explaining a corrected file after it has already been shared.
Read a time aloud before transcribing it
A colon and a decimal point describe different time formats. Two minutes and thirty seconds is 2:30 in minutes:seconds, but 2.5 in decimal minutes. A value written as 2.30 decimal minutes equals two minutes and eighteen seconds. Copying the digits without the unit can therefore change the result even when the entry looks familiar.
Use the field labels in your installed app and the original record. If it asks for separate minutes and seconds, enter each component in its own field; do not put a decimal-minute calculation into a seconds box. If a source uses decimal minutes, confirm that interpretation before converting. The arithmetic conversion is minutes plus seconds divided by 60; it is not an official event-score calculation.
For a fictional transcription check, a source says 3 minutes 45 seconds. Read that aloud, record 3:45 where minutes:seconds is expected, and compare the exported result with the same source. The equivalent decimal value is 3.75 minutes, not 3.45. These examples are format checks and do not assign points or establish a passing result.
If the original notation is ambiguous, ask the person responsible for the original record. Do not infer the intended format from whichever entry yields a plausible total. After resolving it, recheck the event score using the applicable current Army standard and open the exported file again.
1. Confirm the Soldier and test date
Check the name and identifying fields against the record you intend to complete. Make sure the test date is the actual date of the event. If you are preparing several records, review each one separately rather than assuming the previous Soldier’s settings carried over correctly.
Keep personally identifying information within your unit’s approved handling process. A sample file used for practice should contain clearly fictional data.
2. Compare raw results with the original record
Read back each event result before focusing on the converted score. Check weight units and repetitions carefully. For timed events, confirm that a value represents minutes and seconds in the format the app expects. A transposed digit can still produce a believable number.
For example, 2:05 and 2:50 are different times even though they contain the same digits. This hypothetical example illustrates an entry check, not an event-specific scoring rule.
3. Verify the applicable scoring criteria
Use the current official Army Fitness Test resources to confirm the relevant tables and standard. Do not reuse an old ACFT worksheet or infer the applicable requirement solely from the total. Profile situations and other special circumstances should be checked against current policy and your unit’s guidance.
The Army’s AFT page links official scoring resources. Treat those as the authority when a saved sheet, an app display or someone’s recollection disagrees.
4. Review both the event scores and the total
A total is a summary; it is not a substitute for reviewing the individual event entries and applicable requirements. If something looks unusual, return to the raw result and settings before changing a number simply to make the total look right.
For unit work, have the original results available during the review. If a result is uncertain, resolve the uncertainty with the responsible person rather than guessing.
5. Open the exported file
After exporting from AFT Ready, open the actual file you plan to share. Confirm the identity, date, all event rows and the total. Check that the page is readable and that any fields your workflow requires are completed through the appropriate process. Keep the verified version distinct from drafts.
For the app’s export steps, see the DA Form 705 guide. For scoring details, use the AFT scoring guide alongside the current official Army materials. A calculator helps with preparation; it does not replace the responsible officials’ review of the record.
If you discover an error after sharing
Return to the original recorded result before editing the calculator. Identify the exact field that was wrong and verify its replacement with the responsible person. Do not change an adjacent event just to reproduce an expected total.
In a hypothetical transcription error, a timed result was entered as 2:50 when the original record says 2:05. Correct that field, recheck the resulting event score and total against the applicable current standard, and export a fresh file. This example demonstrates transcription only; it does not assign a score to either time.
Open the replacement file and compare it with the original record again. Clearly distinguish the corrected copy from the earlier draft in your approved record-handling workflow. If someone already received the earlier file, identify which copy replaces it rather than assuming a new export updates files they already downloaded.
Keep a short correction note
A useful note records the affected field, the verified source and the date of the correction. Keep personal information in the unit’s approved system, not a public message or sample screenshot. An app export is a file; it does not by itself amend an official record or notify everyone who received an older copy. Follow the responsible officials’ process for the actual record.
For a batch, reconcile the files with the roster
Checking one good export does not validate the rest of a batch. Use your unit’s approved roster and handling process to reconcile the expected records with the actual files. Count the records, then check identity and test date on each file before reviewing the event entries. Two files with different filenames can still contain the same person’s record.
For a fictional three-person practice batch, expect three distinct records. If you find two copies of Sample Soldier A and one of Sample Soldier C, the file count is correct but Sample Soldier B is missing. A count check and an identity check catch different problems. Use fictional details for demonstrations; do not put a real roster into a public tutorial or shared screenshot.
Review the exported document itself, including later pages if present, at a readable size. Look for blank event fields, clipped text, and a record that carries over an earlier test date. Compare against the original results; do not fill an empty field from memory. If printing is part of your authorized workflow, check the print preview too.
Keep a simple checked/not-yet-checked list inside the approved process. Resolve missing or duplicate records before distribution, and identify the final version clearly. This is a suggested file-review method, not an official validation or signature process. The responsible officials still determine how the scorecards become part of the official record.