Custom Shabbat Lighting: From Brief to Certification

When a community centre, hotel group or distributor needs Shabbat lighting that no catalogue product matches — a specific finish to match a sanctuary, a fixed dimension to fit a recess, a branded run for retail — the answer is a bespoke project. Bespoke lighting is manufactured, not selected, and it succeeds or fails on process. This is how a well-run project is sequenced, and what you should prepare at each stage.

Stage 1 — Design brief

Everything downstream depends on the brief. A useful brief covers:

• The setting and the mounting — where the fixture goes and how it is fixed.
• Dimensions and clearances — the physical envelope it must fit.
• Materials and finish — and any existing fittings it must match.
• Light source and output target — task, ambient or decorative; desired range.
• Mechanism requirement — a written statement that the design must be purely mechanical, if that is required.
• Branding — logo, labelling and packaging, if applicable.
• Quantity and destination — for both pricing and logistics.

Submit this in writing. A brief that lives in a phone call produces a prototype that misses the point.

Stage 2 — Prototyping

The supplier produces a functional prototype from the brief. This is the stage where design intent becomes a physical object, and where assumptions surface:

• Does the mechanism move smoothly across its full range?
• Does the finish match the intended environment?
• Does the fixture fit the intended recess or surface?
• Does the light level reach the level the project actually needs?

Treat the prototype as a review object, not a formality. Changes are cheapest here and most expensive after tooling and batch production.

Stage 3 — Rabbinic review

For a compliance-driven project, the prototype is the point at which your Rabbinic authority reviews the actual design — not a marketing description. Two practical notes:

• Review and certification are usually per design or per run, so the review should name the model the project will receive.
• If your project serves a specific community, that community’s authority may be the relevant reviewer.

Running technical acceptance and Rabbinic review in parallel shortens the project; running them sequentially lengthens it.

Stage 4 — Certification

Where certification applies, it is issued by an authority against the reviewed design, and documentation should be provided for the specific run. Not every project requires third-party certification — some require only the buyer’s own community approval — and the project brief should state which is expected.

Stage 5 — Fulfilment and batch production

With the design frozen and reviewed, production and delivery follow:

• batch production to the approved specification
• quality checks against the prototype
• packaging per the agreed requirement
• freight and delivery terms arranged for the destination

What to prepare before you start

• A written brief (see Stage 1).
• Contact details for your technical reviewer and Rabbinic authority.
• Reference imagery for finish and setting.
• Branding assets and packaging requirements, if any.
• A realistic schedule that allows for review, not just manufacturing.

Common mistakes

• Approving a prototype informally. Get written approval from every reviewer before production.
• Assuming certification transfers. A listing for one model does not automatically cover a bespoke variant.
• Leaving branding to the end. Artwork and packaging affect tooling and schedule.
• Treating a quote as a schedule. Production and freight sit on top of quoting time.

A note on halachic questions

Certification decisions rest with the recognised authority or your community’s Rabbinic reviewers, and different bodies may evaluate a design differently. This article describes the project process; it does not issue compliance determinations.

Budgeting and scheduling a bespoke project

A bespoke engagement has more cost lines than a catalogue purchase, and each should appear in the quotation:

• Design and engineering — turning a brief into a buildable specification.
• Prototyping — one or more physical units for review.
• Tooling — where a new part or profile is required.
• Certification and review — the time and cost of Rabbinic review and any formal certification.
• Batch production — scaled from the approved prototype.
• Packaging — standard, retail-ready or branded.
• Freight and clearance — to the destination.

Schedule review and manufacturing as parallel tracks wherever possible. The most common cause of delay is treating Rabbinic review as a step that happens after the prototype is approved, rather than alongside technical acceptance.

What a good approval looks like

Approval is not a reply that says “looks good”. A project is protected when:

• the specification carries a version number, and the version under review is stated;
• technical acceptance and Rabbinic review are recorded separately, by name and date;
• open questions are listed explicitly rather than resolved verbally;
• the production release references the approved version;
• any change after approval triggers a re-review of the changed element.

Written approvals cost an hour and prevent the two most expensive failures in bespoke manufacturing: producing the wrong design at scale, and producing a design that no longer matches the certification it was reviewed against.

Documents to keep on file

For institutional and large bespoke orders, a complete project file protects both sides long after delivery:

• the versioned specification that production was released against;
• prototype photographs and sign-off, dated;
• technical acceptance and Rabbinic review records;
• the certification document for the run, where applicable;
• packaging artwork approval, if branded;
• the quotation and delivery terms actually agreed.

If a reorder or a warranty question arises later, these documents answer it without relying on anyone’s memory — and they make a second run reproducible rather than a fresh negotiation.