What a Submittal Needs Before Visuals Start

Entitlement visuals fail in a way that is invisible at delivery. The image looks correct, the client approves it, it goes into a submittal, and the problem surfaces weeks later when somebody who knows the street points out that the building next door is a storey taller than shown.

That failure is almost always traceable to an input that was not supplied and was estimated instead.

This guide sets out what has to exist before production, what genuinely can be resolved in parallel, and how to avoid producing material that cannot be defended.

The inputs that block defensible production

1. Survey

Site boundary, levels and, where the ground is not flat, enough topographic information to model it accurately.

This is the foundation of everything else. Without it the ground is assumed, the building sits at an assumed level, and every height relationship in the resulting image is approximate.

On a flat site the consequence is minor. On a sloped one it is the substance of the likely objection.

2. Neighbouring building heights

Obtained rather than estimated. Survey data, published records, or measured from a source that can be cited.

This is the most scrutinised element in any submittal image and the most common source of a public challenge. An estimate that happens to be low reads as deliberate whether or not it was.

3. The jurisdiction requirements

Whether visual material is specified, from which vantage points, in what format, and whether simulations or analyses are required.

Producing something reasonable and discovering afterwards that the authority required something specific costs a review cycle, which is the expensive unit of time in this process.

4. Current drawings with the revision identified

Producing against a superseded set is a silent error in a context where the record accumulates and where the drawings govern.

A discrepancy between the submitted imagery and the submitted drawings is a problem the applicant has to explain, and explanations of that kind consume credibility.

5. A decision about design commitment

Whether the imagery represents a committed design or an indicative one, because that determines both the resolution and the caption, and because a photoreal depiction can become a condition.

What helps but does not block

Site photography. Genuinely useful for context accuracy and for matching light, and a phone is sufficient for reference purposes provided the positions are noted.

The architect model. Usually accurate about the proposal and approximate about everything else, which is normal and still worth having.

Landscape design. Frequently unresolved and easily indicated at installed size rather than mature.

Material references. Helpful for tier, and only necessary where materials are being depicted specifically.

Previous applications on the site. Where a scheme has been submitted before, the record shows what was objected to and what conditions were discussed, which is the most accurate available guide to what this submittal has to answer.

What can wait

Camera composition, which is a production decision. Additional viewpoints beyond the required and the obvious. Any interior content, which is rarely relevant to a planning body. Presentation formatting for a hearing, which is a later step.

Projects are frequently delayed over these while the blocking items remain open.

The assembly checklist

Reading the jurisdiction requirements properly

The step most often skipped and the cheapest to perform, since it is reading rather than producing.

Requirements vary considerably. Some authorities specify nothing. Others name vantage points by street corner, require photographic simulations to a stated method, mandate shadow studies at particular dates, or specify how existing conditions must be represented.

Those are not preferences. A submittal that misses them is deficient and returns, and the cost is a review cycle rather than a revision.

The requirements are usually published. Reading them before commissioning converts a vague brief into a specification, which improves the output and makes quotes comparable at the same time.

Getting neighbouring heights right

Since this is the most challenged element, a short method for handling it properly.

Start with any survey that covers adjacent structures. Where it does not, published municipal or assessor records frequently carry storey counts or heights. Where neither exists, measurement from photography against a known reference is defensible if the method is recorded.

What is not defensible is a visual estimate, and the tell is an image where every neighbour happens to be a comfortable height relative to the proposal. Real streets are not that tidy, and a reviewer who knows the block notices the tidiness before they notice anything else.

Recording the source for each height takes minutes and means that if the depiction is questioned, the answer is a citation rather than an argument.

Choosing viewpoints deliberately

Where the jurisdiction does not specify, the choice is the applicant, and it is worth making thoughtfully rather than aesthetically.

The useful positions are the ones a reviewer or an objector would choose: the approach along the street, the view from the nearest public open space, the position in front of the most affected neighbouring property, and the corner where the massing reads largest.

Choosing the flattering angle is transparent to anybody who knows the site, and it invites the question of what the other angles look like, which is a question best answered rather than provoked.

Producing from the difficult viewpoint and having a defensible answer is a stronger position than producing from the easy one and being asked.

Deciding what must not be shown

An input that nobody volunteers and that occasionally causes real problems in a public process.

Development sits inside commercial relationships that are not all public. An adjacent parcel may be under negotiation, and depicting it as acquired or as redeveloped signals something the applicant has not disclosed. A tenant may be unannounced. A later phase may be commercially sensitive.

There are also representational sensitivities specific to this context. Showing a neighbouring building demolished, an access route across land not yet secured, or a view that implies rights the project does not hold, are each claims somebody may challenge and that a public record preserves.

