Integrated Design Project: Top Deliverables Your Evaluator Expects

An Integrated Design Project isn’t just a “big final submission.” It’s proof you can think like a real-world design team: align stakeholders, translate needs into requirements, coordinate multiple disciplines, and communicate decisions with clarity. In most evaluations (capstone juries, studio critics, client panels, or academic assessors), the best Integrated Design Project work feels inevitable: every drawing, model, and calculation tells the same story — and nothing looks like it was added at the last minute.

Evaluators usually grade on two big ideas: your process (how you got there) and your package (what you delivered). The trick is that the deliverables they expect aren’t random; they map closely to established professional design phases and documentation standards — like the AIA’s typical design service phases and deliverables, and the RIBA Plan of Work stage structure.

Below is a practical, evaluator-minded breakdown of the deliverables that most often separate “good” from “top-tier.”

What an Integrated Design Project means in evaluation terms

In evaluation language, “integrated” means your architecture, structure, MEP, site, sustainability, cost, and user experience are not separate mini-projects. They are coordinated decisions that agree with one another.

This matches how Integrated Project Delivery (IPD) and integrated design thinking are described in industry: early collaboration, shared goals, and continuous coordination across disciplines to reduce rework and improve outcomes.

So your evaluator is typically looking for two kinds of integration evidence:

First, a clear chain of reasoning: requirements → concept → design development → technical documentation.

Second, coordination proof: drawings and models that don’t contradict each other, and decisions that consider tradeoffs (cost, carbon, comfort, constructability).

Integrated Design Project deliverable #1: A sharp project brief that reads like a contract

A surprising number of teams lose marks right here. Evaluators want a brief that is specific enough to judge your final solution against it.

A strong brief usually includes user needs, project goals, constraints, and measurable success criteria. In engineering capstone assessment research, rubrics often emphasize requirements understanding early because requirements become the yardstick for verifying outcomes later.

Your brief should also show context: site conditions, climate assumptions, codes/standards you chose to follow, and stakeholder priorities.

If you include one “definition-style” paragraph near the beginning — something like “In this Integrated Design Project, integration means…” — you make it easier for evaluators to reward your intent.

Deliverable #2: A requirements + concept narrative that connects every major decision

Most evaluators don’t want poetic concept statements that float above the work. They want a concept that behaves like a decision-making engine.

Your narrative should answer, in plain language:

What problem are we solving?

What are the design drivers (daylight, adjacency, privacy, energy use, cost limits, accessibility)?

What tradeoffs did we accept and why?

Professional design frameworks (AIA-style phases and RIBA stages) treat early phases as the time when options are explored and then narrowed with increasing definition. A concept narrative is where you prove that narrowing was rational.

Deliverable #3: Coordinated drawings that look like one brain made them

Evaluators often scan drawings for one thing: consistency. If your plan says one thing but your section implies another, it signals weak integration.

At minimum, your set should show enough to communicate spatial intent and technical feasibility, typically aligning with standard documentation expectations across design phases (schematic through construction documentation).

Instead of trying to “submit everything,” prioritize a coherent core set:

Plans, sections, elevations that match.

Key details where systems intersect (façade-to-structure, duct/beam conflicts, wet area assemblies, roof drainage).

A code/egress logic that is easy to verify.

If your evaluator comes from practice, they’ll also appreciate sheets that read cleanly on mobile: fewer tiny notes, more legible hierarchy.

Deliverable #4: A BIM or digital model that proves integration, not just visualization

If your program expects BIM, don’t treat it as a rendering machine. Treat it as your coordination engine.

Evaluators typically look for:

Clash awareness (even if you didn’t run formal clash detection, show how you avoided conflicts).

Model-based schedules (doors, spaces, key equipment) that match drawings.

Clear naming and version control.

Integrated workflows are a core promise of IPD-style approaches — collaboration and reduced rework through shared models and early coordination. Showing model-based coordination aligns with that professional logic.

Deliverable #5: Structural concept + checks that match the architecture

Evaluators don’t require a full design for every project type, but they do expect structural logic that is consistent, buildable, and explained.

Your structural deliverable should include your chosen system (RC frame, steel frame, load-bearing walls, long-span strategy, etc.), a clear load path story, and a few representative checks or sizing decisions.

The fastest way to lose credibility is to present dramatic cantilevers, huge atriums, or long spans with no structural narrative that supports them.

If you include one “why this system” paragraph, tied to your project goals (cost, speed, local availability, embodied carbon), you earn integration points.

Deliverable #6: MEP strategy focused on comfort, efficiency, and coordination zones

Even when MEP depth is limited, evaluators want you to show you understand space, routing, and performance implications.

