Planning File, Handover & Ongoing Compliance

This guide distinguishes between:

- the RJUE and related property, construction and sector rules in force on 21 August 2026;

- the amendments made by Decree-Law 108/2026, scheduled to enter into force on 1 October 2026 following the postponement made by Decree-Law 155-B/2026;

- and the municipal procedures, platform records, titles and technical requirements applicable to the specific project.

Decree-Law 108/2026 changes the form and content of several planning titles, the procedures for use, commencement, amendments, inspection and registration, and the treatment of project records and responsibility.

A handover prepared before 1 October 2026 should therefore identify which law governed each act and be reviewed if completion, use, registration, transfer or another material event occurs on or after that date.

Do not replace historic documents merely because a new regime enters into force. Preserve the original evidence and add the later procedural or legal layer.

The objective is a traceable history, not a folder containing only the most recent version.

At the end of this phase, you should be able to determine:

- whether the complete municipal planning file has been obtained and audited;

- which decision, communication and title governs each operation;

- whether the approved, constructed and final conditions reconcile;

- whether all project changes were lawfully treated;

- whether the title of use or applicable use procedure covers the actual operation;

- whether land-registry, tax, cadastral, planning and physical descriptions align;

- whether urbanisation works, utilities and public-realm obligations have been completed or remain outstanding;

- whether municipal security can be reduced or released;

- which planning, technical, environmental, operating or maintenance obligations continue after completion;

- which original and certified documents must be retained;

- which documents must be transferred to the owner, operator, condominium, manager, lender or purchaser;

- how the digital data room should be structured and controlled;

- which future events trigger review, renewal, inspection or notification;

- and whether the asset is ready for due diligence without reconstructing its planning history from incomplete sources.

The output should be a planning and regulatory asset book supported by a complete evidence register, not a narrative summary without documents.

The website tool should build a project-specific handover index from the development facts.

Asset profile

Ask for:

- municipality and parish;

- property description and tax reference;

- project company and current owner;

- project type and use;

- buildings, lots, units and phases;

- allotment or other planning framework;

- construction completion date;

- use commencement date;

- sale or operating status;

- and intended recipient of the handover.

Planning procedures

Ask whether the file includes:

- prior information request;

- licence;

- prior communication;

- allotment;

- urbanisation works;

- demolition;

- infrastructure or public-realm works;

- changes during construction;

- use communication or authorisation;

- legalisation;

- extension or renewal;

- and external-authority procedures.

Physical status

Ask whether:

- works match the approved project;

- final drawings exist;

- a measured as-built survey exists;

- all phases are complete;

- common areas are complete;

- private and public infrastructure boundaries are defined;

- defects remain;

- and the asset is occupied or operating.

Transaction and operation

Ask whether the handover is for:

- internal project closure;

- first occupation;

- lender completion;

- sale of the land or project company;

- first sale of units;

- condominium establishment;

- operator commencement;

- lease;

- refinancing;

- or long-term asset management.

Preliminary output categories

#### A — Complete and verified

The controlling document is present, authentic or reliably sourced, current where required and reconciled with the asset.

#### B — Present but unverified

A copy exists, but its completeness, final status, source or legal effect has not been confirmed.

#### C — Pending

The document, decision, test, registration, receipt or release has been requested but not completed.

#### D — Inconsistent

The document conflicts with another official record, drawing, area schedule, physical condition or project statement.

#### E — Missing

The expected evidence has not been located.

#### F — Continuing obligation

The underlying approval or agreement remains valid but requires monitoring, reporting, maintenance, renewal or later closure.

Tool disclaimer: The builder provides an organisational framework only. It does not certify legal title, planning compliance, document authenticity, physical conformity, completion, use, registration or satisfaction of a continuing obligation and does not replace legal, registry, planning, architectural, engineering, surveying, municipal or sector advice.

Project information is often distributed across:

- municipal platforms;

- paper files;

- architect and engineer systems;

- contractor software;

- email;

- lender data rooms;

- operator systems;

- sales platforms;

- and personal drives.

The handover process should identify one controlled asset record without destroying the original sources.

The asset record should answer five questions

#### What is the property?

Ownership, boundaries, lots, buildings, units, common areas, easements and public or private infrastructure.

#### What was authorised?

Planning parameters, use, projects, conditions, phases and external decisions.

#### What was built?

