Apartment lease-up in Auckland starts before the first tenancy agreement is signed. The opening campaign has to connect completion dates, access, pricing, applications and the handover into ongoing management. When those parts are treated as separate jobs, the first 90 days become a series of avoidable resets.
The common mistake is to prepare for a collection of vacancies instead of the launch of one asset. A building may contain many units, but its early leasing decisions interact. The first advertised rents influence later conversations, applicants compare units within the same development, and every incomplete handover item competes with the work of settling new tenants. Developers need one operating plan for the whole building.
The lease-up clock starts before completion
Waiting for practical completion before planning the campaign leaves too much work on the critical path. Unit information still has to be checked, marketing material prepared, viewing access agreed and the application process tested. If every task begins when the keys arrive, vacancy is built into the programme before the first listing appears.
A useful pre-completion file should identify every unit by a consistent name and record the features that affect rent or applicant fit. Car parks, storage, outlook, outdoor space and accessibility need to be attached to the correct unit. Plans and specifications can prepare the campaign, but the final information must be checked against what was actually built.
Access deserves its own decision. The manager needs to know when photography can happen, whether a show unit will be available and how viewings will operate while contractors are still closing work. A vague promise of access next week is not a leasing plan. It is a dependency that should have an owner and a confirmed date.
Use one rent schedule for the building
Pricing units one at a time creates internal competition and makes later decisions hard to explain. A building-wide schedule gives each unit a clear position before advertising starts. Differences should relate to real attributes such as size, level, aspect, parking or outdoor area, rather than the order in which listings happen to be written.
The schedule is a working control, not a document to lock away. Enquiry quality, viewing attendance, applications and accepted rents should be read across the whole building. If one unit type is attracting attention and another is quiet, the response may involve presentation, listing detail or release timing before it involves a rent change. Recording each decision keeps the campaign coherent and gives the owner a useful explanation of what changed.
This is where property management for developers differs from ordinary single-property letting. The manager needs a portfolio view of availability and pricing while still understanding the features of each home. A row of isolated listings cannot provide that view.
Run one application pipeline
An applicant who misses one unit may still suit another. That opportunity disappears when enquiries are divided between separate inboxes or managers. The leasing team should be able to see the applicant pool alongside the complete availability schedule, then offer a suitable alternative without asking the person to restart.
Viewings need the same coordination. Grouping access into useful blocks can make the building easier to understand and reduce interruptions for the project team. It also gives the leasing team comparable feedback across unit types. The aim is not to rush applicants. It is to make the path from enquiry to a suitable unit clear while applying the same assessment process throughout the development.
The earlier article on what developers should expect from property management covers the broader operating model. During lease-up, that model becomes practical: one source of unit availability, one application workflow and one accountable team following every open decision.
Separate defects from ordinary maintenance
New buildings still generate maintenance work. The important distinction is whether an issue is a construction defect, an incomplete handover item or a problem arising during occupation. If everything enters the same maintenance queue, owners can lose sight of what the builder remains responsible for and tenants may receive conflicting updates.
The handover should therefore establish a defect route before move-in. Managers need the right project contact, a way to record the affected building element and a clear escalation path when access or urgent work is required. Tenants should have one place to report a problem, even when the resolution sits with the builder. Internal ownership can change without asking the tenant to chase several organisations.
Property records need the same discipline. Keys, appliance information, condition material, compliance evidence and emergency contacts should arrive against the correct unit. A missing record may look minor at handover and become expensive to reconstruct once the project team has moved on.
Report the campaign as an operating asset
A developer needs more than a count of signed tenancies. Useful reporting shows what remains available, where applications sit, which pricing decisions changed and what is blocking the next move-in. It should also separate leasing activity from defects and ongoing property management so attention goes to the right constraint.
Good reporting is concise because the underlying records are structured. Meros built Scout to create a daily operating view across the group’s information. For a lease-up, the principle matters more than the software name: the owner and operating team need to work from the same current picture rather than reconcile separate spreadsheets after the fact.
Use days 31 to 90 to build steady management
The campaign does not finish when the last listing is removed. Early tenancies create the building’s first rent collection cycle, maintenance history and communication rhythm. This is the point where a leasing project has to become a dependable management operation after handover.
By the end of the first 90 days, every tenancy should sit inside the normal operating cadence with clear ownership of open work. The manager should be able to distinguish unresolved handover matters from new issues, see upcoming tenancy dates and give the owner one portfolio view. That continuity is part of the operating value of a rent roll: reliable records and relationships matter after the initial transaction is complete.
Questions to settle before the keys arrive
Before appointing a lease-up manager, ask who owns the unit schedule and how pricing changes will be recorded. Ask how an applicant is moved between suitable units, what access is required before completion and how builder defects will be separated from maintenance. Then ask to see the report the owner will receive during the campaign and after the building reaches steady management.
The answers should describe a working process. A promise to market each unit well is incomplete if nobody can show how the units, applicants and handover tasks connect.
Build the operating system before launch
Meros has managed Auckland rentals since 2010 and now manages more than 700 properties. Our developer approach treats a completed development as one coordinated portfolio from lease-up into ongoing management. The first 90 days work best when the information, responsibilities and reporting are designed before the opening campaign begins.
If you have an Auckland development approaching completion, talk to the developer property management team while the lease-up plan can still shape the handover.