Move a Guest NDT Draft into Your Saved Report Library

A guest can prepare report fields, import supported template tables, add inspection entries and download a draft PDF. That is useful for trying the workflow or preparing an initial document without first organizing an account. The open workspace is still a working draft in the browser tab. It should not be treated as a privately saved account record simply because it has a title, a client name or a professional-looking PDF. Before leaving the page, understand which copies of the work actually exist and whether you can continue editing them if the tab is closed.

The free digital NDT reporting tool provides an editable backup action as well as PDF export. Use that distinction when deciding to save your guest work in an account. A PDF preserves a readable output for review, while the JSON backup supports restoration of editable report content. Neither action is the same as saving a tracked record to the account library. Make a deliberate transition plan: preserve the current content, complete the account requirements, return to the original workspace and confirm a successful first save before relying on the library.

A saved report belongs to the authenticated owner account. Decide which legitimate account should hold the record before the first save, particularly if the browser is used for more than one organization or purpose. A company name typed into the report does not choose the account owner, and a client logo does not create client access. Keep document identity and account ownership as separate questions. If you are preparing reports for an employer, follow its agreed record process rather than assuming that a personal account automatically becomes a shared company reporting system.

The tool should not be described as offering team permissions or automatic transfers between owners. Avoid sharing login credentials to simulate a multiuser document workflow. Instead, establish who will maintain the saved record and how other authorized people will receive the intended outputs through your existing communication process. This decision can be simple for an independent inspector using one account, but it still matters. The person who saves should understand that the library contains private report details and that exporting a file creates a separate copy requiring appropriate handling.

Download an editable backup while the guest draft is still open and recognizable. Confirm that the file download completed and that you can locate it. If useful, also download a draft PDF so you have a readable reference for comparing the eventual saved report. Give the files enough external context to distinguish them from previous downloads without adding unnecessary sensitive information to their names. The content itself can include client details and logos, so store it through the record-handling practices that apply to the project rather than leaving it indefinitely in an uncontrolled shared location.

CISA's Cyber Essentials backup guidance recommends testing recovery from backups. For this specific transition, the practical question is narrow: if sign-in takes you away from the open draft, do you have a usable editable copy? A browser warning about unsaved changes is helpful but cannot replace that copy. Do not depend on the browser restoring a crashed tab or preserving every unsaved value after navigation. Establish the checkpoint before changing the session, not after discovering that the original workspace is no longer available.

When a save requires authentication or verification, the editor presents account options and retains the current entries. The offered sign-in and registration links open in another tab so the report workspace can remain open. Follow that separation deliberately. Keep the original report tab identifiable, complete the account task in the new tab and return to the tab containing the actual draft. A redirect that opens a fresh reporting page after sign-in does not mean the old tab's contents have automatically moved into that new page. The original workspace remains the place to inspect and save your existing work. Keep the account and report tabs in the intended browser profile. A sign-in completed in another browser or a separate private session should not be assumed to authenticate the original draft tab.

If the browser or device makes multiple tabs confusing, stop and compare the visible report contents before continuing. The correct tab should contain the known client, project and tables from the guest draft. A blank starter report in another tab is not evidence that the work was lost or successfully transferred. Avoid entering the same report again while the original remains available, because that can lead to two separate saved drafts later. Use the backup as a recovery option when needed, but first establish which open workspace actually holds the current content.

Signing in establishes the account session, while saving reports also requires a verified account. These are distinct steps. If the interface directs you to verification settings, complete the actual process and then return to the original draft. An email address typed into the company contact field does not verify the account, and a verification message in an inbox is not necessarily proof that its required confirmation step has been completed. Read the account's current status and the application's save response rather than inferring readiness from a previously received email or an open settings page.

Keep the technical purpose of verification in perspective. It enables the account-saving workflow; it does not certify the inspecting company, validate the inspector's qualifications or approve the report's conclusions. Similarly, a certificate record elsewhere in the account does not automatically populate or approve the reporting workspace. Enter and review the report's personnel evidence deliberately. This distinction helps prevent a successful sign-in or verification from being mistaken for a completed technical review. Account readiness and examination readiness belong to different parts of the workflow, even when the same person performs both administrative and reporting tasks.

Return to the original tab and check the report title, method, inspection date and numbering pattern before the first tracked save. Date tokens use the entered inspection date when present; otherwise they use the UTC date at save time. The number assigned at first save remains stable through later draft edits. That makes this a useful point to correct an accidental blank date or a carried-over method selection. Do not change the facts merely to obtain a preferred identifier. Enter the actual information and choose a pattern whose meaning is clear for your record process.

