eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

Why English? | Reading Acrobat’s Preflight Profile Results Before Applying PDF Fixups

—

by

eduKate Asia
ACROBAT PRO · PREFLIGHT PROFILE · PDF FIXUPS

Prove what the selected profile checks and what its fixups will change before a technical report becomes permission to rewrite the PDF

Use a destination–specification–source-file–source-PDF–derivative–library–profile-name–profile-summary–check–property-statement–severity–result-object–wrench-icon–fixup–permanent-change–before-and-after–report–standard–release chain. Treat preflight as criteria-based evidence, not universal approval.

ROUTE 1OrientDefine the destinationROUTE 2InterpretConfirm the exact profileROUTE 3ControlRead property statements and severityROUTE 4VerifyApply fixups to a derivative

Open the full chapter index ↓

Why this English matters now

Reading Acrobat’s Preflight profile results before applying PDF fixups is practical English for students, designers, researchers and print teams searching how to check a PDF for printing, validate PDF/A or PDF/X, inspect fonts and colour, or correct a PDF before submission.

Adobe’s Preflight guidance, updated 26 February 2026, says a profile contains one or more checks, fixups or both. Checks evaluate defined property statements; profiles with fixups carry a filled grey wrench icon, and fixups can permanently change a document. Adobe organises predefined profiles into groups including Digital Printing, PDF Analysis, Prepress, PDF/A, PDF/E and PDF/X Compliance, while reports can be saved as PDF, XML or text.

A green result means the selected criteria found no reported problem under that profile; it does not prove the PDF is correct for every destination. Strong reviewers preserve the source, obtain the recipient’s specification, confirm the Preflight library and exact profile, read every check and fixup, distinguish report from repair, inspect severity and objects, prefer correcting the source file when appropriate, apply fixups only to a derivative, compare before and after, create a report and verify the exact released PDF.

Checked against the linked first-party sources on 2 November 2026. Interfaces, managed-device rules and school procedures can change, so reopen the current source before a live assessment, disclosure or account decision.

The practical reading method

Use a destination–specification–source-file–source-PDF–derivative–library–profile-name–profile-summary–check–property-statement–severity–result-object–wrench-icon–fixup–permanent-change–before-and-after–report–standard–release chain. Treat preflight as criteria-based evidence, not universal approval.

  1. Adobe says a Preflight profile contains checks, fixups or both.
  2. Adobe says each check uses property statements and reports an error only when the check’s defined error conditions are met.
  3. Adobe says a filled grey wrench icon identifies a profile that includes a fixup.
  4. Adobe warns that a fixup permanently changes the document.

Official factual floor

  • Adobe says predefined profile groups include Digital Printing, PDF Analysis, Prepress and standards-oriented PDF/A, PDF/E and PDF/X compliance.
  • Adobe says fixups can convert colour spaces, change PDF version, flatten transparency, widen hairlines, remove objects and prepare standards conversions.
  • Adobe says Preflight result reports can be created as PDF, XML or text, with PDF reports offering overview or detailed presentations.
Scope: This guide cannot supply a printer’s or archive’s specification, prove a standard is legally required, validate the source content, preserve every interactive feature or signature, guarantee colour on a physical device, certify accessibility, authorise permanent changes or replace prepress, archival, legal, records and accessibility expertise.

Did You Know?

A profile can both inspect and fix. The grey wrench is therefore more than decoration: it warns that running the profile may change objects, colour, transparency, versions or metadata rather than merely reporting what the PDF contains.

Full chapter index

  1. 1. Define the destination
  2. 2. Preserve source and PDF
  3. 3. Choose the Preflight library
  4. 4. Confirm the exact profile
  5. 5. Read the profile summary
  6. 6. Distinguish checks from fixups
  7. 7. Read property statements and severity
  8. 8. Locate problem objects
  9. 9. Prefer source correction when appropriate
  10. 10. Apply fixups to a derivative
  11. 11. Compare before and after
  12. 12. Create and preserve a report
  13. 13. Verify standards and release
CHAPTER 1 OF 13

1. Define the destination

Back to contents

The mechanism

Print, archive, engineering exchange and screen delivery have different requirements.

Adobe says a Preflight profile contains checks, fixups or both. In this chapter, the decisive phrase is define the destination. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A PDF/X profile is run because it sounds rigorous even though the recipient requested PDF/A.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. name the recipient
  2. 2. obtain the specification
  3. 3. record the date
  4. 4. confirm the intended standard

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A standard label does not replace destination instructions.

Transfer: Purpose language supports relevant validation. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 2 OF 13

2. Preserve source and PDF

Back to contents

The mechanism

Fixups can permanently change the derivative and may be best reproduced from the authoring source.

Adobe says each check uses property statements and reports an error only when the check’s defined error conditions are met. In this chapter, the decisive phrase is preserve source and pdf. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The only PDF is fixed without retaining the layout file or original.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. save the source application file
  2. 2. store the source PDF read-only
  3. 3. create a derivative
  4. 4. record identities

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: The source can still contain unresolved errors.

