The transmission record is the part of electronic fax that a machine never really gave you. A confirmation slip proved something happened to whoever was standing there. A record proves it to somebody asking two years later, which is a different and more useful thing.
What a transmission record should contain
- An identity for the transmission, so it can be referred to unambiguously.
- Who or what submitted it: a named account or a named system, not simply the organization.
- The destination as dialed, which is not always the destination as typed.
- Timestamps for submission and for each delivery attempt.
- The outcome, and where it failed, a reason specific enough to act on.
- Page count and the document reference, so the record can be tied to what was sent.
- Your own reference, where a system submitted it, tying the fax to the case or record that caused it.
The last one is the difference between a log and an audit trail. Without it you can prove a fax was sent; with it you can prove which obligation it discharged.
Why the reason code matters more than the status
A record that says "failed" has thrown away the information that determines what to do. Busy, no answer, answered by a voice line, and rejected before dialing are four different events with four different responses, and only one of them wants a person.
When you evaluate a service, ask to see a failed transmission's record rather than a successful one. Success looks the same everywhere; the quality of a system is visible in how precisely it describes what went wrong.
Retention attaches to the record, not to the fax
This is the part that catches organizations out, and it is worth separating carefully.
The document has a retention period determined by what it is: a health record, a student record, a contract, a purchase order. The transmission record has one determined by what it evidences, which may be different and is often longer, because the evidence that something was sent on a particular date can outlive the interest in the thing sent.
Neither period is set by the fax service. Both are set by your records schedule, and the service's retention setting has to be checked against it in both directions. Retention shorter than your obligation loses the record. Retention longer than a disposal requirement keeps something you were obliged to destroy, and that is equally a finding.
Where the obligation comes from
Different rules reach the same conclusion by different routes. For organizations handling protected health information, 45 CFR 164.312 makes audit controls a standard in its own right: mechanisms that record and examine activity in systems containing that information. NIST SP 800-53's Audit and Accountability family sets out the same idea in more detail for federal systems and for anyone who adopts it as a framework.
For public bodies the driver is usually records law rather than security. In Texas, retention periods for local government records are set by schedules published by the Texas State Library and Archives Commission, organized by record type rather than by the medium the record arrived on. A fax does not have a shorter life because it was a fax.
The common thread is that all of these expect the organization holding the records to have decided and documented an answer. None of them is satisfied by a supplier's retention default.
Who reads it, and when
Audit trails are written continuously and read rarely, which is why their quality is usually discovered at the worst moment. Three occasions account for nearly all reading.
- A dispute. A partner organization says a document never arrived.
- An incident. Something reached a destination it should not have, and the question is what else went to that number.
- A request or an audit, where the record itself is what has been asked for.
Each of those is a query, not a browse. The test worth applying to a service is whether you can answer "everything sent to this number in this period" and "everything sent by this account" without asking the supplier to run it for you.
Exporting it
A record you cannot get out is a record you hold on sufferance. Establish before you commit whether the transmission history can be exported, in what format, and whether the export includes the reason codes or flattens them.
This matters most at the end of a relationship, which is exactly when goodwill is least available and when the retention obligation does not lapse. It is a contract question, and it is much easier to settle while a supplier is competing for the work than afterwards.
The record is not the document
One distinction is worth holding onto, because conflating the two produces awkward conversations later. The transmission record says a document was sent; it is not the document. Some services retain both, some retain the record for much longer than the content, and the two settings are frequently independent.
Decide deliberately which you need. Evidence that a submission was made on a date is often all an obligation requires, and retaining page images for years afterwards may create exposure rather than assurance.
Where to go next
For the compliance framing this sits inside, see electronic fax and HIPAA compliance. For the criteria to judge a service on more broadly, what to look for in electronic fax. To discuss retention against your own schedule, tell us what you are working with, or see the feature overview.
Sources
- 45 CFR 164.312, Technical safeguards, Government Publishing Office. Audit controls as a standard, alongside integrity and transmission security.
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations. The Audit and Accountability control family.
- Texas State Library and Archives Commission, local government records retention schedules. Retention by record type, independent of medium.