Create FPO


Pending

In Progress

QC (Inspection)

Ready / Delivered

Factory Operations Procedure

OPERATIONAL CONSTITUTION & WORKFLOW GOVERNANCE

SECTION 1 — PURPOSE

This document defines the official operating system of the Custom Office production environment. It establishes mandatory communication channels, workflow authority, accountability rules, and production execution logic.

The objective is to eliminate: Information loss, order ambiguity, internal blame disputes, and production inefficiency.

SECTION 2 — CORE PRINCIPLE

The system is the authority. Not memory. Not hierarchy. Not conversation.

Any instruction not recorded in the digital Shop Floor Control (SFC) system is operationally invalid.

SECTION 3 — SINGLE SOURCE OF TRUTH RULE

All orders must originate and exist inside the Production Control System.

Prohibited channels for order instructions: WhatsApp/text messages, verbal requests, emails directly to the Foreman, sticky notes.

Enforcement: If instructions arrive through these channels, they must be rejected by production until entered by Sales.

SECTION 4 — ORDER VALIDATION PROTOCOL & FPO

No order is accepted into the queue unless it contains mandatory data fields. Sales must utilize the standardized Factory Production Order (FPO) format.

💡 Click highlighted fields to type before printing

FACTORY PRODUCTION ORDER (FPO)

Client/Ref:
Date Req:
Date Del:
SKUQTYDescriptionSizeHandleRunnerPortholeMaterial
Sign off Draftsman:

SECTION 5 — ROLE AUTHORITY MATRIX

RoleSystem Authority
SalesCreate and edit orders only. Cannot alter production status.
ForemanStart production, Block orders, Send to QC. Cannot create orders.
QCApprove (mark Ready) or Reject (send back to Progress).
DispatchRelease and deliver completed items.

SECTION 6 — STATE TRANSITION LAW & FLOWCHART

Orders move through rigid states. They cannot skip steps or reverse unless officially rejected by QC.

LIFECYCLE OF AN ORDER

Sales Input (Validated Data)
PENDING
Foreman Starts Job
BLOCKED
IN PROGRESS
QC Rejects
Foreman sends to QC
QC INSPECTION
QC Approves
READY

SECTION 7 — ERROR RESPONSIBILITY AUTOMATION

Error TypeResponsible Party
Wrong specs entered into system/FPOSales
Incorrect build matching system specsProduction
Quality failure shipped to clientQC

SECTION 8 — VIOLATION CONSEQUENCES

FINAL DIRECTIVE
This FOP is not mere documentation. It is operational law.
Compliance is not cultural; compliance is structural.