A linear luminaire can look resolved on a reflected ceiling plan long before it is ready to be specified.
The drawing may show a clean line, a fixture tag and an overall length. Then coordination begins. The architect needs the actual ceiling opening. The electrical engineer wants to know where the driver sits and which control protocol has been selected. The lighting designer needs photometry for the specified optic, not a generic file for the product family. On a continuous run, somebody has to establish where the sections divide and where power enters. If the line becomes a circle or a curve, even the basic geometry can become ambiguous: outside diameter, inside diameter or centerline?
These are not unusual exceptions. They are what happens when a luminaire moves from design intent into a building.
A useful linear luminaire cutsheet has to survive that transition. It does not need to contain every drawing, test report or installation instruction associated with the product. It does need to identify the configuration being specified, show the information that materially affects selection and coordination, and make clear where the rest of the technical record can be found.
For a standard individual fixture, that may be straightforward. For a recessed continuous run, a large suspended ring or a custom curved system, the cutsheet is usually the first layer of a larger documentation package.
Identify the Exact Luminaire Configuration
A product family can contain several profile sizes, outputs, optics, finishes, colour temperatures and control options. Naming the family does not yet establish what will be ordered, coordinated or installed.
The cutsheet should therefore provide a clear route from family to configuration. Depending on the manufacturer, that may be an ordering code, a configured model number or a selection table that shows the chosen values without forcing the reviewer to infer them.
That matters because downstream information can change with the selection. A different optic can require different photometry. A different control protocol can mean a different driver. A different mounting condition can change the hardware and architectural preparation.
A reviewer should be able to answer a simple question without cross-reading three unrelated PDFs:
Which configuration of this family are we actually approving?
Document revision and date are useful for the same reason. A technically correct sheet can still be the wrong sheet if it describes an obsolete configuration or earlier product revision.
Check the Mechanical and Installation Information
Width, height and length belong on a cutsheet, but their value is not in filling three cells of a table. They matter because something else has to fit around them.
For a suspended luminaire, profile dimensions establish physical scale and can influence sightlines, ceiling clearance and suspension geometry. For a recessed system, the coordination becomes more sensitive: housing width, visible aperture and ceiling cutout are not necessarily the same dimension. A nominal width without the relevant interface dimension can leave the ceiling contractor to infer the opening.
Useful mechanical information may therefore include:
- housing or profile width and height;
- overall or nominal fixture length;
- visible luminous aperture;
- required cutout or opening where applicable;
- principal housing and optical materials;
- finish;
- weight where support or handling is affected;
- end conditions that change the visible or installation dimension.
Curved and circular products need an additional discipline: the dimensional reference itself must be defined. A ring described only as “3 m diameter” is not fully resolved if the drawing does not state whether that means outside diameter, inside diameter or centerline diameter.
Continuous runs create a similar distinction between architectural length and manufacturable length. The RCP may show one uninterrupted line; production, transport and installation may require several sections.
The dimension is useful only when the project team knows what it governs.
“Suspended” Is a Mounting Category, Not an Installation Detail
Mounting descriptions can be technically correct and still leave the project unresolved.
These views compare external installation types. Use the selected model’s detail for actual openings, fixings and service access.
A large pendant ring may indeed be suspended. That tells the specifier very little about how many suspension points are involved, where power enters, how the canopy is arranged or whether the fitting is shipped as one piece or several.
A recessed system asks different questions. What is the ceiling interface? Is there a required opening? Does the housing need access from above? Where is the driver? Can it still be serviced after the ceiling closes? Does the interface change between gypsum board, acoustic ceiling and joinery?
The cutsheet does not need a construction drawing for every condition. It should make the applicable mounting method unambiguous and point to the detail that resolves the interface.
That is the point at which product information begins to become architectural coordination.
Review Photometric and Electrical Evidence
Lighting data can look precise while still being too generic for a project decision.
A cutsheet may state wattage, delivered lumens, efficacy, CCT, CRI and beam angle. Those numbers are useful only if the reviewer understands which configuration they describe.
State the conditions behind a performance value. If a family contains several lengths, optics or outputs, one generic performance table may not represent every possible configuration.
For calculated projects, the cutsheet should therefore make it easy to identify the relevant optical condition and locate the appropriate IES or LDT file where available. The point is not simply to prove that “photometry exists”; it is to know that the photometry is sufficiently representative of the product under review.
Colour Data and Glare Information Need Their Own Context
Not every lighting metric belongs in the same category.
Record the colour-rendering data required by the project and identify the selected source or luminaire configuration. Additional colour-quality documentation may be relevant to a particular application; do not turn every available metric into a universal cutsheet requirement.
UGR requires still more caution. A single glare figure can be attractive in a comparison table, but glare evaluation depends on distribution, room geometry, layout and viewing conditions. Where visual comfort is a design priority, the documentation should provide enough photometric information for the actual application to be evaluated rather than treating one number as a universal property of the product.
The cutsheet should support analysis, not replace it.
Electrical Data Should Describe the Supplied Condition
A luminaire eventually has to connect to a power system, and the driver is part of that interface.
The basic electrical block should identify the input voltage and relevant power data. It should also make clear, where applicable, whether the driver is integral or remote and provide enough driver identification for compatibility, access and maintenance to be reviewed.
For a straightforward pendant, the selected input, driver and control information may answer much of the initial electrical question. On a long continuous system or large feature installation, it may not. Driver grouping, remote-driver location, feed arrangement and service access can become project-specific coordination issues.
The rule is simple: state what is actually supplied for the selected configuration, not every electrical option the family might theoretically support.
“Dimmable” Is Not a Control Specification
The same discipline applies to controls.
A cutsheet that says only “dimmable” still leaves the most important question unanswered: dimmable by what system?
The selected protocol might be 0–10V, DALI, phase dimming or another control method. The relevant driver has to support it, and the building controls team has to know what interface is being coordinated.
Where dimming is part of the order code, the selected method should be visible in the configuration. Where additional control modules, gateways, emergency functions or sensors are required, they should be identified through verified supporting documentation rather than implied by a generic product-family statement.
This is one area where a concise cutsheet can be stronger than a crowded one. The document does not need to reproduce the entire driver manual. It needs to tell the reviewer exactly which control condition applies and where the detailed driver data can be found.
The CIE description of UGR explicitly includes observer position and direction of view and distinguishes tables based on standard conditions. See the UGR diffuser guide for the component-versus-application boundary.
Verify Ratings and Supporting Documents
IP, IK, safety listings, operating conditions and warranties are useful only when their scope is understood.
An IP rating can help establish environmental suitability, but it does not answer every regulatory question. A certification may apply to a specific model, size, component arrangement or market; it should not automatically be extended to every configuration in a family.
For international B2B projects, the cutsheet should therefore distinguish between:
- a verified product characteristic;
- an available option;
- a project- or market-specific compliance requirement;
- a claim that still requires supporting certification or test evidence.
A professional cutsheet makes compliance easier to verify without making the claim broader than the evidence.
A Cutsheet Is Part of a Technical Record, Not the Whole Record
The word cutsheet is often used interchangeably with specification sheet or technical datasheet. In practice, it sits between two different kinds of information.
On one side is the brochure: useful for presenting the family, applications and appearance, but rarely sufficient for technical approval. On the other is the deeper project record—photometric files, driver documentation, installation instructions, CAD/BIM resources, certificates and, where required, project-specific shop drawings.
Trying to compress all of that into one PDF does not necessarily make the documentation better. It can make the information harder to trace.
The cutsheet is therefore best understood as the entry point to the technical record. Its job is not to replace every supporting document. Its job is to make the selected product traceable through them.
Keep Custom Geometry and Project Records Traceable
A standard fixture can often be described as a discrete object.
Continuous linear lighting is different. Architecturally, the object may be one line. Manufacturing and installation may divide it into profiles, diffusers, LED boards, drivers, joiners, feeds and mounting points.
That difference is easy to hide on an RCP. It becomes impossible to ignore on site.
Imagine a 12 m suspended run divided into five manufacturable sections. The overall length does not tell the installer where the joints occur. A power requirement does not identify the feed position. “Suspended” does not establish the suspension locations. A driver specification does not show how drivers are grouped or where they remain accessible.
For a continuous system, the technical package may therefore need to resolve:
run length → module lengths → joint positions → power feeds → driver grouping → suspension or mounting locations → end conditions → assembly sequence.
Some of that information may be suitable for the standard cutsheet. Much of it may belong in installation documentation or a project-specific shop drawing.
The important point is that the project team can see the boundary. A catalogue option such as “continuous run” should not conceal the coordination work required to turn that option into a buildable system.
Curves and Rings Turn Product Data Into Project Geometry
Custom geometry exposes the limits of generic catalogue documentation even more quickly.
A straight linear luminaire may be defined through family, length and mounting. A curved run adds radius. A ring adds diameter. An oval can require several geometric references. Once the size exceeds practical manufacturing, packaging or transport constraints, segmentation follows.
Then the project starts asking questions that do not exist on a standard straight fixture:
- What dimension governs production: OD, ID or centerline?
- Where does each section start and stop?
- Where will the joints be visible?
- Where does power enter?
- How many suspension points are required, and where?
- How are the sections identified for field assembly?
- Where are the drivers, and how are they accessed?
This is also where a sample or mockup can become useful—not as an automatic requirement, but where drawings and calculations leave meaningful uncertainty around a joint, diffuser continuity, finish, brightness relationship or architectural interface.
The cutsheet can define the product platform. The project drawing has to define the project.
What Is Often Missing Is Not Data, but Traceability
The weakest cutsheets are not always the ones with the fewest numbers.
Often, the information exists but the relationship between the pieces is unclear. A product family is shown, but the selected configuration is not. An IES file exists, but the sheet does not identify which optic it represents. The housing width is stated, but the ceiling opening is not. Dimming is offered, but the selected driver is unidentified. A custom-length run is possible, but no document shows how it will be segmented or fed.
These gaps create decisions downstream.
The architect assumes the opening. The electrical engineer assumes control compatibility. The contractor chooses a feed position. The installer discovers a joint where the design team did not expect one.
By then, a documentation gap has become a coordination issue.
A strong cutsheet therefore does more than carry data. It helps the reviewer trace each important claim back to the selected configuration and forward to the next required document.
Use the curved profile geometry guide to clarify the dimensional reference, then carry the selected configuration into the project drawing and delivery record.
Use the Cutsheet to Close the Remaining Questions
This checklist separates broadly useful information from fields that become necessary only when the application demands them.
The list is deliberately not reduced to a universal “20 mandatory fields.” Linear lighting changes category as it becomes more integrated, continuous or customised. The documentation has to change with it.
Before Approval, Ask What Is Still Unresolved
The most productive submittal review is not a search for a perfectly populated PDF. It is a search for assumptions.
Does the ordering code describe the configuration shown in the schedule? Does the photometry belong to that configuration? Has the ceiling interface been defined? Does the control method match the selected driver? For a continuous run, are the modules, joints and feeds resolved? For a ring or curve, is the controlling geometry unambiguous?
Then ask one final question:
Which answers belong on the cutsheet, and which require another project document?
That question keeps the cutsheet concise without allowing the technical record to become incomplete.
Machine-readable data remains a proposal to evaluate
In his August 2026 ARC article on the Universal Luminaire Cutsheet, Foad Shafighi proposes a machine-readable schema alongside familiar product documents. It is an evolving proposal, not a universal regulatory requirement. The immediate review task remains the same: trace the selected configuration to its original supporting evidence.
Discuss the documentation for your selected system. Identify the series or model, optical arrangement, mounting interface and intended supply scope, together with the specific documents still needed. For a North American product programme, include the destination market and identify which team is responsible for the final assembly and its applicable approvals; a profile or optical-kit document alone does not establish those approvals. Use the custom profile inquiry checklist if the configuration is still being defined.