Final measured and certified condition, materials, systems and infrastructure.

#### What can lawfully happen now?

Permitted use, operating conditions, transfers, occupation and continuing restrictions.

#### What must happen later?

Maintenance, monitoring, renewal, defects, adoption, security release, registration, reporting and change control.

If the file cannot answer these questions, it is not ready for handover.

Create a chronological schedule of every relevant planning event.

Include:

- application or communication reference;

- date submitted;

- applicant or communicant;

- property and area covered;

- operation type;

- procedure;

- decision date;

- notification date;

- title date;

- effective date;

- approved use and parameters;

- conditions;

- external decisions;

- fees and charges;

- security;

- commencement date;

- amendments;

- extensions;

- completion date;

- use procedure;

- registration;

- enforcement or inspection events;

- and current status.

Include unsuccessful and withdrawn procedures where relevant

An abandoned design or negative decision may explain later conditions, title boundaries or authority concerns.

Do not include irrelevant drafts, but preserve material procedural history.

Identify controlling documents

For each event, distinguish:

- application;

- acknowledgement or receipt;

- technical opinion;

- draft decision;

- final decision;

- title;

- proof of effectiveness;

- and later amendment.

A favourable internal opinion is not the same as a final planning title.

Do not assume that the developer’s folder reproduces the complete municipal record.

The RJUE gives interested persons defined rights to information, process consultation and copies or certified reproductions, subject to the applicable requirements.

Request the correct scope

The audit may require:

- complete process index;

- all applications and supporting documents;

- municipal technical opinions;

- external consultations and responses;

- notices and requests for further information;

- applicant responses;

- decisions;

- title documents;

- fee and security records;

- inspection and enforcement records;

- amendments;

- extensions;

- completion and use documents;

- and closure or receipt records.

Compare the municipal file with the project file

Identify:

- documents submitted but absent from the developer’s file;

- developer documents not shown as received by the municipality;

- different drawing revisions;

- unsigned or undated documents;

- conditions never transferred into design;

- and decisions that refer to missing annexes.

Preserve source information

For each municipal document, record:

- source;

- date obtained;

- certified or ordinary copy status;

- municipal reference;

- file name;

- and hash or other integrity control where used by the project.

The user-facing data room does not need to expose technical integrity metadata, but the project administrator should be able to demonstrate provenance.

Portuguese property projects may have several official or technical descriptions that serve different purposes.

Land registry

Shows registered ownership, description, areas, rights, charges and registrations.

Tax record

Shows the fiscal property record and tax-relevant description.

Cadastre or geospatial record

May show georeferenced boundaries or cadastral information, subject to the applicable system and evidential status.

Planning record

Shows the property and project covered by the planning procedure and approved drawings.

Physical condition

Shows what exists on the ground, based on survey and inspection.

These records may differ without every difference having the same legal consequence.

The reconciliation table should include:

- source;

- property reference;

- ownership;

- total land area;

- boundary;

- building footprint;

- construction area;

- floors;

- use;

- units or fractions;

- common areas;

- annexes;

- parking;

- easements;

- and inconsistencies.

Do not force false precision

Historic property and planning documents may use different measurement methods.

The task is to explain the difference, determine whether correction or registration is required and prevent inconsistent representations in a transaction.

Property registration

Where a planning act, allotment amendment, horizontal-property title, land transfer, easement or other event requires registration, confirm that the registered position reflects the final legal structure.

Predial Online provides access to property registration services and permanent land-registry certificates. Use current certified information for transaction-critical decisions.

Every planning and external decision should be converted into an obligation register.

For each condition, record:

- source document;

- condition number;

- exact subject;

- responsible party;

- action required;

- evidence of satisfaction;

- required timing;

- dependency;

- continuing effect;

- transfer to owner or operator;

- and status.

Classify the condition

#### Before title effectiveness

Payment, security, contract, land transfer or another step required before the approval can be relied upon.

#### Before commencement

Notice, appointment, project, insurance, public-domain or other requirement before works begin.

#### During construction

Inspection, monitoring, archaeology, environmental control, traffic, working-hour or technical requirement.

#### Before completion or use

Testing, certification, infrastructure, correction, final drawing, connection or use requirement.

#### Before first sale or transfer

Certificate, receipt, registration, disclosure or other transaction requirement.

#### Continuing

