1. Kitting & Assembly
  2. Features
  3. Build planning
Feature · Build planning

Build planning

A build plan ties demand to a quantity the team can make and a date by which the components and people should be ready. Warehouse Manager creates a kit work order for the intended output product and storage location. An order line may link the build to a dealer commitment. Planned start and end dates give the team a schedule to review, while the work order status distinguishes a draft from released work.

OverviewMy kit builds
Kitting & Assembly · Build planning

My kit builds

Kit builds

New
Work order numberStatusPlanned startPlanned endPlanned quantityManager
KB-67313Draft16 Oct18 Oct460
KB-41926Pending approval24 Oct30 Oct470
KB-60639Released27 Oct02 Nov870
KB-76696In progress12 Oct20 Oct750
KB-26639Partially completed08 Oct11 Oct900
6 of 6 records
KB-67313Kit builds · KB-67313
Draft
Planned start16 Oct
Planned end18 Oct
Planned quantity460
Example screen with sample data

What you can do

Make the release decision explicit

Release is the point at which the selected bill, routing, output product and standard cost become the work’s basis. The manager checks that each belongs to the correct organization, that planned quantity is positive and that the chosen versions are effective. The approval decision records who accepted that scope. A released work order also records when release happened. Operators can then use its frozen instructions instead of interpreting a changing master record.

A request for fifty promotional kits may be covered by one build or several planned builds. The sales order line gives the demand context, but the warehouse still has to assess component availability for the planned dates. A build number by itself does not consume components. Reservations and actual issues are separate records.

How the work is organized

  • Demand link. A kit work order can point to the sales order line that explains why output is needed.
  • Planned scope. Quantity, dates, product, warehouse, bill, routing and output standard form the release basis.
  • Decision. The assigned manager and an independent review decision keep release separate from preparation.

What to agree during setup

Agree who prepares work orders and who decides release in each organization. Set a rule for how far ahead to plan kits when supplier dates or dealer promises change. Confirm which storage location receives finished output and which area holds production components. The warehouse should rehearse both a fully supplied build and one whose component position is held.

If a dealer changes an order after planning, assess the difference against the current build quantity. Do not silently expand a released work order to absorb more demand. The new scope needs its own reviewed basis. The planned dates should remain distinct from actual operation start and end times so the team can explain late work.

Check the handoff on an actual case

Use a dealer order with one kit line and a promised delivery date. Create a draft build with a quantity that covers a defined portion of that order. Confirm the output item, bill version, route, standard and destination. Compare its required components to available positions, including reservations already held for other orders. Submit the build for approval. The Warehouse Manager should be able to reject a wrong bill or incomplete cost basis and release a corrected revision with clear evidence.

What your team sees

  • Kit builds awaiting release — Planned builds needing a manager’s decision before component issue.
  • Build schedule — Released and active work arranged by planned start and end.
  • My kit builds — Work assigned to the current manager.

Follow the work through

What it keeps track of

Data model
Kit builds
Released bounded assembly/kitting/repacking, without plant APS or payroll scope.
Sales order lines
Bounded accepted quantity/value and retained original promise.
BO ms
Effective distribution assembly/repacking recipes with explicit output basis.
Production routings
Versioned assembly/repacking instructions, distinct from delivery routes.
Standard costs
Entity/product standard per base unit with immutable effective versions.
Stock items
Trade goods and assembly outputs; master values do not rewrite transactions.
Storage locations
Physical sites may host segregated entity-owned positions; legal owner stays on each position.
Review decisions
Authoritative human decisions independent of document lifecycle.
Document revisions
Immutable typed document snapshots and source basis.

Who uses it

Permissions
Warehouse Manager
Plans and reviews kit release.
Sales Representative
Supplies order context.
Purchasing Manager
Follows component needs.
Finance Manager
Reviews cost exceptions.

Set up Kitting & Assembly your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started