Alter layouts, finishes, building services or existing installations.
AlterWorks Management, governed end to end
Every AlterWork.
Every AlterWork.
One controlled
journey.
Modifications
Improvements
AlterWorks
Fit-outs
Reconfigurations
Developer-led governance
PMO-managed delivery
Audit-ready records
Portfolio control centre
Live
DEVELOPER PORTFOLIOFit-out command centre
August 2026Active applications14812 need action
Technical reviews244 disciplines
Inspections31This week
Application pipelineLive portfolio
Priority actionsToday
Technical response overdueRetail unit · 2 days
Inspection outcome pendingOffice · Level 14
Developer NOC readyHealthcare suite
ApprovalDeveloper NOC readyAll conditions verified
Portfolio96% SLA complianceAcross active workflows
One application recordEvery document, decision and communication stays connected.
One operating standardConsistent rules across communities, assets and project types.
One accountable teamTechnology and professional delivery under one PMO framework.
A clearer category for existing-property works
AlterWorks Management turns planned changes into a controlled delivery process.
The process can be configured for internal refurbishments, building-services upgrades, extensions, landscaping, structural works and authority-dependent changes, with requirements determined by each Developer and property.
Upgrade performance, amenity, safety, accessibility or asset quality.
Change how an existing unit, villa or shared area is arranged or used.
Manage additions, GFA implications, external works and authority dependencies.
Unit→Application→Approved scope→Controlled delivery→Verified outcome
The operating challenge
Existing-property works are too important to run through inboxes and spreadsheets.
Each application touches property information, customer expectations, Contractor competence, technical compliance, commercial obligations, site access and final handover. When those records are fragmented, Developers lose time, visibility and control.
OnePermit creates a governed route from first request to final closure. It makes requirements clear, presents the next action to the right party and gives the Developer and PMO team a live, defensible portfolio record.
01
Less administrative frictionGuided submissions, structured reviews and automatic status updates reduce avoidable follow-up.
02
Earlier risk visibilityTechnical, financial, authority and inspection dependencies are surfaced before they become delays.
03
Consistent decisionsConfigured rules, approval gates and controlled records support fair and repeatable governance.
Inside the platform
One workspace for the complete application lifecycle.
Each participant sees the work relevant to them. The underlying application remains connected, current and visible to authorised stakeholders.
01
Intake & scope
Start with a guided, complete application.
Customers identify the property, proposed works and supporting information through a structured journey. Property, identity and company documents can be extracted for confirmation, while missing or inconsistent information is flagged for review.
- Property and applicant verification
- Configured scope-of-work catalogue
- Document requirements by project type
02
Technical control
Coordinate reviews without losing context.
Drawings, calculations, comments, revisions and approvals remain attached to the same application. PMO can route work to the required disciplines while customers see one clear external status.
- Architectural and MEP coordination
- Structural and specialist inputs
- Versioned comments and submissions
03
Site assurance
Turn inspections into traceable evidence.
Initial, work-stage, hold-point and completion inspections are scheduled against availability and recorded with findings, checks, photographs, violations and rectification outcomes.
- Community-based scheduling
- Assigned inspectors and site contacts
- Defect closure and repeat inspection history
04
Commercial governance
Keep fees, deposits and liabilities visible.
Application charges, deposits, invoices, payment evidence, violations, adjustments and refunds are linked to the relevant record, with role-controlled verification and management reporting.
- Payment and deposit gates
- VAT-ready financial records
- Portfolio statements and reconciliations
05
Approvals & handover
Issue controlled records and close with confidence.
Owner consents, authority approvals, Developer NOCs, compliance agreements, work permits and handover documents follow defined approval paths. Final issued records are locked into the application history.
- Digital approval and signature paths
- Authority and Developer dependencies
- Completion and closeout evidence
06
Portfolio intelligence
Move from record tracking to operational insight.
Dashboards and monthly reports bring together application volume, pipeline status, SLA performance, inspections, Contractors, violations and financial position for informed management decisions.
- Role-specific dashboards and filters
- Management and finance reporting
- Drill-down from KPI to source record
AlterWorks Management
The platform organises the work. PMO provides the professional judgement.
OnePermit is offered as an operating model, not simply software access. PMO Consultancy can configure the governance framework, manage applications, coordinate technical inputs, carry out inspections and support the Developer through reporting and continuous improvement.
Fit-out programme management
Operating procedures, responsibility matrices, approval authorities, service levels, risk controls and escalation routes aligned to the Developer's portfolio.
Design and submission review
Coordinated review of architectural intent, building interfaces, structural implications, constructability and the required specialist submissions.
Authorities and NOC coordination
Clear mapping of Developer requirements, relevant authority dependencies, supporting documents, conditions and approval status.
Inspection and quality assurance
Planned inspections, photographic evidence, observations, violation controls, rectification verification and readiness for completion.
Cost, deposit and risk control
Transparent fees, payment verification, deposits, violations, adjustments and auditable financial histories across every application.
Handover and record assurance
Completion checks, defects closure, as-built and closeout-document verification, final records and portfolio reporting.
Professional services behind OnePermitPMO's broader capabilities include project and programme management, fit-out management, risk management, PMO set-up, concept design, design review, structural calculations, quantity surveying, procurement, planning, authorities coordination, feasibility and training.
Explore PMO Consultancy
Designed around real responsibilities
Clearer for every participant.
Clearer for every participant.
Controlled for the Developer.
Developers & asset owners
See the portfolio, set the rules, approve critical decisions and monitor performance without becoming the administrative bottleneck.
- Portfolio and community oversight
- Developer NOC and GFA decisions
- Management and finance reports
Customers & tenants
Understand what is required, what has been completed and exactly what must happen next through one guided workspace.
- Application and payment journey
- Owner consent and documents
- Neutral, understandable status
Contractors & consultants
Manage formal submissions, site requirements, inspections, workers, variations and closeout records against a defined scope.
- Technical submission control
- Inspection bookings and evidence
- Work permits and handover
PMO delivery teams
Coordinate high volumes of work with role-based queues, internal collaboration, measurable service levels and a complete audit trail.
- Assignment and review workspaces
- Inspection and finance controls
- Escalation and SLA visibility
Governance by design
Control is built into the operating model—not added at the end.
OnePermit translates the Developer's requirements into visible workflow gates, permissions and decision records. Teams retain the flexibility to manage real projects while the system protects accountability and historical evidence.
Discuss your governance modelRole-based access
Customers, contractors, reviewers, inspectors, finance, PMO management and Developer representatives receive appropriate permissions and views.
Approval and payment gates
Configured prerequisites prevent work from moving forward before the required scope, financial, inspection or authority conditions are met.
Versioned controlled records
Rules, comments, drawings, approvals and final documents retain their relationship to the applicable application and scope version.
Audit and management evidence
Actions, timestamps, decisions and report outputs support operational oversight, escalation, investigation and continual improvement.
Implementation
Configured around your portfolio.
Configured around your portfolio.
Introduced with your teams.
A OnePermit implementation begins with the operating model: the assets, stakeholders, approval authorities, service standards and risk controls that must be reflected in the platform.
- 01
Discover
Review the portfolio, current process, pain points, project types, communities and stakeholder responsibilities.
- 02
Design
Define the target workflow, approval matrix, scope catalogue, documents, fees, deposits, inspections and reporting needs.
- 03
Configure
Prepare the branded environment, users, rules, templates, notifications, integrations and management controls.
- 04
Validate
Run role-based scenarios, data and security checks, operational acceptance and team training before controlled launch.
- 05
Operate & improve
Monitor adoption, service levels and portfolio performance, then refine processes through managed governance reviews.
A connected operating environment
Built to support secure communication, payments and future integrations.
Transactional notices and user-controlled notification preferences keep stakeholders informed without exposing internal PMO discussions.
Hosted payment and verified callback architecture supports secure settlement while retaining the full financial record in OnePermit.
Provider-neutral signing workflows can return completed approval evidence to the correct controlled record.
A versioned application interface supports future enterprise, mobile, SMS and external-system integrations as requirements mature.
Frequently asked questions
What organisations usually ask before adopting OnePermit.
Every portfolio has different rules and risk priorities. These answers explain the standard OnePermit model; the implementation workshop determines how it should be configured for your organisation.
Ask us a questionIs OnePermit only a software portal?
No. OnePermit combines the workflow platform with PMO Consultancy's governance, technical coordination, inspection and programme-management capabilities. A Developer may operate the configured platform internally or appoint PMO for AlterWorks Management.
Who is OnePermit designed for?
It is designed for Developers, asset owners, community managers and portfolio operators that need a consistent way to manage tenant or owner fit-outs, property modifications and the related approvals, inspections, commercial controls and records.
Can OnePermit follow our existing rules and approval structure?
Yes. The implementation process maps your communities, unit types, scope items, document requirements, approval authorities, fees, deposits, inspection requirements, service levels and reporting needs. Governance remains controlled and versioned as requirements evolve.
Does the platform replace professional technical review?
No. The platform structures and records the review process; qualified professionals still exercise technical judgement. PMO coordinates the required architectural, structural, building-services, authority, commercial and site inputs for each project.
What records remain with each application?
The application can retain property and identity documents, scope versions, drawings, technical comments, payments, approvals, NOCs, agreements, inspection evidence, violations, work permits, communications and completion records, subject to role permissions.
Can customers and contractors see internal PMO discussions?
No. OnePermit separates internal PMO collaboration from public application messages. External users receive appropriate status and action information without access to confidential internal routing, reviewer discussion or management decisions.
How are fees, deposits and payments managed?
Configured charges and deposits are linked to the applicable workflow stage. The platform records invoices, evidence, verification, settlements, adjustments and refunds. Payment-gateway activation depends on the selected provider and agreed commercial setup.
How long does implementation take?
The schedule depends on portfolio complexity, data readiness, integrations and the number of workflows being introduced. PMO begins with discovery and target-process design, then agrees a controlled configuration, validation, training and launch plan with the Developer.
Can OnePermit support multiple developments or communities?
Yes. The architecture supports multiple Developers and portfolios, with community-specific configuration, users, inspector availability and operating controls. The final deployment model is agreed during solution design.
What integrations are available?
The platform supports transactional email today and has secure patterns for hosted payments, external signatures and versioned APIs. SMS and other enterprise integrations can be enabled when the required providers, credentials and operating requirements are available.
Start with the operating challenge
Let us design a better fit-out journey for your portfolio.
Share your current process, portfolio and priorities. PMO will explain how the OnePermit platform and AlterWorks Management model can be configured around your governance framework.