Maintenance, monitoring, management, public access, landscape, environmental, infrastructure or operating obligation.

Closed does not mean deleted

Retain the condition and attach evidence of satisfaction.

The completed record is often more valuable in due diligence than the original condition alone.

The core title folder should contain:

- final planning decision;

- applicable title or proof of communication;

- approved or submitted project list;

- proof of fee and charge payment;

- proof of security;

- urbanisation or infrastructure agreement;

- land-transfer or compensation documents;

- public-domain permission;

- commencement information;

- and all amendments, extensions and endorsements.

Explain the route

Prepare a short legal and planning note stating:

- procedure used;

- legal basis;

- title;

- effective date;

- area and works covered;

- use;

- amendments;

- expiry position;

- and current status.

The note should point to evidence and should not replace it.

Tacit decisions

If the project relies on a tacit decision, retain:

- complete procedural chronology;

- applicable deadline calculation;

- proof of submission and completeness;

- proof of expiry of the decision period;

- required certification or evidence;

- fee payment;

- legal analysis;

- and any later municipal action.

Do not reduce a tacit-title file to a screenshot showing no response.

The asset record should preserve three distinct design states.

Approved or submitted planning set

The legal baseline for the planning procedure.

Issued-for-construction set

The coordinated design used to build, including properly authorised changes.

Final or as-built set

The completed physical condition based on verified information.

Drawing register

For every sheet, record:

- discipline;

- drawing number;

- title;

- revision;

- date;

- author;

- status;

- approval or submission reference;

- superseded document;

- and final location.

Never overwrite history

Do not save the as-built drawing under the filename of the approved drawing.

Keep superseded documents in a controlled archive and prevent accidental use.

Native files and long-term access

The handover should include agreed native and interoperable formats where the owner needs them for future operation or alteration.

Confirm:

- intellectual-property licence;

- software dependencies;

- fonts and linked files;

- model coordinates;

- and future-use rights.

A PDF may be sufficient evidence of approval but inadequate for future facilities management or redesign.

Prepare one controlled schedule that reconciles:

- planning areas;

- construction areas;

- gross and net areas;

- saleable or lettable areas;

- common areas;

- technical areas;

- parking and storage;

- lots;

- autonomous fractions;

- use;

- capacity;

- and phase.

State the measurement basis

The same word can be used differently by planning, valuation, architecture, tax, sale and lease documents.

For each area field, define:

- legal or contractual source;

- inclusions and exclusions;

- measurement standard;

- drawing source;

- and rounding.

Reconcile horizontal property

Where the development is divided into autonomous fractions, compare:

- approved project;

- final physical condition;

- horizontal-property title;

- land registry;

- tax records;

- plans;

- permilages or other shares;

- common parts;

- parking and storage allocations;

- and actual operation.

Planning approval alone does not create the horizontal-property structure.

Managed and tourist assets

For hotels, tourist developments, student residences, senior living and other operated assets, reconcile planning use with:

- classification or registration;

- operator inventory;

- room or unit count;

- common services;

- shared facilities;

- and management structure.

The handover should identify every professional responsible for the project and completed works.

Include:

- project authors;

- project coordinator;

- director of works;

- site supervision director;

- contractor;

- specialist designers;

- inspectors and certifiers;

- appointment periods;

- qualifications;

- terms of responsibility;

- insurance evidence;

- substitutions;

- and handover records.

Responsibility by revision

Where designers changed, state who authored and assumed responsibility for each revision and construction stage.

Outstanding liability and insurance

Check:

- claims-notification requirements;

- run-off or continuing insurance where relevant;

- warranty periods;

- contractual limitation and notice provisions;

- and access to records if a consultant ceases trading.

The planning file should not attempt to resolve professional liability, but it should preserve the evidence required to assess it.

The RJUE requires relevant facts concerning licensed or prior-communicated works to be recorded in the book of works by the director of works.

Under the current regime, the book should record, among other matters, commencement, completion, stoppage or suspension and project changes.

The law also states that the book is retained at the works for municipal inspection and is not itself an element to be sent to the municipality at the end merely for prior analysis, validation or opening and closure formalities.

Preserve the project copy

Even where it is not a completion-submission document, retain the final controlled book within the asset record together with:

- site instructions;

- inspection records;

- non-conformance reports;

- change approvals;

- test results;

- photographs;

- survey records;