Strong MEP deliverables often include system selection rationale (e.g., VRF vs. central plant), zoning logic, riser/shaft strategy, and key equipment placement that doesn’t fight the plan.

This is where integrated design becomes visible: you show how early architectural decisions supported mechanical efficiency (orientation, shading, glazing ratios, natural ventilation opportunities).

Deliverable #7: Sustainability metrics that go beyond “green intentions”

Most juries can spot vague sustainability claims instantly. What wins marks is measurable performance thinking.

Depending on your course expectations, that might mean:

Daylight targets and glare control strategy.

Energy-use reasoning (even if simplified).

Water strategy.

Embodied carbon awareness tied to structural/material choices.

Integration is about tradeoffs, so show at least one explicit trade: for example, how you balanced glazing for daylight with heat gain risk, and what you did about it.

Deliverable #8: Cost plan and feasibility snapshot that doesn’t feel like an afterthought

Evaluators often ask: “Could this be built?” A simple, credible cost narrative can answer that.

Industry guidance on project delivery methods highlights that early alignment on scope and collaboration influences performance; in evaluation terms, your cost plan is evidence you managed scope instead of drifting.

Your cost deliverable doesn’t need to be perfect, but it should be consistent with your design choices. If you designed a complex façade or premium finishes, acknowledge what that does to cost and propose an alternative option.

Deliverable #9: Risk register thinking (even if it’s lightweight)

You don’t need corporate project management jargon, but you do need awareness of what could break your project:

Code approvals and egress constraints.

Constructability and sequencing challenges.

MEP/structure coordination risks.

Client/user acceptance risks.

A short “top risks and mitigations” section is often enough to show maturity.

Deliverable #10: The final presentation package that tells one unified story

Your evaluator experience is part design review, part communication test. The end package should make it easy to grade you.

Strong final packages usually include:

A one-page executive summary (problem, solution, key numbers).

A narrative flow from brief to final design.

Drawings and visuals that match your spoken defense.

Capstone assessment practices frequently include rubrics for presentations/posters/demos because communication is part of the deliverable itself.

A realistic scenario: why integration marks are won (or lost)

Imagine two teams designing the same mid-rise academic building.

Team A has beautiful renderings and a decent plan set, but their section shows a ceiling plenum that can’t fit ducts, their structure collides with their atrium concept, and their cost plan ignores the expensive façade system.

Team B has slightly simpler visuals, but every sheet agrees. Their atrium span is supported by a clear structural strategy, their shafts are placed where the plan already “wants” vertical elements, and their façade choice is justified with daylight and cooling-load reasoning. Their cost plan acknowledges premium areas and value-engineering options.

Most evaluators will score Team B higher because they can trust the project.

Common questions evaluators ask

What are the most important Integrated Design Project deliverables?

Evaluators typically prioritize a clear brief, a coherent concept-to-decision narrative, coordinated drawings, and proof of cross-discipline integration through model coordination and technical strategies. These align with established professional phase expectations for design and documentation.

How do I prove my work is “integrated”?

Show consistency across plans/sections/details, explain tradeoffs (cost–carbon–comfort), and include coordination evidence (BIM overlays, resolved junctions, shaft strategies). IPD-style guidance emphasizes early collaboration and coordination as the mechanism behind better outcomes.

Do I need a full construction document set?

Not always. But you do need enough technical documentation to show feasibility and resolve key intersections — especially where systems meet. Typical architectural deliverables increase in detail across phases, and evaluation generally mirrors that logic.

What’s the fastest way to lose marks?

Contradictions. If your drawings disagree, your model conflicts with your plans, or your sustainability/cost claims aren’t supported by decisions, evaluators will assume weak integration.

Practical quality checks before you submit

Do a “single-story pass.” If someone only reads your brief summary, concept narrative, one key plan, one section, and one coordination view, do they understand the whole project?

Then do a “contradiction hunt.” Pick five common conflict points — structure vs. MEP, façade vs. daylight/heat, egress vs. layout, roof drainage vs. form, cost vs. finishes — and verify your submission resolves them.

Finally, check mobile readability. Many evaluators review PDFs on tablets or phones. Make headings obvious, reduce dense paragraphs, and ensure text sizes are legible.

Conclusion: Build the submission your evaluator can trust

A top-tier Integrated Design Project submission is not the thickest PDF. It’s the most coherent one. When your brief sets measurable goals, your concept explains decisions, your drawings agree with your model, and your technical strategies reflect real constraints, evaluators can confidently reward you.

If you aim for one outcome, aim for this: every deliverable should reinforce the same story, from requirements through coordinated documentation — because that’s what an Integrated Design Project is ultimately proving.