Read the land. Build the case. Move the file.

Three disciplines carried as one continuous strategy—from the first feasibility question to the last condition that makes the approval usable.

01READ

Read the land before the concept hardens.

The first task is not to draw more. It is to understand what the site, policy framework, municipal context, infrastructure, access, and surrounding uses will permit—and where the real planning risk sits.

Questions answered

What is permitted now?
What change would be required?
What constraints will shape the proposal?
Which approval route is proportionate?

Working output

A candid feasibility position and approval roadmap: what appears viable, what remains uncertain, which studies are likely, and where the client should not spend yet.

02BUILD

Build the case before asking for the decision.

A complete submission is not merely a collection of consultant reports. The evidence must answer one coherent planning question: why is this development appropriate here, in this form, at this time?

Work coordinated

Pre-consultation and study list
Planning strategy and application sequence
Planning and urban-design reports
Technical consultant inputs and revisions

Working output

A coordinated application whose drawings, reports, studies, and requested permissions support the same proposition rather than competing versions of the file.

03MOVE

Move the file without losing the argument.

Municipal review creates comments, dependencies, revisions, negotiations, public meetings, conditions, and sometimes appeals. The task is to keep each response connected to the core planning case.

Work carried

Comment matrix and consultant assignments
Revision strategy and municipal meetings
Committee, council, and OLT preparation
Agreements, conditions, clearance, and certificates

Working output

Clear reporting, disciplined revisions, and a file advanced toward a decision that can be implemented. G-Force does not promise approval; it builds and carries the case for it.

04Working principles

Four controls on every file.

Straight answers early.

If the proposal does not presently carry, the client should know before avoidable design and consultant costs accumulate.

One planning argument.

Drawings, reports, technical studies, and municipal responses should support one coherent development proposition.

One coordinated schedule.

Consultant dependencies, client decisions, submissions, and comment responses are managed as a file—not as separate disciplines.

Honest status.

In review means in review. A favourable decision, cleared conditions, and a buildable approval are not the same thing.

05Starting point

WHAT WE NEED FIRST

A site, an objective, and the documents already in hand.

A first conversation does not require a finished concept. The property address, intended use or development ambition, transaction timing, and any survey or prior drawings are usually enough to identify the first planning questions.

Property address or roll number
Survey, if one exists
The objective in one sentence
Known transaction or timing constraints
Prior approvals, drawings, or municipal correspondence

Start with the site →