- hidden-works evidence;

- and completion certificates.

Explain gaps

If entries are missing or inconsistent, do not recreate them retrospectively as if contemporaneous.

Record the gap, obtain lawful supporting evidence and legal or technical advice on the consequence.

The pack should demonstrate both physical completion and the legal basis for use.

Depending on the applicable regime, include:

- completion communication;

- professional term of responsibility;

- final drawings where required;

- use communication or use authorisation;

- municipal acknowledgement or title;

- inspection and decision records;

- energy certification;

- fire-safety evidence;

- electrical, gas, lift and other system certificates;

- acoustic and technical tests;

- water and drainage tests;

- utility activation;

- address and numbering evidence;

- and sector operating authorisations or registrations.

Use must match operation

Confirm that the actual occupation or business:

- is within the planning use;

- complies with conditions;

- has the required sector title;

- and does not depend on temporary arrangements that have expired.

Partial or phased completion

For each completed phase, define:

- area covered;

- access and essential services;

- common systems;

- temporary interfaces;

- completion evidence;

- use status;

- and dependency on later works.

Do not represent the whole development as complete if only one phase has reached the necessary status.

For each asset, include:

- approved design;

- connection agreement;

- construction responsibility;

- test and commissioning evidence;

- as-built drawings;

- ownership boundary;

- land right;

- operator acceptance;

- municipal inspection;

- provisional receipt;

- defects;

- guarantee period;

- definitive receipt;

- security reduction and release;

- and maintenance responsibility.

Distinguish connection from adoption

An operational network may remain privately owned or subject to later formal transfer.

Keep security visible

The handover register should show:

- instrument;

- provider;

- beneficiary;

- secured obligation;

- amount;

- expiry or validity mechanism;

- reduction history;

- release condition;

- collateral;

- and current status.

Do not assume the outgoing developer’s security will disappear automatically when the asset or project company is transferred.

Public-realm defects

Outstanding roads, landscaping, drainage, lighting or public-space defects should be listed with:

- responsible contractor;

- rectification date;

- municipal contact;

- inspection status;

- and cost retention or security.

Guides 09 and 10 explain the underlying infrastructure, connection and receipt processes.

The asset may depend on decisions outside the municipal planning process.

Create a schedule containing:

- authority or operator;

- decision or registration;

- legal holder;

- property and activity covered;

- issue date;

- validity;

- conditions;

- monitoring;

- reporting;

- renewal;

- transfer process;

- contact;

- and current status.

Depending on the asset, this may include:

- environmental titles;

- water-resource titles;

- protected-area or heritage decisions;

- road and access permissions;

- tourism classification and registration;

- health or care authorisations;

- food and commercial requirements;

- industrial procedures;

- fire-safety measures;

- energy and utility agreements;

- advertising or terrace permissions;

- and public-domain occupation.

Check the holder

An authorisation held by the developer may not automatically support operation by a separate operator company.

Check the project covered

A valid decision may still describe an earlier layout, capacity, activity or operator.

Check continuing conditions

Operating obligations can begin only after completion. These are easily lost if the development and operations teams use different systems.

Convert every future obligation into a controlled calendar.

For each item, record:

- obligation;

- source;

- asset or activity;

- responsible entity;

- responsible person;

- frequency or trigger;

- evidence required;

- notice period;

- escalation;

- and consequence of failure.

Date-based obligations

Examples include:

- renewal of an authorisation;

- inspection or maintenance cycle;

- guarantee-period expiry;

- definitive receipt application;

- security review;

- insurance renewal;

- monitoring report;

- certification update;

- or temporary-permission expiry.

Event-based obligations

Examples include:

- change of owner;

- change of operator;

- change of use;

- physical alteration;

- increased capacity;

- incident;

- complaint;

- sale of a unit;

- refinancing;

- or commencement of a new phase.

Condition-based obligations

Examples include:

- repair after failure;

- reporting when a threshold is exceeded;

- additional monitoring during construction;

- or corrective works after inspection.

Do not rely on the memory of the original development manager.

Use a structure that follows the asset rather than the organisation chart of the development team.

01 — Property and ownership

- land-registry certificate;

- tax records;

- cadastral information;

- surveys;

- acquisition and title documents;

- easements;

- and ownership chart.

02 — Planning history

- procedure index;

- prior information;

- licences and communications;

