Find a Private NDT Report Without Sharing Its Data

A request for the latest inspection report can be ambiguous. It may mean the last issued version, the newest working draft, the report for a particular examination date or the version previously sent to a recipient. Establish the purpose of retrieval before opening the library. Ask for the known number and revision when available, plus enough project context to distinguish similar reports. This avoids treating the first plausible match as the intended record.

Write a short retrieval target using information you already hold legitimately: the number, client, title or project reference and the required document state. Do not gather unrelated personal information to make the search more specific. A good target should help you recognize the result and decide what to do with it. It does not need to reproduce the report's complete scope or reveal sensitive observations in an informal request.

The NDT Connect digital reporting library shows saved records belonging to the authenticated account. A company name or client logo inside a report does not give that company or client access to the library. Confirm the account context before searching, particularly on a device used for different organizations or browser profiles. An empty result in the wrong account is not evidence that the report was deleted.

Use authorized account access rather than sharing passwords to simulate team permissions. The reporting tool is not a client portal with delegated access to every report bearing a client's name. If another authorized person needs a copy, the owner can retrieve the appropriate output and use the organization's established delivery process. Keep the decision about who may receive the content separate from the software's ability to display it to its owner.

You can search the saved library while a draft is open, but opening a result replaces the active workspace. If the current draft contains unsaved changes, the editor asks for confirmation before that replacement. Read the prompt and preserve any work you still need. Download an editable backup or complete the intended save before opening the retrieved report. Searching successfully does not automatically save the draft you were working on.

This matters when retrieval is an interruption during report preparation. A colleague may ask for an old PDF while you are halfway through new table entries. Finish a deliberate checkpoint first rather than assuming that the application will remember the interrupted state. Keep the working draft and the retrieval task distinguishable so that a later save does not accidentally apply new content to the wrong report identity.

Start with the most specific reliable identifier you have. A report number is usually more discriminating than a common client name or a broad title such as ultrasonic inspection. The visible search field supports report number, title and client; saved project references are also searchable. Enter the reference carefully, retaining meaningful punctuation and characters rather than rewriting it from memory. A transcription error can produce no results even when the intended record exists.

If the exact reference is uncertain, try a distinctive portion and inspect the resulting candidates. Do not assume that the search understands synonyms, resolves renamed clients or searches every observation in a result table. It is a practical text search over selected report fields. A component identifier stored only in a table cell may therefore require you to locate the report through its title, client or project context first.

The library submits its search text within the authenticated search request rather than adding the client name or title to the page's query address. This avoids making those search terms part of a copied page link. It does not turn the browser address into a shareable link to the matching private reports. Another person opening the public tool page will still need their own authorized account context and will not inherit your library results.

Do not manually append client names, report titles or observations to the address bar to create a convenient bookmark. Use your permitted record index or a minimal internal reference instead. Privacy also depends on what appears on screen, in downloaded files and in messages you send. The search design limits one route of accidental disclosure; it is not a claim that every surrounding device, communication channel or user action is automatically protected.

Each library result shows the tracked number, revision, status, title, client and method. Read those fields together. A familiar number can appear on several revisions, and a similar title can appear on entirely different reports. Check whether the requested state is draft or issued before selecting Open report. An issued revision may be the required delivery copy even when a more recent draft is still being prepared.

The library's ordering should help you find recently updated records, but list position is not a substitute for identity. A draft saved today can appear ahead of an older issued version that remains the current approved-for-delivery document under your project process. Use the actual revision and status, then inspect the report content where necessary. The software does not decide which version your recipient is authorized or expected to use.

A broad client search can return more results than fit on one page. Use the report-list pagination to inspect the remaining matches rather than assuming that the first page is the entire account history. Keep the retrieval target in mind as you move between pages. If the results are too broad to review confidently, refine the search with a more distinctive report or project reference that actually appears in the saved fields.

When you change the search, submit it deliberately and check the new result count and page state. Avoid treating a page left open from an earlier query as a current answer to a different request. A simple note of the search used and the candidate identity can help during a longer retrieval exercise. There is no need to copy the full private result list into an external spreadsheet merely to remember one report.

If no record matches, check spelling, punctuation, account identity and the search field's scope. Clear the search to inspect your broader saved list when appropriate. Consider whether the work was ever saved to the account, or whether it existed only as a guest draft, downloaded PDF or editable backup. A local backup is not automatically listed in the account library, and a guest PDF does not establish that a tracked record was created.

