One platform for clients, contractors, agents, properties, orders and invoicing.
A national property-services business was running multiple regions on standalone systems that did not talk to each other. We replaced them with a single web platform, and have been building on it ever since.
Several regions, several systems, one business.
The client managed large REO property portfolios nationally, with a different set of tools in each region and a local contractor network attached to each one. Nothing reconciled. A property could exist in three systems with three different statuses, and the only way to establish the truth was to phone somebody.
Access control was the second problem. Head office, regional managers, field agents and external contractors all needed to see part of the picture and none of them should have been able to see all of it. Bolting permissions onto systems that were never designed for them had produced a set of workarounds nobody was comfortable defending in an audit.
The third was evidence. Work orders moved by email and phone call, so when a client queried a charge or a timeline, reconstructing what had happened was archaeology instead of a query.
A single system with the permission model designed in.
We built one web platform covering the whole operational chain, client, property, contractor and employee management, property bidding, work-order ticketing, invoicing and support, with the access hierarchy as a first-class part of the design instead of a layer added afterwards.
Communication moved inside the system. Bidirectional messaging between office staff, field agents and contractors happens against the record it relates to, so the conversation and the work order are the same artefact. Media captured in the field is processed automatically and attached to the property.
Everything is audited. Every status change, bid, assignment and invoice line carries who and when, which turned client queries from an investigation into a report.
The platform has been extended continuously since. That longevity is the part worth noting: it is not a project we delivered and left, it is a system we have kept current for well over a decade.
Ten modules, one permission model.
Client management
Contracts, service levels, contacts and the reporting each client expects, held per client rather than per region.
Property management
The core record. Location-aware search, status history, verification and the media captured against each visit.
Contractor network
Onboarding, coverage areas, compliance documents, capacity and performance history feeding straight into assignment.
Bidding
Work put to the contractor network and awarded inside the system, so the basis of every award is recoverable later.
Work-order ticketing
The operational spine. Assignment, progress, exceptions and completion evidence against a single ticket.
Employee management
Roles, regions and the permission hierarchy that governs what each person can see and do.
Invoicing
Charges assembled from completed work, not re-entered, which is where most of the old reconciliation effort went.
Search
Location-based property queries and cross-entity search, built for people who know one fact and need the record.
Audit trail
Immutable history on every entity, designed for client queries and internal review, not for developers.
MIS reporting
Operational and financial reporting across regions, from one dataset instead of five spreadsheets.
ColdFusion, SQL Server, and fifteen years of continuity.
Application
Data
Front end
Integration
What the business got.
- Standalone regional systems retired. One record per property, per client and per contractor, which removed the reconciliation work that had been absorbing a meaningful share of head-office time.
- Client queries became a report instead of an investigation. The audit trail answers questions about what happened and when without anyone reconstructing it from email.
- Contractor coordination moved inside the system. Bids, assignments and field evidence live against the work order, which cut the communication failures that had been the most common source of dispute.
- Access became defensible. A permission hierarchy designed in from the start, rather than a set of exceptions that had to be explained during an audit.
- Fifteen years of continuous development. The same team has extended the platform as the business changed, which is why the system still matches how the company operates.
“We endorse iSummation software development team as highly skilled IT experts, very humble and supportive. It is more than 15 years since they are our IT solution provider and become an integral part of our business.”