- decisions;

- titles;

- amendments;

- extensions;

- and expiry or renewal records.

03 — Approved design

- architecture;

- engineering;

- landscape;

- infrastructure;

- technical studies;

- and drawing register.

04 — External authorities

- requests;

- decisions;

- conditions;

- titles;

- and correspondence.

05 — Fees, land and security

- calculations;

- payments;

- land transfers;

- compensation;

- agreements;

- and security.

06 — Construction and changes

- commencement;

- appointments;

- book of works;

- instructions;

- inspections;

- changes;

- tests;

- and non-conformities.

07 — Completion and use

- final drawings;

- professional declarations;

- completion submission;

- use evidence;

- certificates;

- and inspections.

08 — Utilities and public realm

- connection documents;

- commissioning;

- as-builts;

- adoption;

- defects;

- and maintenance.

09 — Registration and unit structure

- allotment registration;

- horizontal property;

- fraction plans;

- tax updates;

- and address or numbering.

10 — Operation and continuing compliance

- operator titles;

- maintenance obligations;

- monitoring;

- renewals;

- manuals;

- and compliance calendar.

11 — Transactions and disclosures

- lender reports;

- sale and lease disclosure;

- first-transfer evidence;

- and handover receipts.

12 — Archive

- superseded documents;

- historic drafts with continuing relevance;

- and closed procedures.

A useful filename should identify:

- project;

- discipline or document type;

- reference;

- title;

- revision;

- date;

- and status.

Avoid ambiguous labels

Do not use:

- final;

- final final;

- latest;

- approved new;

- or scan 1;

without a controlled reference and date.

Status must be explicit

Examples include:

- draft;

- for review;

- submitted;

- municipally approved;

- issued for construction;

- superseded;

- as built;

- certified copy;

- and executed.

Preserve signatures and evidence

Do not convert an executed or digitally signed document in a way that destroys verification.

Retain the original electronic file and provide a viewing copy only where useful.

Access control

Separate:

- administrator rights;

- editing rights;

- upload rights;

- and read-only recipient access.

Sensitive personal, security and commercial information should not be shared merely because it sits in the same project folder.

Different recipients need different extracts from the complete asset record.

Owner or asset manager

Needs the full legal, planning, technical, operating and continuing-obligation record.

Condominium or owners’ association

Needs documents relevant to:

- common parts;

- shared infrastructure;

- access;

- maintenance;

- insurance;

- warranties;

- plant;

- public or private boundaries;

- and continuing conditions.

Individual purchaser

Needs the legally and contractually required property, use, specification, common-area and disclosure information relevant to the acquired unit.

Lender

Needs title, planning validity, cost-to-complete, completion, use, insurance, security and outstanding-obligation evidence.

Operator or tenant

Needs planning use, operating titles, capacity, technical systems, maintenance, monitoring, restrictions and incident obligations.

Facilities manager

Needs asset registers, access, manuals, as-builts, warranties, maintenance frequencies, emergency information and escalation contacts.

Do not give every recipient the entire unrestricted data room. Build controlled handover views from the verified master.

The handover should be documented.

The certificate or schedule should state:

- project and asset;

- transferor and recipient;

- date;

- document index and location;

- original documents transferred;

- access credentials or repository rights;

- open items;

- missing items;

- continuing obligations;

- deadlines within the next 12 months;

- security and warranties;

- disputes and notices;

- responsible contacts;

- and acceptance or reservations.

Do not use a blanket “complete” statement

State the actual status.

If a definitive receipt, registration or external title remains pending, identify it and allocate responsibility.

Transition period

For complex assets, include:

- knowledge-transfer meetings;

- site walkover;

- system demonstrations;

- authority introductions;

- operator account changes;

- and follow-up closure reviews.

A sale or refinancing data room should be built from the verified asset record, not assembled independently.

Before launch, confirm:

- current ownership evidence;

- complete planning history;

- valid title and use;

- final area schedule;

- registered structure;

- outstanding conditions;

- infrastructure status;

- security;

- external titles;

- continuing obligations;

- disputes;

- enforcement history;

- and material document gaps.

Prepare a disclosure schedule

Disclose clearly:

- pending registrations;

- incomplete urbanisation works;

- temporary arrangements;

- unadopted infrastructure;

- ongoing monitoring;

- outstanding defects;

- open authority correspondence;

