Architecture competition renderings: a submission QA checklist

Read the competition brief as a production specification

Competition visualisations are not ordinary marketing images. Before modelling or rendering, extract the organiser's exact submission requirements: number and type of images, permitted media, board dimensions, file naming, maximum upload size, resolution, colour space, deadlines and any prohibition on identifying the author. Treat the official brief and subsequent clarifications as the source of truth. This guide is a production checklist, not a statement of any particular competition's rules. A beautiful image that violates an entry requirement may be unusable.

Build a deliverables matrix before commissioning images

Make one row for every required board, view and supporting diagram. Include its intended message, aspect ratio, pixel target, responsible editor, latest design-model revision and final destination. Distinguish mandatory outputs from optional storytelling images. If the brief allows only a small number of boards, decide where each view belongs before selecting a cinematic crop. A late decision to place a wide exterior into a narrow board column can destroy the composition and make important architecture unreadable.

Audit anonymity beyond the visible title block

Where the rules require anonymous judging, inspect the entire export chain. Author names can appear in a logo, watermark, drawing title, project label, QR code, linked website, PDF metadata, filename, embedded image metadata or the name of an identifiable office shown in the image. Check the competition's prescribed identification method rather than inventing your own. Keep a private internal asset register with author and project data, but produce a separate anonymised submission package when required. Do not remove mandatory attribution or copyright notices if the rules require them; resolve any conflict before submission.

Separate proposal, existing context and visual invention

A jury needs to understand what is proposed and what already exists. Mark or otherwise distinguish conceptual surroundings, future planting and uncertain neighbouring buildings according to the competition's graphic conventions. Avoid replacing a difficult site condition with a fictitious park, shifting a heritage building to improve the composition or depicting a proposed structure as completed. If the competition calls for a conceptual atmosphere, make sure the board also provides enough drawings and labels to interpret the architectural proposal. A render cannot verify compliance, feasibility or buildability.

Choose views that answer jury questions

Give each image a job. One view may explain massing and site connections, another public approach, and a third a distinctive interior sequence. Select camera height and lens deliberately. A dramatic wide-angle image can exaggerate a narrow room; an elevated view can conceal the pedestrian experience. Ask what the jury cannot understand from plans and sections alone, then use the rendering to clarify that gap. Avoid submitting several nearly identical hero images merely because they look polished.

Lock visual settings across the entry

Use a controlled material palette, model version, landscape assumptions and entourage style across all images. Record camera IDs, sun direction, exposure and export settings. A scheme should not change facade colour, window spacing or the surrounding tree line between boards without an explicit design reason. If multiple authors produce imagery, agree on a reference frame and shared approval criteria before rendering. For option studies, the matched-camera comparison guide explains how to avoid bias introduced by inconsistent exposure and staging.

Compose for board reading distance

A competition board is usually read first as a whole and then at closer range. Test the main image at the size it will occupy on the actual board, not only full-screen on a studio monitor. Check whether building edges, entrances, landscape structure and the relationship to diagrams remain legible. Avoid heavy atmospheric haze, oversized foreground people or dramatic reflections that hide the proposal. Keep a clear hierarchy between headline view, technical drawings and supporting annotations; the image should not compete with every diagram for attention.

Check image rights, people and contextual assets

Maintain a source list for photographs, textures, vegetation assets, fonts and other third-party material. Confirm that the licence permits the intended competition submission and subsequent publication; do not assume an asset is cleared because it was available in a modelling library. Avoid recognisable people without appropriate rights or permissions. If a competition may publish shortlisted entries, confirm whether the permitted use extends to that context. This checklist does not establish ownership or usage rights for any particular asset.

Preflight pixels, type and colour

Work backwards from the organiser's final output specification. A 4,000-pixel-wide render placed across a 600 mm board has an effective resolution of about 169 pixels per inch before cropping (4,000 ÷ (600 ÷ 25.4)). That calculation does not automatically mean the image is sufficient: inspect its content, sharpening and expected viewing distance. Check any required bleed, fonts, colour profile, embedded images and PDF export preset. Use the print-ready architectural imagery guide for pixel calculations and print preflight; competition rules take precedence over general production advice.

Freeze the model and track late changes

Set a documented model-freeze milestone and a final approval owner. A change to roof geometry may affect an aerial view, elevation diagram and interior window view. Record impacted deliverables rather than correcting only the most prominent image. Keep versioned exports with stable IDs, and compare final board images with the approved preview. Do not silently swap in an attractive earlier render after a late design revision. For publication beyond the competition, the rendering change-control guide covers downstream asset tracking.

Fictional example: an anonymous civic-library competition

Fictional illustrative example, not an Atmosferi commission or real competition. A design team has three boards and two required exterior views. The initial render set contains four sunset hero images but no clear entrance approach. The team replaces one repeated view with a pedestrian-level entrance image, aligns facade materials across both exteriors and checks the board crop at final size. During preflight, a PDF export still contains an office name in document metadata. The team removes that identifier only after checking the hypothetical anonymity rule, then exports a new verified package. No jury result, client or project outcome is claimed.

Deliver a traceable, rule-compliant package

Store the official brief version, clarification log, approved model revision, view IDs, source-asset rights notes, export preset and submission filename in one handover record. Generate a final PDF or image set from a clean output directory, then open the actual exported files rather than trusting the source layout. Verify page count, orientation, text legibility, missing images, file size and filename conventions. Where upload portals are involved, allow time for a complete transfer and any required confirmation receipt. Never treat a successful local export as proof that the organiser received the submission.

Final competition-rendering QA checklist

• Every required view and board is mapped to the current competition brief.
• Anonymous-entry rules are checked in artwork, filenames and document metadata.
• All renderings depict the same approved design revision.
• Proposed architecture and uncertain context are not misrepresented as built fact.
• Camera choice clarifies the design instead of concealing important conditions.
• Materials, landscape, entourage and lighting are consistent across boards.
• Image crops are reviewed at their actual board dimensions.
• Third-party assets have suitable documented usage rights.
• Pixel dimensions, colour, type, page count and file size match the rules.
• Final exports are reopened, checked and identified by version.
• Submission confirmation is retained separately from the design files.

Use the competition's official instructions for every binding requirement. This visual checklist supports an accurate submission workflow; it cannot guarantee eligibility or a jury decision.