# Pre-Production Meeting (PPM) Minutes Template

> Source: https://netray.co/tools/pre-production-meeting-ppm-minutes-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Minutes for the pre-production meeting that releases an apparel order to cutting, with approvals, risks and an action list.

## Category

industry-templates

## Industry

Textile & Apparel

## Audience

- Plant manager
- Merchandiser
- Quality manager
- Production manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Factory

**Key:** factory

**Type:** text

**Default:** Sunrise Apparel Pvt Ltd

#### Buyer

**Key:** buyer

**Type:** text

**Default:** Northline Outdoor

#### PO number

**Key:** po

**Type:** text

**Default:** NL-PO-88231

#### Style

**Key:** style

**Type:** text

**Default:** NL-JKT-2217 Men's quilted shell jacket

#### Order quantity

**Key:** qty

**Type:** text

**Default:** 18,000 pcs in 4 colours

#### Ship date

**Key:** ship

**Type:** date

**Default:** 2027-02-12

#### Meeting date

**Key:** meeting_date

**Type:** date

**Default:** 2026-10-20

#### Attendees

**Key:** attendees

**Type:** textarea

**Default:** Merchandiser, production manager, cutting manager, sewing line supervisors, quality manager, planning, buyer QA representative

#### Approval status

**Key:** approvals

**Type:** textarea

**Default:** Fit sample approved Rev 02. Pre-production sample approved with comments. Lab dips approved for 3 of 4 colours. Trim cards signed.

#### Risks and open issues

**Key:** risks

**Type:** textarea

**Default:** Wadding delivery 5 days late. Colour 4 lab dip pending. Taping machine capacity limited to two lines.

**Blocks:**

#### Pre-Production Meeting Minutes

**Body:** Factory: {{factory}}
Buyer: {{buyer}}
PO: {{po}}
Style: {{style}}
Quantity: {{qty}}
Ship date: {{ship}}
Meeting date: {{meeting_date}}

#### Attendees

**Body:** {{attendees}}

#### Approval Status

**Body:** {{approvals}}

#### Readiness Check

**Table:**

**Columns:**

- Item
- Status
- Owner
- Due

**Rows:**

**0:** Fabric in house and inspected

**0:** Trims and labels in house

**0:** Pattern and marker approved

**0:** Line layout and operator skills

**0:** Special machines available

**0:** Packing material and cartons

**0:** Test reports submitted

#### Risks and Open Issues

**Body:** {{risks}}

#### Action List

**Table:**

**Columns:**

- No.
- Action
- Owner
- Due date
- Status

**Rows:**

**0:** 1

**0:** 2

**0:** 3

**0:** 4

#### Release Decision

**Signatures:**

- Production manager
- Quality manager
- Merchandiser
- Buyer representative

**Notes:** Buyer requirements for this meeting differ. Use this as a starting point and add any buyer-specific checkpoints. Minutes should be issued within one working day of the meeting.

## Content

**Intro:** The pre-production meeting decides whether an order is ready to be cut. These minutes capture the approvals, material status, risks and owners so that the sewing floor starts with the same facts as the merchandiser and the buyer.

**Sections:**

#### How to use the minutes

**Body:** Fill in the order header and attendees before the meeting, then update approvals and risks while you talk. During the meeting, complete the readiness check and agree owners and dates in the action list. The release decision is the last step: the production manager and quality manager sign only when blocking items are closed or have a dated plan. Send the exported PDF to everyone the same day.

**Bullets:**

- Hold the meeting before cutting starts
- Bring approved samples to the table
- Name one owner per action
- Date every action
- Do not release with an unplanned blocker

#### What the meeting should settle

**Body:** A good meeting covers sample and fit approvals, fabric and trim availability, pattern and marker plans, line allocation, quality plan with critical points, testing and packing. It is also where you agree what happens if the plan slips. Production release without answers on material and approvals is a frequent cause of late shipment, rework, and costly air freight.

#### Common mistakes and ERP notes

**Body:** Meetings often end without owners, or approvals are verbal and not recorded. Record the approved sample reference and revision so that it can be traced later. In an ERP, the readiness items map to purchase order receipt status, inspection lot status and capacity plan. If the system shows material not received while the meeting assumes it is, resolve that gap before release.

**Cta:** If production release depends on spreadsheets and chasing, we can review how readiness status could be pulled from your ERP before each meeting.

**Faq:**

#### Who must attend a pre-production meeting?

**Answer:** At minimum the merchandiser, production, cutting, sewing, quality, planning and stores or purchasing. Buyer QA often joins for key orders. The aim is to have every function that can block cutting in the room at once.

#### When should the meeting be held?

**Answer:** After the pre-production sample is approved and the fabric and trims are in house, and before cutting begins. Holding it earlier leaves too many unknowns, and later means rework is already in the cut parts.

#### What if the order is not ready?

**Answer:** Record the blockers, owners and due dates, and set a follow-up date. Release in stages if the buyer agrees, for example cutting only the colours with approved lab dips, rather than releasing the whole order.

#### How long should minutes be kept?

**Answer:** Keep them with the order records for at least as long as your buyer agreement or audit scheme requires. They are useful evidence of what was approved, by whom, and when.

## Search terms

pre production meeting template, PPM checklist garment, pre production meeting format, PPM minutes apparel, garment pre-production meeting agenda, PP meeting report, apparel production release checklist, pre-production meeting minutes

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
