The problem
Work-in-progress reporting is one of the most spreadsheet-heavy processes in any service-based business. Time and expenses sit in a practice management or time recording system, billing decisions sit with project leads, and the WIP position itself is usually rebuilt every month in Excel. Numbers are copied across, ageing buckets are recalculated, and commentary is chased from partners or project managers just before the management pack is due.
The result is a WIP report that is already out of date by the time it lands. Old WIP hides in the detail, write-offs are made reactively, and no one has a live view of which jobs are slipping into risky ageing bands.
Why it matters
WIP is cash that has not yet been billed. The longer it ages, the harder it becomes to recover. Stale WIP leads to write-offs, margin erosion and difficult conversations with clients who do not expect a large invoice for work done months ago.
From a control perspective, manual WIP reporting also creates risk. Different versions of the spreadsheet circulate, ageing logic is inconsistent between teams, and there is little audit trail behind the numbers presented to leadership. For a CFO or finance director, that undermines confidence in both the reported position and the decisions being made from it.
The opportunity
A governed WIP ageing dashboard pulls time, expenses, billing and project data directly from source systems, applies consistent ageing rules, and presents the position in a way that finance, operations and project leads can all trust.
No-code automation makes this realistic without a major IT project. Data can be refreshed on a schedule, exceptions can be flagged automatically, and AI can be used to summarise ageing trends, draft commentary or highlight jobs that look unusual compared to historic patterns. The aim is not a one-off report but a repeatable process that finance owns and operations can act on.
Example workflow
1. Connect the source data
Connect to the practice management or time recording system, the billing or ERP system, and any project or job master data. Include client, project, partner or owner, time entries, expenses, bills raised and write-offs.
2. Standardise and prepare the data
Normalise project codes, client identifiers and owner names across systems. Convert time and expenses to a consistent monetary value using the correct charge-out rates. Flag missing rates, missing project owners or jobs without a status.
3. Apply business logic
Calculate WIP by job as time and expenses minus amounts billed and written off. Apply ageing bands such as 0-30, 31-60, 61-90, 91-180 and 180+ days based on the date work was performed. Allow different rules by service line or office where needed.
4. Run checks and controls
Reconcile total WIP to the general ledger or practice management control account. Check for negative WIP, jobs with no recent activity, jobs over a value threshold, and clients with multiple ageing jobs. Log every check and its result.
5. Produce outputs
Publish a dashboard with WIP by ageing band, by partner or owner, by service line and by client. Provide drill-down to job level. Generate partner-specific views so each owner sees only their portfolio. Optionally use AI to draft a short commentary on movements since last month.
6. Review exceptions
Route flagged jobs to the relevant partner or project manager for a billing, write-off or hold decision. Capture the decision and the reason against the job so the audit trail is complete.
7. Move to governed operation
Schedule refreshes, lock down the logic, document the data sources and ageing rules, and assign clear ownership in finance. Treat the dashboard as a controlled process, not a personal spreadsheet.
What good looks like
- A single, trusted WIP position that reconciles to the ledger.
- Consistent ageing rules applied across the whole business.
- Live or daily refresh rather than a monthly rebuild.
- Clear ownership of every aged job, with documented decisions.
- Exception-based review instead of line-by-line spreadsheet checks.
- Full audit trail of data sources, logic and write-off approvals.
- AI used to support commentary and pattern spotting, not to replace judgement.
Benefits
For the finance team
Less time rebuilding spreadsheets each month, faster close, and confidence that the WIP position presented is consistent and reconciled. Write-offs become a controlled decision rather than a year-end surprise.
For leadership
A clear view of unbilled work, ageing risk and billing performance by partner, service line or office. Better input into cash flow forecasting and earlier visibility of margin risk.
For the wider business
Project leads and partners see their own WIP in near real time and can act on it. Clients receive more timely bills, which improves both cash collection and the client relationship.
Where to start
Start with one service line or office where WIP is material and the data is reasonably clean. Replicate the existing ageing logic first so the numbers can be trusted against the current report, then improve the rules and add exception handling. Once finance trusts the output, extend it across the business and retire the manual spreadsheet.
How 4th Revolution can help
4th Revolution is a finance-led, data-led specialist in no-code automation and embedded AI. We understand WIP, billing and the practical realities of professional services finance. We do not just build a dashboard and walk away. We design a governed, repeatable process with documented data sources, controlled logic, clear ownership and the right level of AI support, so the WIP ageing dashboard becomes part of how the business runs rather than another spreadsheet to maintain.
Example outcome
Before: WIP is rebuilt every month in a large spreadsheet, takes several days to prepare, and is already out of date when presented. Aged WIP is only discussed at quarter-end, and write-offs are a recurring surprise.
After: WIP is refreshed automatically from source systems, reconciled to the ledger, and available to partners and finance on demand. Aged jobs are flagged as they cross thresholds, decisions are captured against each job, and month-end reporting becomes a review rather than a rebuild.