Give the sample a reader
Imagine two fictional assignments: explaining a screening test to the public and documenting an analysis method for researchers. Both require accuracy, but they require different vocabulary, background information, and levels of detail.
The Bureau of Labor Statistics describes technical writing as communicating complex information for users. A portfolio can make that audience relationship explicit: who needed the information, what they were trying to do, and why the chosen format helped.
The annotation can be brief
Audience: readers comparing two study designs. My contribution: proposed the angle, wrote the draft, checked the source papers, and revised after editorial review. The published headline was written by the editor.
That invented note communicates ownership without diminishing collaboration. It is more useful than an unexplained list of publication logos.
Show the difficult choice
A sample becomes especially informative when the accompanying note identifies a meaningful decision: removing a causal claim unsupported by the design, explaining an uncertain estimate, or replacing a jargon-heavy paragraph with a worked example.
There is no need to present confidential editorial correspondence. A short explanation of the decision and the public result may be sufficient.
If there is no published clip yet
A clearly labeled independent sample can demonstrate writing ability. It should not imply that a publication commissioned or accepted it. A narrowly focused piece with checkable sources may be more revealing than an ambitious overview that never gets specific.
The portfolio's job is to help an editor assess the work they would be hiring someone to do. Selecting fewer, relevant samples can make that assessment easier than asking them to infer a specialty from a large archive.