Transfer: Provenance language supports recovery. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 3 OF 13

3. Choose the Preflight library

Back to contents

The mechanism

Different libraries expose different profiles and expectations.

Adobe says a filled grey wrench icon identifies a profile that includes a fixup. In this chapter, the decisive phrase is choose the preflight library. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A user searches only Essentials and assumes a needed standards profile does not exist.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. open the library menu
  2. 2. name the selected library
  3. 3. search deliberately
  4. 4. record the environment

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: Available libraries and labels can vary by version.

Transfer: Library language supports correct discovery. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 4 OF 13

4. Confirm the exact profile

Back to contents

The mechanism

Similar profile names can check different versions or output conditions.

Adobe warns that a fixup permanently changes the document. In this chapter, the decisive phrase is confirm the exact profile. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A generic analysis profile is treated as the recipient’s required compliance test.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. copy the profile name
  2. 2. read its description
  3. 3. confirm the standard version
  4. 4. mark custom profiles

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A custom profile may differ between computers.

Transfer: Identity language supports repeatable inspection. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 5 OF 13

5. Read the profile summary

Back to contents

The mechanism

A summary explains the checks and criteria before execution.

Adobe says a Preflight profile contains checks, fixups or both. In this chapter, the decisive phrase is read the profile summary. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The result is accepted without knowing that image resolution was not checked.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. create the summary
  2. 2. list checks
  3. 3. list fixups
  4. 4. match criteria to the specification

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A summary describes rules, not the document’s actual content.

Transfer: Criteria language supports defensible review. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 6 OF 13

6. Distinguish checks from fixups

Back to contents

The mechanism

Checks report conditions; fixups attempt specified changes.

Adobe says each check uses property statements and reports an error only when the check’s defined error conditions are met. In this chapter, the decisive phrase is distinguish checks from fixups. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A production PDF is modified when the user expected a read-only inspection.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. identify each check
  2. 2. identify each fixup
  3. 3. look for the wrench
  4. 4. run a report-only profile first when suitable

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A profile may combine both behaviours.

Transfer: Action language supports safe operation. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 7 OF 13

7. Read property statements and severity

Back to contents

The mechanism

Errors, warnings and information reflect defined profile logic.

Adobe says a filled grey wrench icon identifies a profile that includes a fixup. In this chapter, the decisive phrase is read property statements and severity. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Every informational finding is treated as a production failure.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. open result details
  2. 2. read the property
  3. 3. identify threshold and severity
  4. 4. map it to the real requirement

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: No finding appears for criteria the profile does not include.

Transfer: Result language supports proportional response. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 8 OF 13

8. Locate problem objects

Back to contents

The mechanism

Page and object details connect abstract findings to visible content.

Adobe warns that a fixup permanently changes the document. In this chapter, the decisive phrase is locate problem objects. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A low-resolution image warning is fixed globally without identifying the affected object.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. expand the finding
  2. 2. locate pages
  3. 3. inspect highlighted objects
  4. 4. verify context

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A reported object may be invisible or clipped yet still relevant.

Transfer: Object language supports targeted repair. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 9 OF 13

9. Prefer source correction when appropriate

Back to contents

The mechanism

Authoring applications often preserve intent better than PDF repair.

Adobe says a Preflight profile contains checks, fixups or both. In this chapter, the decisive phrase is prefer source correction when appropriate. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A missing font and low-resolution image are patched in PDF while the editable source remains wrong.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. open the source
  2. 2. repair fonts and images
  3. 3. export again
  4. 4. rerun the same profile

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: Some received PDFs have no available source.

Transfer: Source language supports maintainable quality. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 10 OF 13

10. Apply fixups to a derivative

Back to contents

The mechanism

Adobe warns that fixups permanently change the document.

Adobe says each check uses property statements and reports an error only when the check’s defined error conditions are met. In this chapter, the decisive phrase is apply fixups to a derivative. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: Flatten transparency and colour conversion are applied to the only approved PDF.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. confirm authority
  2. 2. duplicate the PDF
  3. 3. record the fixup
  4. 4. apply once and compare

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: A successful fixup can alter appearance or interactivity.

Transfer: Change language supports controlled production. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 11 OF 13

11. Compare before and after

Back to contents

The mechanism

Technical compliance can introduce visual or functional differences.

Adobe says a filled grey wrench icon identifies a profile that includes a fixup. In this chapter, the decisive phrase is compare before and after. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: A profile passes after repair but a form field and signature no longer behave as expected.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. compare page count
  2. 2. inspect fonts and colour
  3. 3. test links forms and tags
  4. 4. check signature status

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: Visual equality does not prove structural equality.

Transfer: Comparison language supports trustworthy output. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 12 OF 13

12. Create and preserve a report

Back to contents

The mechanism

PDF, XML and text reports serve different review workflows.

