Document investigations3 min readField note 12

What does “uninspected” mean on an AI file upload?

Follow a protected PDF selected on Claude. Compare its receipt with two readable PDFs, then write a case note that a data owner can act on.

Document search finds Vendor_contract_protected.pdf on Morgan Reed’s device, with Claude as the destination.
The idea in focus

The fictional Northstar document search returns one file selection and zero related HTTP responses for this contract.

Field note / 12
In brief

An unreadable file belongs in the coverage report and may still need a data owner’s review.

  • Record what prevented inspection when the receipt gives a reason.
  • Count unreadable files separately from completed inspections.
  • Keep business classification and transfer outcome as separate questions.
In this article

Find the contract version in question#

A procurement manager asks whether a supplier contract went into Claude. In the public demo, open Document evidence and search Vendor_contract_protected.pdf. The receipt places a 405 KB file on Morgan Reed’s device, NS-WIN-042, at 15:40 UTC on November 17. Give the owner these details so they can distinguish the signed contract from another draft with the same name.

The contract receipt lists Claude, file selected, NS-WIN-042, 405 KB, unknown sensitivity and uninspected content.
The file’s size, destination and device are available even though its contents could not be read.

Read why inspection stopped#

Open the evidence trail. This example explicitly says that encrypted content was unavailable. The filename alone would have been a poor reason to assume encryption. The browser recorded a selection on Claude, while submission and provider retention remain unknown. Keep the reason for missing content and the transfer question in separate fields.

The evidence trail records a browser selection, encrypted content unavailable and one sample monitoring policy.
Here the receipt gives a reason for the gap. It also describes exactly which gesture the browser saw.

Compare a readable PDF with zero findings#

Search Product_brief.pdf and open its receipt. This file passed through inspection and none of the enabled detectors returned a finding. The protected contract never reached that point. If both files go into your report as “zero sensitive documents,” the reader loses the distinction. For these two examples, report one inspected file and one file with unknown contents.

The Product_brief.pdf classification panel reports no detector findings in the sample.
A different fictional Claude selection, Product_brief.pdf, completed inspection and returned zero matches.

Check what a positive result would look like#

A third lookup, Customer_summary.pdf, returns six email-address matches. If these three distinct PDFs were your entire pilot sample, two were inspected, one of those had a finding and one PDF remained unreadable. That gives Procurement a meaningful denominator. A count of six matches alone cannot establish how many people or documents were involved.

Customer_summary.pdf has a local email-address finding with six matches and a redacted example.
Six email-address matches belong to Customer_summary.pdf. They say nothing about the contents of the supplier contract.

Give the contract its own review#

Return to the protected PDF and choose Start a case with this event. Call it “Legal review of protected vendor contract.” Ask the data owner to check the classification of that version in the approved contract repository. If the business question is whether an attachment reached a particular conversation, record who can verify that destination and what evidence they have.

An open Legal review case contains the single protected PDF selection on Claude.
Only the contract receipt belongs in this case. The other PDFs served as comparison examples.

Write down the decision that is still open#

A handoff can fit in three sentences. “Legal to confirm the classification of this contract version. Claude file selection observed. Contents unavailable and submission unknown.” If Legal later confirms the document was restricted, add the source and date of that determination. The original endpoint receipt still describes the same selection and the same inspection gap.

A sample review note asks Legal to confirm classification and records that submission is unknown.
The example note gives Legal a specific task without reproducing the contract.
Read the primary sources

Sources & further reading

  1. Explore document evidence in the public demo
  2. Investigate a filename across AI tools
  3. Understand file inspection limits
← Back to all articlesBack to top ↑
A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope
More supported tools

This creates a planning document. It does not enroll devices or submit a request.