- expiry or renewal dates;

- and known inconsistencies.

Control representations

Transaction warranties should be based on verified facts and appropriately qualified by disclosed information.

A data-room upload does not always amount to legally effective disclosure under the transaction documents.

The planning file must remain active after handover.

Future events may require review, including:

- refurbishment;

- subdivision or combination of units;

- façade or roof works;

- new signage;

- terrace or public-domain occupation;

- change of use;

- new operator;

- increased restaurant, hotel or industrial capacity;

- installation of equipment;

- photovoltaic or battery systems;

- electric-vehicle infrastructure;

- accessibility alterations;

- fire-safety changes;

- or changes to private infrastructure.

Establish a pre-change gate

No material alteration should be instructed until the asset manager has checked:

- planning route;

- title and conditions;

- condominium consent;

- landlord or lender consent;

- external authorisation;

- designer and contractor qualification;

- and effect on the asset record.

Update the master record

After each completed change, add:

- procedure;

- approved project;

- construction record;

- final information;

- certificates;

- and revised compliance calendar.

The asset should not accumulate a second undocumented physical history after completion.

An organised file allows the owner or operator to respond quickly and accurately.

Prepare a response protocol for:

- municipal inspection;

- fire or safety inspection;

- environmental inspection;

- utility incident;

- neighbour complaint;

- water or drainage failure;

- public-realm defect;

- unauthorised use allegation;

- and construction-defect claim.

Response principles

- preserve evidence;

- identify the competent authority;

- notify the correct insurer and contractor;

- do not alter or destroy relevant conditions without advice;

- use the controlling documents;

- record communications;

- and update the risk and compliance register.

Avoid unsupported assurances

Do not tell an authority, lender or purchaser that the position is “approved” until the file identifies the relevant decision and scope.

Different documents have different legal, technical and commercial retention needs.

The retention policy should be reviewed for:

- planning titles and approved projects;

- land and registration documents;

- contracts and guarantees;

- professional responsibility;

- construction records;

- health and safety;

- environmental monitoring;

- tax and accounting;

- personal data;

- warranties and defects;

- insurance;

- and litigation limitation periods.

Permanent asset record

Documents that define the lawful physical and use position should normally remain available for the life of the asset and later alterations, subject to legal advice and data-protection requirements.

Personal data

Do not retain or disclose unnecessary identity documents, signatures, addresses or personal contact information merely because they were collected during development.

Separate the enduring asset evidence from personal and transaction-specific data.

Disposal

Any disposal process should be controlled, documented and suspended when litigation, investigation, insurance or authority action is pending or reasonably anticipated.

The website or internal tool should present a high-level view without replacing the evidence.

Core indicators

- planning title: verified / pending / issue;

- use status: verified / pending / issue;

- approved versus as-built: reconciled / review / discrepancy;

- property registration: aligned / pending / discrepancy;

- external titles: current / renewal due / expired;

- infrastructure receipt: complete / defects / pending;

- security: released / reducing / outstanding;

- document pack: complete / gaps;

- continuing obligations: current / due / overdue;

- and active change procedures: none / pending / at risk.

Evidence link

Each indicator should link to:

- source document;

- responsible person;

- last review date;

- next action;

- and deadline.

No invented percentage

Do not display “95% compliant” unless the project has a defined, transparent and legally meaningful method.

A red, amber and green evidence status is often more useful than a false precision score.

Step 1 — Freeze the completed physical condition

Complete final surveys, inspections, testing and photographs.

Step 2 — Obtain the municipal record

Retrieve and index the complete relevant planning file.

Step 3 — Reconcile approval and construction

Compare approved, construction and final projects and resolve every departure.

Step 4 — Complete use and sector procedures

Obtain or confirm all evidence required for lawful occupation and operation.

Step 5 — Close utilities and infrastructure

Complete connections, adoption, receipt, defects and security steps.

Step 6 — Reconcile property records

Align planning, registration, tax, cadastral and physical descriptions.

Step 7 — Build the continuing-obligation register

Transfer every future duty into the compliance calendar.

Step 8 — Structure the data room

Apply controlled indexing, naming, access and version rules.

Step 9 — Prepare recipient packs

Create owner, operator, condominium, lender, purchaser and manager views.

Step 10 — Execute handover

Sign the document schedule, record reservations and complete knowledge transfer.

