Equipment report filenames: match the file to the record

A filename helps you find an equipment report PDF. Keep the report reference alongside it, identify the copy you received, and describe any comparison that was actually performed. Those details give the next reviewer something more precise than a file called final-v2.pdf.

What changes when you rename a PDF

Microsoft’s Get-FileHash documentation explains that filenames and extensions can change without altering file contents or their content hash. The reverse is possible too: an edited file can keep its old name. This describes a change to the name alone; it makes no promise about what an app does during export or Save As.

The suggested name in an HTTP download has a similarly limited role. RFC 6266 says its filename parameters help name the saved response and that the supplied name is advisory. That is a protocol rule for the download label, not a report identity check.

A suffix such as final, v2 or verified may be useful to the person organising a folder. Read it as their label. Establish the report revision or check from the relevant record and result, rather than from the suffix.

Tie the filename to the report reference

For a handoff, keep these details together:

• Filename received: the local file label, including any name you give it for filing.
• Report reference: the identifier visible in the report or its associated record. If you cannot find it, say that it is missing.
• Copy label: what the document says it is, such as a canonical report or a redacted public-share derivative. Leave an unclear copy type unresolved.
• Comparison note: what was compared, against which reference value and with what result. If no comparison was performed, record that plainly.

Here is a fictional example. A recipient gets final-v2.pdf; the document shows the demonstration reference DEMO-RETURN-A and identifies itself as a public-share copy. The handoff could read: “Local filename: final-v2.pdf. Report reference: DEMO-RETURN-A. Copy: public-share derivative. No file comparison performed.” The name’s v2 suffix adds no established revision to that note.

Where the file handoff also includes an equipment code, the asset-code and report-verification guide covers which record to inspect.

Compare the copy you actually received

NIST’s hash-function glossary describes a cryptographic hash as a mapping from an arbitrary-length input to a fixed-length bit string. For a file comparison, the input is the file you actually hash. Record the file, algorithm, reference value and observed result together. A name that says verified supplies none of those details.

Copy type matters when choosing the reference value. An AuditIt Redacted Share Report is a redacted public-share derivative, and its digest is labelled Public-share PDF SHA-256. Keep that label with the derivative; use the canonical report’s value when reviewing the canonical PDF. The redacted-share and canonical-report guide covers the distinction.

If the copy type or reference value is absent, ask the record holder to clarify it. Leave the comparison pending until you can describe the actual input and comparison. Changing the filename cannot fill that gap.

Using an AuditIt equipment record

AuditIt’s default public PDF-hash check compares the saved PDF hash metadata with the signed manifest. Re-reading stored PDF bytes is a separate check. Use the result that is actually shown and preserve its scope; the public-verification guide explains what those checks read.

Match the record to the workflow as well. Equipment checkout and return uses a before-and-after record; a damage report is a single-visit record. Renaming the damage-report file cannot supply a missing checkout stage. Start with the equipment checkout-and-return guide when reviewing a paired handover.

AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability. A person still reviews what the submitted condition evidence means.

To prepare an equipment condition record in AuditIt, create an account and choose the workflow that fits the visit or handover.

• Equipment rental
• PDF filenames
• Record review
• File comparison