# Partner review brief

IAP projects work best when the engineering question is real, the scope is visible, and feedback arrives early.

## Review a proposal through four lenses

### Relevance

Does the project map to a problem, technology area, or future capability your organization understands?

### Feasibility

Are the deliverables and timeline realistic for the student team and available resources?

### Learning value

Will students make meaningful technical decisions, test assumptions, and communicate the results?

### Follow-through

Can your team provide a point of contact, a useful review cadence, or access to context and constraints?

## Good feedback is specific

Instead of “make it more practical,” try:

- “The prototype should operate within a 5 W power budget.”
- “Please compare the baseline approach against the proposed model.”
- “A useful demo would show the failure case as well as the success case.”

## A lightweight collaboration rhythm

1. Review the proposal and identify one question.
2. Join an early scope check with the faculty lead.
3. Give feedback at the midpoint.
4. Attend the final presentation and discuss next steps.

> The most valuable partner contribution is often a precise constraint shared early enough to shape the design.