Outdoor lighting sample approval should turn a promising fixture sample into a clear project reference for the next build. The safest handoff does not rely on a good-looking sample alone. It records the scene, installation position, beam plan, color plan, voltage input, control preference, surface finish, drawing status and buyer review points in one shared file set.
For landscape, facade, villa, park and hotel projects, this checklist helps buyers and project teams confirm what must stay the same when a sample moves into repeatable outdoor lighting production. It is a planning guide, not a fixed promise about every product or market.
What should be confirmed before a sample becomes the project reference?
| Review area | Buyer question | Safe confirmation record |
|---|
| Project scene | Where will the light be used? | Record facade, path, garden, villa, hotel, plaza, park, tree, sign or mixed outdoor scene. |
| Installation position | How will the fixture sit on site? | Record recessed, spike, wall, pole, base, bracket or bollard-style position before final selection. |
| Lighting effect | What visual result should the sample prove? | Record accent, wall wash, path guidance, tree highlight, entrance focus or broad outdoor projection. |
| Technical inputs | Which parameters guide the review? | Record wattage class, voltage input, beam angle, color temperature, surface finish and control preference as project inputs. |
| File set | Which files should the team follow? | Record approved drawing, sample photo, specification note, project markup and buyer comments by version. |
How does the buyer brief shape the sample review?
| Buyer input | Why it matters | How to write it down |
|---|
| Site role | A pathway edge, tree, facade and entrance need different beam and glare review. | Use one scene name and attach site photos or plan marks when available. |
| Mounting condition | The same fixture family can behave differently in ground, spike, wall or pole positions. | Record mounting direction, fixing surface, cable route and maintenance access. |
| Beam plan | Beam angle changes brightness distribution, glare and visual focus. | Record target distance, target width, aiming direction and preferred beam range. |
| Color plan | Color temperature and finish influence project atmosphere and brand presentation. | Record warm, neutral or cool direction, surface finish, housing color and sample comparison notes. |
| Control preference | Dimming or scene-control needs affect wiring and project coordination. | Record the requested control approach without treating any protocol as a universal default. |
Which sample details should be checked under outdoor project conditions?
| Sample detail | Review point | Decision record |
|---|
| Appearance | Shape, finish, visible screw position, accessory fit and design language. | Approve, revise or hold with photo reference and revision note. |
| Optics | Beam spread, glare direction, target coverage and viewing comfort. | Record beam choice, aiming note and review condition. |
| Electrical input | Voltage input and wiring path must match the project plan. | Record confirmed input, cable direction and connector request. |
| Installation fit | Fixture size, cut-out or bracket condition must match the site detail. | Record drawing version, mounting note and accessory need. |
| Project files | The team needs one reference set before repeatable build confirmation. | Record drawing, photo, specification note and buyer comments together. |
Why can a good sample still create rework later?
| Common gap | What goes wrong | Better control point |
|---|
| Unclear version | Teams follow different drawings or email notes. | Name one approved file set and mark older versions as reference only. |
| Missing site input | The sample looks fine on a desk but not in the real outdoor position. | Review scene, mounting height, target distance and viewing direction together. |
| Loose color note | Finish or light color expectations differ between buyer and factory. | Record color temperature direction, housing finish and sample comparison note. |
| Accessory mismatch | Mounting parts, glare parts or cable details are discussed too late. | Confirm accessory path at the same time as the sample. |
| No release wording | People approve the sample but not the exact build reference. | Use a written release note that names the sample, drawing and remaining open items. |
How should drawings and project files be handed over?
| File type | Purpose | Buyer-side check |
|---|
| Product drawing | Shows size, mounting relation and visible structure. | Check dimensions, installation direction and accessory position. |
| Specification note | Summarizes wattage class, voltage input, beam angle and color plan. | Check that it matches the sample and the project brief. |
| Site markup | Connects fixture choice to facade, path, tree, garden or plaza positions. | Check each fixture family against the intended scene. |
| Sample photo set | Documents appearance and visible finish. | Check that photos include angle, finish and accessory state. |
| Buyer comment sheet | Keeps revision notes and release decisions in one place. | Check open items before moving to repeatable build planning. |
Which product families need sample-to-build confirmation most?
| Fixture family | Typical review focus | Neutral selection path |
|---|
| In-ground lights | Cut-out, depth, beam direction, glare and surface finish. | Review in-ground light options |
| Garden spike lights | Spike position, aiming angle, cable route and landscape target. | Review garden spotlight options |
| Wall and down lights | Wall position, downward beam, facade rhythm and visual comfort. | Review wall light options |
| Outdoor spotlights | Beam plan, bracket direction, glare control and accessory match. | Review outdoor spotlight options |
| Bollard lights | Path spacing, height relation, visual rhythm and landscape fit. | Review bollard light options |
How can OEM and private-mold projects reduce handoff confusion?
| Project type | Useful record | Reason |
|---|
| OEM adaptation | Buyer brief, sample note, drawing revision and finish direction. | Keeps custom requests tied to a clear project file set. |
| Private-mold discussion | Design aim, product-family role, sample review and file ownership discussion. | Separates sourcing model from unverified universal promises. |
| Repeatable family build | Fixture family map, shared appearance language and parameter range. | Helps several fixtures feel consistent across one project. |
| Project coordination | Scene map, installation note, beam plan and buyer comments. | Reduces mismatch between design intent and product selection. |
| Document request | Only files needed for the selected configuration and market. | Avoids assuming that every document exists for every product. |
What should be reviewed before repeatable build confirmation?
| Gate | Pass condition | Open-item signal |
|---|
| Scene fit | The sample matches the real outdoor use case. | Scene, height, surface or target distance is still unclear. |
| Beam fit | The beam plan matches the desired visual effect. | Glare direction, beam range or aiming angle still needs review. |
| Appearance fit | Finish, shape and visible details match buyer expectation. | Finish, housing color or accessory appearance is still undecided. |
| File fit | Drawing, specification note and comments point to the same version. | Different files carry different instructions. |
| Build note | The release note records what is approved and what remains open. | Approval is verbal or scattered across separate messages. |
What related pages help buyers prepare the handoff?
How many sample rounds are usually needed?
The number depends on the project brief, fixture family, design change level and buyer review speed. A simple family selection may need fewer revisions than a custom appearance or private-mold discussion. The safer rule is to count unresolved review points, not sample rounds.
Should sample approval include every final market file?
No. Sample approval should name the files available for the selected configuration and list any remaining file requests separately. Do not treat a general catalogue, one sample or one discussion as proof that every market file is already available.
Can this checklist be used for both standard and custom outdoor lighting?
Yes. Standard selection still needs scene, beam and installation confirmation. Custom or OEM projects also need clearer drawing control, sample notes, appearance review and buyer sign-off records.
