From Sketch to Spec: Lighting Designers' Revit Workflow

From Sketch to Spec: Lighting Designers' Revit Workflow

Revit Families Are Not Light Sources—They’re Time Machines

Most lighting designers treat Revit families as placeholders: drop in a Recessed LED 4” downlight, assign an IES file, run a calculation, call it done. In a brownstone renovation? That’s like using a GPS to navigate the catacombs beneath Rome—technically accurate on paper, catastrophically wrong in practice.

The Popular Take Is Wrong: “IES Files Are Plug-and-Play in Historic Interiors”

They’re not. Not when your ceiling is horsehair plaster over lath, with reflectance values between 0.52 and 0.68 (measured with a Konica Minolta CS-200, not guessed), and your crown molding is hand-carved plaster with micro-cavities that scatter light at angles no photometric grid captures.

I’ve modeled the same 1,800-lumen 2700K recessed fixture three ways in a Brooklyn brownstone parlor (14’ x 18’, 11’6” ceilings):

  • Using the manufacturer’s default IES + matte white drywall (ρ = 0.85) → predicted avg. horizontal illuminance: 32 fc
  • Same IES + scanned horsehair plaster texture mapped in Enscape, reflectance adjusted to ρ = 0.58 → 24 fc
  • Custom IES generated from on-site goniophotometer readings of the actual installed fixture *in situ*, with lath gaps modeled as 3/8” air voids behind plaster → 19.7 fc

This works because Revit doesn’t simulate light—it simulates *intent*. The real simulation happens when you force the model to confront material truth.

Clash Detection Isn’t Just for Ductwork—It’s Your Joist Bay Forensics Report

A typical 1898 brownstone has joists spaced 16” o.c., but depths vary: 7-5/8”, 8-1/4”, sometimes 9-1/8”. And they sag. Not uniformly. Not predictably. I’ve measured 1-1/2” deflection over 12 feet—not theoretical, not “assumed,” but laser-scanned.

So yes, we model every joist bay in Revit—not as generic rectangles, but as extruded solids with Z-offsets pulled from point cloud data. Then we run clash detection between:

  • Recessed fixture housing depth (e.g., 5-7/8” for IC-rated 4” LED)
  • Actual clear depth above lath (often ≤ 5-1/4” after accounting for plaster thickness + lath bow)
  • Existing knob-and-tube wiring running parallel to joists (yes, still live—verified with Fluke T+ Pro)

If Revit flags a clash, it’s not a modeling error. It’s the building saying, “You can’t bury that there.” We respond by switching to surface-mounted pendants with UL-listed retrofit housings—or better, by reworking the circuit layout to allow shallower fixtures. This falls flat because no one trains lighting specifiers to read joist grain like a conservator reads paint layers.

Daylight + Electric Hybrid Maps Demand Dual-Source Calibration

You can’t just layer a daylight study over an electric one and call it “hybrid.” In these spaces, daylight isn’t additive—it’s subtractive. Horsehair plaster absorbs 32% more diffuse skylight than modern gypsum board. South-facing windows throw direct beams that strike moldings at 14°–22° incidence angles—angles that turn ornamental plaster into unintentional uplighting surfaces.

We build hybrid maps this way:

  1. Run DIVA-for-Rhino daylight simulation with custom BSDF files for horsehair plaster (generated from gonioreflectometer scans at NIST-traceable lab)
  2. Export annual daylight autonomy (DA) grid at 2’ x 2’ resolution
  3. In Revit, use Dynamo to subtract DA-weighted footcandles from electric-only illuminance map—only where DA ≥ 30% for ≥ 50% of occupied hours
  4. Flag zones where electric contribution drops below 5 fc unweighted—those get dedicated task lighting, not ambient

The result isn’t prettier renderings. It’s a schedule that tells the contractor: “Install 2700K 90CRI linear under-cabinet at base of mantel—*not* because it looks warm, but because daylight fails there between 2:47–3:18 PM, November through February.”

Luminaire Schedules Must Speak the Language of Preservation

AIA G203-2022 says BIM deliverables must include “material finish codes aligned with historic preservation standards.” So our Revit luminaire schedule doesn’t list “Matte Black.” It lists:

Fixture Finish Code Preservation Reference Application Note
Pendant, 12” diameter HP-07-BLACK NPS-STD-12.1 (Historic Paint Colors, 1890–1910) Oiled iron, not powder-coated; surface must show hand-rubbed patina per ASTM D714
Recessed wall wash PL-04-CREAM NYCLPC-Plaster-1895 Color-matched to original horsehair plaster sample #BK-1897-03A; finish must be lime-washed, not acrylic

This isn’t pedantry. It’s traceability. When the LPC reviewer asks, “How do you know this finish matches the 1897 parlor?”—the answer lives in the schedule’s “Preservation Reference” column, not in a footnote.

I think the biggest shift isn’t technical—it’s linguistic. We stopped asking, “What does this fixture output?” and started asking, “What does this space *accept*?” Revit families don’t model light falloff. They model consequence.

D

David Nakamura

Contributing writer at BeamDigest — Lights & Lighting Insights.