Do not immediately rebuild and save a duplicate report to compensate for an unsuccessful search. Locate the original evidence and determine whether there is a saved identity to recover. If only an editable backup exists, restoration creates a new unsaved draft and a later first save will assign a new number. Keep that outcome explicit rather than presenting the recreated content as the missing original record.

After opening a candidate, compare the inspection date, project reference, scope, procedure, client and method with the request. Check the result tables and conclusion where they are needed to distinguish otherwise similar records. A matching title does not prove that the report covers the correct components or examination stage. Confirm the relationship to any external data manifest or attachment references before deciding that the retrieval is complete.

Avoid making incidental edits while you are only checking identity. An unnecessary change creates an unsaved workspace that may differ from the retained version and complicates the next export decision. If you discover a genuine error, record it and use the appropriate draft-edit or issued-revision workflow. Retrieval and correction can be connected tasks, but they should not become indistinguishable simply because the report is now open.

In a fictional exercise, a client asks for the last issued report for an invented project reference. The owner's search returns revision zero marked issued and revision one marked draft. The draft was updated more recently, but its new limitation is still under review. The owner opens the issued version, confirms the inspection date and scope against the request and downloads the intended issued PDF rather than assuming the newest row is the delivery copy.

The owner then notices a separate request to review the working limitation. That request is handled with an explicitly labeled draft output through the agreed review channel. The two recipients and purposes are kept distinct. This example demonstrates retrieval decisions, not a universal rule that an earlier issued report remains suitable after every proposed change. If the change affects continued use of the earlier report, the responsible project decision must address that separately.

A PDF is a readable report output. An editable backup preserves the report content for restoration as a new draft and can include private fields and logos. These are different handoffs. Do not send a backup merely because it is available when the recipient only needs a readable issued copy. Equally, do not assume that a PDF alone will restore editable tables if the purpose is to continue preparation after losing the open workspace.

Check the current editing state before exporting. A PDF can reflect local unsaved changes, and a modified workspace associated with an issued identity is treated as draft output. If you need the exact retained issued version, open that saved version and avoid altering it before export. If you need the current local draft, label and handle it accordingly. The output choice should follow the document's purpose and state rather than a habit of clicking the nearest download button.

CISA's Cyber Essentials access guidance recommends restricting access to necessary information. Apply that narrow principle when deciding what to distribute from a retrieved report. Confirm the recipient, the purpose and the permitted content before sending a file. A report can contain more than measurements: contact details, location references, logos and narrative may also require deliberate handling.

Do not alter a retained issued record simply to produce an informal extract without explaining the relationship. If the project permits an extract or redacted distribution copy, follow its agreed process and identify what the copy represents. The reporting workspace does not provide automatic recipient permissions or a dedicated redaction approval workflow. Keep the complete retained record and the intentionally prepared distribution output distinguishable.

Sharing the public reporting-tool address can help someone find the tool, but it does not deliver a saved report or grant access to your account. Do not tell a client that the link opens their private record when no such sharing feature is present. Retrieve and deliver the appropriate file through your authorized channel, or use an existing organizational system that provides the permissions and records your project requires.

Similarly, a screenshot of the library is usually a poor substitute for the requested report. It may reveal unrelated clients and still omit the actual document content. If you need help resolving a retrieval problem, describe the behavior with minimal identifiers and avoid exposing the full private list. Keep support context separate from the report evidence itself, and provide detailed content only through a suitable authorized process when it is actually necessary.

Open the downloaded PDF and check the number, revision, status, client and scope inside the file. Confirm that the pages and tables needed for the request are present and readable. Do not rely solely on the filename or on the fact that the browser reported a successful download. A downloads folder can contain several similarly named copies from earlier proofing sessions, and selecting the wrong one can undo an otherwise careful retrieval process.

Keep the final file in the project's approved location and record the delivery identity through the normal handoff process. The reporting application does not automatically email the client, synchronize a third-party document repository or withdraw earlier attachments. Those actions remain part of your distribution workflow. A concise record of what was sent, to whom and for which purpose makes later retrieval requests easier to answer accurately.

For recurring work, maintain a permitted index connecting the tracked report number and revision to your project reference and the authorized location of supporting data. Avoid copying all report observations into that index when references are sufficient. The saved reporting library and an equipment record can contain useful identifiers, but the tools do not automatically join those records or validate their relationship. Check the references you enter rather than assuming a shared serial number creates a verified connection.

Use the worksheet below to standardize the final retrieval check. It should make the requested state, selected identity, content match and chosen output explicit. That is enough to support a clear handoff without turning a simple search into a second uncontrolled report archive. The successful outcome is the correct retained version delivered for the intended purpose, with the private workspace and unrelated records kept out of the distribution.