A project may continue into a second semester when additional work is useful.
How we work together
A structured path from problem to progress.
Each engagement moves from a preliminary business need to a jointly confirmed project plan, regular working reviews, and a practical final handoff that supports a decision or action.
- 1
Initial inquiry
The organization shares a short, non-confidential description of the need, intended users, decision to support, and technology context.
- 2
Preliminary scope
Faculty review fit, likely outputs, data needs, constraints, risks, success measures, and the appropriate technology angle.
- 3
Team matching
Students are matched and selected according to project needs, interests, experience, and availability.
- 4
Kickoff & project plan
All parties confirm a project liaison, the question, deliverables, access, boundaries, success measures, and review schedule.
- 5
Working & midpoint reviews
Student-led work continues with faculty guidance; the organization joins hybrid check-ins every one to two weeks and gives timely feedback.
- 6
Presentation & handoff
The team presents its work, transfers agreed files and recommendations, and the organization reviews next steps and partner feedback.
Engagement framework
Enough structure to support real work.
Students maintain consistent work between project reviews.
Meetings use a hybrid format according to project needs.
The final format follows the scope and agreed outputs.
What organizations contribute
The access and attention that make a project useful.
The organization does not need to arrive with a finished project plan. It does need to make a real question, appropriate context, and timely feedback available to the team.
Decision owner
Name a sponsor or decision-maker who can explain why the work matters and help assemble the right stakeholders for final review.
Project liaison
Identify one day-to-day contact who can answer questions, coordinate access, and join hybrid check-ins every one to two weeks.
Business context
Share current workflow, relevant systems, intended users, constraints, and what a useful outcome would enable the organization to decide or do.
Appropriate data
When data matters, provide authorized information—or privacy-protected simulated data—along with clear limits on access and use.
Stage feedback
Review assumptions, a midpoint direction, and final recommendations promptly so the team can adjust while the work is still useful.
Clear boundaries
Confirm confidentiality, intellectual-property, tool, security, and implementation expectations before affected work begins.
Organization responsibilities
Provide context and feedback.
- Work with the team to clarify the need and decisions it should support
- Make an appropriate liaison and relevant stakeholders available
- Provide timely review at working, midpoint, and final stages
- Provide suitable data or privacy-protected simulated data when required
Student and faculty responsibilities
Protect quality and boundaries.
- Confirm the project plan, roles, agreed outputs, and review schedule
- Communicate progress, questions, and emerging risks clearly
- Use organizational information responsibly
- Complete the final presentation, handoff, and agreed deliverables
Important to know
Thoughtful scoping protects everyone’s time and information.
Initial inquiries should never include confidential, regulated, personally identifiable, or proprietary information. When an NDA or other written agreement is needed, it is completed before the affected work begins.