Controlling Photoperiod and Spectrum for Indoor Crop Consistency

Indoor farming succeeds on repeatability: the same recipe should produce the same crop every week. Two levers decide most of that repeatability — photoperiod (how long the lights are on) and spectrum (the colour recipe). Both must be controllable and logged, because an unlogged dimming drift or a silently changed schedule is the difference between a consistent product and a batch that finishes late. This article covers how the control side works and the mistakes that break consistency.

Photoperiod is the cheapest DLI lever

Because DLI equals PPFD times photoperiod times 0.0036, you can hit a DLI target two ways: hold PPFD and change the hours, or hold hours and change intensity. Photoperiod is the cheaper lever — extending hours adds wall-clock time, not wattage. But very long or continuous photoperiods interact with plant respiration and quality, so most operations fix a sensible schedule and tune intensity with dimming.

Dimming must be calibrated, not assumed

A 50 percent dimming setting does not always mean 50 percent PPFD. Driver behaviour, thermal state and optics all shift the curve. For consistency you should map dimming percentage to measured PPFD at least once, then log the setting per recipe. This is where the PPF vs PPFD vs PPE guide and efficacy matter: efficacy (µmol/J) tells you how much light each watt buys.

Spectrum: use bands, not marketing colours

For most indoor crops the spectrum conversation is about a few bands: blue (around 400-500 nm) for compactness and morphology, red (around 600-700 nm) for photosynthesis and flowering response, and far-red (around 700-750 nm) for shade-avoidance and morphology effects. White fixtures are typically a red-blue base with a phosphor fill. The practical question is not "full spectrum vs not" but which bands your crop and stage respond to, and whether your fixture can hold that mix.

Common controllability mistakes

• Assuming dimming percentage equals PPFD percentage without measuring.
• Changing the schedule between batches without logging it.
• Mixing fixtures with different spectra in one zone and calling it one recipe.
• No calibration after driver or LED replacement.
• Controls that cannot report what they actually delivered.

Building a dimming and scheduling plan that survives operations

A photoperiod plan is only as good as the controls behind it. Timers drift, manual overrides get forgotten, and a room that was supposed to run 18 hours ends up running 22 because nobody reset a switch. The practical answer is to centralize scheduling in a lighting controller, log actual on/off times, and review the log weekly. A controller that records delivered hours turns schedule questions from arguments into data.

• Define the photoperiod per crop zone, not per room, when zones hold different crops.
• Use sunrise and sunset ramping where the controller supports it; abrupt switching is rarely a crop problem but can disturb staff working in the space.
• Keep a weekly exception log: every override, power event and deviation from schedule, with a one-line reason.
• Review logged photoperiods monthly against plan; a 3 percent drift is invisible day to day and significant across a season.

Spectrum control in practice

What channels actually change

Most commercial fixtures offer either a fixed full spectrum or two to four controllable channels (commonly deep blue, deep red, white and sometimes far-red). Spectrum control matters most at crop transitions: raising the blue fraction can compact growth and deepen colour, while far-red exposure at the end of day can influence elongation in some species. These responses are crop and cultivar specific, so treat any spectrum recommendation as a hypothesis to test on a few trays before changing a whole room.

Documenting a spectrum recipe

Write spectrum settings down the same way you write a feed recipe: channel percentages by crop stage, the date the recipe changed, and the reason. If a supplier later asks what spectrum your trial used, or a colleague has to reproduce a run, the recipe is the only reliable record. Fixtures from different vendors rarely share channel naming, so record the channel percentage and the fixture model together.

Questions to ask before you buy

• How many controllable channels does the fixture have, and what is the wavelength peak of each?
• Is the control protocol open (0-10V, DALI, or a documented API) or locked to a proprietary hub?
• Can schedules and spectrum settings be exported, so your recipes survive a controller replacement?
• What happens to fixtures on control failure: a defined fail-safe state or random behaviour?
• Does the supplier support integration with the environmental controller you already run?

Common mistakes in photoperiod and spectrum control

Control systems fail quietly, which is what makes these mistakes common. Each is worth checking in an existing room, not only at design time:

• One schedule for the whole room when zones hold crops with different photoperiod needs; the compromise pleases no crop.
• Timers instead of logged controllers, so a 22 hour day runs for weeks unnoticed because nobody sees the log.
• Spectrum settings adopted from a demonstration without a trial, then left in place so long that nobody knows what the room is running.
• Overrides after maintenance that were never returned to schedule; the room drifts and the drift becomes the new normal.
• Night-interruption lighting omitted for day-sensitive species in propagation, then explained later as mysterious early stretching.
• Documented recipes kept in one persons head; when that person is unavailable, the room runs on guesses.

Crop transitions and the light calendar

Planning the year as a light calendar

Indoor rooms are often described as seasonless, but the crop plan still has seasons: propagation cycles, production waves, cleaning windows. A light calendar maps photoperiod and spectrum settings per zone per period, including the transition dates between crops. The discipline pays off when a new crop arrives: the zone schedule is written, the previous recipes are archived, and nothing depends on memory. It also exposes conflicts early, such as two crops sharing a room with incompatible day lengths.

Verifying that control equals intent

A controller can be programmed correctly and still deliver the wrong result: a faulty relay, a firmware update, or a power event can leave a zone dark or lit for hours. The verification habit is cheap: a weekly look at logged hours per zone against plan, plus a monthly spot-check of spectrum settings where channels are controllable. Fifteen minutes of review per week protects the integrity of every crop scheduled on that system.

References you can verify

• MSU Extension / e-GRO - controlled environment lighting guidance
• Michigan State University College of Agriculture and Natural Resources
• University of Florida IFAS - horticulture extension
• Royal Horticultural Society - light and plants

Frequently asked questions