Establishing this at the outset costs one line in a brief. Establishing it afterwards means reissuing material that has already been submitted, which is a considerably more visible correction.

The half day that prevents most of the problems

If there is one intervention worth insisting on before commissioning, it is a short session with the right people.

In the room: the architect, the planning consultant, and whoever holds the decision on design commitment. On the table: the survey, the current drawings, the jurisdiction requirements and a map of the neighbouring properties.

The output is a list of required outputs, an agreed set of viewpoints, the sources for neighbouring heights, a decision on commitment level and a named approver. That is the complete brief.

Half a day, and it eliminates nearly every failure described in this guide. The alternative is discovering the same items one at a time across three weeks, each discovery pausing production while somebody is asked a question they could have answered at the start.

Who assembles this internally

The inputs sit with different people, which is why assembly stalls.

The architect holds the drawings and usually the model. The surveyor holds the survey. The planning consultant knows the jurisdiction requirements. The developer holds the decision about design commitment and about what may not be shown.

One person needs to be accountable for gathering across those and declaring the package ready, with authority to decide the commitment question. Projects with that person proceed. Projects without one discover each missing item sequentially over several weeks.

The planning consultant is frequently the right holder of that role rather than the developer or the architect, because they are the party who understands what the submittal has to contain and who is already tracking the calendar it has to meet.

Working from the architect model

Usually the starting point and usually not sufficient on its own, which is worth understanding before assuming it saves the work.

A design model is accurate about the proposal because that is what it was built for. It is frequently approximate about everything else: neighbours as extruded blocks at assumed heights, terrain simplified or flat, and boundaries drawn rather than surveyed.

That is entirely appropriate for design and it is not a defensible base for material entering a public record.

So the practical sequence is that the architect model supplies the proposal and the context is built or verified separately against survey and published data. The second half is usually the larger task.

Requesting the model early is still worthwhile, because rebuilding the proposal from drawings is avoidable work, and because reviewing it reveals quickly whether the design is settled enough to produce against.

Timing against the submittal date

A scheduling point specific to this process, where the deadline is set by somebody else and the review cycle is the expensive unit.

Working backwards: the submittal date is fixed, the material has to be reviewed and approved internally before it, production takes as long as it takes, and the inputs above have to be assembled before production starts.

The item that most often breaks that sequence is the survey, because obtaining one takes real time and it is frequently assumed to exist when it does not.

Establishing at the outset whether a current survey covering the neighbouring context exists is therefore the single most useful scheduling question, and it is answerable in a phone call.

Where it does not exist and cannot be obtained in time, the honest response is to produce at a resolution that does not claim precision, and to say so, rather than to produce something precise looking from estimated data.

What goes wrong when preparation is skipped

Heights get estimated. The most likely challenge, and it lands publicly.

Ground gets flattened. On a sloped site, every level relationship in the image is then wrong.

A required analysis is missing. The submittal returns and a review cycle is lost.

The imagery contradicts the drawings. Usually because the drawings moved after production began.

Over resolution creates conditions. A material shown precisely becomes something the project must deliver or amend.

The sensitive item gets depicted. An adjacent parcel under negotiation, an unannounced tenant or an unsecured access route appears in a public document because nobody said it should not.

The survey turns out not to exist. Discovered late, it either delays the submittal or forces production from estimated data, which is the origin of most of the failures above.

One boundary worth stating

This guide covers preparing to commission visual material. It does not cover planning strategy, legal advice or environmental analysis, and no vendor obtains approvals or can guarantee them or accelerate any statutory process.

Our own terms, stated rather than implied: first visuals in 48 to 72 hours once these inputs exist, and reasonable revisions are included at no extra charge. We do not represent projects before any public body.

Frequently asked questions

What is the most common cause of a challenged submittal image?

Neighbouring building heights that were estimated rather than obtained. It is the most scrutinised element, and an estimate that happens to be low reads as deliberate whether or not it was, which transfers doubt to everything else in the application.

How should neighbouring heights be established?

From survey where it covers adjacent structures, from published municipal or assessor records where it does not, or measured against a known reference with the method recorded. Recording the source means a challenge is answered with a citation rather than an argument.

Why read the jurisdiction requirements before commissioning?

Because some authorities name vantage points, require simulations to a stated method or mandate shadow studies at particular dates. A submittal that misses those is deficient and returns, costing a review cycle rather than a revision.

How should viewpoints be chosen where none are specified?

The positions a reviewer or objector would choose: the street approach, the nearest public open space, the front of the most affected neighbour, and the corner where the massing reads largest. Choosing the flattering angle is transparent and invites the question.

What decision only the developer can make?

Whether the imagery represents a committed or an indicative design, since that sets both the resolution and the caption and determines whether a depiction can become a condition of approval.