A partner opens a dashboard midway through the month and sees fees below the previous month's total. Is the firm falling behind? Before answering, check whether the comparison covers equivalent periods and whether both numbers describe the same event.
A useful monthly review separates three questions: what changed, what records explain it, and what action follows. This workflow focuses on making the comparison dependable before interpreting the result.
Choose the question and the period together
For a completed-month review, compare two completed months. For an in-progress check, use explicitly dated partial periods and acknowledge the difference in elapsed working days. A month with holidays or significant planned leave may have less available working time even when the calendar ranges look similar.
Write the comparison dates in the meeting notes. Labels such as current month are convenient on a dashboard, but become ambiguous when someone reads a screenshot later. If seasonality is relevant, add the corresponding month from the prior year as context rather than replacing one imperfect comparison with another.
In Keeney Analytics Flexible Date Ranges, use a preset or custom range for the question being investigated. Check the displayed range on each view you use. Keep the currency, workspace, and scope consistent, or explicitly explain why they differ.
Check what date each measure follows
Clio warns that limiting dates can produce differences when activity occurs in one month and appears on an invoice in another. It also explains that different report types have their own calculation criteria. Matching report names or selecting identical dates does not by itself establish that two totals should agree. Read Clio's date-range guidance. Review its revenue-report definitions.
For Keeney Analytics, net billed fees follow invoice issue dates. Recorded hours follow work dates. Paid-invoice fees concern fully paid invoices and their paid dates; that measure is not a complete account of payment transactions or partial collections. Read the report notes when deciding which measure answers your question.
Hypothetical example: work performed on September 28 is invoiced on October 3 and the invoice is fully paid on November 5. That work can contribute to different months in work, billing, and paid-invoice views. The dates describe different stages, so the timing difference is not automatically an error or a deterioration in performance.
Inspect the change before assigning a cause
Suppose net billed fees rise from $40,000 to $50,000 across two comparable completed periods. The arithmetic increase is $10,000, or 25%. It does not establish that demand, efficiency, or profit increased by 25%. A large invoice issued in the second month could explain much of the movement.
Open the supporting invoice detail and identify the entries responsible for the largest differences. Ask whether they represent repeatable work, an unusual matter, a change in billing timing, or a correction. Keep an explanation attached to the observed number rather than replacing it with a general story about growth.
If you calculate a change outside the product, show both the amount and the percentage. When the earlier value is zero, a percentage increase has no usable denominator. When credits make a baseline negative, a standard percentage can also mislead. Describe those changes in amounts and investigate the records.
Separate period results from current balances
A historical reporting range does not make every number on the page historical. Keeney Analytics' Receivables and Work in Progress reports describe the current sync, including older outstanding records. They do not reconstruct a previous month-end balance.
Keep these figures in a separately labelled part of the meeting pack. They can support today's follow-up decisions, but should not be presented as the balance that existed at the end of the month being reviewed.
If a historical balance comparison is important, use an appropriate dated source or a retained report whose basis is understood. Do not infer the missing earlier balance by changing the date picker. Record when each snapshot was produced and what it includes.
Make the review repeatable
The Keeney Analytics Reports library includes Revenue & Billing and other focused reports, with PDF and CSV exports. Prepare the same report type and scope for each period and retain its measurement notes and source timestamp.
A saved configuration can reduce repeated setup, but it stores choices rather than a frozen report. Relative dates resolve again when the configuration is opened. Preserve the actual export used for the meeting if the team needs to refer back to that version.
Agree a sensible reporting cutoff with the people who maintain the source records. If entries or invoices are corrected after the first review, note the revision rather than assuming the earlier export and the refreshed view must match. Apply the same approach each month.
Finish with an explanation and an action
A concise review note might say: billed fees increased, most of the change came from two invoices for earlier work, and the billing lead will check whether the next cycle contains a similar backlog. That is an illustrative management note, not a claim about any real firm.
Choose the next action only after the explanation is supported. It may be a source-data correction, a billing-process discussion, or closer investigation of a practice area. A dependable monthly comparison gives partners a reason for the movement and a clear next step, instead of a percentage that invites guesswork.