Cumberland Council to face questions on agency costs and finances
Summarised from 2 outlets · Updated 31 Oct, 06:17 · Archive
Councillors will quiz Cumberland Council leadership on agency staff expenditure and financial management at a meeting next week.
Cumberland Council members are due to meet at The Civic Centre on Tuesday, 3 November, where councillor Robert Betton will question senior leaders on staffing and finance issues.
Robert Betton will ask council leader Mark Fryer how much the council has spent on agency staff in the current financial year compared with the previous year and whether this spending is increasing or decreasing. He will also seek details of expected savings from measures to reduce reliance on external workers, particularly given the council's ongoing financial challenges.
He will also question Barbara Cannon, the financial planning and assets portfolio holder, about CIPFA's concerns regarding the council's financial management arrangements. He will ask for the total project cost of a new integrated financial system, whether implementation remains on schedule, and what independent verification will be undertaken before the system goes live to ensure it is fully operational and fit for purpose.
How it is being reported
- Cumberland Council to face questions over agency staff costs and finance systemIssues including Cumberland Council staffing and concerns regarding the authority's financial management arrangements will be raised in Carlisle next week.Whitehaven News · 31 Oct, 05:00
- Cumberland Council to face questions over agency staff costs and finance systemIssues including Cumberland Council staffing and concerns regarding the authority's financial management arrangements will be raised in Carlisle next week.Cumberland News · 31 Oct, 05:00
In this story: Cumberland Council · Mark Fryer · Barbara Cannon · Robert Betton · CIPFA · Carlisle
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)