Adobe warns that a fixup permanently changes the document. In this chapter, the decisive phrase is create and preserve a report. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The team records only a screenshot and cannot reconstruct settings or findings.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. choose the report type
  2. 2. include needed detail
  3. 3. protect sensitive content
  4. 4. link report to file identity

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: Reports can reveal document content and production data.

Transfer: Evidence language supports auditability. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

CHAPTER 13 OF 13

13. Verify standards and release

Back to contents

The mechanism

A passed rerun must correspond to the exact delivered derivative.

Adobe says a Preflight profile contains checks, fixups or both. In this chapter, the decisive phrase is verify standards and release. It identifies the state or boundary to check before a click, upload, disclosure or connection turns an assumption into a real consequence.

A practical school or study situation

Example: The fixed file passes but the original is uploaded to the printer.

A Preflight result describes the selected profile’s criteria and the PDF state it observed. It does not evaluate requirements absent from that profile, prove the content is correct, guarantee device output or turn an automatic fixup into an authorised editorial or production decision.

Decision sequence
  1. 1. rerun the intended profile
  2. 2. save close and reopen
  3. 3. compare file identity
  4. 4. verify the actual delivery

Preserve the authoring source and source PDF; obtain the destination’s dated specification; create a controlled derivative; open the correct Preflight library; record the exact profile name and version; create or read its profile summary; list checks and fixups; identify the wrench state; run inspection first where possible; read severity, pages and problem objects; decide whether to correct the source application; if authorised, apply fixups only to the derivative; compare page count, appearance, fonts, colour, transparency, links, forms, tags, signatures and metadata; rerun the intended profile; save a PDF, XML or text report as required; open the exact released PDF and verify the destination receipt. Then name the remaining uncertainty. A successful click is evidence about one operation at one time; it is not an unlimited promise about safety, authorship, privacy, delivery or future behaviour.

Build a reproducible note

Record destination and specification date, source-application file, source PDF identity, derivative identity, Acrobat version, Preflight library, exact profile and summary, checks, fixups, wrench state, run date, severities, pages and objects, source corrections, applied fixups, before-and-after comparisons, rerun result, report type and identity, reviewer and released PDF identity.

Important boundary: Passing one profile does not certify accessibility or content accuracy.

Transfer: Release language supports study and work. The transferable habit is to preserve exact nouns and verbs, match them to authority and test the resulting state. That is a career skill as much as an English skill.

Four useful discoveries

Define the destination

Print, archive, engineering exchange and screen delivery have different requirements.

Boundary: A standard label does not replace destination instructions.

Preserve source and PDF

Fixups can permanently change the derivative and may be best reproduced from the authoring source.

Boundary: The source can still contain unresolved errors.

Choose the Preflight library

Different libraries expose different profiles and expectations.

Boundary: Available libraries and labels can vary by version.

Confirm the exact profile

Similar profile names can check different versions or output conditions.

Boundary: A custom profile may differ between computers.

Practice with realistic decisions

Read the profile summary

The result is accepted without knowing that image resolution was not checked.

  • create the summary
  • list checks
  • list fixups
  • match criteria to the specification

Distinguish checks from fixups

A production PDF is modified when the user expected a read-only inspection.

  • identify each check
  • identify each fixup
  • look for the wrench
  • run a report-only profile first when suitable

Read property statements and severity

Every informational finding is treated as a production failure.

  • open result details
  • read the property
  • identify threshold and severity
  • map it to the real requirement

Advice for students, families and educators

For students

  • Run an inspection profile on a copy and read its description before using any wrench-marked fixup.
  • Keep the editable source so a font or image problem can be corrected properly.

For families

  • Ask what destination or submission rule the selected profile represents.
  • Help preserve originals without making technical approval decisions for the learner.

For educators

  • Teach checks, fixups, standards and reports as separate layers.
  • Assess explanation of criteria and before-and-after verification alongside a passing result.

Frequently asked questions

What is a Preflight profile?

A package of checks, fixups or both for defined PDF properties.

What is a check?

A rule that evaluates property statements and reports defined mismatches.

What is a fixup?

An automatic correction that changes the PDF when possible.

What does the grey wrench mean?

Adobe uses it to mark a profile containing a fixup.

Are fixups permanent?

Adobe warns that a fixup permanently changes the document.

What profile groups exist?

Examples include Digital Printing, PDF Analysis, Prepress, PDF/A, PDF/E and PDF/X.

Does a passed profile prove the whole PDF is correct?

No; it covers only that profile’s criteria.

Should I fix the source file?

Often yes when the authoring source is available and can preserve intent better.

What report formats are available?

Adobe documents PDF, XML and text reports.

Why English?

Because profile, check, property, severity, fixup, wrench, report and standard describe different evidence and actions.

Useful next reading

Closing thought

Preflight is most useful when everyone can explain what was checked, what was changed and why. Read the profile before the result, read the wrench before the repair and preserve enough evidence to rebuild the PDF safely from its source.