Find the correct route for a public-records request

Why use this

1. A records requester may know the document they want but not which municipal office holds it or which channel starts a valid request. Search results can surface archived instructions, generic contact forms and unofficial services that add confusion.

2. This job could assemble a route summary for the jurisdiction and record type. Separating verified contacts from unresolved procedural questions helps the requester prepare without assuming that finding a form guarantees access.

Why an agent / simpler alternative

Useful judgment

Interpret departmental responsibilities and reconcile official contact pages with request guidance.

Simpler alternative

Use the municipality’s current records page directly when the record holder is obvious.

Unsuitable when

The user needs legal advice about exemptions, litigation strategy or enforceable deadlines.

Proposed inputs

1. Name

   Request description

   Owner

   Requester

   Minimum scope

   Record type, date range and relevant municipality or department

   Quality check

   Avoid unnecessary personal details while identifying the likely custodian.

2. Name

   Official guidance copies

   Owner

   Research owner

   Minimum scope

   Current contact pages, request instructions and linked legal guidance

   Quality check

   Record dates and distinguish official pages from search snippets.

Access and setup — proposed or unknown

Proposed minimum

1. Read public official pages and produce a route summary; do not submit a request.

Compatibility unknowns

1. Unknown: current municipal contact details, portal access and applicability of published guidance.

External actions requiring approval

1. Filing requests, sending personal information, paying fees or accepting request terms.

Expected deliverable and review checks

Proposed artifact

Verified-channel summary with department, contact route, official links, guidance date and questions still requiring confirmation.

Critical checks

1. The channel belongs to the correct municipality and record holder.

2. Procedural guidance is described accurately without inventing legal entitlements or deadlines.

Missing output evidence

This overlay adds no new output inspection or execution validation. Preserve the canonical implementation evidence and its outcome limits.

Failure signals and proposed responses

1. Signal

   An archived page lists an office that has been reorganized.

   Why it matters

   The request could be delayed or sent to the wrong recipient.

   Proposed response

   Prefer current official navigation and flag conflicting contact details for confirmation.

2. Signal

   A general enquiries form is mistaken for the records-request channel.

   Why it matters

   Submission may not enter the intended process.

   Proposed response

   Verify the form’s stated purpose and preserve the official request instructions separately.

Effort and cost — unknown

Setup work

1. Specify the record category and likely custodial department.

Ongoing review

1. Recheck changed links and review any fee or clarification notices separately.

Unknowns

1. Unknown: processing time, applicable fees and need for legal advice.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Synthetic municipal pages show an old contact, a current records portal and a general enquiries form.

Acceptance checks

1. Only the current dedicated route is recommended.

2. The old contact conflict and relevant guidance link remain visible.

Stop conditions

1. Legal interpretation, a fee commitment or an actual submission is required.

Limits

1. A route summary supports preparation; it does not establish disclosure rights or predict the authority’s response.