Home › Customer Stories › Cork City Council: Parking Permit Process Redesign
Case Study • Local Government • Ireland
How Cork City Council Simplified Its Residential Parking Permit Application
Cork City Council reviewed and redesigned its residential parking permit application process using Submit.com. By introducing persona-based conditional logic, the council removed unnecessary questions for applicants, reduced incomplete submissions, cut staff follow-up workload, and strengthened GDPR compliance across the process. The project was delivered in three structured phases: process review, redesign, and implementation.
<6%
Paper applications remaining at peak digital adoption
3
Structured phases: process review, redesign, implementation
Multiple
Resident personas (homeowners, occupiers, renters) handled by one adaptive form
Background
Cork City Council is one of Ireland's largest local authorities, serving a population across the city and its extended region with approximately 1,300 employees across multiple departments (Cork City Council case study). The council has used Submit.com to manage a broad range of resident-facing and internal processes, from arts grants to road licensing. Parking permit applications were among the first workflows the council digitised, and they remain one of the highest-volume resident services the council manages online.
As the parking permit process matured, the council undertook a dedicated project to review and improve it. The goal was not simply to move a paper form online, but to rethink the process from the resident's perspective: reduce friction, remove unnecessary data collection, and align the form more closely with how different residents actually apply.
The Challenge
The existing application process had several friction points that affected both residents and council staff. The form presented every question to every applicant, regardless of whether those questions were relevant to their situation. A homeowner applying for a permit saw the same set of questions as a renter, even where the information required was entirely different. This created confusion, increased the time it took to complete the form, and contributed to incomplete submissions.
For staff, the downstream effects were equally visible. Incomplete applications generated follow-up workload. Internal processes relied on ICT support for changes that should have sat with the programme team. Email communications to applicants were inconsistent. And the process lacked the documentation and data minimisation practices needed to satisfy GDPR requirements fully.
The council set out to address all of this in a structured way, with clear objectives rather than incremental changes.
Project Objectives
- Improve clarity and usability of the online application process for residents
- Simplify form structure and remove repetitive or unnecessary questions
- Reduce redundant data collection and align with data minimisation requirements
- Improve internal staff knowledge and reduce reliance on ICT support
- Ensure compliance with data protection requirements (GDPR)
- Improve consistency of communications through updated email templates
The Approach: Three Structured Phases
The council delivered the project in three defined phases, moving from diagnosis through redesign to a managed public launch.
Phase 1: Process Review
The council began by mapping the existing process end to end. This involved engagement with key stakeholders to identify where inefficiencies sat, where data was collected unnecessarily, and where applicants were most likely to drop off or submit incomplete forms. The review gave the project team a shared understanding of what needed to change and why, rather than making changes in isolation.
Phase 2: Redesign Using Persona-Based Conditional Logic
The most significant change in the redesign was the introduction of a funnel-based, persona-led form structure using Submit.com's conditional logic (child question) functionality. Rather than presenting all questions to all applicants, the redesigned form identifies each resident's situation early in the process through a multiple-select question. From that point, the questions shown are tailored to that applicant's circumstances.
The council identified three primary applicant types: homeowners, occupiers, and renters. Each has different documentation requirements and different circumstances. Under the old process, all three groups saw every question in the form, including questions that did not apply to them. This added length and caused confusion.
With Submit.com's child question feature, a resident selects their situation at the start of the form and is shown only the questions relevant to their persona. Questions that do not apply are hidden entirely. This shortens the form, removes a source of confusion, and produces more complete submissions because residents are no longer confronted with questions they cannot answer.
How child questions work in Submit.com
Submit.com's child question (conditional logic) feature lets administrators attach follow-on questions to specific answers within a multiple-choice or multiple-select question. When an applicant selects a particular option, only the questions relevant to that selection appear. Questions attached to other options remain hidden. This creates a form that adapts to the applicant, rather than requiring the applicant to navigate a form designed for everyone at once. It is available on multiple-choice, multiple-select, yes/no and image-select question types.
Phase 3: Implementation and Communication
Before the new process went live, the council ran a planned communication campaign to inform residents that the old process would be retired. Notices were published on the council website and within the existing form itself, giving applicants clear advance notice of the changeover date. The phased communication reduced the risk of confusion at the point of transition and meant residents arrived at the new form having been told what to expect.
Internal staff received training to support the updated process, reducing the dependency on ICT for day-to-day administration. This gave the programme team clearer ownership of the form and its configuration without requiring specialist technical input for routine changes.
Outcomes
The project delivered improvements across the resident experience, internal operations, and compliance. The council's project overview (the primary source for this case study) records the following outcomes.
| Area | Outcome |
|---|---|
| Resident experience | Simplified, more intuitive application process with less duplication; questions personalised to each resident's situation |
| Communications | Improved and more consistent applicant communications through updated email templates; clearer upfront information |
| Submission quality | Reduced incomplete submissions |
| Staff workload | Reduced staff follow-up workload resulting from incomplete or unclear applications |
| ICT dependency | Reduced reliance on ICT through enhanced staff training and clearer internal process ownership |
| Compliance | Strengthened internal processes including identification and management of GDPR considerations across the form |
Note: The outcomes above are drawn directly from the council's internal project overview document. Specific before/after volume figures and precise time savings are not stated in that document and cannot be verified independently. The broader Cork City Council case study records that paper applications fell to under 6% at their lowest across high-volume processes including parking permits (Cork City Council case study).
What This Means for Other Local Authorities
Residential parking permits are a common high-volume, resident-facing process for most local authorities in Ireland and the UK. The problems Cork City Council addressed are not unique to Cork: forms that show irrelevant questions to all applicants, inconsistent communications, staff following up on avoidable errors, and GDPR obligations that are hard to satisfy with a generic form design.
The Cork City Council approach demonstrates that process redesign does not require a complete platform change. The council already used Submit.com. The improvement came from using the platform's existing conditional logic tools more deliberately, combined with a structured review of what the process was actually asking applicants to do.
Three patterns from this project are transferable to any council managing similar permit or licence application workflows:
- Identify your applicant types before you build your form. If different residents need to provide different information, design for that from the start rather than asking everyone the same questions.
- Map the full process, not just the form. The council's review covered communications, internal ownership and GDPR, not only the questions a resident sees. That breadth is what produced improvements across all three areas.
- Manage the transition actively. Communicating the changeover to residents in advance, through both the website and the old form, reduced disruption at the point of cutover.
Frequently Asked Questions
What is persona-based form design for council applications?
Persona-based form design means structuring an application form so that the questions shown to an applicant depend on who they are. In a parking permit context, a homeowner, an occupier and a renter have different documentation and eligibility requirements. Rather than presenting every question to every applicant, the form identifies the applicant's situation early and shows only the questions relevant to their persona. This reduces form length, improves completion rates and produces cleaner submissions for staff to process.
How does conditional logic reduce incomplete submissions for council permit forms?
Incomplete submissions often result from applicants encountering questions they cannot answer or do not understand why they are being asked. Conditional logic (also called child questions or logic jumps) hides questions that do not apply to a given applicant. The form becomes shorter and more relevant, which reduces the chances of an applicant abandoning mid-way or submitting without completing a required field. For council staff, fewer incomplete submissions means less follow-up correspondence and faster processing.
How does Submit.com support GDPR compliance for council application forms?
Submit.com supports GDPR compliance in council forms through a combination of platform-level controls and good form design practice. At the platform level, Submit.com supports role-based access permissions, audit trails, SSO and MFA, and data protection impact assessment (DPIA) processes. At the form design level, conditional logic helps with data minimisation by ensuring the council only collects information that is actually relevant to each applicant's situation, rather than collecting everything from everyone.
See how Submit.com works for your council
Whether you are managing permits, grants, licences or resident services, Submit.com adapts to your process without heavy IT work.
Book a demo