The numbering preview uses an example sequence and is not a reserved report number. Wait for the successful save confirmation to learn the actual assigned identity. Keep any external record list or client reference draft uncommitted until that point. A guest PDF downloaded earlier may show an unassigned draft identity, so it should not be confused with a later PDF from the tracked record. Both can represent the same working content at different stages, but they carry different document context. After saving, generate the intended current output and compare its number and draft status with the application.

A successful save should be followed by a focused content check. Confirm the assigned number and revision, then inspect the client, project, technical references, table titles and a representative set of known entries while checking the complete expected table and row inventory. The goal is to establish that the intended guest draft was saved, not a blank tab or an older restored copy. Where the content was particularly important or complex, perform the fuller reconciliation appropriate to the project. The presence of a report in the library does not by itself establish that every expected field is present.

The editor distinguishes unsaved changes from a workspace that matches its saved version. Use that message to understand whether a subsequent edit still needs saving. A PDF export can include current local edits even when those edits have not yet been retained in the account. That is useful for proofing, but it means the PDF and saved library record can temporarily differ. Before closing the workspace, decide which version you intend to retain and confirm the relevant save. Do not use the existence of a newly downloaded PDF as a substitute for checking that the latest account save succeeded.

Consider a fictional inspector who prepares a practice report with two tables and twelve invented observations while signed out. The inspector downloads an editable backup and a draft PDF, then attempts to save. The editor asks for a verified account and retains the entered content. The inspector opens the offered sign-in link in a new tab, completes sign-in and confirms verification status. A reporting page appears in that tab with a blank starter. Instead of rebuilding the practice report there, the inspector returns to the original tab and checks the two tables and known project details.

The inspector reviews the inspection date and pattern, saves the original workspace and receives a tracked number. The saved-library entry is checked against the practice report's title, method and draft status. A new PDF is then downloaded with the assigned identity and compared with the earlier unassigned draft. Nothing in this example represents a real examination or an automatic qualification decision. It demonstrates a state transition: the same understood editable content moves from an unsaved guest workspace into a private tracked draft, while the preparer retains a recovery copy and avoids accidentally saving the wrong tab.

If a save fails, read the actual message and keep the draft open. Authentication and verification errors call for account action; invalid content messages call for correction of the described fields or limits. Repeatedly refreshing the page does not resolve either problem and can put unsaved work at risk. Preserve a current editable backup if one is not already available. Then make the narrow correction and retry from the understood workspace. Do not create a new account or a duplicate report simply because the first attempt did not immediately produce the expected confirmation.

An interrupted response can be different from a confirmed failed creation. The application has recovery behavior for an earlier save and can retain current edits while identifying the previously created record. Follow its messages, inspect the recovered number and verify whether further draft changes still need saving. Do not assume that every retry should allocate a fresh report identity. If the situation remains unclear, keep the backup and record the visible problem without placing client report content into a public support message. A useful problem description identifies the action and error while minimizing disclosure of the actual inspection record.

Once the intended draft has been saved, use the private saved-report library to locate it. Search by the supported fields, then confirm number, title, client, method, revision and status before opening. If another report has unsaved changes in the current workspace, the application asks before replacing that open work. Preserve a backup or save the work you intend to keep before confirming. Opening a library record is a content replacement in the workspace, not a merge between two drafts. Treat it as a deliberate choice of which record you are now editing.

A successful reopen is a useful check that the account workflow retained the report, but it does not mean every external artifact is also stored. Keep original Excel or Word templates and supporting examination evidence in the approved project record process. The report can carry references and entered content; it is not a general repository for every native inspection file. Likewise, a private library link is not a way to grant a client access to your account. Choose a deliberate export and authorized delivery method when someone else needs the report, and confirm the exact version being provided.

After saving and checking the record, decide whether the next action is further draft editing, responsible review or a deliberate export. Saving a report is not the same as issuing it. An issued version is preserved, and later changes use the revision workflow. Do not rush through issue merely because the account transition succeeded or because the document now has a tracked number. Complete the actual examination information, resolve technical questions and follow the project's review responsibilities. The software can require certain fields, but the truth and adequacy of their contents remain the user's responsibility.

Keep a short transition note when it helps your work: which account holds the record, its assigned number and revision, where the editable backup is kept and which PDF was last reviewed. Avoid maintaining a second uncontrolled narrative of all inspection data just to prove that saving occurred. The note should direct you to the correct records, not duplicate them unnecessarily. With that information clear, the guest-to-account step becomes predictable: preserve the content, establish the right session, save the intended workspace, verify its identity and continue the report's actual review process.