DOCUMENT DETAILS, UNDER CONTROL

Publisher Submission Packet Checklist

Build requirement profiles; check supplied filenames and sections; export outstanding items.

Worked exampleBrowser processingUseful downloads

A clear result starts here

Add your input or try the worked example.

Using Publisher Submission Packet Checklist

Build requirement profiles; check supplied filenames and sections; export outstanding items.

Choose the supported local files or use Try example to see a complete worked result.
Set manuscript headings / notes. Read the field notes for supported values.
Choose Review input and inspect the result, including any review flags or unsupported cases.
Use the relevant download buttons to keep your result. CSV and report JSON preserve the available findings; original files are not changed.

Example

Try example creates a small, usable local file with the control values shown on this page.

Questions & answers

What does Publisher Submission Packet Checklist do?

Build requirement profiles; check supplied filenames and sections; export outstanding items.

What input does this tool support?

Requirements: item,type,pattern,required: Types: file (wildcards * and ?), section (literal text), note (manual).. Manuscript headings / notes File formats: .pdf,.docx,.txt,.png,.jpg.

What should I check before using the result?

User-defined submission requirements, not a current publisher policy database. A filename or heading match does not validate content or permissions.

Can I keep or share the result?

Yes. Use the result-specific downloads, CSV where available and report JSON. Downloads can contain your supplied information, so review the content before sharing. Processing runs in this browser; public pages also include the site’s approved advertising and optional analytics.