Why one view misleads
A partner at a small accounting firm opens the monthly report and sees two engagements that both look fine. The first is a fixed-fee bookkeeping client. The hours look normal, but the client has been sending extra requests all quarter, a second entity here, a lender package there, and none of it was ever discussed as outside the agreed scope. The second is an hourly advisory engagement. Time has been logged faithfully, but it has sat unbilled for weeks, and the client has no idea the work is close to the estimate they were given. One problem surfaces at renewal, the other when the invoice goes out.
That scene is an original illustration, not a TwoQM client and not a measured result. The report was accurate. It just showed both engagements the same way when they needed different signals.
TwoQM has already written about recurring bookkeeping task boards by close date, which covers the work of each period, and about engagement letters and organizer completion before work starts, which covers the start-of-work gate. This article is about the partner's view after work is underway: a dashboard that reads fixed-fee and hourly engagements differently.
This is an operations article, not accounting, pricing, or tax advice. Your firm decides how it prices work, what it bills, and what it tells clients.
Hours and fees mean different things in each model:
On a fixed-fee engagement, hours are an internal effort measure. The client does not see them. The risk is quiet scope growth that nobody names until renewal.
On an hourly engagement, hours become the invoice. The risk is unbilled time piling up and a client surprised by the total.
A single "hours this month" column hides both risks.
The engagement record both views share
Start with one record per engagement, whatever the pricing model:
Engagement type. Fixed-fee, hourly, or a mix your firm defines.
Scope. The services listed in the signed engagement letter, in plain words.
Partner and manager. Named people, not "the team."
Period or term. The months or year the engagement covers, plus the renewal or review date.
Status. Active, waiting on client, paused, or wrapping up.
Open client items. Documents or answers the firm is waiting for.
What a fixed-fee view should show
For fixed-fee work, the partner needs to see effort against the firm's own internal budget and anything that drifts outside the letter:
Internal hours against the budget the firm set for the engagement, as a simple on-track or over-budget flag.
Out-of-scope requests, logged by staff as they arrive, with a short description and who asked.
Deliverables by period, such as monthly closes or quarterly filings, with status.
A scope conversation flag the partner can set when it is time to talk with the client.
The renewal date, so scope and fee conversations happen before the next term, not after.
What an hourly view should show
For hourly work, the partner needs to see what the client will be billed and whether it matches what the client expects:
Unbilled time and its age, grouped by engagement, so nothing sits for months.
Hours against the estimate shared with the client, flagged when they approach a point the partner sets.
Time entries waiting for partner review before they go on an invoice.
The billing schedule the engagement letter describes.
A client update flag for when the firm should explain the work before the invoice arrives.
A weekly exceptions list, not another report
Partners rarely need every engagement every week. They need the exceptions:
Fixed-fee engagements with out-of-scope requests not yet discussed.
Fixed-fee engagements flagged over the internal budget.
Hourly engagements with aged unbilled time or approaching the estimate.
Renewals coming up without a scope review.
Engagements blocked on the client.
Each item links to the engagement record, so the partner can act or assign follow-up in one place. The thresholds behind each flag are set by the firm, not by the software.
Where custom software and connected systems help
The data usually lives in several places: time tracking, billing, practice management, and signed engagement letters. Custom software can provide a partner dashboard shaped around how your firm prices and reviews work. Where your existing tools allow it, connected systems work can pull time and billing data into that view, as confirmed during scoping; where they do not, a scheduled import can fill the gap.
A CRM workflow can hold client history and renewal conversations, and business automation can remind managers to log out-of-scope requests and send the weekly exceptions list to each partner.
Client financial information is sensitive, so access should be limited by role.
Where AI helps, and where it stops
AI integrations can read time-entry narratives and draft a summary of work that looks outside the agreed scope, for a manager to confirm. AI can also draft a plain-language client update in English or Spanish for the partner to edit.
AI does not set fees, decide what is out of scope, approve time, write down hours, approve invoices, or send anything to clients. Partners make those calls.
Where to start this week
Pick five active engagements, some fixed-fee and some hourly. For each, write the scope in one sentence, then list anything the client asked for that was not in it, and any time not yet billed. If that takes more than a few minutes per engagement, your partners are working without the view they need.
TwoQM builds custom software, connected systems, and automation for accounting and tax firms. If your engagement reviews still depend on spreadsheets and memory, TwoQM can scope a partner dashboard around the tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Discuss Your Engagement Dashboard Project · Explore custom software