> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/implementation/submission-workflow/create-proofsheets.md).

# Create Proofsheets

The proof page is one of the most important workflow steps because it creates a clear review and approval point before production begins.

### What a proof page typically includes

A proof page usually combines:

* the processed artwork
* product dimensions
* material or finishing information
* order reference details
* warnings or disclaimers where relevant
* other production metadata

The exact content can vary by product type, workflow, and customer requirements.

### When proof generation happens

Proof generation usually happens after:

1. the customer uploads and reviews the artwork
2. the full production preflight runs
3. any required automated corrections are applied
4. the file is considered ready for approval

### Why proof pages matter

A proof page helps:

* confirm what is actually going to production
* reduce misunderstandings about output intent
* create a clear approval checkpoint
* support internal and customer-side review

### Best practice

Treat the proof page as the approved production reference point, not just a visual extra.

Its structure, templates, and metadata should be consistent and reliable across the workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.atomyx.io/atomyx-submit/implementation/submission-workflow/create-proofsheets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.