Your work. Your records.
Desktop Publishers: Workplace Records
Approval of a sample layout does not necessarily approve every word or image in a later production master. When a workplace concern involves a printed error or a missed handoff, connect the approved sample, the proof that was checked and the version delivered for production. Those may be different files reviewed by different people.
Call now(800) 800-5555Free initial case evaluation. Representation depends on work state and case eligibility. This guide explains record preparation; it does not determine whether a legal claim exists.
A record map for your role
What to organize first
Sample scope
Record which aspect of the layout was approved and which still needed review.
Correction trail
Connect the annotated proof to the version containing the change.
Master reference
Identify the exact delivered version without retaining restricted artwork.
Receipt distinction
Keep delivery, acceptance and later production results separate.
Start with the work you actually do
Format typescript and graphic elements using computer software to produce publication-ready material.
O*NET classifies this occupation as Desktop Publishers (43-9031.00). Its description covers a typical occupation, not every workplace or individual job. It does not establish employee status, overtime eligibility or employer misconduct.
- Prepare sample layouts for approval, using computer software.Source task 2824 · updated 08/2021
- Check preliminary and final proofs for errors and make necessary corrections.Source task 2815 · updated 08/2021
- Transmit, deliver, or mail publication master to printer for production into film and plates.Source task 2830 · updated 08/2021
Identify what the sample approval covered
Note the permitted project reference, sample version and the feedback received. Describe whether the response concerned layout, content or another specified part of the work, using the actual instruction rather than guessing. Keep a requested revision separate from an approval. Do not describe approval of the page’s appearance as approval of text or images added afterward unless the record supports that conclusion.
Follow a correction from proof to revised version
Identify the proof containing the issue and the instruction to correct it. Record the version to which you applied the change and any subsequent review response. If a correction was requested after your handoff, note that sequence. Keep an annotated proof distinct from a file that actually incorporated its changes, and preserve uncertainty when the available records do not establish which version was used.
Record the production-master handoff
Identify the authorized delivery reference, file version and recipient responsible for the next production step. Separate sending a master from receiving confirmation that the intended version was accepted. If the employment concern concerns a later printed result, link it only to the version supported by the permitted record. Do not export unpublished content or customer artwork, or send a new production file to recreate the event.
Source context and limits
The selected O*NET 31.0 tasks describe sample-layout approval, proof corrections and delivering a publication master for production. They are dated August 2021 and include historical print-production terminology. They provide work context rather than current prepress specifications or copyright advice. This guide does not establish responsibility for an error, the scope of an approval or whether an employment action was justified.
Choose your next step
Review the workplace retaliation guide, unpaid wages guide, or discrimination guide if those concerns fit your experience. A job title alone does not establish a claim.
Call now(800) 800-5555Current service-state coverage
AK, AL, AR, AZ, CT, DE, FL, GA, HI, IA, ID, IN, KS, KY, LA, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NM, NY, OH, OK, PA, RI, SD, TN, TX, UT, VA, VT, WI, WV, WY. Eligibility is evaluated individually; this list does not promise representation.
Explore state resources