Guida

From signing up to a report in your client's hands takes an afternoon: set up the company, bring your own report form or take one of ours, add a client and a project, write and issue a report, and invite the client to the portal where it lands. This topic walks that path and says where each setting is.

Everything in NDT Intact hangs on one line: a client has projects, a project inspects assets, an asset has welds and TMLs, and reports, requests and files belong to a project and, where it matters, to one of its assets. Once you know that line, every page is a step along it, and the sidebar, the breadcrumbs and Jump to… take you up and down it.

A weld can be Not inspected in the tracker, In progress on its line of the scope of work and Rejected in the field, all at once, and all three are right. The tracker now says the field's word beside the record, and What do these mean? on the tracker and the scope opens a legend of each list; this page is the long form. They are different records of different things: what issued reports say, what the client asked for and how far it has got, what a technician saw on site today, and where a report is in its life. This page sets out each list of words, what each word comes from, and how to read them side by side.

A report is written in the editor: a form made from one of your templates, filled in section by section and saved as you type. It stays a draft, changeable by its examiner and by owners and admins, until it is signed. This topic covers starting a report and filling it in. Issuing a report covers the checks, the signatures and what happens after.

Issuing turns a draft into the record: the data is locked, a PDF is printed for each edition with its fingerprint and QR code, the client is told, and the tracker and thickness trending learn from it. Before that come the checks, the signatures and, where your company asks for it, a review. This topic follows the Sign-off card of the editor from the first signature to a withdrawal. Writing a report covers everything before it.

Every report gets its number once, and the number never changes. A revision keeps it; a cancelled report keeps it too, marked void, so every number is accounted for in the report register.

A template is the report form your technicians fill in and your clients receive. In NDT Intact you make and change your own on a page that looks exactly as the report will print. Owners and admins design templates; everyone uses them.

Every issued PDF carries a QR code that leads to a public page: the record of the report as NDT Intact holds it, which anyone can read without an account and check a copy of the PDF against. Share links open a report, a folder or a file to someone by link alone, on your portal address. This topic covers both, and how they differ from the client portal.

A client is a company that receives your reports. A project is one job you do for a client. An asset is a thing the project inspects: a vessel, a tank, a line, a structure, an exchanger. Reports, welds, drawings, requests and files all hang off a project and, where you name one, off its asset. Everything in this topic is under Clients and projects in the sidebar.

The scope of work is what the client asked to have examined: the lifting lugs by MT, the thick seams by PAUT and TOFD, the nozzles by UT or PAUT, the tubes by eddy current, before heat treatment, after it, or both. NDT Intact keeps it per asset, or for the whole project, and works out from the issued reports how far each inspection has got. Nobody types "done".

The tracker is the table of every weld and TML in a project and where each one stands. Issued reports fill it in by themselves; a repair is recorded on the weld's page; drawings carry a pin per weld; welders get their repair rates from it; and the client sees all of it in the portal once you release it. It replaces the shared spreadsheet.

An inspection request is what a client, or your own staff, asks to have inspected: which welds or items, by which methods, by when, and everything the client's own paper states about them. A request is taken up by a report started for it and answered when that report is issued. What it states reaches the report, so nothing is typed twice. The requests of every project are listed under Requests in the sidebar, Open or All; a project's own are on its Requests tab.

Every thickness reading in an issued report is kept as data, per TML and per position, so that the next inspection can be compared with the last. From that NDT Intact works out corrosion rates and remaining life against a minimum thickness you enter, and shows them per TML, per project and, when the tracker is released, to the client. The figures are indicative: every view says how they are worked out.

A project's Files tab holds its scan data, photos, drawings and anything else, in folders you name. Files go straight from the browser to storage and come back through short-lived links, never through the application itself. From here you share a folder or a file with the client, make a share link, link files to reports and welds, look at scan data, and keep plain tables. Owners, admins and technicians upload and arrange files; every staff member reads what the folder gives them.

A handover dossier is the data book a client takes over at the end of a job, or at any point along the way: one file with everything that stands for a project, or for one asset of it, built in one action. It is made in the background and lands among the project's files, where it is shared and downloaded like any other file. Owners, admins and technicians build one.

Your clients receive their reports in a portal of their own, at your company's portal address or your own domain, with your logo and your colour, not ours. Client users are free and unlimited: they never count toward your plan. They see issued reports and what you release to them, never a draft, and they can comment, formally accept, raise requests and sign what you send them.

Two registers decide what a report can say: Equipment, the instruments, probes, wedges and blocks with their calibrations, and Personnel, your staff with their certificates. Reports take their equipment and their signers from them, the checks before issue hold them against the inspection date, and the handover dossier prints their certificates. Owners and admins keep both registers; everyone on staff reads them.

Documents, in the Work section of the sidebar, holds your company's controlled documents: procedures, standards, technique sheets, validation, the quality manual, work instructions, forms, accreditations, safety and training material. Each person reads what they are given; a download, where allowed, is a numbered copy stamped with their name. Owners and document controllers keep the library and decide who reads what.

Team, in the Organisation section of the sidebar, lists everyone who works in your company and what each person is allowed to do. Owners and admins open it, invite colleagues, give roles, and deactivate people who leave. Nobody is ever deleted: signatures, reviews and the activity log point at people, so a person who leaves is deactivated and keeps their name on what they signed.

Your company's people write to each other inside NDT Intact, as they work: one conversation per pair, and groups for a job, a site or a crew, with text, pictures and documents. Messages arrive as they are sent, and an email tells someone away from the app that messages are waiting. Only the people in a conversation read it, and nothing reaches a client or another company.

The Operations module is the step between a client's request and the reports that answer it: who goes where with which kit, the hours they work, and the client's signature on those hours. Everyday jobs come first; a shutdown or turnaround is the same things at a larger scale, with worklists, norms, demand, estimates and blockers added. With the module off, nothing of it shows and reports work exactly as before. With it on, a report can still answer a request directly: a job is never required.

Settings, in the Organisation section of the sidebar, holds everything about the company as a whole: its name and languages, how reports are reviewed and numbered, the methods it offers, the client portal, and the connections to other systems. The pages are listed in groups: Organisation, Client portal, Access and integrations, and Owners only. This topic goes through them in that order and says who may change each.

In NDT Intact, AI drafts work for a person to check: the free text of a report in its other languages, and what a document says, such as a client's request, an equipment list, your own report form or a scope of work. Nothing an AI drafts counts until a person confirms it, and whoever confirms it is recorded. AI works only once your company has switched it on, and only on what someone asks it to read.

A plan is the size of your company. It sets how many people it takes, how much storage comes with it and which features are open. One subscription covers your company in every app of the family it chooses, and a person is paid for once, whichever apps they use. Every figure is on the pricing page, on our website and at intactapps.com; this topic says how the pieces fit and where to change them.

Your account is yours, not any company's: your name, password, second factor, language and appearance follow you into every company you work in. They live in your own menu, at the foot of the sidebar: Your account, My work, every company, Security, Language and Appearance, with Help, Write to support, What's new and Sign out.

Site work loses the connection. NDT Intact keeps the pages you have opened and what you type in a report draft on your device, and sends it when the connection returns, so nothing typed in the field is lost. Your phone does two more things: it shows your day on site, and it takes photos straight into a project. There is no native app yet; everything here runs in the phone's browser or in the web app installed from it.

The desktop app opens every app of the family your company holds in one window, signed in once, and keeps a copy of your company's records and files on your own computer on a schedule. It runs on a Mac today; Windows follows. It changes nothing in how NDT Intact works: each app runs inside it exactly as in the browser.