Alpha Covenant Holdings · Government Forms Register · https://alphacovenantholdings.com/forms/osha-300a

OSHA 300A · 29 CFR 1904

OSHA Form 300A — Summary of Work-Related Injuries and Illnesses

Injury and illness recordkeeping and electronic submission (29 CFR 1904) — the steps as written

#StepWhoWhenRecordCitation
1Record each recordable work-related injury or illness on the OSHA 300 Log within seven calendar days.employer (establishment)within 7 days of learning of the caseOSHA 300 Log and 301 Incident Report29 CFR 1904.29(b)(3)
2Complete, certify and post the 300A annual summary.employer; certified by a company executivepost February 1 – April 30 for the prior yearOSHA Form 300A29 CFR 1904.32
3 ●Submit 300A data (and, for covered establishments, 300/301 data) electronically to the Injury Tracking Application; OSHA publishes establishment-level 300A data.establishments of 250+ employees, or 20–249 in designated industriesby March 2ITA submission; OSHA's published ITA dataset by year29 CFR 1904.41
4 ●OSHA inspects, cites and records the enforcement history of the establishment.OSHAon inspectionOSHA inspection and citation record, dated29 U.S.C. 657; 29 CFR 1903

● a dated receipt is the record at this step.

Keeping the file

#StepRecordWhere
F1At each ● step, pull the dated receipt under the party's exact name or UEI and file its receipt id with the transaction record.receipt id (r_…) on the procurement, subaward or payment recordhttps://alphacovenantholdings.com/screening
F2Anchor your own document for the step — the signed check, the certification, the memo — by its SHA-256 beside the receipt. The document stays with you; only its hash is logged.anchor id (a_…) in the same log as the receipthttps://alphacovenantholdings.com/r/{receipt_id} → Anchor
F3Note the retention line the file sits under and, once the trigger date is known, the date the period runs to.the rule's own words and date (FAR 4.703/4.705 or 2 CFR 200.334)https://alphacovenantholdings.com/api/retention/rules
F4At period end, keep the signed file statement for the organization: every receipt and anchor, the sources read and which did not answer, the log head they chain to.one signed page per UEI; its hash and signature verify without Alpha Covenanthttps://alphacovenantholdings.com/file/{uei}

How the dated records are kept, not what they prove. A receipt shows what the official file printed on the read date; an anchor shows a document existed in that exact form on that date; the file statement lists what the file holds. None of them states that a step was done correctly or that the organization is eligible or compliant.

How the auditor tests it

The steps as the regulation and the auditor's program state them, each with its citation. Nothing here is advice or a determination; the agency's text controls. A dated receipt is the record at the marked steps — it shows what the official file printed on the read date, not that the step was done correctly.

Not legal advice, not a compliance determination, not a statement that any filer's certification is true or false. Form numbers and line numbers are as published on the date noted and may be renumbered by their agencies; the official page controls. Audit findings quoted are the auditor's words as filed at the Federal Audit Clearinghouse, cited by report id; they describe a documentation gap, not a conclusion about any party.