Who Is Responsible When Public Roles Overlap?

The common mistake in a public process involving several organisations is to assume that the body named most prominently controls the whole matter. That can leave a resident asking the wrong office for an explanation while the actual decision or action sits elsewhere. To understand who is responsible when public roles overlap, trace the authority and record for the particular matter, rather than building a general chart of every organisation involved.

Which document records the decision?

Start with the material closest to the decision: a committee report, signed notice, published decision record or formal agreement. A service page may explain where to send a query, but it may not identify who had power to approve a proposal. A project notice may name a lead organisation for communication without describing its authority.

Look for the exact decision, the body or officer that made it, and the record of what was approved or refused. Then note which document supports each point. If a paper says a committee “recommended” a proposal, do not treat that as proof the committee approved it; look for the decision that followed.

This approach keeps the inquiry tied to a particular act. It also avoids conflating three different things: a body’s legal or delegated authority, its contribution to a process, and its public-facing contact role.

How do you distinguish a decision from delivery?

Public work often moves from a decision-making body to a team or provider that carries it out. The decision record may identify who authorised a change; a contract, work notice or operational update may identify who must implement it. These records answer different questions, so read them together only where the matter requires both.

Use the verbs in the source, but do not rely on verbs alone. “Advises”, “recommends”, “approves”, “commissions” and “delivers” suggest different functions; the surrounding text should show what each function means in that process. A body that coordinates the work may not be entitled to alter the decision, while a delivery team may have discretion over practical details without owning the underlying policy choice.

If a record names no decision-maker, or the stated responsibilities conflict, keep that uncertainty visible. Ask for the specific decision record or delegation that identifies who had authority, rather than inferring authority from a logo, meeting venue or job title.

What does a handover leave unresolved?

A referral can move a task without settling who must explain the outcome. When an organisation passes a matter to another body, the useful record is not just the name of the recipient. Look for what was transferred, what information went with it, who now has the next action, and where the resulting decision or update will be recorded.

Say you report a damaged bus shelter to the borough because its website lists street faults. Imagine the borough replies that the regional transport authority owns the shelter and forwards your report. You now have a starting record: the original report, the borough’s reply and the named recipient. The next question is whether the authority will assess the repair and where it will record the outcome; if the borough remains the contact for updates, the handover has moved the repair task but not necessarily the communication duty. The resulting distinction is concrete: one body may assess the asset, while another remains the route for tracking the report.

Keep the trail concise: save the notice or report, record the organisation contacted and any reference it supplies, and note the wording of the reply. This makes it easier to ask a precise follow-up without treating your own notes as an official record.

How can you check overlapping responsibilities?

• Decision record: If a report names a body that approved the proposal, treat that as the stated decision-maker; if it only says “recommended”, look for the later approval record instead.
• Delegated authority: If a paper identifies an officer or committee exercising delegated powers, use that record to understand who could decide; if it gives no delegation, ask which authority applied rather than assuming from the title.
• Delivery record: If a work notice names a contractor or operations team, treat it as evidence of who carries out the work; if it does not identify who authorised the work, consult the underlying decision record.
• Scope: If a map or notice clearly covers the place and subject of your query, use it to narrow the responsibility; if the boundary is ambiguous, ask which area or issue the document covers before relying on it.
• Handover: If a reply names a receiving body and the next action, follow that route; if it only says “referred”, ask who now owns the task and who will provide an update.
• Disagreement: If two bodies give conflicting accounts, retain both replies and ask each to identify the record supporting its position; if neither does, describe the boundary as unresolved rather than choosing one account.

What questions clarify who holds authority?

How should you keep an account of the roles?

For a single matter, a short note is usually enough. Record the decision, the source that identifies the decision-maker, the body expected to act, and any unresolved handover. Separate what the documents state from what an organisation has told you in a reply.

For example, write “The committee record approves the change; the works notice names the contractor; the published material does not say who will provide progress updates.” That is more useful than assigning every organisation a broad label such as “lead” or “partner”. If a body corrects your account, note the correction and the source it points to.

When checking who is responsible when public roles overlap, follow the record from authority to action and keep gaps explicit. The most useful next question is often not who owns the whole process, but which document should exist for the particular decision or handover that remains unclear.