How to Get Scope Changes Approved by a Board That Meets Monthly

Why this matters

On a house, a scope change is a conversation in the driveway. On an association or a board-governed property, the same conversation is a motion that has to reach an agenda, survive a packet deadline, and get voted on by people who meet once a month and do not know you. A tech can identify the problem in twenty minutes and the answer can take nine weeks, and if you sit idle waiting, you have parked a crew, held a part, and let a tenant live with a defect for two months. The skill is not persuading a board. It is building the request so the calendar works for you instead of against you.

Step 1: Learn the calendar before you need it

For every board-governed account, capture four facts on the account record at onboarding: the meeting cadence and day (most commonly monthly, on a fixed weekday), the packet deadline (usually five to ten days before the meeting, and it is a hard cutoff because the packet gets distributed), whether an executive committee or a board president holds interim spending authority between meetings, and whether the board recesses for a month in summer or December.

Skip this and every scope change becomes a discovery exercise at the worst moment. You find out the packet closed yesterday while a tech is standing at an open panel.

Step 2: Find the authority line, not just the price

Two ceilings usually sit between you and a yes. The manager holds a per-incident cap under the management agreement. The board holds authority above that up to whatever the governing documents allow from operating funds, above which a reserve draw or a membership vote is required. Ask the manager for both numbers and for what the second one triggers.

The line matters more than either number, because it tells you where to cut the work. Skip this and you will send the whole job to the board when half of it never needed to go.

Step 3: Split at the authority line, not at the technical line

The instinct is to split a job where the trades change. Split it instead where the authority changes: everything the manager can approve today, and everything that has to wait.

The near-side piece is whatever stops the condition getting worse and restores service. The far-side piece is the durable fix. Where a hazard is involved, the near side is not optional and does not wait for anybody's calendar. Water reaching an energized panel or fixture: nobody re-enters the space until the affected circuits are isolated at a dry point by a qualified person, and you shut the water at the nearest upstream valve you can reach without standing in it. A gas odor in a unit or common corridor: everyone leaves the building immediately, no switches or thermostats touched, no phone used inside, call the gas utility emergency line from outside, then the manager. Those actions happen on the tech's authority and get documented after.

Skip the split and you either do nothing for a month or you do the whole job on hope.

Step 4: Write the one page the manager will actually forward

The manager is not your advocate, they are your translator, and they are presenting to people who will read your document in a packet at 10 p.m. Give them something that survives that. One page, and it carries:

• The condition, in plain language, with a photo. Not "compressor drawing high amps." What is failing, what it is doing to the building, and what happens if it keeps doing it.
• Two or three options, not one number. Boards approve choices far more readily than they approve a single price, because approving a single price feels like being handed a decision already made. Give a do-the-minimum, a do-it-right, and a defer-with-monitoring, each with what it buys and what it risks.
• The consequence of deferral, dated. "If this is deferred past the next meeting, the failure moves from a repair to a replacement" is a sentence a board can act on. "It should be addressed soon" is not.
• What you already did and under whose authority. The near-side work, the manager's name, the date.
• Validity in cycles, not days. See step 7.

Skip this and the manager writes the summary themselves from your invoice, which means your recommendation reaches the board filtered through someone who was not in the crawlspace.

Step 5: Submit before the packet deadline, and name the motion

Send it to the manager at least two business days before the packet closes so they can format it into their template. Include the sentence you want the board to vote on: "Motion to approve the proposed repair under option B, funded from operating." A board that has to draft its own motion language tables the item, because tabling is the safe move when nobody is sure exactly what they are approving.

Skip the deadline by even a day and the whole thing moves a full cycle. This is the single most expensive avoidable delay in board work.

Step 6: Handle all four meeting outcomes

Approved is one of four things that happen, and the other three are more common than shops expect.

Tabled is not a no, and treating it as one costs you the account. Tabled almost always means one specific question was unanswered. Get the question in writing while the meeting is fresh.

Step 7: Price the wait into the quote

Quote validity written in days will expire inside a single board cycle, and a re-quote is a fresh reason to table. Write validity in cycles instead: valid through the second regular board meeting following the issue date. Add one re-open trigger tied to a percentage rather than a calendar, for example that the quote is re-issued if material lead times extend beyond the stated window or input costs move more than 10% before approval. That is a clause a board understands and it stops you eating a change you did not cause.

Worked example: six days apart in discovery, twenty-two days apart in a decision

A 40-unit association. The board meets the second Tuesday of each month and the packet closes seven days before. Month one has 31 days and its second Tuesday falls on the 12th, so its packet closes on the 5th. Month two's second Tuesday lands on the 9th, packet closing on the 2nd.

Two findings in the same building, six days apart.

Finding A, discovered on the 2nd of month one. Three days to package before the packet closes on the 5th. Decided at the meeting on the 12th. Discovery to decision: 10 days.

Finding B, discovered on the 8th of month one. The packet for the 12th closed three days earlier. The item goes to month two's packet, closing on the 2nd, decided on the 9th. Discovery to decision: 23 days left in month one plus 9 days into month two, so 32 days.

Six days apart in the field, 22 days apart in the answer. Nothing about the two faults explains that gap. The packet deadline does.

Now run Finding B forward with a tabled outcome. At the month two meeting the board asks for a comparison bid. That pushes it to month three's meeting, which is the 14th (month two has 30 days, and its second Tuesday on the 9th puts the following month's first Tuesday on the 7th and the second on the 14th). From the 8th of month one: 23 days plus 30 days plus 14 days is 67 days. A twenty-minute diagnostic, a 67-day decision.

The split at the authority line is what makes those 67 days survivable. Say the whole job is 34 labor-hour equivalents and the manager's per-incident cap is 6.0. The stabilization piece, the part that restores service and stops the condition worsening, comes to 4.5 labor-hour equivalents, which is 25% under the cap and gets done in week one on the manager's authority alone. The remaining 29.5 labor-hour equivalents go to the board. The tenant is served on day two; only the durable fix waits for the 14th.

Compare that with the shop that sends all 34 to the board: the building carries the defect for the full 67 days, the tenant calls the manager four more times, and the manager quietly starts asking a second vendor for a price. Losing the account here has nothing to do with your work quality.

Step 8: Close the loop in writing before you order anything

Get the approval as a document: an email from the manager stating the motion passed and what was approved, or the minute reference. Boards change composition, managers change companies, and an approval that exists only as a phone call from a manager who left in the spring is not an approval you can invoice against.

The check that catches this is simple. Before any material is ordered on a board-approved job, the work order should carry an approval field with a date and a source. If the source field says "verbal, manager," stop and get the email. It takes four minutes and it is the difference between a receivable and an argument.

References

• Association governing documents in typical hierarchy: state condominium or common-interest statute, then the declaration or CC&Rs, then bylaws, then board rules (the applicable statute varies by state; read the declaration for the specific association)
• Community Associations Institute, guidance on board meeting procedure, agendas, and minutes
• See related: How an HOA Decision Actually Gets Made, The Approval Limit That Is Really a Liability Limit
• See related: The Change Order Discipline Commercial Work Demands, How to Get Approval Before You Do Extra Work