×

iFour Logo
 

Building Voting System

About Customer

The customer is a well-known training and development service provider in Australia that offers training on various computer courses such as MS Excel, MS Office, SQL, Xero, PHP, HTML, CSS, JavaScript, jQuery, and many more. They have helped several clients, both corporate and government with cost-effective training and development services.

Challenge

Managing operations while nominating and electing executives for the building voting process was a difficult and time-consuming task. Keeping a transparent voting process, maintaining confidentiality and security is quite challenging. To overcome the confidentiality issue and automate the voting process, our customer realized the need to develop a reliable and sustainable system for building a voting process which could offer resilient features to the users.

Building Voting System - 01

Technology Used

Technology
Website

Type

Technology
IIS

Web Server

Technology
ASP.NET (C#) Framework 4.0

Programming Language

Technology
Microsoft SQL Server

Database Management Server

Technology
MVC NHibernate

Architecture

Technology
JavaScript, JQuery

Client Technology

Technology
SVN

Version Control

Building Voting System - 02
Building Voting System - 03

Get In Touch With Us

We encourage you to contact us with any questions or comments you may have.

image

The system offers the following features.

  • Secure registration for users and strata managers

  • "Creation, Maintenance and Monitoring" of an AGM (Annual General Meeting) includes owners and general public attendance, registration of proxy voters, registration of executives

  • Generation of the paper-based vote, creation of encrypted URL for vote validators to enter the votes, send URL via email or SMS to vote validators managed by the strata managers

  • Administrator and Strata manager manages nomination of executives and vote validators for each AGM.

  • "Creation and Assignment of owners to lots" is handled by the strata managers

  • "Admin Portal" provides full privileges of the system including administration of strata managers

  • Strata managers are responsible for "Management of Building Managers and Owners"

  • Assignment of EC member for building after EC Vote

  • "Report Generation" module produces dynamic and accurate reports of the results as per the need of the customer

  • Import/Export functionality provides offline utilization of the reports

image Conclusion/Results

With the reliable solution provided by the iFour Technolab Pvt. Ltd., customer was able to automate the entire building voting process. The new system ensured the transparency in voting and confidentiality of the casted votes. The system made the voting process secure by encrypting the voting URL.

 

Related case studies

 

What do our clients say

iFour Testimony - Jan Marteen Kops
iFour Testimony - David Stewart
iFour Testimony - Matthew Bellgrove
iFour Testimony - Darren Fisher
iFour Testimony - Gavin Kretzschmar
iFour Testimony - Carlos Hernandez
iFour Testimony - Jeroen Van Megchelen
iFour Testimony - John Schenk
iFour Testimony - Tim Grant
iFour Testimony - Jan Entjes
iFour Testimony - Michael
 
Blog Our insights
Modernizing applications with the 7 R strategy – A CTO’s Guide

16 October 2025

Lochan Paliwal

Modernizing applications with the 7 R strategy – A CTO’s Guide

Think about the last time CTOs spent most of their time fixing old systems. Updates were slow, servers were expensive, and adding new features took time. Now, things have changed....

Top Shift Left security Best Practices CTOs should consider

10 October 2025

Lochan Paliwal

Top Shift Left security Best Practices CTOs should consider

According to HackerOne, fixing a security issue after software is released can cost 30 times more than fixing it during development. Today, CTOs take a different approach. Shift...

Real-world Consequences of Ignoring DevSecOps In Your Strategy

29 September 2025

Lochan Paliwal

Real-world Consequences of Ignoring DevSecOps In Your Strategy

A few years ago, companies built software first and thought about security later. Developers and security teams did not cooperate, and problems were fixed only after release. This activated DevSecOps vulnerabilities and many DevSecOps failures.