Start here
What a review committee is actually asking.
An architectural review committee isn't judging your taste. It's checking that what you attach to the outside of the house fits the covenants everyone in the neighborhood agreed to. In practice that comes down to three questions: what is being attached, what it looks like from the street in daylight, and how it behaves after dark.
Permanent outdoor lighting answers all three well, which is why it's usually an easier submission than a fence, a shed or a paint change. There's nothing to see by day, nothing goes through the shingles, and the entire night-time behavior is a schedule you set. The work is showing the board that on paper, before install day.
Every association writes its own covenants and runs its own process, so none of this is legal advice and we can't tell you what your board will decide. Read your covenants and ask your manager. What we can do is hand you the technical answers boards ask for, in the format they ask for them.
The packet
What an ARC submission contains.
Most boards want a short packet, not a binder. Some communities use a one-page exterior-modification form; others want a full architectural-review application with a sketch of the house. Either way, the content is the same short list, and every item on it is something we can put in your hands before you file.
Product spec sheet
Mounting method and location
Track color
A lighting schedule
Reference images
The acknowledgment
The daylight argument
Why color-matched track clears review where strands don't.
A strand hung on the roofline
- Bulbs and cord are visible from the street in daylight, every day it’s up.
- Clips run along shingle edges and gutter lips, in plain view.
- Almost always falls under the seasonal-decoration clause, with put-up and take-down dates attached.
- Reads to a committee as a decoration — temporary by definition, and regulated that way.
Low-profile color-matched track
- The track is color-matched to your fascia or trim and sits under the gutter line; from the street it reads as trim.
- No exposed wire, and nothing fastened through the shingles.
- The lights only exist visually when they’re on.
- Reads as a permanent exterior fixture, which is the category most covenants are more comfortable with.
That's the whole argument, and it's why the system usually clears review. Most covenant language about exterior appearance is written around what the neighborhood sees in daylight. A system that's invisible by day removes the objection before anyone raises it. Say it plainly on the form: by day, the house looks exactly as it does today.
The mounting detail carries the same weight. Committees that have seen a bad exterior install are wary of anything near a roof, so spell out that the track lands on fascia and under the gutter line. We wrote that out in full in the guide on roof damage and mounting.
Objections
The four things boards push back on.
Glare and light trespass onto neighbors
This is the legitimate one, and it's worth answering seriously. The fixtures sit in a track tucked under the gutter line along the face of the house — not on poles, not in spot fixtures aimed across a property line. Beyond that, the system runs in zones, so a run that faces a neighbor's bedroom windows can be dialed back or left off independently of the front elevation. Output level is something to look at directly at your demo: ask to see the system at the setting you'd actually live with, then write that into the submission.
Color restrictions
Plenty of covenants limit exterior lighting to white or warm white outside a holiday window. That isn't a problem here, because the system is RGBW — it has a dedicated true-white diode, so warm white is a real white, not three colors mixed to fake one. Committees who've only seen RGB-only systems expect a blue-ish or pinkish white and are right to flag it. Commit in writing to warm white as your everyday setting, with color reserved for the dates you name, and the restriction and the system stop being in conflict.
Hours of operation
Many communities have a lights-out hour. Scheduling answers this cleanly: the system runs dusk-to-dawn or on set evening hours, up to a year of calendar in advance, and the controller keeps running the schedule locally even if your internet drops. Put your off time on the form as a number. “Off at 11pm” is a commitment a board can hold you to, which is exactly why it reassures them.
“It'll look like Christmas lights all year”
This is the fear underneath most of the others, and the honest answer is that it can — if you run it that way. That's a choice you make in the app, not a property of the hardware. Most owners run warm white on the roofline the other eleven months and treat color as an occasion: a game weekend, a birthday, the Fourth of July. Describe that pattern in the submission and you've answered the objection with the same schedule you were going to run anyway.
The distinction that matters
Year-round lighting vs. a seasonal display.
Most covenant documents handle these in two different places. There's usually a seasonal or holiday decoration clause with dates attached — how many days before a holiday something may go up, how many days after it has to come down — and separately a section on exterior lighting or architectural modifications, which covers anything permanently attached to the structure.
A permanent system lives in the second section. It's a fixture, installed once, that happens to be capable of producing a seasonal display. Confusing the two is the single most common reason a submission stalls: the form gets filed as a decoration, someone points at the take-down date, and now you're arguing about the wrong paragraph.
So ask your manager which section applies before you submit anything. If your community treats it as an architectural modification, you file once and you're done — the everyday warm white is a fixture doing fixture work. If the seasonal clause also applies to color displays, you keep the color inside the window the covenants describe and run warm white outside it. Either way you want that answer in writing before install day, not after.
Our part
What we hand you for the submission.
We bring the technical pages to your free quote and on-home demo: the product spec sheet, the mounting method, the track color we'd match to your fascia, and a written description of the schedule you tell us you want. We'll walk you through the acknowledgment and the submission so nothing on it is a guess.
You sign and file it. Most associations only accept submissions from the owner of record, so the paperwork goes in under your name — our job is making sure every technical line on it is accurate and specific to your roofline rather than generic boilerplate.
Start earlier than feels necessary. Committees meet on their own cadence, and a board that meets once a month sets your timeline more than we do. Tell us where you are in the process when you book the demo and we'll schedule the install around the answer instead of ahead of it.
Before you file
What to ask your board.
- Does our community treat permanent exterior lighting as an architectural modification, a decoration, or neither?
- Is there an approved-color rule — white or warm white only — for exterior lighting outside holiday periods?
- Is there a lights-out hour, and does it apply to architectural lighting or only to decorations?
- What dates does the seasonal-display clause cover, and does a color scene fall under it?
- Does the committee want a spec sheet and mounting detail, or just the modification form?
- When does the committee meet, and how long does a decision usually take after submission?
Bottom line: submit the fixture, not the light show. A committee approving low-profile track color-matched to your fascia, mounted under the gutter line with no shingle penetration, running warm white on a stated schedule, is approving something almost nobody in the neighborhood will ever notice at noon. The color is a setting you choose afterward, inside whatever rules your covenants set. Answer the daylight question first and the rest of the conversation gets short.
Keep going