Project Title:

Requestor:

Date of Discovery Meeting:

Evaluator(s):

Date of Evaluation:

---

Quick Reference Summary

Item	Details
Primary User Group	Blank (for templating purposes)
Estimated Users	Blank (for templating purposes)
Funding Status	☐ Funded ($______) ☐ Unfunded ☐ Partial
Requested Timeline	Blank (for templating purposes)
Development Estimate	☐ Days ☐ Weeks ☐ Months

---

Evaluation Criteria

1. Strategic Fit & Impact

Consider: Does this align with our mission? Will it meaningfully benefit the UBC community? Is there potential for broad adoption or significant depth of impact?

Assessment:

• Alignment with LTIC/University Mission:
  ☐ Strong fit ☐ Moderate fit ☐ Weak fit ☐ Misaligned
• Potential Impact:
  ☐ High (100+ users or critical need for smaller group)
  ☐ Medium (20-100 users or important improvement)
  ☐ Low (<20 users or minor enhancement)
• Strategic Value:
  ☐ Addresses key university priority
  ☐ Enables innovation in teaching/learning
  ☐ Solves known pain point
  ☐ Reusable/scalable across UBC
  ☐ Other: _________________________________

Notes:

---

2. Feasibility & Complexity

Consider: Can we realistically build/implement this? Do we have the skills, tools, and time? What’s the technical complexity and risk level?

Assessment:

• Technical Complexity:
  ☐ Simple (familiar tech, straightforward requirements)
  ☐ Moderate (some new tech or complex integration)
  ☐ Complex (significant R&D, multiple complex integrations)
  ☐ Unknown (needs further technical investigation)
• Development Time Estimate:
  ______ hours/days/weeks
• Skills/Resources Required:
  ☐ Available in current team
  ☐ Requires specific expertise: _______________________________
  ☐ Need to hire/contract: _______________________________
• Key Technical Risks:
  ☐ Integration challenges (Canvas, SIS, other systems)
  ☐ Performance/scalability concerns
  ☐ Unproven technology/approach
  ☐ Data migration/legacy system issues
  ☐ Security/privacy complexity
  ☐ None identified
  ☐ Other: _________________________________

Notes:

---

3. Sustainability & Support

Consider: Can we maintain this long-term? Is there a realistic support model? Will the requestor/department be engaged partners?

Assessment:

• Ongoing Maintenance Requirements:
  ☐ Minimal (stable, infrequent updates)
  ☐ Moderate (regular content updates, seasonal support)
  ☐ High (continuous development, high support volume)
• Support Model:
  ☐ LTIC provides all support
  ☐ Shared with requestor/department
  ☐ Department/faculty leads after launch
  ☐ Unclear/needs discussion
• Requestor/Champion Engagement:
  ☐ Strong (committed, available, resourced)
  ☐ Adequate (willing but limited capacity)
  ☐ Weak (low engagement or capacity concerns)
• Long-term Viability:
  ☐ Clear path to sustainability
  ☐ Depends on continued funding
  ☐ Uncertain/concerning

Notes:

---

Additional Considerations

Compliance & Approvals

Required approvals/consultations:

☐ IT Security review
☐ PIA/FIPPA consultation
☐ Accessibility assessment
☐ Faculty/department formal approval
☐ Research ethics (if applicable)
☐ Legal review
☐ None needed
☐ Other: _________________________________

Estimated approval timeline:

Notes:

---

Resource Implications

Can we do this with current capacity?
☐ Yes, within normal workload
☐ Yes, but will need to defer other work
☐ No, need additional resources

Budget implications (if unfunded):

• Estimated development cost: $
• Estimated annual operating cost: $
• Potential funding sources:

Staffing needs:

☐ Current team adequate
☐ Need student hiring ( hours)
☐ Need contractor/specialist:
☐ Need FTE hire:

Notes:

---

Dependencies & Risks

External dependencies:

☐ Third-party services/APIs
☐ Other UBC departments/systems
☐ Vendor/licensing agreements
☐ Grant funding timelines
☐ Other:

Major risks or concerns:

---

Overall Assessment

Recommendation

☐ Accept – Move forward as proposed

☐ Accept with Modifications – Move forward with changes (specify below)

☐ Defer – Good idea but not feasible right now (specify conditions)

☐ Redirect – Better avenue elsewhere at UBC

☐ Reject – Not aligned with mission/capacity

---

Rationale

Why this recommendation?

If Accept with Modifications, what changes?

If Defer, under what conditions would we reconsider?

If Reject, key reasons:

---

Next Steps (if Accepted or Modified)

Immediate actions:

Timeline:

• Discovery/planning phase:
• Development phase:
• Testing/pilot phase:
• Launch target:

Key milestones:

Assigned team members:

• Project lead:
• Developers:
• Other:

---

Required Follow-up with Requestor

Questions still outstanding:

Information/materials needed:

Key discussion points for response:

---

Sign-off

Evaluated by: _______________________________________________ Date: __________

Reviewed by (Academic Director): _______________________________________________ Date: __________

Final Decision: ☐ Accept ☐ Accept with Modifications ☐ Defer ☐ Redirect ☐ Reject

---