Deferred cases
Delay means approval
Summary
When the board defers a case rather than deciding it immediately, the eventual outcome overwhelmingly favors approval. Of deferred cases that were later decided, 90.2% were approved and only 9.8% refused.
Key findings
What happens after a deferral?
| Eventual outcome | Count | % |
|---|---|---|
| Approved | 9,602 | 90.2% |
| Refused | 1,043 | 9.8% |
Out of 10,645 deferred cases that later received a final decision, 9,602 were eventually approved.
What this means
Deferral is not a neutral act — it's a strong predictor of eventual approval. The board defers cases rather than refusing them, giving applicants time to address concerns, revise plans, or provide additional information. The result is that the deferral process functions as a path to approval rather than a genuine pause for reconsideration.
Only ~10% of deferred cases are ultimately refused. Compare this to the overall refusal rate of ~16% for PA cases (all decisions), and deferrals look like a mechanism that tips the scales further toward approval.
The deferral as override mechanism
Combined with other findings:
- Officer recommends refusal → board defers → architect revises → board approves
- This creates a softer path than a direct override, but the outcome is the same
Why this matters
The deferral mechanism reveals another route the planning system takes to avoid saying no. When combined with the override pattern (Discovery 01), reconsideration (Discovery 54), and sanctioning (Discovery 55), deferrals complete the picture: Malta's planning system has multiple paths that convert potential refusals into eventual approvals. A 90% post-deferral approval rate suggests that deferral is functionally a delayed approval, not a genuine reconsideration. The question is whether any case that reaches the board ever truly faces a meaningful risk of refusal.