Project Presentation

Whatever makes the decision possible, arranged in the order the client will follow. In practice that is a narrative sequence. The site and its constraints, the program, then the design idea. After that come plans and sections drawn for a reader rather than a builder, then the renderings, the materials, and the numbers. Formats vary by audience. A client meeting usually gets a deck. A jury or a public meeting gets boards. A developer often gets a document that survives being forwarded to people who were never in the room. The same content is rebuilt for each. What a remote designer adds is the assembly work. Laying out the boards, building the deck, redrawing plans for legibility, and producing diagrams. And making every page look like it came from the same office.

Yes, and they should be working in nothing else. The template, the typefaces, the color palette, and the way your firm titles a board are the visible part of your practice. A presentation that does not match them undoes the impression it was meant to make. Onboarding starts with your template, your font files, three presentations you consider representative, and your brand guidelines if they exist. Where no template exists, one gets built during the first project and becomes an asset your office keeps. Files stay in your environment and the licenses stay in your name. A designer who has built twenty presentations in your template gets faster in a way a rotating vendor never does. They stop asking, and they start anticipating. That is the practical argument for a dedicated person.

By translating, not by decorating. A client who cannot read a floor plan is not helped by a bigger floor plan. What works is a sequence. An image that establishes where they are, then a simple diagram of the idea. Then the plan, carrying only the information that supports the point. Color and labeling do the work that hatching and line weight do for an architect. Comparative pairs help more than single images, because a decision is between options. Sections and axonometrics explain vertical space in a way that plans never do for a non-architect. Physical or digital scale references give a viewer something human to measure against. The test is simple and worth running before every client meeting. Can someone outside your firm explain the design back after seeing the presentation once?

Yes, and the work is close enough that firms usually keep it with one person. A competition entry is a presentation with a fixed format, a jury, and a deadline that does not move. An RFP or qualifications submission is a document with mandatory content, a page limit, and an evaluator scoring against published criteria. Federal work follows the SF-330 form published by the GSA, and public agencies at state and city level publish their own equivalents. The production work is the same in both. Laying out the response, assembling project sheets and team bios, redrawing what needs redrawing, and checking every mandatory item before submission. Your firm writes the argument and signs the submission. Ask us to take one submission end to end before you decide whether it belongs here.

That depends on what exists already, so any fixed number would be invented. What can be said is how the schedule behaves. A deck built on your existing template, from a model and renderings that are already done, moves fast. A presentation that also requires the renderings, the diagrams, and a redrawn plan set is a different job and should be scoped as one. Because the professional works your hours, the last review before a meeting happens live rather than overnight, which is usually where presentation deadlines are lost. The way to protect a date is to fix the page structure early and leave the content to arrive into it. Bring us the date and whatever material already exists. We will tell you honestly what fits inside it and what does not.