A real estate director at a 70-location quick-service brand once told me their last attempt at a multi-site lease audit took eight months and never produced a single dispute letter. The reason was not the audit firm. The reason was the rollout. Documents went into a SharePoint folder, the analyst worked one store at a time, findings drifted, the operator's real estate team rotated, and the engagement died.
I built CAMAudit to compress the parts of the rollout that should not take eight months. This playbook is the six-week sequence I have watched work on portfolios from 25 to 350 locations. Each week has a clear deliverable and a clear handoff. If you are running this engagement — as the operator's real estate director or as the partner — use it as the operating template.
Week 1: Document collection
The first week is unglamorous and it is where most engagements stall. The partner needs the executed lease (with all amendments) for every location, the most recent two reconciliation statements per location, and the current year's estimated CAM/tax/insurance pass-through schedule. For a 50-location portfolio across 18 landlords, that is 50 leases and 100 reconciliations.
Run this through the operator's lease admin system if there is one. Visual Lease, Lucernex, MRI, AppFolio. If documents are scattered across SharePoint, email threads, and the AP team's filing cabinet, expect to spend the full week chasing. Build a tracking spreadsheet on day one — store ID, document type, status, owner. The spreadsheet is the engagement's nervous system for the next six weeks.
The other deliverable in week 1 is the engagement plan signed by both sides. Scope, fee model (covered in the pricing breakdown), timeline, points of contact, and the business case packet on file. Skipping this step is what creates scope creep later.
Week 2: Detection and findings review
Week 2 is where the math runs. The partner loads every reconciliation into CAMAudit, runs the 14 detection rules per location in parallel, and produces a portfolio-level findings table. Three days of partner time, not three weeks of analyst time. That compression is the entire reason the 6-week rollout is possible.
The findings table groups by store, by overcharge category, and by dollar size. The partner ranks findings by recovery dollars and pulls the top 30 into a working-session document. The operator's real estate director and CFO (or their delegate) review the working-session document with the partner — usually a 90-minute call.
The decisions in this meeting are: which findings to dispute hard, which findings to use as renewal leverage rather than current-year recovery, and which findings to drop because the dollar size is too small to justify the relationship cost. The drop list is rarely empty. A 50-location engagement might surface 80 findings; the dispute list typically lands at 30–40.
40% of CAM reconciliations contain material errors (Tango Analytics / PredictAP, 2023)
Week 3: Dispute packet drafting per landlord
The pivot in week 3 is from per-store to per-landlord. If the operator has 50 locations across 18 landlords, the dispute packets are organized by landlord, not by store. A single packet covers every location one landlord owns, with the findings tabbed by store inside the packet.
Each packet contains a cover letter exercising the audit rights clause, a per-store findings summary with dollar amounts, lease clause cites, and the supporting math, and a request for response within 30 days. The cover letter and findings tables are produced from CAMAudit's dispute letter draft output and edited for the operator's voice and the specific landlord's history.
Partners draft the full packet in week 3. The operator's legal team reviews if the engagement scope includes legal review (most do not — the dispute letter is a business communication, not a litigation filing, and landlord controllers respond to it as such).
Week 4: Operator review and approval
Week 4 is operator-side. The real estate director reviews each packet, the CFO approves the dollar amounts being claimed, and any internal stakeholders sign off on landlord-specific decisions. This is the week where 5–10 of the 30–40 disputes might get pulled or modified for relationship reasons.
The partner's job in week 4 is to handle revisions, answer questions, and prep the submission logistics. The operator's job is to make decisions. Internal time on the operator side concentrates here — most of the 15-hour total budget for the engagement lands in week 4.
The other thing that happens in week 4: the partner builds the recovery tracking dashboard. Per-landlord, per-finding, expected response date, expected recovery amount, status. This dashboard becomes the operator's asset for the next 90 days.
Week 5: Landlord submission
Week 5 is the dispute letter submissions go out. Certified mail or the equivalent contractual delivery method specified in the lease, simultaneous to all landlords on the same day. Simultaneous matters because it prevents one landlord from coordinating with another. The submission window is one calendar week.
Partners include their own contact information in the dispute letter for technical questions and route relationship questions to the operator's real estate director. Most landlord controllers respond first with a request for clarification — which finding, which lease section, which year — and the partner handles those responses through week 6.
Week 6: Response tracking and follow-up
Week 6 begins the response cycle. Most landlords respond within 30–60 days of submission. Some respond in two weeks, some take 90 days. The partner tracks every response, categorizes it (acknowledged/credit issued, partial agreement, dispute denied, no response), and updates the recovery dashboard.
For findings the landlord acknowledges, the credit shows up on the next reconciliation cycle or as a refund check. For findings the landlord disputes, the partner runs a second-round response with additional supporting documentation. For findings the landlord ignores, the partner escalates either with a follow-up letter or, in cases where the dollar amount justifies it, with formal escalation under the lease's dispute resolution clause.
Recovery tracking is the engagement's deliverable. The dashboard shows per-finding status and expected recovery date. The partner reports out quarterly on the engagement's recovery total until every finding has either been recovered, denied, or escalated.
The handoffs that determine success
Three handoffs make or break the rollout. Document collection in week 1 — if the operator does not deliver leases and reconciliations in week 1, every subsequent week slides. Findings review in week 2 — if the operator's CFO is unavailable for the working session, the dispute scope cannot be set and week 3 stalls. Operator approval in week 4 — if internal stakeholders take three weeks to review packets, submissions slip into week 7 and the response cycle pushes into the next quarter.
The partner's job is to drive these handoffs. The operator's job is to staff the right people for them. Both sides need to know which weeks are heavy on operator time (week 1 and week 4) and which weeks are heavy on partner time (weeks 2, 3, 5, and 6).
For partners running this as a service line, the niche-services framing covers how to package the rollout as a productized offering with clear deliverables and clear pricing. The white-label program puts the rollout under the partner's brand. The revenue-sharing program is the alternative for partners who refer engagements to other firms.
Where CAMAudit fits
CAMAudit handles week 2. The platform ingests every reconciliation, runs the 14 detection rules in parallel per location, and produces the findings table that drives the rest of the engagement. The dispute letter draft output in week 3 is generated from the same findings, with lease clause cites and supporting math attached automatically.
For operators, the most useful pre-rollout step is a free scan on one reconciliation before week 1 starts. The scan validates that the engagement will produce findings and gives the partner a calibration point for the occupancy cost benchmarking that may be layered into the engagement scope.
Frequently Asked Questions
What is a multi-site lease audit rollout?
The rollout is the operational sequence for running a multi-site lease audit engagement end to end. It covers document collection, detection across all locations, findings review, dispute packet preparation, landlord submission, and recovery tracking. A clean rollout takes 6 weeks elapsed time on a 50-location portfolio with the partner doing most of the work.
How do partners actually run the rollout?
Week 1 is document collection — leases, reconciliations, estimated CAM schedules. Week 2 is detection through CAMAudit and findings review. Week 3 is dispute packet drafting per landlord. Week 4 is operator review and approval. Week 5 is landlord submission. Week 6 is response tracking and follow-up. The partner runs every step except operator-side decisions, which is where the 15-hour internal time estimate comes from.
What does a multi-site lease audit rollout cost or pay?
The rollout cost is the engagement cost — $25K–$125K for a 50-location portfolio depending on fee model. Recovery timing matters: most landlords respond to disputes within 30–60 days, so cash recoveries land 90–120 days after engagement start. Partners are paid on contingency at the recovery date or on flat-fee at engagement milestones. Rollout discipline is what makes the timeline predictable.
Where does CAMAudit fit into the rollout?
CAMAudit handles week 2 — the detection and findings generation. The platform ingests every reconciliation, runs all 14 rules per location in parallel, and produces a portfolio-level findings table with lease clause cites and dispute language drafted per finding. That compresses what was previously 4–6 weeks of manual analyst work into 3–5 days, which is what makes the 6-week rollout possible at all.
Run the rollout, not the project
The difference between an engagement that ships in six weeks and one that drifts for eight months is rollout discipline. Use the week-by-week structure, drive the three critical handoffs, and let the platform compress week 2 so the rest of the timeline holds. If you are scoping a portfolio engagement now, the business case packet is the prerequisite document, and the free scan is the validation step that should happen before you commit to the rollout.
See also: Multi Unit Operator Real Estate Services