Start a dated shift-comparison log the first time you notice the symptom. Each entry should pair what the light did with where and when it happened, the task underway, and the conditions you could see at that moment.
Next, compare that entry with a period when the symptom was not observed, and send the pattern to maintenance. A useful log records an observed pattern rather than diagnosing a fixture fault, because a problem that shows up on only one shift may not be a constant fixture problem.
Start a Shift-Comparison Log at the First Observed Symptom
Write the first entry while the details are fresh, ideally during the same shift. A short entry written right away is more useful than a detailed one rebuilt from memory days later.
You don't need a special form. A DOE FEMP relighting checklist includes fields for date, operating hours, space description, planned usage and worker tasks, and the current lighting system and controls. It was built for federal relighting projects, not shift reports, but those same categories work well for shift notes.
Use this field order for every entry: location (building, area, and which fixture or row); date, time, and shift; the symptom you saw; the task underway; conditions you know about at that moment; whether the account is firsthand or reported; and whether the symptom was observed or not observed on another shift.
Here is an illustrative entry: "Packing area, fixture above station 3. Wednesday, 10:15 p.m., second shift. Fixture looked noticeably dimmer than its neighbors. Team was packing small orders at the station. Overhead door closed, no daylight. Firsthand. Not observed by me on first shift; day lead says she has not noticed it."
Describe what happened, not what you think caused it. "Light went dark for a few seconds" gives maintenance something to work with. "Bad ballast" is a guess that can send the investigation the wrong way. If you don't know a detail, such as whether a control was set differently, write "unknown." Don't leave it blank or guess. And keep secondhand reports labeled as reported, even when you trust the coworker who told you.
Compare the Affected Shift with a Symptom-Free Period
Compare conditions, not just shift names. Put an affected period next to a period when the symptom was not observed, using the same location and the same log fields, then mark each field as matched, different, or unknown.
Keep the comparison tight. Use the same fixture or area and a similar task wherever you can. A first-shift note about the loading dock does not compare well with a second-shift note about the break room. Note only the differences you actually observed, such as a different task or activity level, daylight through windows or open doors, or a visible control setting such as a dimmer position.
Be careful with the word "normal." If you did not watch the lights during the other shift, write "not observed" instead. "Normal" suggests someone checked and found nothing, which may not be true. A coworker's "it seems fine on days" is a reported observation, so label it that way.
Sometimes the two periods are too different to compare. For example, one shift may run heavy equipment while the other does quiet inspection work. In that case, say the periods are not directly comparable and explain why. That is still useful information for whoever investigates.
Write the result as an observed pattern: "Seen twice on second shift during packing; not observed by me on first shift; daylight differs between the two." The same structured, field-by-field approach to feedback appears in a commercial lighting pilot scorecard, where it's used to review lighting before a wider rollout.
Use the Pattern to Choose a Safe Next Observation
Your pattern can point to one more thing to watch, as long as that check stays purely observational. Lighting controls are one possible factor worth noting when the space has them.
DOE guidance on lighting controls for offices and public buildings describes occupancy sensors that respond to people in the space and daylight-responsive controls that adjust lighting as daylight changes. Separately, federal-building LED guidance names dimmers and electronics as possible factors in flicker.
| Symptom | Possible factor to investigate | Safe next check |
|---|---|---|
| Lights switch off during a low-movement task | Occupancy-sensing response, if present | Note how much people were moving and when lights went off |
| Output changes as daylight changes | Daylight-responsive control, if present | Note visible daylight or shade and what the lights did |
| Flicker when lights are dimmed | Possible dimmer or electronics factor | Record the visible dim setting; ask maintenance to assess |
Use a row only when it fits what you saw and the equipment you know is there. If the area uses motion-activated lighting or a wall or ceiling sensor, the first row is worth watching. If no one knows what controls are installed, write that down as an unknown for maintenance to answer.
Stick to watching and writing things down. Don't change sensor or dimmer settings, open fixtures, or test equipment to "confirm" a pattern. Changing a setting also changes the conditions you're trying to document, and assessing equipment is maintenance's job.
Turn the Comparison into a Maintenance Request
Send a short request that leads with the location and the pattern, not a guessed cause. Maintenance needs to know where to look, when the symptom shows up, and what was different when it didn't.
A fill-in sentence works for most requests: "At [location/fixture], I observed [symptom] on [date/time/shift] during [task], with [known condition]; it was [observed/not observed/unknown] during [comparison period]. Can you assess which operating or control conditions should be investigated?" Attach the full log so the recipient can see each entry without retyping it.
This clear record hands the investigation to the right person without guessing at causes. If a technician visits and the symptom doesn't appear, add the visit time and shift to the log as one more observation. Don't record it as a fix. From there, maintenance or an electrician may take the next steps, such as working through a driver-versus-voltage diagnostic flowchart. If the case later becomes a warranty claim, your dated shift entries can sit alongside the voltage logs for warranty claims that qualified staff collect.
FAQs
What if the lighting looks normal during the maintenance visit?
Keep your earlier entries exactly as written. Then add a new entry with the visit date, time, and shift, and note that the symptom was not observed during the visit. One symptom-free visit doesn't show that the problem is gone, especially if the visit happened during a different shift or task.
Should I log shifts when the lighting seems normal?
Yes, when you can watch the same location during a similar task. Mark the symptom as not observed and note any real differences in task, daylight, or visible settings. If the work or conditions are very different, label that shift as a weak comparison rather than a clean baseline.
Does a shift-specific pattern identify the cause?
No. A shift pattern shows when the symptom appeared and what conditions were present. That helps maintenance decide what to investigate first, but it doesn't confirm a fixture fault, a control problem, or any other cause. Diagnosis comes from maintenance's assessment, not the lighting issue report itself.
