Independent thinking. Documented progress.Field notes on working with AI

Workflow · Version 1.1

Check the file people will actually print

A practical preflight for exported handouts and guides, including grayscale, page breaks, writing space and a visible review record.

For
Teachers, workshop leaders and document makers
Level
Practical
Evidence & status
New companion workflow; no printer-specific guarantee
Download Markdown

Version 1.1 · Published October 13, 2026 · Revised October 13, 2026

Newly authored public companion, October 2026. This is a practical review procedure for checking a finished file.

Use the real output

Review the final exported file as a reader would see it. A clean editing canvas does not tell you whether a page break splits an instruction or a printer clips an edge. Choose the intended paper size, orientation and output format before reviewing.

1. Prepare a small test

Save an editable master and export a review copy. Include a version and date in a discreet place. Choose the most crowded page, a page containing a diagram, and a page on which people must write. If the file is short, inspect every page.

2. Inspect every exported page on screen

  • Is any text, label or footer clipped?
  • Is a heading separated from the material it introduces?
  • Does a question remain with its source, diagram or answer space?
  • Are page numbers and instructions consistent?
  • Did a font substitution change line breaks or symbols?
  • Is teacher-only material absent from learner-facing copies?
  • Does the final page contain a meaningful ending rather than a stray line?

Fix the editable master and export again. Do not assume a repaired source file means the exported copy was also repaired.

3. Check the reading task

Read the directions aloud once. Complete the first task yourself. If a person needs to write, try fitting a plausible response into the available space. If the page refers to a link, offer enough title or citation information for a printed reader to locate it. A QR code should have a readable alternative.

4. Check color and readability

Preview in grayscale or print a grayscale sample. Make sure the task still works when colors become similar shades. W3C's web-design guidance supports redundant labels and adequate contrast; applying those ideas to print is an editorial adaptation, not a claim of formal print conformance.

Do not rely on a universal font-size or margin promise. The appropriate size depends on the typeface, paper, printer, audience and viewing distance. Test the actual intended use, and offer an accessible digital version when appropriate.

5. Print a representative copy if possible

Use the intended printer settings. Check page size, scaling, duplex direction and binding space. Hold the page at normal reading distance. Fold, staple or place it in a binder if that is how it will be used. Record whether this physical check happened. If it did not, label the result “screen review only.”

Review record

File and version:
Intended paper and orientation:
Export format:
Pages visually checked:
Grayscale checked: yes / no
Physical print checked: yes / no
Printer and settings, if checked:
One task attempted:
Problems found:
Repairs made:
Re-export checked: yes / no
Remaining limitations:
Decision: ready for this use / revise / needs physical check

Copy-ready review prompt

Review this document for the specified printing and reading task.
Paper, orientation and audience: [fill in]
Expected reader task: [fill in]

Report concrete issues by page and location. Separate content problems,
layout problems and checks you cannot perform. Do not claim a physical
print test, font embedding check or complete accessibility review unless
you actually performed it. Give a prioritized repair list, then identify
what must be rechecked after the next export.

A passing review applies to the file and use you checked. Revisit the decision after changing content, format, paper size or printer settings.

Revision note

Revised October 13, 2026: added a practical worked check and a clearer next decision. Original publication and evidence limits are preserved.

Turn a defect list into a release decision

Consider an invented two-page activity sheet. Screen review finds three issues: the instructions refer to a missing diagram; an answer area breaks across pages; and a footer is close to the printable edge. These defects need different evidence.

The missing diagram is a content blocker. Add the intended diagram or rewrite the question, then attempt the task again. The broken answer area is an export-layout defect: repair the source, re-export and inspect both pages. The footer remains a print uncertainty until you check the intended paper, scaling and printer.

A useful decision after the first two repairs is: “The revised two-page export was checked on screen; the task and answer area are complete. Physical print fit remains untested.” Do not convert that statement into “print-ready on every device.” The quoted result is illustrative, not a review performed for this guide.

Recheck what a repair can disturb

A new image can push instructions onto another page. A font change can fix one line and break symbols elsewhere. After repair, inspect the changed page, its neighbors and the repeated elements such as headings and page numbers. Open the exact copy that will be distributed rather than an older file with a similar name.

If an essential reading task cannot be completed, hold the file. If the only remaining limit is a physical print check, describe that limit clearly to the person making the release decision. Use Assemble a release people can actually use when several files must travel together.

Public references

Plain text for copying

Public sources & context

New companion workflow; no printer-specific guarantee A reusable method is not evidence that a future result will be correct. Check its fit for your own work before relying on it.

Explore the full resource collection · Follow new materials