Can the review leave the supplied signed document intact?
A reviewer needs to ask about a measurement in a supplier’s PDF. The proposed tool can put a text box on the page, and its output looks convenient. That does not yet establish that it meets the receiving organisation’s document requirement.
In this fictional equipment-record review, the requirement is to retain the exact supplied, digitally signed document and send a separate question about it. The organisation is not asking the reviewer to amend the supplier’s statement or sign a replacement. The capability comparison therefore begins with what must remain unchanged.
Establish the original and the review task
The supplied fixture is D-41, a four-page PDF with an electronic signature and a visible document reference. The isolated test arrangement has a configured signature-validation tool. Its initial check records the signature result, the signed revision and the validation conditions. A file hash separately records which bytes were received.
The reviewer’s question concerns the dimension labelled W on page three. They want the supplier to explain the basis of that figure. The review note must identify D-41 and that location without making the question appear to be part of the supplier’s original signed content.
D-42 is a second document with a similar page layout but a different reference. It provides a useful control: a note attached to the wrong document can look plausible even when nobody has changed the PDF itself.
Inspect what the proposed editor actually saves
In the inspected fictional editor, placing ordinary page text and saving produces a rewritten PDF, D-41-edit. It is a new byte sequence. The validator reports a modification affecting the signed content in that output; its result differs from the retained original’s result. The attractive text box has not preserved the required artifact.
This outcome belongs to the selected operation, document and validator configuration. Digital signature workflows have different permitted-change rules. It would be incorrect to infer that every possible annotation always has the same effect, or that a familiar-looking signature image proves a cryptographic signature remains intact.
Adobe’s guidance on comparing signed versions explains a way to inspect changes after signing. That is a useful question for the chosen tool, not a certificate that another editor’s output satisfies the organisation’s requirement.
The team keeps D-41-edit as labelled test evidence. It is neither substituted for D-41 nor sent as the supplier’s original. Clearing a signature or asking for an unsigned source would change the task and require a separate authorised decision.
Compare the actual alternatives
The review considers three paths. Editing the supplied file fails the exact-original requirement. Asking the supplier for a new edition may be appropriate if the supplier decides to revise its statement, but it does not help the reviewer ask the initial question. A separate review note can express that question while leaving the supplied artifact alone.
The existing document area supports storing an original file and a separately identified note. In this example, that supported arrangement is selected. It does not require a new PDF editing feature.
Note N-41 names D-41, its recorded file identity, page three and the W label, followed by the actual question. The note has its own author, date and revision. It is presented as the reviewer’s message, not as part of the signed supplier document. Access to both items follows the already agreed customer relationship.
Complete the receiving check
The recipient opens the original from the review package. Its bytes match the retained D-41 fixture. The configured validator performs its own check under the recorded test conditions and reports the same signature result. The hash comparison establishes file identity; it does not replace signature validation, establish the signer’s authority or prove the measurement is correct.
The recipient then finds N-41 and locates the intended dimension on page three. The supplier can answer the question without mistaking it for an approved correction to the original. A later clarification changes the note to N-41 revision two; the supplied PDF remains D-41.
| Review | Required result in this fixture |
|---|---|
| Original plus first note | Recipient identifies D-41 and the question about W on page three. |
| Revised note | Revision two is distinguishable; D-41 bytes and separately checked signature result remain unchanged. |
| Note offered with D-42 | Document-reference mismatch is identified; the note is not accepted as a question about D-42. |
| Unsigned control document | It is described as unsigned; matching bytes do not create a signature result. |
| Rewritten D-41-edit | It remains separate test evidence and does not replace the received original. |
State what the chosen capability establishes
The result is a usable review exchange with a preserved supplied artifact. It does not establish technical suitability, regulatory acceptance or the legal effect of a signature. Those questions belong to their appropriate reviewers.
Before choosing an editing product, ask which document the recipient must receive and what the proposed operation changes. Bring a permitted sample and the exact preservation requirement to project planning. A separate, well-linked question can be the complete first result when altering the supplied file would defeat the task.