Write Personnel Requirements into an NDT Draft Brief

Typing Level II into a procedure request leaves the reader to guess the issuing route, method scope and responsibilities intended. It also leaves unclear who confirms that a particular person may perform the work. A useful personnel brief identifies the controlling source and the duties it applies to, while keeping actual private records in their authorized location. This guide helps prepare that brief for the procedure generator. It does not select a certification scheme, award a qualification or decide that a particular individual is eligible to perform an examination.

The deliverable is a qualification-source and responsibility map. It connects the general procedure requirement to the employer’s evidence review without copying complete personnel files into a drafting tool. The distinction matters because a procedure describes requirements for work, while an individual’s record demonstrates what that person has actually completed or been authorized to do. Those documents need to agree, but they serve different purposes. A clear map helps the technical reviewer see which source governs each role and which questions remain open before a substantial draft is mistaken for an approved instruction.

Ask the responsible employer reviewer which written practice, certification program or project requirement applies to the intended work. Identify the relevant revision through the controlled process. Do not choose a familiar source merely because its name appears in an older template. The procedure brief should reference the actual basis, including any project-specific condition the reviewer identifies. If the basis is unresolved, record it as an open input rather than filling the field with several schemes and hoping the generated draft will reconcile them. The generator cannot decide which requirement the contract or employer intends.

ASNT’s employer-based certification explanation distinguishes employer responsibility from central certification. Use that distinction to avoid ambiguous source labels. An employer-issued record, a central credential and a training certificate should not be described as interchangeable merely because each contains a method or level. Ask which one the procedure’s personnel requirement actually relies on and what additional employer decision remains. Keep the answer concise in the draft input and retain the supporting controlled reference elsewhere. A short accurate source description is more useful than a lengthy list of prestigious names without an identified role.

List what people will do under the procedure: prepare the examination arrangement, perform the examination, interpret findings, evaluate against the applicable basis, prepare the report and review or authorize the result as required by the project. The actual division of duties belongs to the responsible organization, so do not assume that each activity needs a separate person or that one person necessarily performs all of them. The purpose of the map is to make the intended arrangement visible. Each role should have a source and a person or function responsible for confirming its authorization.

Use concrete verbs instead of broad phrases such as qualified staff will handle everything. A report preparer may organize information without making the technical disposition, while a reviewer may have a different responsibility from the examiner. If the same person performs several duties, the basis for those duties still needs to be understood. A generated document cannot infer the arrangement from a job title. Clear role language helps the employer review the personnel requirement and helps the eventual report avoid implying that every name appearing on a document performed or approved every part of the work.

Ask how the organization handles an unavailable reviewer or a change in the assigned team. The procedure requirement should not depend on an informal assumption that one familiar person will always be present. Identify the process for confirming a replacement’s actual role and authority without naming an unapproved substitute in the draft. A schedule change does not itself transfer technical responsibility. Keep the required function in the procedure and the individual assignment evidence in the employer’s controlled records. This makes the document usable across personnel changes while preserving the need for a real decision about each assignment. If a project requires a specifically designated role, retain that condition accurately and ask how changes are authorized. The generator cannot resolve a staffing gap by producing another signature line or substituting a generic approval title.

Describe the method or technique and the relevant product or application scope at the level needed for the procedure review. Avoid assuming that a broad method label explains every proposed activity. Ask the reviewer to identify any scope distinctions that matter and keep them linked to the source requirement. Do not paste certificate numbers, personal addresses, photographs, vision records or examination results into the personnel input. The drafting brief needs the requirement and the review question, not the private evidence that the employer or issuer evaluates through its own process.

If the project involves several personnel groups, identify the relevant duty arrangements without building an individual roster inside the generator. A procedure may remain applicable while assigned personnel change. The employer needs a separate way to establish who is authorized for the actual examination date and scope. Keep the relationship clear: the procedure states the reviewed requirement, and the controlled personnel process demonstrates the individual assignment basis. This avoids a draft becoming obsolete because a named person changes while also avoiding the opposite error of assuming that a generic requirement proves every available technician meets it.

The qualification evidence planner can help organize questions before you summarize the personnel requirement in the procedure brief. Select the intended route and describe the task generally, then mark evidence statuses according to what is actually known. The output is a self-reported question list, not a review of documents or a qualification decision. Use it to ask which source applies, which records are relevant and who accepts them. Keep the employer’s answers separately from the generated prompts so the final procedure input does not present unanswered planning questions as settled requirements.

There is no automatic transfer from the qualification planner to the procedure generator. Manually summarize the confirmed requirement in the generator’s personnel field and leave unresolved points visible. The qualification planner holds entries only in its open page, with deliberate TXT or CSV export, while the procedure workflow creates a separate draft. Do not assume that using the same account or browser synchronizes their content. Review the wording you carry across. A general planning phrase can lose an important limitation if it is shortened casually to fit the procedure form’s bounded text field.