Step 11 — Review after occupation

Run an initial compliance review after systems and operations have stabilised.

Step 12 — Maintain the record

Update the asset book after every material change, renewal, inspection or transfer.

Timing depends on the size and condition of the project file.

As an initial management assumption:

- document inventory: 1–3 weeks;

- municipal file retrieval and comparison: 2–8 weeks or longer;

- approved versus as-built reconciliation: 2–8 weeks;

- final surveys and drawings: 2–6 weeks;

- completion and use evidence: project-specific;

- infrastructure close-out: 1–12 months or longer where defects or receipt remain;

- property and registration corrections: 1–6 months or longer;

- data-room structuring and quality control: 2–6 weeks;

- recipient review and handover: 1–4 weeks;

- and closure of material gaps: dependent on the authority, consultant, contractor or registry involved.

These activities should begin before practical completion.

A handover assembled after the project team has demobilised is slower, more expensive and less reliable.

Allow for:

- legal and planning audit;

- municipal copies and certificates;

- land-registry and tax documents;

- surveys and measurement;

- final architectural and engineering drawings;

- document control;

- scanning and digital conversion;

- data-room platform;

- technical inspections;

- testing and certification;

- outstanding authority and registration work;

- infrastructure defects;

- security and guarantee management;

- consultant and contractor close-out;

- operator training;

- facilities-management mobilisation;

- and contingency for missing or inconsistent records.

The cost plan should distinguish:

- ordinary close-out;

- rectification of incomplete documents;

- physical corrective works;

- and legal or planning regularisation.

Do not declare planning close-out complete until the following questions can be answered.

Property

- Is ownership current and verified?

- Do boundaries and areas reconcile?

- Are easements, lots and fractions correctly registered?

- Are public and private areas identified?

Planning

- Is the complete planning history indexed?

- Is the controlling title effective?

- Are all amendments and extensions included?

- Are no expiry or enforcement issues unresolved?

Physical conformity

- Are approved and final conditions compared?

- Are all departures lawfully treated?

- Are final drawings measured and controlled?

- Is responsibility for each revision clear?

Use and operation

- Is the legal basis for use documented?

- Does actual operation match the authorised use?

- Are all sector titles and registrations current?

- Are temporary permissions closed or valid?

Infrastructure

- Are essential connections operational?

- Are asset boundaries and maintenance defined?

- Are receipt and adoption complete or accurately disclosed?

- Is security reduced or released where possible?

Documentation

- Is the municipal file audited?

- Are executed and certified originals preserved?

- Is the drawing register complete?

- Are the book of works, tests and certificates retained?

- Are file names, versions and access controlled?

Continuing compliance

- Are all future obligations in a calendar?

- Is each obligation assigned?

- Are near-term deadlines funded and monitored?

- Is a change-control gate in place?

Handover

- Has the correct recipient pack been prepared?

- Are missing and pending items disclosed?

- Has a handover certificate been signed?

- Has operational knowledge been transferred?

If the asset cannot answer a material due-diligence question without contacting a former consultant, the handover is not yet resilient.

Closing the project when construction finishes

Use, registration, adoption, security and continuing obligations may remain open.

Keeping only the latest drawings

The legal history and approved baseline are lost.

Treating the architect’s folder as the municipal file

The municipality may hold different revisions, opinions and decisions.

Using an internal spreadsheet as proof

The schedule is a control tool; the underlying decision, title or certificate is the evidence.

Mixing approved and as-built status

A final physical drawing should not be labelled “approved” unless it was actually approved or submitted under the applicable route.

Ignoring small area differences

Some are measurement differences; others reveal a real legal or physical inconsistency. They must be explained.

Forgetting historic amendments

The original title is read without the later conditions that changed it.

Losing professional responsibility continuity

It becomes unclear who designed or certified the final condition.

Assuming utility operation means municipal adoption

Private ownership, defects or security can remain.

Handing everything to every recipient

Sensitive information is disclosed unnecessarily and the relevant obligations are harder to identify.

Using “final” filenames without revision control

Recipients cannot determine which document governs.

Failing to preserve digital signatures

Conversion or printing can remove electronic verification.

Treating the data room as legally effective disclosure

Transaction documents may require a defined disclosure process.

Forgetting the post-occupation change gate

The asset begins accumulating undocumented alterations.

