A one-page TNA brief the plant head will actually read

The plant head asked for two pages. The L&D team sent thirty-four. It carried the survey instrument, the respondent breakdown, all six sites, the interview quotes, a competency heat map and a bibliography. The finding sat on page nineteen: most of the rework on the packing line was probably not a training problem. He read the first two pages, asked the one question they did not answer, and the file went into a drawer. Nothing was funded.

That is not a writing problem. It is a category error. A TNA report and a TNA brief are different documents, and most teams write the first when the reader asked for the second.

The brief is a decision document, not a summary

The analysis has to be complete to be defensible. Every cut feels like a place a reviewer could attack you, so nothing gets cut. The document grows in the order the work was done: scope, method, sample, instrument, data, findings, recommendations. That order is right for an audit trail and wrong for a decision. A plant head is not auditing your method. He is deciding whether to release people, money and production time next quarter. He needs the decision first, and the method only if he distrusts it.

PPS International's guidance starts elsewhere: find out who will use the findings and what decision they will make, before collecting anything. Long briefs are usually written by people who skipped that conversation and are making up for it with pages.

A summary compresses the analysis. A brief selects from it. If the reader could get a line by reading the report, it does not belong. The brief carries only what the reader needs to say yes or no.

That gives a fixed structure, in the order the reader decides:

The US Office of Personnel Management says a complete needs assessment also considers the consequences of ignoring the gaps. On a brief, that consequence is line three, not a paragraph in the discussion.

Write the decision line first

Before any other prose, write line one on a blank page. Not "create awareness of calibration". "Approve a two-day maintenance refresher for 18 fitters on lines 2 and 3 in Q1, hold the operator retraining request, decision with the plant head by 12 December." The second names an action, a population, a scope, an owner and a date. The first names a mood.

The decision line fixes what evidence matters. A brief asking for a refresher needs cause evidence; a brief asking to hold a request needs evidence against the original assumption. Write it first and the cut list writes itself, because anything that does not bear on that sentence has no home on the page.

If the decision owner is unclear, settle that before cutting a single page. Who owns the TNA is a separate argument, but a brief without a named owner is a newsletter: read, forwarded, acted on by nobody.

Rank the causes, do not list the findings

This is the part specific to a TNA, and the part most briefs get wrong. A needs analysis produces findings: survey scores, interview themes, observation notes, gap ratings. A plant head does not act on findings. He acts on a cause. The brief has to rank the candidate causes and show what separates them.

AIHR's guidance says a TNA report should include both training and non-training solutions, with priorities. On one page that becomes a hard rule: if the top-ranked cause is not a skill deficit, say so on line four and stop asking for a course. A brief that ranks a process defect third because the original request assumed operator error is a justification, not a brief.

The ranking is the argument. Everything else on the page exists so the reader can check it. Each row carries evidence against as well as for. A list of supporting facts is marketing. A ranked cause with its counter-evidence is a decision the reader can interrogate.

The method for producing that ranking, with weighting and routing, lives in the one-page competency gap analysis. That page is the analysis, not the brief. Confusing the two is exactly how a thirty-four-page document happens.

Cut with a rule, not with nerve

Analysts do not keep everything because they write badly. They keep everything because deleting feels like losing rigour. Give them a rule and the page gets short without anyone feeling exposed.

The rule: if a line exists to defend a number rather than to make the decision, it moves to the appendix.

Number every appendix item. The brief points to A3, not to "supporting detail". A pointer a reader cannot follow is decoration.

The appendix is the report's real home. The rigour is not deleted, it is relocated: nothing is rounded, the thirty-four pages still exist with every exclusion logged. Deleting from the brief is not deleting from the work. Once an analyst believes that, one page stops feeling like a compromise. A brief with no appendix is a claim. A brief with a numbered appendix is a checkable claim.

Worked example: the packing line brief

All figures below are illustrative. A plant commissioned a TNA because first-pass yield on the packing line had been flat for three quarters and the operations head wanted operator retraining. The draft report ran to thirty-four pages and recommended it on page nineteen.

Here is the one page that should have gone out:

Decision requested. Approve a maintenance refresher for 18 fitters on lines 2 and 3 in Q1 and hold the operator retraining request. Decision with the plant head, 12 December.

Gap. First-pass yield has sat between 91 and 93 percent for three quarters against a 97 percent standard. Source: shift production log, pulled 4 November.

Cost of inaction. Rework and scrap averaged about Rs 2.8 lakh a month over the same three quarters. Source: quality rework register.

Ranked causes. 1. Seal-jaw calibration drift on lines 2 and 3: 71 percent of rework tickets name a seal fault; drift found on 4 of 6 jaws at the last service. Against: lines 1 and 4 use the same jaw model with no fault. 2. Calibration check skipped at shift handover: check sheets unsigned on 22 of 30 observed shifts; three fitters say the step is dropped when the line runs behind. 3. Operator packing technique: weak. Rework does not cluster by operator, and the most experienced crews have the same fault rate. This is the cause the original request assumed.

What this does not establish. Whether a refresher changes handover behaviour. That needs observation after training, not another survey.

Appendix. A1 ticket analysis, A2 service records, A3 handover check sheets for the 30-shift sample, A4 interview notes, A5 survey instrument and respondent breakdown, A6 data-cleaning log.

The original report recommended operator retraining because its first eighteen pages described a survey that asked operators about technique. The brief reverses the conclusion: the assumed cause ranks third, and the decision asks to hold it. Same evidence, different order, opposite ask. A1 to A6 are the same thirty-four pages, numbered and uncut.

The honest limit

A one-page brief cannot be the audit trail. If the decision is contested, the appendix is what gets read, and it has to be good. A crisp brief on a thin appendix is a shorter way to be wrong. The analysis can still be thirty-four pages. It should be.

The format can also hide weak analysis. A confident decision line and three tidy causes are persuasive even when the ranking is guesswork. The defence is structural: every cause carries evidence against, the limits line is written by the author, and the appendix pointers are specific. If you cannot fill the "evidence against" column, the ranking is not ready.

The post-programme version is a different thing. The six-line training impact report has to make every number retrievable, because its reader is auditing a result, not funding a diagnosis. Different reader, different worry, different page.

There is one precondition: somebody must be able to say yes or no, with a date. If the TNA was commissioned as research with no owner and no review slot, a one-page summary will not create a decision the organisation has not scheduled. Write a short note naming what is still unknown and who must book it.

Do this before the next review

Take the last TNA report you sent. On a blank page, write the decision line at the top in one sentence with a name and a date. If you cannot, that is the finding, and it is worth more than the report. Move every line that exists to defend a number into a numbered appendix. Rank the causes with evidence on both sides. Put the cost of inaction on line three and the limits on line five. Send one page, keep the rest intact where a sceptic can ask for it.

The analysis stays long. The decision gets a page. BolderBrain's assessment and reporting features keep the instrument, the evidence and the gap in one place, which makes the appendix cheap to assemble each quarter. The plant head will read the page. He may then ask for A3. That is the whole point.