Most budget guides tell you how to build the numbers. Almost none tell you how to defend them.
That gap shows up every fall, in the same moment. A manager makes the case for more front-desk coverage. Package volume is up. The lobby backs up most afternoons. The current schedule can't keep pace. And a board member looks up and asks the question that stops the room:
"Where's the number for that?"
The honest answer, most years, is a version of last year's figure plus a little. A sense that it's busier. A feeling the team can't quite put on paper.
The problem isn't the estimate. It's that there's nothing behind it. When the operation was never counted, every line item comes down to who argues best in the room rather than what the property actually did all year.
This guide covers what to count, when to start, and how to turn a count into a line a board can approve without a debate.
Operational data is the record of what a property actually did: how many packages arrived, how many guests and vendors came through the gate, how often amenities were booked, how much valet ran at capacity. It sits underneath the budget's service and staffing lines and provides the evidence for them. It is not financial data, and it does not come from the accounting system.
Financial data tells you what you spent. Operational data tells you what you spent it on, and whether the amount matched the demand.
Boards are not usually rejecting a manager's request. They are rejecting the absence of a record.
A board member has a fiduciary duty to the owners and no independent way to verify that the front desk needs four more hours a day. Absent evidence, the safe vote is no. The manager reads that as distrust. The board reads the request as a guess. Both are behaving reasonably, and the outcome is a budget shaped by whoever is most persuasive that evening.
Evidence dissolves the standoff. Once the number exists, the conversation stops being about judgment and starts being about arithmetic.
Earlier than most calendars suggest.
Florida's Department of Business and Professional Regulation advises associations to begin gathering budget information about three months before the budget takes effect. For a January 1 fiscal year, that means starting in October.
But October is when you assemble the numbers. It is far too late to begin generating them. A count that starts in October gives you six weeks of data going into a November adoption meeting, and six weeks of anything is easy for a board to dismiss as a fluke or a holiday anomaly. A count that starts in July gives you a summer baseline, a back-to-school shift, and the early edge of holiday package season. That is a pattern, and a pattern is much harder to argue with.
For condominium associations governed by Chapter 718, Florida Statutes:
| Requirement | Deadline |
|---|---|
| Notice of the budget meeting to all owners | At least 14 days before the meeting |
| Affidavit of notice executed and kept in official records | At the time of notice |
| Board adoption of the annual budget | At least 14 days before the start of the fiscal year |
| Budget meeting open to all owners | Always |
Two details worth flagging. Budget committee meetings carry the same notice and access requirements as board meetings. And effective January 1, 2026, the association website posting requirement extended from associations of 150 or more units down to those with 25 or more units, which means the budget and the reasoning behind it are now visible to a substantially wider group of owners than in prior years.
Homeowners associations operate under Chapter 720 and follow a different set of procedures. Confirm your specific timeline and notice obligations with association counsel. This guide is operational, not legal advice.
Each of these maps to a line a board will question. Start with whichever one you have already been asked to defend.
Count: every package received, logged at the moment it arrives, with a timestamp.
Why it matters: package handling is the single largest uncounted labor cost at most residential front desks. It has grown steadily for a decade and almost no association tracks it.
What it proves: whether you need added coverage, a package room, a locker system, or a change in hours. Daily peaks and holiday surges also tell you whether the problem is volume or timing, which are different problems with different price tags.
Count: every guest, contractor, delivery driver, and service vehicle, recorded as they arrive.
Why it matters: most gatehouse schedules were set years ago against a traffic pattern that no longer exists. Renovation cycles, short-term rental activity, and delivery growth all move the curve.
What it proves: whether post hours match real volume. Often the finding is not that you need more hours, but that you need different ones, which is a much easier line to get approved.
Count: bookings, no-shows, capacity hits, and the hours when valet runs at or over its limit.
Why it matters: amenity and valet spend is usually the first thing cut when a budget tightens, because it feels discretionary. Usage data is what makes it defensible.
What it proves: which amenities justify their operating hours, when to staff up seasonally, and whether the resident complaints you are hearing reflect a genuine capacity problem or a few loud voices.
Count: how many vendors come on property, how often, and how much staff time goes into chasing certificates of insurance and licensing.
Why it matters: compliance work is real labor that appears nowhere in the budget until something goes wrong and it appears as a claim.
What it proves: the true administrative cost of vendor management, and the association's exposure if an uninsured vendor is working on the property today.
Count: completed inspections, open items, and how long items stay open.
Why it matters: deferred items become capital expenses. The gap between "we inspect regularly" and a record of what was inspected and when is the gap a board feels in year three.
What it proves: whether preventive maintenance is actually happening, and where the next reserve pressure is coming from.
1,213
packages through the door in a single week at a 199-unit oceanfront high-rise in South Florida. Nearly half of them arrived in the three hours between 11 AM and 2 PM.
Read that second sentence again, because it is the part that changes a budget.
The property was not understaffed all day. It was underwater for three hours. The residents who saw a line, the calls that went unanswered, the guests who waited, nearly all of it concentrated in one window, and the rest of the shift went to catching up on it.
That is a materially different request than "we need more front desk help." It is four hours a day, 11 to 2, with a week of volume behind it. One version invites a debate. The other invites a decision.
A number alone does not carry a meeting. Four things do.
Lead with the pattern, not the total. 1,213 is a big number that means little. "Half of it lands in three hours" is a small observation that means everything.
Name the consequence in resident terms. Boards are owners. Frame the gap as what a resident experiences at 12:30 on a Tuesday, not as a staffing ratio.
Bring the cost of doing nothing. Overtime, turnover, complaint volume, and the manager hours spent absorbing overflow are all real and all currently invisible.
Show the range. Give the board a version at full coverage and a version at partial coverage, with what each one buys. Boards approve choices more readily than they approve requests.
Livvie is not an accounting system and it does not build your budget. Your management company, your CPA, and your reserve study still do what they do.
What operational data does is quantify the activity the budget is built on. The two work together: the accounting system records what the association spent, and the operational record shows whether the spending matched what the property actually handled.
Anyone selling you a single system that does both is selling you something that does neither well.
At least three to four months before the budget is assembled, which for a January fiscal year means July or August. Florida's DBPR advises gathering budget information about three months before the budget takes effect, but data has to exist before it can be gathered. Two months of counting is an anecdote. Five months is a pattern.
Most often: package volume, guest and vendor traffic, amenity usage, and anything that supports a change in staffing hours. These are the lines boards question, because they are the lines that grow and the lines with the least evidence behind them.
You can, and a spreadsheet is far better than nothing. The failure mode is consistency. Manual logging drops off within a few weeks, usually during exactly the busy periods you most needed to capture, which leaves you with a record that understates your peaks.
No. A certificate proves a vendor was insured on the date it was issued. A compliance record shows who was on the property, when, and whether their coverage was current at that moment. Boards increasingly ask for the second one.
One full season, at minimum, with the peaks intact. Enough to show a pattern rather than a snapshot, and enough that a board member cannot reasonably attribute the number to an unusual week.
Budget season is not a month. It is a window that opens in the summer and closes when the board votes.
The number that ends the debate in the fall has to start counting now. Every week you wait is a week of evidence you will not have when someone asks where the number is.
Livvie was built by people who have run front desks, gatehouses, and budget meetings. If you want to walk through what your property should be counting before September, book 15 minutes.
Book 15 minutesLivvie is the operating entity QWKIN, LLC d/b/a Livvie. All property data referenced in this article is reported at the building level and anonymized. This article is operational guidance, not legal or financial advice. Confirm statutory requirements and deadlines with your association's counsel.