Publish architecture project submission, e-architect building design marketing, architects brand online

How to Write a Publishable Architecture Project Submission for e-architect

18 March 2026

Being featured on e-architect is a genuine milestone for any architect or design studio. The site reaches a global readership of professionals, students, and architecture enthusiasts who come to it for thoughtful, serious coverage.

That also means the editorial bar is fairly high. Plenty of strong projects never make it to publication, not because the work is weak, but because the submission is. This checklist lays out what editors typically need in order to move a project forward.

Understanding What the Platform Actually Publishes

Before you put a submission together, it is worth taking a close look at e-architect’s content categories, including news, project profiles, interviews and awards. Understanding where your project fits editorially will shape the way you present it from the start.

The platform publishes completed buildings, conceptual proposals, urban design, interiors, and landscape work from around the world. Projects with a clear architectural story tend to stand out most — whether that story is rooted in sustainability, technical resolution, cultural context, or a genuinely original design approach. By contrast, submissions that read like promotional copy, or never quite explain the thinking behind the work, are much less likely to get traction.

Key questions to answer before submitting:

Does the project have a clear design concept that can be communicated concisely?
Is the building completed, or is it a concept or competition entry?
Does the project have sufficient visual documentation?
Is there a named architect or practice attached to the work?

Crafting a Project Description That Editors Can Use

This is the part many architects underestimate. The writing in a submission matters just as much as the images, because editors are reviewing a high volume of material and making quick decisions. If your project arrives with a clean, well-organized description that is close to publishable as-is, you immediately make the editor’s job easier.

A strong project description typically includes:

Project name, location and completion date — stated clearly at the outset
Design concept — a concise explanation of the central idea driving the architecture
Key design decisions — materials, structural approach, spatial logic
Context — the site, the client brief and any constraints the design responded to
Outcome — how the completed building performs against the original intent

The text should be written in third person and kept free of marketing language. Phrases such as “innovative solution” or “world-class design” do not tell an editor anything useful. What works better is specific, grounded language: what was built, why certain choices were made, and how the design responds to its context.

Length matters too. In most cases, 300 to 500 words is the right range for a project description. Much shorter, and it can feel underdeveloped. Much longer, and the key points may get buried before the editor reaches the end.

Images Are Your Primary Editorial Currency

Even excellent writing cannot rescue weak visuals. Architecture publishing is, above all, visual, and e-architect’s standards reflect that. A submission should include high-resolution photography, ideally produced by a photographer who knows how to document architecture properly.

Make sure to credit photographers correctly and include their names with every image file. That is not simply good etiquette; on most serious architecture platforms, it is a basic editorial expectation. Submissions with missing credits or generic stock-style imagery rarely inspire confidence.

Practical image requirements to follow:

Minimum resolution of 1920px on the longest edge
A mix of exterior and interior shots where possible
At least one image that communicates the full building in context
File names that are descriptive, not generic (avoid “IMG_4521.jpg”)
Avoid heavy post-processing or HDR effects that distort the building’s appearance

Floor plans, sections, and concept diagrams can also make a real difference, especially for technically demanding or spatially complex projects. They show depth, clarify the design thinking, and give editors more material to build a strong feature from.

Navigating the Submission Process Professionally

Once the text and image package are ready, the next step is to send everything through the correct submission contact or portal for the platform. It sounds obvious, but many submissions go astray simply because they are sent to the wrong address or without checking the publication’s own submission guidance first.

If you need to follow up, keep it measured. One polite message after two weeks is reasonable. Chasing repeatedly usually has the opposite effect and can make the submission feel less professional.

Architects who work across disciplines often notice that the same habits — preparation, clarity, and attention to detail — carry over into very different fields. The discipline required to assemble a strong submission is easy to recognise in other structured, process-led environments.

Final Preparation Before Sending

A submission checklist worth running through before sending any materials:

Project description written in third person, 300–500 words
All images high-resolution and correctly credited
Architect and practice name clearly stated
Project location and completion date confirmed
Submission sent to the correct editorial contact

Getting published on a platform like e-architect is not only about the quality of the project itself. It is also about how well that project is presented. When a submission is clear, complete, and easy to work with, the chances of publication improve considerably. Architects who treat the submission process with the same care they bring to design usually give themselves the best chance of being featured.

Comments on this guide to Publish architecture project submission article are welcome.