Rank your CAM review queue
The biggest CAM bill should not lead every queue.
A ready file may deserve earlier review. A larger file may lack basic proof.
CLA describes CAM reviews that compare lease terms with year-end CAM totals. That page does not set queue weights.
This board keeps each file check beside its rank.
Gate file readiness first
A queue only works with comparable inputs.
Start each row with these fields:
- Client and site
- Reconciliation year
- Annual CAM billed
- Prior comparable amount
- Comparison method
- Statement delivery date
- Delivery date source
- Objection window source
- Lease state
- Amendment state
- Backup state
- Complexity flags
- Assigned reviewer
- Review class
- Queue state
Require three source groups. Keep the governing lease package first.
Then require the annual statement. Last, require a sourced date anchor.
Do not guess a review deadline. Record the source or mark it unknown.
Use the document request SOP. It can guide the first request.
Use four queue states
Give each file one clear state.
| State | Meaning | Next owner |
|---|---|---|
| Waiting | A named source is missing | Client owner |
| Ready | Core proof is present | Queue manager |
| In review | A reviewer accepted the file | Assigned reviewer |
| Decision | The file needs partner judgment | Partner |
Do not hide missing files inside Ready. Return them with one reason.
Use these return codes:
| Code | Missing source |
|---|---|
| LEASE | Signed governing lease |
| CHANGE | Signed amendment or side letter |
| STATEMENT | Annual CAM statement |
| DATE | Delivery date proof |
| BACKUP | Needed landlord support |
The return note should name the owner. It should also name the next request.
Score only ready files
The score below is a planning model. It is not an industry benchmark.
Score four factors from zero to two. Keep the source beside each point.
Date pressure
- Zero: No sourced date event
- One: A sourced event exists
- Two: A sourced event needs prompt review
The lease and current law control real rights. Internal dates do not.
Source-backed change
- Zero: No comparable source
- One: A source-backed change exists
- Two: The client asked about that change
State how you checked the change. A change does not prove an error.
Amount exposure
- Zero: Annual amount is unknown
- One: Annual amount is known
- Two: The amount matters to client scope
Do not turn amount into expected recovery. It only supports review order.
Hard review flags
- Zero: No known review flag
- One: One review flag exists
- Two: Send it to a senior reviewer
Flags may include amendment conflicts. Share questions may also need senior time.
Legal meaning should go to counsel. Do not score it as staff work.
Sort six fictional files
This example is fictional. It does not show client results.
Each score follows the model above.
| File | Date | Variance | Amount | Complex | Total |
|---|---|---|---|---|---|
| Alder | 2 | 1 | 1 | 1 | 5 |
| Birch | 1 | 2 | 1 | 0 | 4 |
| Cedar | 1 | 1 | 2 | 0 | 4 |
| Dogwood | 0 | 1 | 1 | 1 | 3 |
| Elm | 2 | 2 | 2 | 2 | Held |
| Fir | 1 | 0 | 1 | 0 | 2 |
Elm has the largest possible score. Yet its signed lease is missing.
Elm leaves the active queue. Its owner requests the signed lease.
Alder enters first. Its sourced date gives it priority.
The order does not predict a finding. It directs scarce review time.
Test the date weight
Now reduce date pressure by one point. Leave every other fact unchanged.
Alder drops to four. Birch and Cedar remain at four.
The queue now needs a tie rule. Choose the lower review class first.
That choice may reduce blocked work. It is still a firm policy.
Record each weight change. Do not rewrite old scores without a note.
Reserve senior review
Some files consume more senior time.
Mark these before work starts:
- Amendment order conflict
- Unclear allocation method
- Missing client approval
- Legal meaning question
- Weak source citation
The first two may need senior review. Legal meaning goes to counsel.
Use the partner signoff sheet. It helps show who approved final work.
Set a work limit
Do not copy a one-size files-per-person target.
IOFM keeps benchmark context with each report. Its archive does not set CAM review capacity.
Build your limit from observed firm work.
Track review start and finish dates. Track the review class too.
Then count open files by reviewer. Watch where quality checks begin waiting.
Set the first limit from that record. Change it only with new evidence.
A limit should protect partner review time. It should not promise output speed.
Run the board weekly
Review Waiting files first. Close stale requests with a reason.
Next, confirm dates and client scope. Move changed rows with source notes.
Then review the active work limit. Do not add work above it.
Last, send Decision files to the named partner.
Use this weekly checklist:
- Every row has one state.
- Every score has a source.
- Every hold has a reason.
- Every file has an owner.
- Every review has a class.
- Every partner choice has a date.
Connect the service line
The queue starts after the offer fits.
Use the CAM offer map. It sets scope before intake.
Use the objection guide. It helps answer client concerns.
Use the local SEO plan. It keeps demand tied to real service proof.
See the expense consultant growth pillar. It joins all four guides.
Compare other paths in the Practice Growth hub.
Browse the expense consultant resource hub. It has more review tools.
Where CAMAudit fits
Expense reduction consultants own the portfolio queue. They choose the ready client file.
CAMAudit can analyze the selected lease and CAM statement. It may flag source-linked items.
The partner reviews and signs the branded CAM audit. The queue then records that decision.
A checked queue item may support a dispute letter draft. Your firm reviews it.
It is not legal advice. Have counsel review before sending.
Use the service line guide. It helps define delivery roles.