--- title: Standard Packages & Page Breaks slug: help/standard-packages-and-page-breaks createdAt: 2025-06-12T16:56:05.207Z --- ## Introduction Precise weight management is crucial for ensuring mail pieces meet postal regulations, qualify for the correct rate categories, and are processed efficiently. This document provides an overview of page break points based on commonly used weights of paper stock, ink coverage, envelope type, inserts, and other mailing components. ## Purpose The purpose of this document is to support accurate job setup, cost estimation, and mailing efficiencies by offering general guidelines for component-based weight calculations. While the figures presented are based on industry standards, actual results may vary due to fluctuations in materials. Therefore, we require a physical test in the production environment for final validation. :::ExpandableHeading ### Scope ### Roles and Responsibilities | Name | Responsibilities | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Account Services | - Receive and review system-generated tickets for each work order that errors out or has been placed on-hold by Production.
- Collaborate with relevant departments to identify the root cause of the issue and escalate when necessary.
- Report recurring issues or workflow gaps to management for continuous improvement efforts.
- Determine whether customer input is required for resolution. | ::: *** ### What are Page Breaks? Page breaks matter as every sheet of paper adds weight to a mail piece. Postage rates (especially for USPS First-Class Mail) are based on weight categories - typically in 1-ounce increments (e.g., 1oz, 2oz, 3oz, etc.). If a document or letter has too many pages, the final mail piece could shift into a higher postage category, costing more money and adding difficulty with the reconciliation of final reporting. ### Who is this guide for? This guide can be an essential resource for first time customers. It can help customers understand the formatting of their documents for seamless production, ultimately improving efficiency, and reducing errors across all mail pieces. ### Consistent page break standards help ensure: - Accurate page counts - Accurate postage estimates and final costs - Easier handling for mailing equipment *** ### Standard Package Names & Page Breaks **20# 8.5x11 Plain Paper** | **Package** | **Page Rage** | | ----------- | ------------- | | LETTER | 1-6 | | LETTERHW | 7-9 | | LETTER6X9 | 10-18 | | FLAT | 19-74 | | OVERSIZED | 75+ | \*\*\*Additional Inserts may alter the final page breaks at a customer/job level **24# 8.5x11 Plain Paper** Example: [https://dfsmail.freshdesk.com/a/tickets/207607](https://dfsmail.freshdesk.com/a/tickets/207607) | **Package** | **Page Rage** | | ----------- | ------------- | | LETTER | 1-6 | | LETTERHW | 7-9 | | LETTER6X9 | 10-15 | | FLAT | 16-62 | | OVERSIZED | 63+ | \*\*\*Additional Inserts may alter the final page breaks at a customer/job level ### Additional Packages that may be used **Foreign Packages** | Package Name | | ----------------- | | LETTER-FOREIGN | | LETTER6X9-FOREIGN | | FLAT-FOREIGN | | OVERSIZE-FOREIGN | **Certified** - Certified packages can vary depending on the package setup. - **DCA = LETTER, LETTER-CERT, LETTER-FOREIGN** - LETTER exists for pieces that fail to qualify as certified. - FOREIGN exists for pieces that are noted as foreign. - **Parathon **isn't fully automated and uses a mix of packages that do not include Certified. - Account Services prefers to include CERTIFIED in package names, when possible, like the DCA scenario above. *** ::::ExpandableHeading{isOpen="true"} ### Feedback & Support For questions, corrections, process updates, or additional guidance related to this SOP, please contact the Technical Writing Department using the button below. :::CtaButton{label="Submit a Support Ticket" externalHref="mailto:techwriting@dfsmail.com?subject=Tech%20Writing%3A%20Standard%20Packages%20%26%20Page%20Breaks&body=Hello%2C%20%0A%0A%0AYou%20are%20about%20to%20submit%20a%20request%20to%20update%20this%20document.%20Please%20provide%20all%20required%20details%20below.%0A%0A%0A%0AState%20the%20reason%20for%20this%20change%3A%20%0A-%20Process%20has%20changed%0A-%20Steps%20are%20incorrect%20or%20missing%0A-%20New%20equipment%20or%20system%0A-%20Other%0A%0A%0A%0ADetailed%20description%20of%20the%20requested%20updates%3A%0A%5BList%20the%20exact%20sections%2C%20steps%2C%20screenshots%2C%20or%20wording%20that%20need%20to%20change%5D%0A%0A%0A%0A%0A%0A%0A%0ASupporting%20Material%20(if%20applicable)%3A%20%0A%5BAttach%20photos%2C%20screenshots%2C%20process%20maps%2C%20or%20additional%20details%5D%0A%0A%0A%0A%0A%0A%0AOnce%20submitted%2C%20the%20technical%20writing%20team%20will%20review%20your%20request%20and%20follow%20up%20with%20next%20steps%2C%20timeline%2C%20or%20additional%20questions%20if%20necessary.%20%0A%0A%0A%0AThank%20you%2C%0ATechnical%20Writing%20Department%0A%0A%0A%0A">https://app.archbee.com/docs/INrki-d2ojCDo8iE_yA3V/DRAFT-m8BuSvNJXaEBf-ZrbGuTE" openInNewTab="true"} ::: :::: *** :::ExpandableHeading ### Revision History | Revision Date | Updater Name | Description | | ----------------- | ------------------ | ------------------------- | | June 30, 2025 | Angelica Gonzalez | Initial draft | | December 5, 2025 | Angelica Gonzalez | Edits to links | | February 9, 2026 | Angelica Gonzalez | Updates to glossary words | | February 19, 2026 | Angelica Gonzalez | Updates to document | :::