Two job titles get used as if they mean the same thing on almost every project: development manager and project manager. They do not mean the same thing, and for a property developer the difference is not academic. It decides who carries the commercial outcome of your site, who you can hold accountable when a number moves, who is acting in your interests when the builder claims a variation, and how two separate fee lines land in your feasibility. Get the distinction wrong and you can end up paying for strategy you are not receiving, or assuming someone is protecting your margin when their scope stops at the site fence.
Most of what is written on this question is produced by development management firms describing their own service, or by general business blogs that never touch an Australian construction contract. This guide takes the developer’s seat instead. It covers what each role actually does across the life of a project, where the two overlap and why the overlap causes trouble, the contracts that sit underneath each appointment, what each role typically costs and how those fees behave in a feasibility, the qualifications and professional bodies behind each title, the state-by-state regulatory position (which surprises people in Victoria), and a practical framework for working out which role your next deal needs, including whether you can run it yourself.
The clean distinction: who owns the outcome versus who delivers the build
The single sentence worth remembering is this. A development manager runs the development; a project manager runs the build.
A development manager sits where you sit as the developer, but with the experience, the consultant relationships, and the available hours to run the project properly. The role is whole-of-lifecycle and commercial. It starts before a site is even bought, with feasibility and acquisition, and it finishes after construction, with sales, settlement, and the final commercial result. The development manager is generally accountable to you (or to a landowner or an investor group) for the outcome of the project: the budget, the programme, the planning result, and ultimately the profit.
A project manager runs the construction phase. The focus is the physical delivery of the building: the trades, the programme, the contracts, the procurement, and the cost of getting the thing built to the agreed standard. A project manager is usually engaged once approvals are in place and the project is ready to go vertical, and the role is most commonly summarised as managing time, cost, and quality through to completion.
Put another way, project management is generally understood as a component of development management rather than a separate, parallel discipline. The construction phase is one stage inside a much longer commercial process, and the project manager owns that stage. The development manager owns the whole arc and coordinates the project manager as one (important) part of it. On a small, simple job the same person may wear both hats. On a large or complex one, the two roles are usually filled separately, with the project manager reporting up to the development manager or directly to the developer.
| Dimension | Development manager | Project manager |
|---|---|---|
| Core question answered | Does this project stack up, and how do we protect the return? | Can we build this on time, on budget, to standard? |
| Typical involvement | Pre-acquisition through to final settlement | Construction phase (sometimes from design) |
| Primary accountability | Commercial outcome of the whole project | Delivery of the physical works |
| Mindset | Generalist, strategic, whole-of-lifecycle | Specialist, operational, delivery-focused |
| Reports to | Developer, landowner, or investors | Development manager or developer |
| Background often seen | Property, finance, planning, development | Construction, engineering, quantity surveying |
Where the confusion actually comes from
If the distinction is that clean, why do the titles get muddled so often? A few reasons, and each one matters to a developer for a different practical reason.
Neither title is a protected or licensed term in most of Australia. Unlike “architect”, which is a protected title in every state, “development manager” and “project manager” can be used by anyone. There is no national register you must be on to call yourself either. That is a recurring theme in this guide, and it is the main reason credentials need checking rather than assuming.
On smaller projects, one person genuinely does both jobs. A developer building a six-unit townhouse project might engage a single consultant who runs the feasibility, lodges the Development Application (DA), coordinates the consultants, and then administers the building contract through construction. Calling that person a development manager or a project manager is, in that case, partly a matter of emphasis. The confusion is understandable because the reality is blended.
The construction contract introduces a third title that overlaps with the project manager: the Superintendent. On most commercial building contracts in Australia the project manager also performs the Superintendent function, and the Superintendent has a specific, contractually defined dual role that is worth understanding in its own right (covered below). Developers sometimes hear “project manager”, “superintendent”, and “contract administrator” used interchangeably on the same job, which adds to the blur.
Victoria adds a genuine statutory trap. The Victorian Building Authority (VBA) renamed one of its building practitioner registration categories to “project manager” under reforms commencing in 2024. That statutory “project manager” is a building-permit document role, not the commercial construction project manager most developers mean. The two share a name and almost nothing else. More on this in the state section, because it is exactly the kind of thing that causes a developer to assume a registration exists where it does not, or to assume a registered “project manager” is qualified to run their build when the registration speaks to something quite different.
What a development manager actually does, stage by stage
The honest description of the development manager role is that it changes shape across the project. The value is concentrated at the front, where the decisions that make or break a project’s profitability tend to get made, but the accountability runs the whole way through. Walking the lifecycle is the clearest way to see the scope.
Pre-acquisition, feasibility, and deal shaping
Before a site is committed, the development manager is doing site analysis and feasibility work: testing what is commercially possible on the land, what yield the planning controls may allow, what it could cost to build, and what it might sell or lease for. This is where the residual land value is set, where the funding structure is sketched, and where a deal is either shaped into something that works or walked away from. A development manager earning their fee here is stress-testing assumptions, not just filling in a template. For the underlying mechanics of how this stage is built up, our property development feasibility guide and the residual land value guide cover the modelling that a development manager typically owns or commissions.
Planning and approvals
Once a site is secured or under option, the development manager runs the planning pathway: setting the strategy, engaging the town planner and design team, managing the Development Application (DA) or planning permit process, and dealing with council and referral agencies. The role here is coordination and judgement. Which scheme to lodge, when to negotiate, when to amend, and how a planning outcome flows through into yield, cost, and programme. The development manager is the one connecting a planning decision back to the feasibility, because a condition that looks minor on paper can move the commercial result.
Design and consultant coordination
The development manager engages and manages the consultant team: architect or building designer, engineers, surveyor, quantity surveyor, planner, lawyer, and others. The job is to keep the design aligned with the budget and the market, not to let it drift into the most elegant scheme rather than the most commercially appropriate one. A useful framing some development managers use is that the goal is to optimise the project across every area rather than maximise any single one. The largest building, the highest specification, or the absolute maximum yield is not always the most profitable outcome, and balancing those trade-offs is core development management work.
Funding and capital
The development manager typically leads or supports the funding process: preparing the information a lender or equity partner needs, modelling the capital stack, and managing drawdowns and reporting once finance is in place. Many lenders also expect to see experienced management behind a project before they will fund it, so the development manager’s track record can itself affect the terms on offer. Our construction finance guide sets out what financiers typically look for, much of which the development manager is responsible for delivering.
Construction oversight, through the project manager
During construction the development manager does not usually administer the building contract day to day. That is the project manager’s job. The development manager instead holds the commercial line: tracking the budget against the feasibility, watching cash flow and drawdowns, managing variations for their commercial impact rather than their technical detail, and keeping investors or financiers informed. On larger projects this is the clearest division of labour. The project manager runs the build; the development manager makes sure the build still serves the deal.
Sales, settlement, and project close
The development manager stays involved to the end: coordinating sales and marketing, managing presales where they are needed for funding, handling settlements, and closing out the project commercially. The role finishes when the last lot or unit is sold and the final return is known, which is often long after the builder has left site.
| Project stage | Development manager | Project manager |
|---|---|---|
| Site search and acquisition | Leads | Not involved |
| Feasibility and funding | Leads | Provides cost input |
| Planning and approvals | Leads | Limited |
| Design development | Coordinates the team | May advise on buildability |
| Procurement and tender | Sets strategy, approves | Runs the tender |
| Construction | Holds commercial oversight | Leads delivery |
| Sales and settlement | Leads | Not involved |
What a project manager actually does
The construction project manager is a delivery specialist. The role is narrower than the development manager’s, but inside that window it is deep and technical. A capable construction project manager typically comes from a construction, engineering, or quantity surveying background, and the work centres on managing every moving part of the build so that it lands on time, on budget, and to the standard documented.
The day-to-day includes managing the construction programme, running procurement and the tender, administering the building contract, assessing and processing payment claims, valuing and certifying variations, handling extension-of-time claims, coordinating site activity and consultants during construction, managing requests for information, and driving the project through practical completion and defects. On most commercial jobs the project manager also performs the Superintendent role under the building contract, which carries its own contractual obligations.
Because the project manager is engaged for delivery, the role is most valuable where the front-end work is already done: the site is known, the approvals are in place, the design is documented, and a builder is lined up or about to be. At that point the remaining task is essentially construction delivery, and that is precisely what a good project manager is set up to do. What the project manager is not engaged to do, unless you specifically scope it, is protect the commercial outcome of the wider deal. That gap is where developers most often get caught.
The Superintendent: the role that muddies the water
This is the part most general comparisons miss, and it matters because it is where a developer can be quietly under-protected. On the common Australian Standard building contracts, including AS 2124-1992, AS 4000-1997, and the design-and-construct form AS 4902-2000 published by Standards Australia, the contract requires the principal (you, or the entity that owns the project) to appoint a Superintendent. In most cases the project manager fills this role.
The Superintendent is not a party to the contract, but is given a defined set of functions, and those functions split into two very different capacities. As LegalVision explains in its overview of the Superintendent role, the Superintendent acts partly as the principal’s agent and partly as an independent certifier. As HopgoodGanim sets out in its analysis of the Superintendent’s dual role, when the Superintendent is conveying the principal’s instructions to the builder it acts as your agent, but when it is assessing a payment claim, valuing a variation, deciding an extension of time, or certifying practical completion, it is required to act honestly, fairly, and impartially rather than simply in your interest.
That distinction has teeth. AS 4000-1997 requires the Superintendent to act reasonably and in good faith, and the courts have consistently held that the certifying functions must be exercised independently. As LC Lawyers notes on preserving the Superintendent’s independence, a principal who interferes with the Superintendent’s certifying decisions can expose itself to a claim from the builder. So the project manager wearing the Superintendent hat is not purely your advocate when certifying. They are bound to be even-handed.
For a developer there are two practical takeaways. First, understand that your project manager, when acting as Superintendent, is not your representative on certifying questions, and if you want someone purely in your corner on commercial decisions, that is the development manager’s job (or your own). Second, be cautious about who fills the role. Letting the builder’s own people, or anyone with divided loyalties, perform the Superintendent function tends to dilute the protection the role is meant to give you. The Superintendent should be genuinely independent of the contractor.
Reporting lines and who carries the risk
The reporting structure follows the accountability. The development manager generally answers to you, the landowner, or the investor group for the commercial result. The project manager generally reports to the development manager, or directly to the developer where there is no development manager, and answers for delivery of the works.
Risk splits along the same line. Delivery risk (the build coming in late, over budget, or with defects) sits with the builder and is managed by the project manager. Commercial risk (the project not making money even if it is built well) sits with the development manager and, ultimately, with you. A project can be delivered flawlessly and still lose money if the feasibility was wrong, the market moved, or the holding costs blew out. That is why a project manager alone, however good, does not cover a developer who is exposed on the commercial side. The two risks are different risks, managed by different people.
This is also where the legal character of the development management relationship becomes relevant. Depending on how the appointment is structured, a development manager acting on your behalf may owe agency obligations, and in some arrangements fiduciary obligations, meaning a duty to act in your interests and to avoid undisclosed conflicts. As Sprintlaw notes in its overview of development management agreements, the agreement is what authorises a development manager to plan, coordinate, and deliver a project on behalf of a landowner or investor, and it is where these duties and authority limits should be spelled out. It is worth taking advice on the structure; our property development lawyers guide covers when to bring legal input into appointments like these.
The contracts underneath each appointment
Two different appointments sit beneath these two roles, and they are not interchangeable.
A Development Management Agreement is the contract between the landowner or developer and the development manager. A well-drafted Development Management Agreement may typically set out the scope of services across the lifecycle, the authority the development manager has to act on your behalf (and the decisions that require your sign-off), the fee and how it is calculated, any performance or incentive component, reporting obligations, conflict-of-interest provisions, insurance requirements, and termination rights. The thresholds matter: a developer should generally define exactly which decisions the development manager can make alone and which need owner approval, so that authority is not open-ended. An “authority to act” provision is also commonly included so the development manager can deal with council, utilities, and other parties on your behalf.
The project manager is appointed either under a separate consultancy agreement or, where the project manager is also the Superintendent, named in the building contract itself. The Superintendent appointment is created by the building contract (AS 4000, AS 4902, or similar), and the project manager’s certifying obligations flow from that contract rather than from any side agreement with you. This is why it is possible, and common, for your project manager to owe contractual duties of impartiality to the builder on certain questions even though you are paying them. Reading the two appointments together, the Development Management Agreement and the building contract, is the only way to see where your real protection sits.
What each role costs
Fees are where the abstract distinction becomes a feasibility line, and the two roles are typically priced on completely different bases. Both numbers below are indicative ranges drawn from market commentary, and both move with project scale, complexity, scope, and the individual firm’s cost structure, so treat them as a starting point for your own quotes rather than fixed figures.
Development management fees
Development management is most commonly charged as a percentage of total project cost or of project revenue, sometimes as a flat negotiated fee for an agreed scope, and frequently as a base fee plus a performance or incentive component tied to hitting a profit hurdle. Indicative percentage ranges discussed in the market often sit in the low single digits of total development cost on larger projects and higher on smaller ones, reflecting the usual pattern that the percentage falls as the project gets bigger. A flat-fee structure means an agreed price for delivering the project end to end, with the fee holding unless the scope changes.
Where development management is brought in-house rather than outsourced, the cost shows up as salary instead of a fee. As a rough guide to that internal cost, advertised remuneration for property development managers in Australia is reported by sources such as SEEK’s property development manager listings to sit broadly in the six figures, varying widely with experience and the scale of projects managed. The University of Technology Sydney’s overview of property development careers gives a sense of how the development management role fits alongside the other disciplines a developer draws on.
The incentive structure is worth dwelling on, because alignment is the point. A development manager paid purely a percentage of cost has a weak incentive to keep cost down. A development manager paid partly on the realised profit has their interests pointed in the same direction as yours. How that performance fee is defined (against what hurdle, measured when, and on what version of the numbers) is one of the more important things to negotiate in a Development Management Agreement.
Project management fees
Construction project management is most commonly charged as a percentage of construction cost, on a sliding scale that falls as the contract value rises. Market commentary on Australian project management fees describes a tiered pattern in which smaller projects attract a higher percentage and large projects a much lower one, with the percentage typically stepping down as you move from sub-million-dollar jobs up through the multi-million-dollar range. The mechanism is straightforward: the percentage reflects the management effort relative to project size, and that effort does not scale linearly with value, so larger projects cost proportionally less to manage.
| Development manager | Project manager | |
|---|---|---|
| Usual fee basis | Percentage of total cost or revenue, or flat fee | Percentage of construction cost |
| Incentive component | Often a performance or profit-share fee | Usually none |
| Sliding scale with size | Yes, falls on larger projects | Yes, falls on larger projects |
| Shows up in feasibility as | Development management line (and incentive) | Preliminaries or professional fees line |
Both fees belong in your feasibility from the outset, not as an afterthought. A development management fee of a few per cent of cost, plus a project management fee on the construction budget, plus a performance fee on profit, can together take a meaningful bite out of margin. Modelling them explicitly, and running the sensitivity on them, is exactly the kind of thing development feasibility software is built for. In Feasly, you can carry development management and project management fees as discrete line items and test how changes to either flow through to residual land value and project margin, rather than burying them in a single professional-fees number. Our sensitivity analysis guide walks through how to pressure-test the inputs that move a result the most, and these fees are often among them.
Qualifications and professional bodies
Because neither title is licensed in most jurisdictions, qualifications and memberships are the main signal of capability, and they differ between the two roles.
For project managers, the most directly relevant Australian credential is certification through the Australian Institute of Project Management (AIPM), the country’s leading project management body. Its Registered Project Manager (RegPM) program offers a tiered certification framework running from Certified Practising Project Practitioner up through Certified Practising Project Manager and Senior Project Manager to Certified Practising Project Director and Portfolio Executive, with continuing professional development required to maintain certification. Internationally, the Project Management Institute (PMI) Project Management Professional (PMP) credential is widely held. For project managers working through a property and construction lens, the Royal Institution of Chartered Surveyors (RICS) offers a project management pathway leading to chartered status. Many construction project managers also hold quantity surveying or engineering qualifications, and bodies such as the Australian Institute of Quantity Surveyors (AIQS) sit behind the cost-management side of the discipline.
For development managers, there is no single licence or certification that defines the role. Development managers typically come from a property, finance, planning, or development background, and credibility tends to rest on a track record of completed projects more than on a particular certificate. Professional bodies such as the Australian Property Institute (API) and education through providers including the Property Council of Australia and postgraduate property development programs are common markers, and the Royal Institution of Chartered Surveyors (RICS) pathways are also relevant for development-side professionals. But the practical reality is that the title carries no statutory gatekeeping, so verifying experience matters more here than reading a business card.
The blunt warning for developers is that anyone can call themselves a development manager or a project manager. There is no register to fail. That places the burden on you to check completed projects, references, professional memberships, and (critically) professional indemnity insurance. A development manager or project manager without current professional indemnity cover is a development manager or project manager you may have no real recourse against if their advice or management causes you loss. Verifying that cover exists, and at a level appropriate to your project, is a basic piece of diligence.
State and territory differences
The commercial development manager and project manager roles are not separately licensed in most of Australia, and the contracts that govern them (the Australian Standard building contracts, consultancy agreements, and Development Management Agreements) operate nationally. So in broad terms the answer to “is this role regulated where I am building?” is usually no, with some important state-specific exceptions and overlaps that are worth flagging.
Victoria
Victoria is the jurisdiction most likely to confuse a developer, because it has a statutory registration category that is literally called “project manager”. Under reforms commencing in 2024, the Victorian Building Authority (VBA) renamed two building practitioner categories, changing “person responsible for a building project” to “project manager” and “draftsperson” to “building designer”, to align titles across jurisdictions. These changes form part of the broader updates to building practitioner registration under the Building Act 1993, which also introduced a stricter fit-and-proper-person test and a continuing professional development regime. The point for developers is that this statutory “project manager” is a building-regulatory role tied to the Building Act 1993, not the commercial construction project manager who runs your build. A consultant can be an excellent commercial project manager without holding this registration, and holding this registration does not by itself mean someone is the right person to manage your project commercially. Do not read across from one to the other.
Queensland
Queensland regulates building work and building design through the Queensland Building and Construction Commission (QBCC), and where a project manager is also undertaking licensed building work, or administering a contract in a way that touches licensed activities, the relevant licensing can come into play. The development management and project management roles themselves are not separately licensed, but the building activities around them may be, so it is worth confirming that anyone performing builder or building-design functions on your Queensland project holds the appropriate licence.
New South Wales
New South Wales does not separately license development managers or commercial project managers, but the broader compliance environment has tightened, particularly for apartment buildings. The Design and Building Practitioners Act 2020 imposes registration and declaration obligations on practitioners involved in the design and construction of Class 2 (apartment) buildings, and a project manager coordinating that work needs to understand who must be registered and what must be declared. The role of the project manager is not itself the regulated thing, but the practitioners they are coordinating, and the documents they are helping to produce, increasingly are.
Other states and territories
Across South Australia, Western Australia, Tasmania, the Australian Capital Territory, and the Northern Territory, the commercial development manager and project manager roles are generally not separately licensed, although each jurisdiction regulates builders, building designers, and certain construction occupations through its own scheme. The sensible position everywhere is the same: the titles “development manager” and “project manager” are not, by themselves, regulated assurances of competence, so verify the person’s track record, insurance, and any licences relevant to the specific building activities they will perform.
| Jurisdiction | Development or project manager licensed? | Watch for |
|---|---|---|
| VIC | No, but a statutory “project manager” registration category exists | Do not confuse Victorian Building Authority (VBA) registration with a commercial project manager |
| QLD | No | Queensland Building and Construction Commission (QBCC) licensing where building or design work is performed |
| NSW | No | Design and Building Practitioners Act obligations on Class 2 work |
| SA / WA / TAS / ACT / NT | No | Builder and building-designer licensing schemes apply to specific activities |
Which role does your project actually need?
The decision is less about the size of your ego as a developer and more about the size and shape of the gap between where your project is and where it needs to get to.
If your project is essentially about getting something built, with a known site, approved plans, a clear scope, and a builder lined up or close to it, a project manager on their own may be enough. The remaining work is construction delivery, and that is the project manager’s home ground. You, or your in-house team, hold the commercial reins, and the project manager runs the build underneath you.
If your project is still early, or genuinely complex (mixed-use, staged delivery, awkward planning constraints, multiple stakeholders, an unfamiliar council, or a funding structure you have not run before), a development manager is usually the better call. They shape the strategy, run the approvals, manage the consultants, and protect the commercial outcome the whole way through, bringing a project manager in during construction and coordinating with them to completion. The signals that point toward a development manager tend to include being a landowner who has not developed before, being a developer with more projects than hours, working in a planning environment you do not know well, or being early enough that the strategy is still being set before serious capital is committed.
On larger projects, the question is usually not “which one” but “how the two work together”. You will often have both, with the development manager owning the commercial outcome and the project manager owning delivery, reporting up.
A short diagnostic, adapted from how experienced development managers frame it, can help you decide whether you have the front-end covered yourself or need development management:
- Do you understand everything required to deliver this project, including the parts you have not done before?
- Do you have local experience and the consultant, legal, and agency relationships the project needs?
- Have you worked in this council area and do you understand its requirements?
- Have you completed genuine due diligence, a realistic approval pathway, and a realistic feasibility?
- Have you secured funding and do you have a credible exit?
- Have you delivered a project of this type and scale before?
If most answers are yes, a project manager to run construction may be all you need. If several are no, that is a strong indicator the project would benefit from a development manager rather than just a builder’s coordinator.
Can you be your own development manager?
For many developers, especially those scaling up from smaller projects, the honest answer is that you already are the development manager, you just have not named it. If you are doing the feasibility, choosing the site, running the consultants, and carrying the commercial risk, you are performing the role. The questions then become whether you have the bandwidth to do it well across every project at once, whether you have the specific local and product experience this deal needs, and whether the cost of your own time is better spent here or elsewhere. Our guide to becoming a property developer covers the broader skill set this involves. Engaging a development manager is, in part, a decision to buy back your time and import experience you do not yet have, and it is a perfectly rational one even for capable developers.
Common mistakes developers make
A handful of errors recur, and each maps back to the distinction this guide is built on.
Assuming a project manager covers strategy. The most common and most expensive mistake is engaging a construction project manager and assuming they are also protecting the deal. They are protecting the build. If no one owns the commercial outcome, no one is watching the margin while the building goes up beautifully.
Letting the builder’s people perform the Superintendent role. Where the party certifying payments, variations, and completion is not genuinely independent of the contractor, the protection that the Superintendent function is meant to give you is weakened. Keep that role at arm’s length from the builder.
Leaving authority open-ended in the Development Management Agreement. A development manager with undefined authority can commit you to decisions you would not have made. Define the thresholds: what they can approve alone, and what comes back to you.
Treating the fees as small. A development management fee, a project management fee, and a performance fee can compound into a real margin impact. Developers who do not model them explicitly, and do not run the sensitivity, are often surprised at how much of the upside they have given away.
Misaligning incentives. A development manager paid only on cost has little reason to keep cost down. Tying part of the fee to the realised result points their interests at the same target as yours.
Bringing it back to the feasibility
The cleanest way to think about all of this is through the number that decides whether you proceed. A development manager exists to protect and improve the commercial outcome; a project manager exists to deliver the building that the commercial outcome depends on. Both cost money, both belong in the feasibility as explicit lines, and both should be tested rather than assumed. Modelling the two fees separately, alongside the construction budget, the funding costs, and the revenue, is what lets you see whether the project still stacks up once the people running it are paid. That is the developer’s question, and keeping it in view is the difference between knowing who you need and finding out the hard way.
This guide is general information for property developers and does not take account of your specific project or circumstances. Fee ranges, registration regimes, and contract obligations referred to here may change and vary by jurisdiction, so confirm the current position and take professional advice before relying on any of it for a live deal.