When a municipal website connects to payment portals, agenda systems, maps, or service-request tools, the best approach depends on the resident’s task. A direct link may be enough. An embed may make a focused tool easier to use in context. An integration may be worthwhile when the website needs to organize information from another system.
Start with the handoff you want a resident to experience. Someone paying a bill needs confidence about where the payment takes place. Someone checking a route disruption needs a clear answer without learning which vendor supplies it. Those are different problems, and they deserve different connections.
Use this decision path
- Can the source system already complete the resident’s task well?
Start with a direct, clearly explained link.
- Does the resident need a focused tool beside your own explanation?
Consider an embed, then test it on mobile and with a keyboard.
- Must the website combine, filter, or present data in a distinct way?
Evaluate an integration and assign responsibility for its upkeep.
This is a starting sequence, not a rule that every project must progress through all three options. Choose the least complicated approach that actually meets the need.
Link when the other system owns the transaction
A link is often appropriate when the destination already provides the complete service. Your website’s job is to explain eligibility, required information, expected steps, and where to get help before sending the visitor there.
For example, a payment page can identify the bill types handled by each portal and use specific links such as “Pay a water bill.” Avoid sending every visitor to a generic vendor homepage and expecting them to find the correct service again. If the destination changes domains, make the handoff clear in nearby text. Do not describe a portal as city-operated if a separate provider operates it.
Keep destination ownership visible internally too: record who can fix a broken link and who handles questions about the transaction. Our guide to organizing municipal payment links explores that content problem in more detail.
Embed when context improves the task
An embed can put a map, calendar, or focused search tool beside useful instructions. That can be helpful when the visitor needs both at once. But sharing a page does not guarantee a smooth experience.
Try the entire task on a narrow screen, with a keyboard, and at enlarged text size. Check whether controls remain visible, nested scrolling is confusing, and an error leaves people stranded. Include a descriptive heading and a direct way to open the original service if the embedded experience fails. For technical implementation, the W3C’s iframe-labeling guidance includes labeling frames so their purpose can be identified.
For maps, also consider whether loading an interactive tool immediately is useful to everyone. Our WordPress map integration guide discusses that tradeoff. Do not assume embedding gives your team control over the vendor’s accessibility or release schedule.
Integrate when the website needs to do more
An integration becomes useful when you need information arranged differently from the source interface: filtering notices by route, collecting agenda links in a consistent archive, or combining automated updates with staff explanations.
Before committing, name the source of truth for each field and define what your website is allowed to change. A website that displays a vendor’s information should not quietly become a competing place to edit it. Confirm available interfaces, access requirements, expected update intervals, and the owner of ongoing maintenance with the provider.
Design failure behavior as part of the feature. Will you show a dated last-known result, a clear unavailability message, or a link to another channel? A missing response must not be presented as proof that no records or disruptions exist. The CARTA service-notifications example illustrates why source ownership and fallback behavior belong in the initial design.
Evaluate the whole handoff
Ask a colleague unfamiliar with the system to complete a realistic task. Can they identify the right service, understand where they are going, finish the task, and find help if it fails? Record where they hesitate. That evidence is more useful than choosing an integration because it appears more sophisticated. A dependable connection earns its complexity by making a specific resident task easier.