The procedure generator includes a personnel scheme and authorization field, separate from equipment, calibration and reporting requirements. Use it to identify the controlled qualification source, the method or technique scope, the intended responsibilities and any unresolved authorization question. Keep the wording technical and general. If a needed reference or decision is missing, say so plainly instead of inventing a credential requirement or approval role. The tool flags unfilled technical fields, but an entered sentence can still be incomplete or wrong; supplied information also needs review.

The default generator assembles a structured draft with 20 planned pages and can produce up to 25 pages with longer entries. It includes responsibility and release-review material, but no generated signature or approval establishes that the work is authorized. Preview is available, with free account saving and PDF or editable-text download. The user remains responsible for completing the technical inputs through the appropriate review process. A substantial document can make unanswered personnel questions easier to find; it cannot turn those questions into evidence or substitute for the employer’s actual assignment decision.

Imagine a fictional inspection coordinator preparing a magnetic particle procedure draft for fabrication work. The first personnel entry says only Level II personnel. During review of the duties, the coordinator discovers that the project distinguishes examination activity from the authority to release the final report package. The coordinator asks the employer for the applicable qualification source and the report-release arrangement. The revised brief identifies the source reference and separates the two responsibilities, while the actual personnel records remain in the employer’s controlled system. The generator has not evaluated any individual or supplied a missing authorization.

In this invented case, the report-release question is still open when the first draft is generated. The draft therefore remains a review document with that condition visible. When the employer later identifies the responsible role, the coordinator updates the relevant input and retains the actual decision reference in the project process. The example does not establish that every magnetic particle project uses two people or a particular approval title. It illustrates why a broad level label is insufficient when the proposed responsibility arrangement contains a distinction the employer needs to resolve.

If the work arrangement includes trainees, assistants or people operating within a limited role, ask the employer to define the actual permitted activities and direction arrangements. Do not treat supervised as a universal permission to perform every task in the procedure. The relevant source and responsible organization determine the boundary. The brief should make that question visible without inventing training hours, examination requirements or a qualification pathway. A person helping with record organization may have a different role from someone performing an examination, even if both participate in the same project meeting.

Keep the boundary connected to the actual task and report wording. If someone assists with data collection or document preparation, the final record should not automatically describe them as the independent examiner or technical approver. Ask how the organization records participation and responsibility. A generic signature table can imply more than intended if roles are not defined before use. The procedure draft can provide places for those roles, but the employer must determine who fills them and on what basis. Preserve that distinction when adapting the generated text into the organization’s controlled document format.

A project may change the technique, product or reporting responsibilities after the personnel brief is prepared. Compare the revised duties with the requirement already reviewed and ask which questions are affected. Do not automatically replace every record, and do not assume that the prior decision covers the new work. Keep the original decision for its original scope and record the new review separately. This approach lets the employer recognize relevant existing evidence while addressing the actual change. The procedure generator does not monitor project revisions or reopen personnel decisions when a field elsewhere changes.

An individual’s record can also change while the procedure requirement remains the same. The employer needs to assess the actual assignment basis through its personnel process rather than editing the generic procedure every time a roster changes. The certificate manager can organize entered credential details and optional dates, but a reminder or saved record is not verification of issuer status or assignment acceptance. Use it for recordkeeping and maintain the employer’s decisions through the appropriate controlled process. No automatic synchronization connects the record manager to the generated procedure’s personnel wording.

Review the report fields alongside the personnel requirement before the procedure is released. Identify which fields record the examiner, preparer, reviewer or other role actually required by the project. Do not add names to a generic approved-by field merely because a template includes it. The field should reflect the organization’s real decision and record process. If a signature or approval is required, use the authorized method for that requirement. A typed name in an editable draft does not by itself establish the necessary technical or organizational authority.

The digital NDT reporting editor provides user-entered report information, editable tables and document output. It does not validate personnel qualifications or confer approval. Manually map the reviewed responsibility requirements into the report structure, keeping any unresolved role visible until the responsible process resolves it. The procedure generator’s output is not automatically imported as a report configuration. This manual handover is useful because it forces the team to check that the duties described in the procedure are represented accurately in the evidence eventually delivered to the client.

Before submitting the draft for review, make sure every personnel statement has an identifiable basis or is clearly marked as an open question. A statement that all personnel are qualified is less useful than a source reference, duty description and evidence-review responsibility. Keep the actual private records out of the general drafting packet unless the authorized reviewer requests them through the agreed channel. The reviewer should be able to identify what must be checked without receiving unnecessary personal information or assuming that the generator has already performed that check.

Use the downloadable worksheet to link the requirement, duty, evidence question and decision owner. The fictional rows illustrate the structure, not a universal personnel rule. Replace them with the actual project arrangement and preserve the distinction between a confirmed requirement and a pending individual review. The outcome should be a concise input that helps the generator produce a useful draft and helps the employer see what remains to be decided. It should never imply that the free tool certifies staff, validates experience, recognizes equivalent credentials or authorizes an inspection assignment.