Before any fixture goes up, compare each delivered variant's identifiers with the zone schedule your project has confirmed. Assign a variant to a zone only when the records actually connect the two. A shared family name or a carton that looks like the others does not count as a match.
When no shared identifier or documented cross-reference links a received variant to a schedule entry, mark it unresolved. Leave it unassigned until the designated project reviewer confirms its zone in writing. That one rule is the core of fixture schedule verification at delivery.
Match each delivered variant to a zone—or hold it
Each received variant should leave receiving with one of two statuses: matched to a named schedule type and zone, or unresolved. When sorting general commercial lighting shipments at the dock, start from the schedule side, because that is where the zone assignment lives.
Schedules differ by project. In one Paulding County electrical specification, a project-specific lighting-fixture schedule lists the fixture type and location for each fixture, and required fixtures must follow the schedule shown on the drawing. Work from the fields your own schedule contains. The zones themselves come out of earlier planning, such as mapping lighting zones by mounting context and controls. Receiving confirms those assignments rather than reinterpreting them.
- Identify the received variant. Copy the full identifier from the fixture label or carton, such as the manufacturer part number or catalog string. The series name alone is not enough.
- Find the schedule entry it should fill. Locate the type designation and its listed zone or location in the schedule revision confirmed for this delivery.
- Test the link. Look for the same identifier in both places, or a documented cross-reference, such as an approved submittal or order line, that ties the part number to that type.
- Record the status. If matched, write the schedule type and zone next to the variant. If unresolved, write what is missing or conflicting and keep those cartons out of zone staging.
Family names fail this test for a simple reason. Two cartons can carry the same series name and packaging while holding different configurations, and that difference may be what separates one scheduled type from another. If the received item is a different product from the one scheduled, treat it as a substitution and run a commercial lighting substitution review before it gets a zone.
Identify the schedule revision tied to this delivery
Use the schedule revision the project has confirmed for this delivery, not the newest file in the folder. Name it in your receiving record before you compare a single carton.
Confirm the project record and revision
Your goal is one named schedule reference with its revision and approval status, or an open question logged for the reviewer.
- Write down the schedule title or drawing reference, plus the revision number or date and any approval status shown on it.
- Check whether the order, the approved submittal, or another project record names that same reference. Count the connection only when a record states it explicitly.
- If nothing ties this delivery to a revision, ask the designated project reviewer which one applies. Log the revision as unresolved until you have the answer.
Some project documents make these fields easy to find. Arapahoe Community College's lighting remodel specifies submittal revision and approval fields: each submittal identifier includes a revision identifier and, where appropriate, the installation location. Only final submittals marked with the project's approval notation may be used, and its product schedule lists product type, unique identifier, manufacturer and model, room, and location. Those rules belong to that project, so note whatever equivalent fields your documents use.
Resolve conflicting versions without guessing
A newer-looking file, a later order date, or a matching family name does not prove which revision governs a delivery. A schedule revised after the order was placed might change a type or location, or it might not affect this shipment at all. Only the project can say which. Keep revision applicability separate from the label check, too. As an illustrative case, a carton could match a row on one revision and fail on the next, so a label match means little until the revision question is settled. When approved records conflict, record both references and request a written, project-specific decision before using either one.
Trace variants across records and split deliveries
Build a cross-reference for each variant using only the identifiers your records share. Don't expect the order, packing list, carton, or fixture label to show a zone; the path to a zone runs through the schedule entry.
Follow identifiers the records actually share
Each record below helps only when it is present and carries an identifier that also appears in the next record in the chain.
- Fixture label or manufacturer part number: the most direct record of what physically arrived.
- Carton label or reference: useful when it repeats the part number or ties to a packing-list line.
- Order line: connects a part number and quantity to what was purchased.
- Packing list or delivery ticket item: for its construction projects, NJDOT's delivery-ticket review guidance checks fields such as project, supplier, date shipped, material description, quantity, item name, and item number.
- Approved submittal reference: the record that can tie a part number to a scheduled type.
A direct match or an explicit cross-reference counts. An inference from appearance does not. When a label shows an abbreviated or coded string, match document claims to exact models by comparing it with the manufacturer's ordering information. For fixtures from our store, you can download product specification sheets to read the full model details.
Track each partial shipment against the schedule
Give each schedule entry and order line its own status: received, outstanding, or unresolved. IECI's fixture-package recordkeeping guidance recommends tracking fixture types, quantities, part numbers, approval and submittal status, purchase-order and shipping or receiving dates, and a worksheet of what arrived, when, and where it is stored. Adding the schedule entry to that worksheet turns it into a practical split-delivery log.
Units that haven't shipped yet are outstanding, not wrong. Reserve "unresolved" for items that arrived but can't be tied to a schedule entry. If a shipment's paperwork doesn't say which scheduled variant it contains, ask the supplier for a documented cross-reference. When the order came from us, contact our support team with the order number and the label details.
Record discrepancies and get a project decision
When a variant, quantity, or revision won't reconcile, document it against that specific item and get a written decision before anyone assigns it. As one example, City of New Braunfels guidance directs contractors to report contract-document discrepancies in writing and obtain written clarification from the Engineer before proceeding with affected work. Your project may name a different reviewer or channel, so use the one your contract documents designate.
A practical discrepancy record holds these fields, in this order:
- Item: carton or shipment reference and the identifier observed on the label.
- Order reference: order number and line, if the paperwork shows them.
- Expected entry: schedule type, zone, and revision, if known.
- Conflict: expected versus observed identifier or quantity, or the specific missing link.
- Question: one question the reviewer can answer directly, such as "Does this part number satisfy Type B on the confirmed revision?"
- Disposition: reviewer name, date, and the written decision.
Keep the item unassigned and staged apart while the question is open. Once the written decision arrives, enter it on the receipt record and assign the zone it names. Apply that decision only to the variant and revision it covers, not to look-alike cartons in the same delivery.
Before mounting begins, make the final go/no-go call: move forward only with cartons showing an explicit written schedule match, and keep all unresolved units segregated in staging until the project reviewer issues written clearance.
FAQs
Is a matching model number or SKU enough to assign a fixture to a zone?
Only when that same identifier appears in the schedule entry, or a documented record such as an approved submittal ties it to that entry on the confirmed revision. A model number proves what arrived. The schedule entry is what proves where it goes, so you need both pieces connected.
Can the fixture family name confirm which zone a carton belongs in?
No. A family or series name can cover several configurations, and two scheduled types may share one name. Treat the family name as a sorting hint at most. Assign the zone only after a full identifier links the carton to a specific schedule type.
Does a signed packing list mean the fixtures are correct for the project?
A packing list can confirm that the shipment matches the order line in item and quantity. It doesn't show which zone a variant belongs to, and the order itself may predate a schedule revision. Use it as one link in the chain, then complete the connection to the schedule entry.
What happens to fixtures received before a schedule revision is settled?
They can be logged as received against their order line, but their zone assignment stays open. Stage them separately and label them with the pending revision question. When the reviewer confirms which revision applies, rerun the match for those variants against that revision only.
