Lux readings need a condition log before they become evidence
A lux number is only useful when the reading condition travels with it. In an Australian home, classroom, warehouse, clinic, office or hospitality space, the same meter can show a different value when the point label, task plane, daylight, control state or shadow condition changes. A reading condition log keeps those details beside the number before anyone averages readings, compares two visits or turns a note into a planning note.
This page is about the condition note, not the physical measuring technique. The measuring sequence belongs with how to measure lux levels. Point spacing and drawing labels belong with lux meter grid point layouts. Change comparisons belong with lux meter before and after notes. The condition log sits between those pages and the numeric tools, so measured illuminance remains attached to a named place, plane and state.
| Log field | What to note | Why it matters |
|---|---|---|
| Meter identity | Meter name, model, asset label or phone app name if known. | Later readers know which device produced the value. |
| Status | Battery, zero check, diffuser state, calibration status if known, and any handling concern. | A reading can be repeated with the same caution. |
| Point label | Desk P1, bench B2, grid G3, aisle A4 or another stable label. | The reading can be found again. |
| Plane | Task plane, floor plane, shelf face, wall face or another named plane. | The number stays tied to the surface being considered. |
| Time and daylight | Date, time, sky condition, blinds, shade and direct sun. | Daylight can change faster than the room layout. |
| Control state | Active lighting zone, scene, dimming level and sensor state. | The electric-light condition is visible. |
| Repeatability flag | Matched, changed, uncertain or not repeatable. | Averaging and comparison notes can stay modest. |
Meter status belongs beside the first reading
The lux meter may be a handheld meter, a datalogger or an app-based tool. A condition log does not need to turn the meter note into a formal instrument note. It simply notes the identity and visible status that were known at the time. If calibration status is unknown, write unknown. If the diffuser was dusty, the battery was low or the meter was held at a slight angle, write that plainly rather than hiding the concern.
| Meter item | Strong field wording | Keep distinct from |
|---|---|---|
| Device identity | Meter M1, handheld meter, phone app name or site asset label. | Assumptions about accuracy that were not checked. |
| Calibration status | Current, expired, unknown or not available, where known. | Any claim that the value is formally verified. |
| Battery or display | Battery normal, low battery icon, display stable or display fluctuating. | Later editing of the measured number. |
| Sensor face | Diffuser clean, dust noted, case shadow avoided or case shadow possible. | A hidden correction factor. |
| Handling note | Laid flat, held level, hand nearby, tripod used or surface uneven. | The point label and plane note. |
When readings will later feed the lux meter average calculator, the meter note helps explain why one value may be marked for caution instead of silently blended with the rest. The condition log should not promise a calibrated result; it should state what was observed.
Point labels and planes keep the reading in place
A point label is the short name that lets a person find the same place again. A plane is the surface or height being considered. A desk reading, floor reading and vertical wall reading are not interchangeable, even when they are taken in the same room. The task plane term is useful because it keeps the reading tied to the surface where the visual task occurs.
| Location detail | Example entry | Related note |
|---|---|---|
| Single task point | Desk P1, centre of keyboard area, 720 mm plane. | Task plane notes |
| Grid label | G2, second row from entry, floor plane. | Lux meter grid notes |
| Bench or counter | Bench B1, front preparation area, 900 mm plane. | Lux meter reading notes |
| Vertical surface | Wall V1, sign face or board face, vertical plane. | Task plane lighting calculations |
| Zone label | Zone Z3, eastern desk row, normal scene. | Lighting zone |
Keep the label short enough for a drawing, spreadsheet or site note. A long descriptive sentence can sit in the remarks field, but the point label should remain stable. That separation makes same-plane comparison easier when a reading is averaged, repeated or compared with a calculated estimate from the room lighting calculator or workplace lighting calculator.
Time, daylight and exposure change the meaning of a value
In many Australian spaces, daylight is the largest changing condition. Morning sun on a classroom desk, cloud over a warehouse rooflight, blinds in a clinic room or late afternoon glare in an office can change the reading without any change to the electric lighting. The condition log should name the time and exposure before the value is compared with another number.
| Daylight field | What to write | Repeatability note |
|---|---|---|
| Time and date | 9:15 am, 12 July 2026, first pass. | Repeat near the same time if daylight is part of the comparison. |
| Sky condition | Clear sun, bright overcast, heavy cloud, broken cloud or night. | Mark changed if the sky moved during the set. |
| Shading | Blinds open, blinds half closed, curtains drawn, awning shade or tree shade. | Match the setting before comparing. |
| Direct sun | Direct sun on plane, no direct sun, sun patch nearby or reflected sun. | Mark caution when a sun patch moves across points. |
| Electric-light mix | Daylight only, electric only, combined or night electric state. | Link the state to the control note. |
The daylight vs electric lighting notes page keeps daylight-only, electric-only and combined readings separate. A condition log can point to that distinction without turning the reading into a daylight study. It is enough to say what light was present and whether the exposure changed during the reading set.
Control state should be written before the number is judged
Electric lighting can change through switches, dimming, occupancy sensors, daylight sensors and preset scenes. The reading condition log should state the active lighting zone, observed scene and control setting. If a sensor changed the level during the note, note that change beside the affected values.
| Control field | Example entry | Why it belongs in the log |
|---|---|---|
| Active zone | Front desk row on, rear desk row off. | The reading does not become a whole-room claim. |
| Scene | Normal, presentation, cleaning, after-hours or dimmed. | A later note can match the same scene. |
| Dimming level | 100 percent, about half, scene 2 or level unknown. | The value can be read beside the observed output state. |
| Sensor state | Occupancy active, daylight sensor active or manual override observed. | Sudden changes can be explained. |
| Control note | Linked to lighting control notes. | Control evidence stays with the numeric note. |
For operating-hour context, keep a distinct note with lighting control zones and operating hours. The condition log only needs the state present at reading time. It should not predict how the zone will behave across every day, season or occupancy pattern.
Shadows, obstructions and handling notes prevent false neatness
A reading can look precise while still being affected by a hand shadow, chair, ladder, parked pallet, open door, temporary screen or nearby person. The log should note visible obstructions before the number is averaged or compared. That does not mean the reading is useless; it means the condition is transparent.
| Field | Plain note | Repeatability flag |
|---|---|---|
| Shadow | Hand shadow possible, person shadow avoided or shelf shadow present. | Caution if the shadow could not be matched. |
| Obstruction | Chair under point, box on bench, pallet beside aisle or ladder nearby. | Changed if obstruction moved between readings. |
| Surface condition | Dark mat on desk, glossy bench, dusty floor or reflective tray nearby. | Match where the surface affects the task. |
| Meter position | Sensor centred, edge of desk, near wall, near screen or angled surface. | Match the position before comparison. |
| Disturbance | Door opened, vehicle passed, screen changed brightness or blind moved. | Mark uncertain for affected readings. |
These notes help keep lux and illuminance in plain language: the number describes light arriving at the meter under the stated condition. It does not, by itself, explain comfort, glare, colour appearance or every nearby surface.
Average only the readings that share the same condition
Before averaging, check that the readings belong to the same point set, same plane and compatible condition. The lux meter average calculator is useful after the note is tidy enough to group. If one point was taken with blinds open and another with blinds closed, or one point was on a desk plane and another on the floor, they may need separate groups.
| Average check | Include together when | Split or flag when |
|---|---|---|
| Plane | Every value belongs to the same task plane or named plane family. | Floor, desk and vertical readings are mixed. |
| Daylight | Time, sky and shading are matched or intentionally grouped. | Sun, blinds or cloud condition changed materially. |
| Controls | Zone, scene and dimming state are matched. | Sensor or scene changed during the set. |
| Meter status | Device and handling notes are consistent enough for the set. | Battery, diffuser or handling concern changed. |
| Point set | Labels belong to the same area note. | Labels came from unrelated rooms or zones. |
Calculated estimates can sit beside measured averages. The lumens to lux calculator estimates illuminance from lumen output, area and assumptions. The lux to lumens calculator estimates lumens from a target level and area. The condition log keeps those estimates distinct from actual field readings.
Comparisons need the same plane and a modest claim
A comparison can show that one point, plane or group of readings was higher or lower under named conditions. It should not stretch into a whole-site statement. The before and after lux comparison notes table is the compact home for repeated value pairs, while the guide on lux meter before and after notes explains how to keep the two sides matched.
| Comparison type | Condition log should show | Claim boundary |
|---|---|---|
| Same point, same scene | Point label, plane, meter state and control state repeated. | The point changed under the stated condition. |
| Same grid, same plane | Grid labels, daylight, obstructions and scene matched. | The point set changed under the stated condition. |
| Daylight change | Time, sky, shading and electric-light state named separately. | The value belongs to that daylight condition. |
| Control change | Scene or dimming change written before the number. | The difference belongs to that observed state. |
| Calculated and measured | Estimate kept beside measured point note. | The estimate and reading are not the same evidence. |
Keep the disclaimer close where a note could be read as more formal than intended. A condition log is a practical note for repeatability and same-plane comparison, not a formal sign-off.
Compact condition log template
The following field set can be copied into a spreadsheet, notebook or site note. It keeps the page distinct from a measuring guide, grid layout and before/after comparison page by focusing only on the conditions that travel with each value.
| Field group | Fields to note |
|---|---|
| Reading identity | Project or room name, reading set name, recorder, date and time. |
| Meter | Meter identity, status, calibration status if known, battery/display and handling note. |
| Location | Point label, zone, plane, plane height and short location description. |
| Light condition | Daylight state, electric-light state, control scene, dimming level and sensor state. |
| Surroundings | Obstruction, shadow, surface condition, temporary object and disturbance note. |
| Value | Lux reading, repeat reading where taken, average group and caution flag. |
| Links | Related calculator, table or guide used to interpret the note. |
| Boundary | Repeatable planning note, same-plane comparison note and non-formal disclaimer link. |
For the tabular note shape, keep lux meter reading notes beside task plane notes and lighting control notes. For point sets, connect the log to lux meter grid notes. For condition-specific comparisons, keep it beside before and after lux comparison notes. Together, these links keep each measured value readable without turning the condition log into a measuring manual or a formal assessment.