Bylaw Guidance on Shared Services & Agreements - Edinburgh
Edinburgh, Scotland councils and public bodies often use intergovernmental agreements and shared services to deliver services efficiently while remaining within statutory and bylaw frameworks. This guidance explains governance roles, approval steps, risk controls, and practical compliance points relevant to City of Edinburgh arrangements and neighbouring partnerships, with clear action steps for officers and elected members.
Legal basis & authorities
Shared services and inter-authority agreements in Edinburgh are governed by the council's constitution, financial regulations and approved partnership frameworks, together with any statutory duties under Scottish law. Operational responsibility usually sits with service directors and the council's legal and procurement teams.
- Council constitution and standing orders determine authority to enter agreements.
- Financial regulations set budgetary limits and approval routes.
- Monitoring Officer and Chief Finance Officer advise on legality and value for money.
When to use intergovernmental agreements
Use agreements for recurring shared services, joint procurement, service delivery partnerships, or where statutory functions are delivered collaboratively. Agreements should record scope, cost-sharing, decision-making, exit arrangements, data sharing and dispute resolution.
- Operational services: waste, IT, shared regulatory teams.
- Commissioning and contract management arrangements.
- Data protection and information sharing protocols.
Governance & decision-making
Agreements should specify governance bodies, reporting lines, budgetary responsibilities and escalation mechanisms. Records of meetings, risk registers and performance metrics are essential to demonstrate ongoing oversight and compliance with bylaws and statutory duties.
- Set regular governance meetings and published minutes.
- Maintain joint risk register and performance targets.
- Record roles for scrutiny and audit.
Penalties & Enforcement
Intergovernmental agreements themselves seldom create criminal offences; enforcement of service standards and bylaw breaches follows the enforcement powers of the relevant service (for example environmental health, licensing, planning or trading standards). Financial remedies, contractual termination and recovery of costs are typical contractual enforcement tools.
- Fines or contractual penalties where specified in the agreement: not specified on the cited page.
- Escalation for breach: first and repeat remedies depend on contract terms and are not specified on the cited page.
- Non-monetary sanctions: performance notices, termination rights, suspension of access, or referral to internal audit or Ombudsman.
- Enforcer and complaints: City of Edinburgh Council governance, legal and the responsible service handle inspections and complaints; report via the council contact page [1].
- Appeals and review: contractual dispute resolution, review by committee, and statutory appeals where bylaw or regulatory powers are involved; statutory time limits depend on the specific regulatory regime and are not specified on the cited page.
- Defences and discretion: agreements commonly include force majeure, reasonable excuse, remediation windows and variation/consent processes.
Applications & Forms
There is no single universal form for intergovernmental agreements; most require governance reports, legal approval requests and procurement documentation prepared by the lead service. Specific licences or permits (for example planning consents or environmental permits) use the council's published application forms.
- Legal approval: internal authority request and draft agreement attached to committee report.
- Procurement: tender documents and contract award forms per procurement rules.
- Fees: where statutory permits are required, fees follow published schedules on the relevant service pages.
Implementation & risk management
Key implementation steps include legal review, procurement compliance, data protection impact assessment, insurance and accountable officer assignment. Risk sharing and exit planning reduce future disputes.
- Complete legal and financial due diligence before signature.
- Create an exit and transition plan with clear liabilities.
- Document service levels and reporting obligations.
FAQ
- What approvals are needed to enter a shared service agreement?
- Committee approval or a delegated officer decision consistent with the council constitution and financial regulations is typically required.
- Who enforces compliance with the agreement?
- The lead service supported by legal, procurement and governance functions enforces contractual terms; regulatory bylaw powers remain with the relevant statutory service.
- Are there standard templates for these agreements?
- Templates are usually provided by the council legal team for bespoke drafting and must be approved by legal counsel.
How-To
- Identify the services, scope and partners to be covered by the agreement.
- Carry out legal, financial and procurement checks, and prepare a committee report.
- Engage internal stakeholders: legal, finance, data protection and the Monitoring Officer.
- Agree governance, performance metrics and an exit plan; formalise in the signed agreement.
- Monitor delivery, report performance and apply contractual remedies if required.
Key Takeaways
- Ensure legal and financial sign-off before entering agreements.
- Document governance, SLAs and exit arrangements clearly.
- Report concerns promptly to the council governance or responsible service.
Help and Support / Resources
- City of Edinburgh Council contact page
- City of Edinburgh Council democracy and committee papers
- COSLA guidance on joint working and shared services