Letting compliance depend on one employee

Knowledge disappears when the project manager or facilities manager changes.

Before closing the planning workstream, confirm that you have:

- prepared the full planning history schedule;

- obtained the complete municipal file;

- identified controlling decisions and titles;

- preserved proof of title effectiveness;

- recorded fees, charges and security;

- indexed all external-authority decisions;

- built the condition register;

- closed pre-commencement conditions;

- closed construction conditions;

- closed completion and use conditions;

- transferred continuing conditions;

- frozen the approved planning set;

- retained the issued-for-construction set;

- completed verified final drawings;

- created a drawing register;

- preserved native files and use rights;

- reconciled land-registry, tax, cadastral, planning and physical records;

- reconciled lots, units, fractions and common areas;

- completed the final area and use schedule;

- indexed professional responsibility;

- recorded all substitutions;

- retained the completed book of works;

- retained inspections, instructions, tests and photographs;

- completed the use pack;

- completed sector operating procedures;

- completed utility connections;

- recorded infrastructure ownership and maintenance;

- completed provisional and definitive receipt where applicable;

- tracked outstanding defects;

- reduced or released security where possible;

- created the continuing-compliance calendar;

- established document-retention rules;

- structured the digital data room;

- applied naming and version control;

- preserved signed and certified originals;

- restricted sensitive access;

- prepared recipient-specific packs;

- prepared transaction disclosures;

- signed the handover certificate;

- transferred operational knowledge;

- and established post-occupation change control.

Planning File Auditor

Compare the developer’s file with the municipal record and identify missing, inconsistent and unverified documents.

CTA

Audit the planning file

Approval & Condition Register

Turn every decision and condition into an assigned, evidenced and time-controlled obligation.

CTA

Build the condition register

Approved-to-As-Built Comparator

Compare use, area, units, implantation, façades, infrastructure and conditions across approved and final projects.

CTA

Compare approval and completion

Property Record Reconciler

Compare land-registry, tax, cadastral, planning and physical descriptions.

CTA

Reconcile property records

Handover Pack Builder

Create owner, lender, operator, condominium, purchaser and facilities-management document packs.

CTA

Build a handover pack

Compliance Calendar

Track renewals, inspections, monitoring, defects, security release and event-triggered reviews.

CTA

Build the compliance calendar

Tool disclaimer: These tools provide preliminary organisational guidance only. They do not certify title, planning compliance, use, physical conformity, registration, completion, document authenticity, satisfaction of conditions or continuing compliance and do not replace Portuguese legal, planning, architectural, engineering, surveying, registry, data-protection, municipal or sector advice.

You now have a 12-guide framework covering the full planning and licensing lifecycle:

1. Planning Framework & Site Constraints;

2. Planning Due Diligence;

3. Prior Information Request — PIP;

4. Licence or Prior Communication;

5. External Authorities & Environmental Procedures;

6. Planning Submission, Decision & Appeals;

7. Construction Start, Completion & Use;

8. Planning Enforcement, Legalisation & Existing Buildings;

9. Municipal Fees, Infrastructure Obligations & Security;

10. Utilities, Access & Public Realm;

11. Planning Changes, Extensions & Project Transfers;

12. Planning File, Handover & Ongoing Compliance.

The guides are decision tools rather than statutory categories. Use them together and revisit earlier stages when the property, project, law, ownership, programme or operating model changes.

PRIMARY CTA

Explore all Planning & Licensing guides

SECONDARY CTA

Continue to Construction & Delivery

Convert the planning history into a transaction-ready asset record

VVA can support investors, developers, family offices, funds, lenders, purchasers and operators in auditing, completing and transferring the legal and planning record of Portuguese real estate assets.

Support may include:

- municipal planning-file audits;

- planning-title and use verification;

- approved-to-as-built reconciliation;

- planning-history reports;

- conditions and obligations registers;

- property and planning-record reconciliation;

- allotment and horizontal-property review;

- completion and use documentation;

- external-authority and operating-title review;

- infrastructure, receipt and security close-out;

- legalisation and corrective procedures;

- project-company and asset-sale due diligence;

- lender completion reports;

- purchaser and operator disclosure;

- project transfer and handover packs;

- continuing-compliance calendars;

- and future change-control procedures.

PRIMARY CTA

Request a planning file audit

SECONDARY CTA

Speak with VVA