Private-Label LED Mask Manufacturing: The Stage-Gate Process from Brief to Pilot Run

Table of Contents

• 1. A Timeline Is Not a Gate
• 2. The Five Stages and Their Exits
• 3. Three Gates That Get Skipped Most Often
• 4. Keep an Open-Item Register
• 5. Commercial Gates, Including Ours
• 6. How We Run a Stage-Gate Project
• 7. References & External Links

---

1. A Timeline Is Not a Gate

Most manufacturing schedules are drawn as a line with five boxes on it. They are useful for telling everyone when to be busy, and useless for telling anyone when to stop. A line moves forward by itself; a gate only opens when something specific is true.

The difference shows up in the way open questions are treated. On a timeline, an unanswered question sits in someone’s inbox while the project advances past it, and by the time it is answered the decision it belonged to has already been made by default. At a gate, the question has to be named and given an owner before anyone moves.

So the discipline is small and unglamorous: for each stage, decide what comes in, what must come out, who signs it off, and what has to be true for the next stage to start. Then hold the line on the fourth item, which is the only one under pressure.

---

2. The Five Stages and Their Exits

Five stages cover a private-label project. The third column is the one that turns a plan into a gate, and the fourth is the one teams forget to assign until the meeting where it matters.

Stage	Deliverable	Exit Criterion	Approval Owner
1. Product brief	Intended use, target user, market, key requirements, packaging, customisation level and commercial scope.	Mandatory requirements are separated from open design questions, and ownership of artwork, specifications, IP and market documents is named.	Product owner
2. Feasibility and quotation	A quotation with technical dependencies, tooling, component lead times, test needs, exclusions and risks identified.	It is explicit whether the price is based on an existing design or new development, and the schedule’s dependencies are defined.	Operations lead
3. Sample approval	Acceptance criteria written before arrival, and an evaluation of function, fit, finish, controls, packaging, documentation and test results.	Deviations are recorded and each has a written decision — not a visual nod that quietly substitutes for technical or safety verification.	Product and quality
4. Pilot and release readiness	Final bill of materials, product revision, production test plan, inspection criteria, packaging and user information.	Test documents correspond to the approved configuration, nonconforming units have a defined path, and release authority is named[2].	Quality and regulatory
5. Post-approval change	A record of changes to components, tooling, firmware, labelling or suppliers, with their effect assessed.	One approved version of each controlled file, and stock already produced has been considered rather than discovered.	Quality

---

3. Three Gates That Get Skipped Most Often

In practice, three specific exits are the ones that get waved through. They share a cause: each can be satisfied by an impression rather than a document.

• Sample approval by appearance. The sample looks right, feels right, photographs well — so it is approved. Function, controls, packaging and the test results themselves are assumed rather than checked. A visual approval is a legitimate part of the decision and it is not a technical or safety verification; letting it stand in for one is the most common way a project enters production with an unverified product.
• Test documents for the wrong configuration. Reports exist, so the stage is marked complete, even though the report describes an earlier revision, a sibling model or a hand-built prototype. The exit criterion is not “a report exists” but “a report corresponds to the configuration you are about to produce”.
• Post-approval change handled informally. A part is substituted, a firmware version is bumped, a label is corrected — each is small, each is sensible, and none is recorded against the stock already made. By the time the difference is noticed, you may be holding two configurations under one part number.

The remedy in all three cases is the same and it is cheap: an exit criterion written as evidence rather than as a state. “Sample approved” is a state. “Sample approved against eight written criteria, with two deviations recorded and dispositioned” is evidence.

---

4. Keep an Open-Item Register

Gate discipline collapses in the same way every time: someone asks whether a stage is done, and the answer is a discussion instead of a document. An open-item register fixes that with five fields per item, maintained from stage one.

• The open question, in one sentence. Written so that “resolved” will be obvious to someone who was not in the meeting.
• The stage it blocks. An item that blocks nothing is information; an item that blocks a gate is a decision waiting to happen.
• Who owns the answer — a person, on a named side of the relationship. Not a department, and not “the supplier”.
• What evidence would close it. A document, a measurement, a written decision. Without this the item will be closed by reassurance.
• The disposition if it stays open. Proceed with a recorded risk, hold the gate, or descope. Deciding this in advance is what stops an open item from quietly becoming a permanent assumption.

Read the register at every gate and keep it after launch. Most of what a team learns in the first year is already written in it, if anyone kept it.

---

5. Commercial Gates, Including Ours

Commercial terms are gates too, and they deserve the same evidence standard. Rainbowdo reports a starting MOQ of 500 units and a stated monthly capacity of 100,000 units. Both belong in the commercial planning discussion, and neither should be treated as a commitment until the quotation says so.

• The quotation should confirm the selected model and customisation scope, because a price for a family is not a price for your configuration.
• It should state the packaging, since packaging is a separate cost line and often a separate minimum.
• It should split pilot and production quantities, so the pilot gate can be funded and scheduled as its own step rather than absorbed into a bulk order.
• It should name the available production window, not the monthly capacity. Those are different numbers, and only one of them describes your order.
• It should list the conditions that could affect delivery — material availability, tooling readiness, your own approval timeline. A committed lead time cannot be inferred from capacity alone.

This is the least dramatic part of a stage-gate process and the one that most often decides whether the launch date holds: a quotation that answers five questions in writing is worth more than a schedule with five dates on it.

Structuring a private-label project? Visit our
Custom Light Therapy Manufacturing Page.

---

6. How We Run a Stage-Gate Project

Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility. A project works best when both sides arrive with the same four fields per stage, so this is what we bring to each gate:

• A feasibility response that names the dependencies — tooling, component lead times, test needs and exclusions — instead of a schedule with no assumptions attached.
• Sample evaluation against your written criteria, with deviations listed and a written decision requested for each one.
• Test documents that identify the configuration, so the release-readiness gate can be judged on evidence rather than on the existence of a file.
• A change record after approval, including the effect on stock already produced.
• Sample and small-batch production from 500 units, with a stated capacity of 100,000 units per month; both figures depend on model, configuration, packaging and schedule, and are confirmed in a formal quotation.
• Compliance documentation matched to the exact model for your target market. Where a model holds a 510(k) record we provide the K-number so you can check its scope in the FDA’s public database; clearance is not the same as FDA approval, and the scope differs from model to model.

---

7. References & External Links