Building Permit Application Management System

Overview

The Building Permit Application Management System was designed to digitise a complex end-to-end process that involves property details, applicant information, builder verification, surveyor checks, supporting documents, fee handling, and downstream workflow processing.

Rather than treating the permit journey as a basic form submission, I designed it as a connected digital service built on Salesforce. The system guided applicants through structured steps, validated key data, integrated external checks, handled document uploads, and connected directly to payment and internal processing workflows.

The challenge

Building permit workflows involve more than collecting names and addresses. They often require multiple parties, such as applicants, builders, and surveyors, as well as supporting evidence, property-specific information, regulatory checks, and payment steps.

The challenge was to design a system that could manage all of this in a structured, user-friendly way without forcing applicants or staff into fragmented manual processes. The experience needed to be clear enough for the applicant, while the data captured needed to be rich enough for operational processing and compliance.

What the system needed to solve

• Guide applicants through a multi-step permit process
• Capture applicant, builder, and surveyor details accurately
• Validate property and address information
• Support builder and surveyor registration checks
• Enable document uploads and checklist handling
• Integrate fee and payment workflows
• Reduce manual rework for internal processing teams

System architecture

I designed the solution as a staged digital workflow that combined guided user interaction with backend orchestration. This made it possible to keep the user journey logical while still handling the real complexity of the permit process.

1. Guided multi-step application experience

The application was broken into clear steps so users could move from property selection to applicant details, builder and surveyor validation, documents, and payment in a structured way.

2. Integrated validation and verification

Key validation points were embedded into the process. These included address handling, applicant data checks, and external validation patterns for builders and surveyors. This improved submission quality and reduced downstream issues.

3. Reusable Salesforce architecture

The system used reusable Lightning Web Components, Apex services, and helper patterns for contact handling, record orchestration, uploads, and payment preparation. That made the design more maintainable and reusable across related application services.

4. End-to-end service orchestration

Once the application data was captured, the solution connected it to supporting documents, internal workflow, and payment processing. This created one continuous service experience instead of a disconnected set of tasks.

Property search and selection
        ↓
Applicant details
        ↓
Builder validation / owner-builder path
        ↓
Surveyor validation
        ↓
Supporting documents upload
        ↓
Fee and payment preparation
        ↓
Salesforce record creation + workflow processing

This structure made the application easier to complete for users while making the resulting data easier to process for staff.

Implementation example

A major part of the implementation was assembling structured application data before handing it to the backend services. The example below shows the type of pattern used to prepare a clean payload for record processing.

const permitPayload = {
    propertyId: this.selectedPropertyId,
    applicantEmail: this.applicantEmail,
    applicantType: this.applicantType,
    builderRegistration: this.builderRegistrationNumber,
    builderType: this.builderType,
    surveyorRegistration: this.surveyorRegistrationNumber,
    uploadedFiles: this.uploadedFileIds,
    paymentAmount: this.totalAmount
};

submitBuildingPermit({ payloadJson: JSON.stringify(permitPayload) })
    .then(result => {
        this.recordId = result.recordId;
        this.cartId = result.cartId;
    })
    .catch(error => {
        console.error(error);
    });

In practice, this kind of submission logic worked alongside Apex services, external verification patterns, file upload handling, and payment orchestration so that the user experience stayed smooth while the system still captured the right operational detail.

The implementation typically combined Salesforce Experience Cloud, LWC, Apex, external API validation, file uploads, and payment processing.

Visual examples

This project is best communicated through workflow maps, screen designs, and architecture diagrams showing how the applicant, validation layers, documents, payment flow, and internal processing fit together into one connected service.

Comparison table

Project highlights

Business value

The biggest value of the system was that it reduced friction on both sides of the process. Applicants received a clearer, more structured way to submit permit information, while internal teams received better-quality data and supporting material to process applications more efficiently.

• Improved applicant experience for complex permit submissions
• Reduced manual rework and follow-up effort
• Improved data quality and completeness
• Supported builder, surveyor, and document workflows
• Created a scalable digital permit architecture

FAQ