Architects

Portfolio Project Description Writer

Write compelling project descriptions for an architecture firm's portfolio, website, and marketing materials. This prompt helps architects translate project facts and design intent into narrative descriptions that demonstrate expertise, communicate outcomes, and differentiate the firm to prospective clients.

This prompt generates three portfolio descriptions at different lengths — a 50-word thumbnail blurb, a 150-word proposal project sheet entry, and a 300-word website project page narrative — each leading with the design concept or problem solved rather than project statistics, and each calibrated to a client audience rather than a peer architect audience. The descriptions avoid generic architectural praise language and reference only documented, verifiable outcomes such as cost performance, certifications, awards, and user metrics. It is for architecture firms developing marketing collateral, website content, or proposal credential packages where the same project must be described differently for different contexts and audiences.

Testedclaude-sonnet-4-6ValidatedMar 2026ScopeVerify all code references and calculations independently. T…TierBasic
AI Role
You are a senior architectural professional with experience in architectural wri…
Models
Claude
Confidence
Basic
Constraints
Verify all code references and calculations independently. This does not replace licensed professional review.
Project descriptions must accurately represent the firm's scope of work — do not describe work performed by other firms or claim credit for outcomes driven by others.
Awards and certifications cited in project descriptions must be documented and verifiable — do not include claimed recognition that is not confirmed.
Tested Models
claude-sonnet-4-6
Uncertainty
Where the design concept or outcome is not clearly articulated in the inputs, draft descriptions with [FIRM TO COMPLETE] notes for the concept and outcome elements — these must come from the design team, not from AI interpretation.
Last updated
2026-05-28Published

The prompt

1,719 characters
portfolio-project-descriptor.prompt
You are a senior architectural professional with experience in architectural writing, portfolio development, and communicating design excellence to clients and peers.

Write portfolio project descriptions for the following project:

Project information:
- Project name: [PROJECT_NAME]
- Project type: [PROJECT_TYPE]
- Client: [CLIENT_TYPE — e.g., corporate, institutional, government, private developer, homeowner]
- Location: [LOCATION]
- Size: [SIZE — gross square feet and/or units/keys/seats as appropriate]
- Budget: [CONSTRUCTION_BUDGET — optional, include only if firm typically shares this]
- Completion year: [YEAR]
- Delivery method: [DESIGN-BID-BUILD / DESIGN-BUILD / CMGC / OTHER]
- Certifications: [LEED LEVEL / OTHER — or None]

Design information:
- Primary design concept: [CONCEPT]
- Key design moves: [KEY_MOVES]
- Client challenge addressed: [CLIENT_CHALLENGE]
- Notable outcome: [OUTCOME — e.g., 15% under budget, LEED Platinum, award recognition]

Generate project descriptions in three lengths:

## Short Description (50 words)
For portfolio thumbnail, website listing, or proposal project list.

## Medium Description (150 words)
For proposal project sheets, award submission briefs, and marketing decks.

## Long Description (300 words)
For portfolio website project page, publication submission, and detailed firm credential packages.

Each description should:
- Lead with the design concept or problem solved, not project statistics
- Include the key outcome or achievement
- Demonstrate the firm's specific contribution and expertise
- Avoid clichés (iconic, seamless, elegant, world-class, transformative)
- Be written for the prospective client audience, not the architecture peer community
WAITLIST

Runner beta coming — join the waitlist.

In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.

How to use this prompt

1

1. Gather outcome data before drafting — a project without a documented outcome (on time, on budget, award, client testimonial, post-occupancy measure) produces a generic description.

2

2. Edit each length version for the specific audience and purpose before using — the short description for a proposal is different from the short description for Instagram.

3

3. Have the project principal review the description for accuracy — ensure it reflects the firm's actual scope and contribution.

Customization tips

Add 'Emphasize the firm's role as design-build architect — this audience values certainty of outcome, not design innovation' for design-build focused marketing.
For institutional portfolio entries, add 'Lead with how the design addresses the client's mission, not the formal architectural concept — institutional clients want to see understanding of their purpose.'
Append 'Include a client testimonial quote (provide the quote) — third-party validation is more compelling than firm self-description.'

Sample output

Mar 2026Basic
PORTFOLIO PROJECT DESCRIPTION — Career and Technical Education Center PROJECT: [High School Name] Career and Technical Education Center CLIENT: [School District] LOCATION: [City, State] PROGRAM: 42,000 sf new construction — automotive technology, construction trades, health sciences, and culinary arts programs COMPLETION: [Year] ROLE: Architect of Record — Full Services PROJECT DESCRIPTION: The [High School Name] Career and Technical Education Center was designed to change what students believe is possible for themselves. The client brief was explicit: this building should look and feel like a professional workplace, not a school. Students in the automotive technology lab should feel like they are in a real shop. Students in the culinary arts kitchen should feel like they are in a real kitchen. We designed it accordingly. The automotive bay has real overhead doors, real hoist pits, real compressed air infrastructure — not a simulation. The culinary kitchen is a commercial kitchen, licensed for food production, used by the school's catering operation. The health sciences suite is built to clinical standards with simulation mannequins and AV recording infrastructure. The organizing concept for the building is what we called "the main street" — a 260-foot-long daylit corridor that connects all four program clusters. From any point on the main street, students can see into all four program areas through full-height glazed walls. A student in culinary arts can see the automotive bay. A student in construction trades can see the health sciences suite. The visibility is intentional — it communicates that all of these paths are real options, and it sparks curiosity across programs. OUTCOMES: - Enrollment in CTE programs increased 34% in the first year after the building opened - The facility is used for community workforce training programs on evenings and weekends - The building received a [relevant award or recognition] RELEVANCE TO COMMUNITY COLLEGE WORK: This project demonstrates our ability to design technical training facilities that meet professional operational standards — the same standard required in community college workforce programs. The distinction between a high school CTE center and a community college technical building is smaller than it appears on paper.

Related prompts

Frequently asked questions

Read the Architects AI Guide
Professional Disclaimer

This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of a licensed architect. Always verify code compliance, structural calculations, and design decisions with qualified professionals.