# Planned Order Release Lead Time Calculator

> Source: https://netray.co/tools/planned-order-release-lead-time-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Add setup, run, queue, safety and inspection time to find how many calendar days before the need date an order must be released.

## Category

supply-chain

## Audience

- Production planner
- Scheduler
- ERP consultant

## Tool

**Kind:** calculator

**Inputs:**

#### Order quantity

**Key:** order_qty

**Type:** number

**Default:** 500

**Min:** 1

**Step:** 10

**Unit:** units

#### Fixed time (setup and paperwork)

**Key:** setup_days

**Type:** number

**Default:** 1

**Min:** 0

**Step:** 0.5

**Unit:** work days

#### Run time per unit

**Key:** run_hours

**Type:** number

**Default:** 0.05

**Min:** 0

**Step:** 0.01

**Unit:** hours

#### Productive hours per day

**Key:** hours_day

**Type:** number

**Default:** 7

**Min:** 1

**Max:** 24

**Step:** 0.5

**Unit:** hours

**Help:** Available hours at the constraint after efficiency

#### Queue and move time

**Key:** queue_days

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

**Unit:** work days

#### Inspection and put-away

**Key:** inspect_days

**Type:** number

**Default:** 1

**Min:** 0

**Step:** 0.5

**Unit:** work days

#### Safety lead time

**Key:** safety_days

**Type:** number

**Default:** 1

**Min:** 0

**Step:** 0.5

**Unit:** work days

#### Working days per week

**Key:** week_days

**Type:** select

**Default:** 5

**Options:**

##### 5 days

**Value:** 5

##### 6 days

**Value:** 6

##### 7 days

**Value:** 7

**Outputs:**

#### Run time in working days

**Key:** run_days

**Expr:** order_qty * run_hours / hours_day

**Format:** decimal

#### Total lead time in working days

**Key:** work_days

**Expr:** setup_days + run_days + queue_days + inspect_days + safety_days

**Format:** decimal

**Primary:** true

**Description:** Sum of all lead time elements

#### Calendar days before need date

**Key:** cal_days

**Expr:** ceil(work_days * 7 / week_days)

**Format:** days

**Primary:** true

**Description:** Ignores public holidays and shutdowns

#### Lead time in weeks

**Key:** weeks

**Expr:** cal_days / 7

**Format:** weeks

#### Share of lead time that is non-run

**Key:** fixed_share

**Expr:** if(gt(work_days, 0), (work_days - run_days) / work_days * 100, 0)

**Format:** percent

**Description:** High share means queue and waiting dominate

**Chart:**

#### Lead time vs order quantity

**Type:** line

**X:** order_qty

**From:** 10

**To:** 3000

**Steps:** 30

**Series:**

- work_days

**Disclaimer:** A planning approximation. Calendar conversion uses a simple ratio and ignores holidays, shutdowns and overlap between operations. Use your ERP calendar for final dates.

## Content

**Intro:** MRP subtracts lead time from the need date to find when an order must start. If the lead time is wrong, every planned release is early or late. This calculator builds the lead time from its parts.

**Sections:**

#### How to use it

**Body:** Enter the order quantity, the fixed time per order such as setup and paperwork, and the run time per unit. Add queue and move time, inspection and put-away, and any safety lead time. Select how many days per week the plant works. The result shows total working days and the calendar days before the need date to release the order. The chart shows how lead time grows with order size.

#### The formula

**Body:** Total working days equal fixed time plus quantity times run hours divided by productive hours per day, plus queue, inspection and safety time. Calendar days are working days times 7 divided by working days per week, rounded up. Many ERPs store a fixed lead time and a variable lead time per unit separately, which matches this split. Entering the same two values in your item or routing data lets the system scale lead time with lot size.

#### Reading the result and common mistakes

**Body:** If the non-run share is above half, most of the lead time is waiting rather than work, so shorter queues or smaller batches help more than faster machines.

**Bullets:**

- Using one fixed lead time for very different lot sizes.
- Counting calendar days where the ERP expects working days, or the reverse.
- Forgetting inspection or receiving time on purchased items.
- Stacking safety lead time at every BOM level.
- Taking nameplate hours rather than productive hours.

**Cta:** If you want lead times proposed from your actual shop order and receipt history, we can analyse that read-only from your ERP.

**Faq:**

#### What is the difference between fixed and variable lead time?

**Answer:** Fixed lead time is the part that does not change with lot size, such as setup, queue and inspection. Variable lead time scales with quantity, such as run time per unit. Separating them lets the system give a realistic lead time for both small and large orders.

#### Why does safety lead time matter?

**Answer:** It releases an order earlier than the pure calculation so that normal delays do not make it late. It reduces late deliveries but also raises stock and work in progress, so use it sparingly and not at every level of the BOM.

#### How are working days turned into calendar days?

**Answer:** Multiply working days by 7 and divide by working days per week. For example 10 working days on a 5-day week is 14 calendar days. This ignores holidays, so check the result against your plant calendar.

#### Does this work for purchased items?

**Answer:** Yes. Use the supplier lead time as the fixed time, set run time to zero, and add receiving and inspection time. If the supplier quotes calendar days, set working days per week to 7.

## Search terms

planned order lead time calculator, mrp lead time offset, order release date calculator, manufacturing lead time formula, working days to calendar days, backward scheduling calculator, queue time setup time run time, lot size and lead time

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