Give each document version a stable label and verify every reported change against both sources. Do not accept a difference report that cannot show which wording belongs to which version.
Establish identity before asking about changes
Perplexity’s guidance describes document-based tasks such as summarising, analysing code and translating. The supplied evidence does not establish a native version-comparison feature. The following protocol is editorial advice for organising a comparison, however you produce the draft analysis.
For each permitted document, record a label, filename, visible version date, page count and distinguishing heading. Use neutral labels such as V1 and V2. Do not assume that a filename containing “final” proves approval or that the later upload is the newer document.
Write a two-sided comparison brief
Define the scope precisely: “Compare eligibility, deadlines and required documents. For every proposed change, provide the V1 wording and locator, the V2 wording and locator, and a short explanation.”
Use four difference categories:
- Added: absent from the relevant V1 section and present in V2.
- Removed: present in V1 and absent from the relevant V2 section.
- Modified: corresponding wording changes meaning or detail.
- Unresolved: a source section is missing, unclear or not confidently matched.
Keep formatting-only changes separate. Moving a paragraph is not automatically a change in policy, and failing to locate a sentence is not proof it was deleted.
Hypothetical version-verification log
Imagine two synthetic workshop notices for a Bengaluru student society. V1 is dated 3 August and has two pages. V2 is dated 8 August and has three pages.
The inputs include:
- V1 deadline: “Submit by 20 August.”
- V2 deadline: “Submit by 22 August.”
- V1 attendance: “Recommended.”
- V2 attendance: “Required for certificate eligibility.”
Log the deadline as modified only after checking both passages. Log attendance as a substantive change, preserving the certificate condition rather than reporting “attendance is always compulsory”.
If V2 page three is unavailable, label any conclusion about removed appendix requirements unresolved. Evaluate the log by checking that every accepted change has two source references and an explanation proportionate to the wording.
Stop when provenance breaks
If labels switch midway, dates conflict or a version is incomplete, stop the comparison. Repair the source set and repeat affected checks before circulating conclusions. Preserve separate originals and a dated review note.
For access research, check the AI tools catalog, confirm access format and save terms before buying. Marketplace account/code/token offers do not prove official subscription equivalence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Perplexity’s upload guidance establishes examples of document tasks, not a comparison feature. Version labelling, difference categories and the fictional notices are editorial guidance.