Rebuilding a regional bank intranet with DotNetNuke

A regional bank can have a strong community presence and still struggle with an intranet that feels dated, fragmented and difficult to manage. In this case study, a growing Australian banking group replaced its ageing internal portal with a secure DotNetNuke platform designed for branch teams, lending specialists, contact-centre staff and corporate services.

The project focused on practical outcomes: faster access to policies, clearer internal communications, simpler content publishing and a dependable experience across offices and regional branches. Aricie’s experience with custom software, business portals and professional training provided a useful foundation for connecting the platform to the bank’s existing systems.

A familiar problem for a distributed bank

The bank operated across New South Wales and Queensland, with teams in Sydney, Newcastle, Brisbane and smaller regional centres. Staff in a branch near Tamworth could need different information from a compliance officer in Parramatta, while a lending manager in Toowoomba required quick access to current forms and approval procedures.

The old intranet had grown through years of additions. Documents were stored in several libraries, news was sent by email, and staff often relied on bookmarks to find frequently used resources. Search results were inconsistent, ownership of pages was unclear, and a policy update could take days to reach every team. In Australian workplace language, the portal had become a bit of a “she’ll be right” system: useful enough to survive, but too unreliable for a regulated organisation.

The bank also needed to support multiple time zones and varied connectivity. A team in western Queensland could not be expected to use a heavy, image-rich interface designed for a metropolitan head office. The new solution had to be responsive, efficient and suitable for employees working from branches, home offices and customer locations.

Turning requirements into a clear portal structure

Aricie began with workshops involving operations, risk, human resources, IT, branch managers and frontline staff. Rather than transferring every old page, the project team mapped common tasks: finding a lending checklist, checking a leave policy, submitting a technology request, locating a branch form and reading an urgent operational notice.

This discovery work shaped a simpler information architecture. The homepage provided role-based shortcuts, current alerts and prominent links to the most-used services. Departments received managed areas with clear publishing responsibilities, while policies were organised by subject, audience and review date. A controlled taxonomy made it easier to filter content by branch operations, lending, compliance, people and technology.

The design also reflected how Australian staff actually work. Pages were tested on standard office laptops, tablets used in branches and mobile screens used during travel between locations. Plain English labels, familiar navigation and restrained use of corporate terminology helped employees find answers without needing a training manual for every task.

Using DotNetNuke for governance and flexibility

DotNetNuke, now commonly known as DNN, supplied the portal framework while allowing the bank to tailor modules, workflows and permissions. Editors could publish news and documents through controlled processes, and business owners could review material before it appeared to staff. Version history and approval records created a clearer audit trail for policies and operational guidance.

Custom components connected the intranet with the bank’s identity provider, service desk and selected internal applications. Single sign-on reduced password fatigue, while role-based access ensured that confidential material was visible only to authorised groups. A searchable document centre gave staff one dependable route to approved templates and procedures.

The bank also retained the ability to evolve the portal without commissioning a full rebuild each time. New departments, campaigns and internal services could be added within the established framework. This was especially valuable in a market where regional financial institutions must respond quickly to regulatory updates, customer expectations and workforce changes.

Making adoption part of the delivery

A technically sound portal would have achieved little if employees continued using old email folders and personal bookmarks. Aricie therefore included administrator coaching, editor training and practical user guidance. Content owners learned how to write concise announcements, apply metadata, retire outdated documents and use approval workflows correctly.

Pilot groups from metropolitan and regional locations tested the first release. Their feedback exposed small but important issues, such as terminology that made sense to head office but confused branch employees, and links that were easy to miss on smaller screens. These findings were addressed before the wider rollout, giving staff a familiar experience from the first day.

The change programme also recognised local workplace culture. Short demonstrations during team meetings worked better than long formal sessions, and quick-reference guides used direct language rather than technical jargon. Staff could see how the intranet would save time during a busy morning rather than hearing only about platform features.

Measuring the value after launch

Within the first quarter, the bank reported fewer requests for routine policy documents and a marked reduction in duplicate email announcements. Search analytics showed which resources staff needed most, helping content owners improve labels and identify gaps. Managers gained a central space for operational notices, while employees had greater confidence that the document they found was current.

The portal’s reporting tools also supported ongoing governance. Unused pages could be reviewed, overdue content could be escalated and high-demand searches could inform future improvements. These capabilities turned the intranet from a static repository into a managed business service.

For an organisation serving customers across large distances, dependable digital communication is a practical advantage. A well-structured DNN intranet helps keep branches aligned, supports compliance and gives employees the information they need without adding another layer of administrative work. Aricie’s presence across several business locations can also support projects that involve distributed stakeholders, as shown through its office network.

Bring your internal portal into line with the way your teams work. Work with Aricie to assess your current intranet, plan a secure DotNetNuke migration and build a platform that is easier to manage, search and use across every branch.