Frequently Asked Questions

Tips from one sponsor to another

Sponsoring an ISSP project isn’t the same as hiring a contractor, and that’s actually the point. You’re getting enthusiastic, learning-focused talent working on your real-world problem. The sponsors who get the most value from ISSP understand how to balance project goals with the learning journey.

1. Start strong: Your first meeting sets the tone

Come prepared with a clear presentation of your project and business needs. A PowerPoint deck or supporting documentation goes a long way in helping students understand your goals and get started on the right foot. Think of this as their project briefing. The clearer you are upfront, the smoother the journey.

2. Build your support network

Students work closely with BCIT supervisors throughout the project. Don’t hesitate to get their contact information and reach out when needed. These supervisors are experienced guides who can help bridge communication and keep projects on track.

3. Lock in the framework early

Students will draft a Project and Scope Plan document; this is your roadmap. Ensure that milestones with specific dates are clearly laid out, and that realistic expectations for each milestone are established together. This document becomes the team’s guiding framework for the entire project. When in doubt, come back to it.

4. Establish a consistent meeting rhythm

Weekly meetings* are the heartbeat of successful ISSP projects. Establish a consistent day and time early on, but be prepared to be flexible. Remember, most of the year, the students are also taking other courses and managing academic deadlines.

Pro tip: Consider meeting with students before their weekly supervisor meeting. This gives them a chance to bounce ideas and develop strategies to tackle problems, making their supervisor meetings more productive.

*Meet more often if working with a team in the condensed 4-week term in the spring.

5. Use agendas to stay aligned

Ask students to prepare a weekly agenda. This simple practice helps both you and the team stay focused on what needs to be discussed and creates a record of decisions made. Don’t hesitate to add “milestone review” as a standing agenda item, regularly checking progress against the Project and Scope Plan keeps everyone accountable and on track.

6. Foster equity within the team

Every group has a natural leader, but encourage participation from all team members during your weekly meetings. Ask each student to present what they’ve been working on; this ensures equity within the group and prevents one learner from carrying the entire load. It’s unfair to place all expectations on a single student, and hearing from everyone gives you a better sense of the project’s actual progress.

7. Balance support with professionalism

Be supportive and encouraging; your students are learning and growing. But also maintain professional standards and don’t hesitate to provide constructive feedback when needed. The best sponsors create a safe space for learning while preparing students for real-world work environments. Your honest, encouraging feedback is one of the most valuable gifts you can give them.

You’re now part of a growing network of industry sponsors who believe in learning by doing. These students will remember your guidance long after the project ends, and many sponsors find that their ISSP teams become valuable additions to their professional networks.

Don’t forget to attend their expo or demo and show your support!

Students in various computing programs undertake ISSP projects in different terms.

For student skills and knowledge, see the following program matrixes:

• Full-Stack Web Development (FSWD) Diploma
• Computer Systems Technology (CST) Diploma
• Computer Information Technology (CIT) Diploma
• Systems Software Developer (SSD) Certificate

Or check out our diploma comparison page to learn about each computing program’s strengths and focus areas.

Since there is no guarantee of success or when/if a project is selected, mission-critical or time-sensitive projects are not recommended.

Top

The ISSP program runs three times a year: in September, January, and April. There are various durations depending on the program the students are enrolled in. Please see the ISSP options table to get a better idea.

Top

We welcome any IT and software development projects for consideration. Projects for proof-of-concept, engineering or research development are also suitable. See also the list of project areas.

However, considering there is no guarantee of when or if a project will be selected, or of its success, time-sensitive or mission-critical projects might not be suitable.

Top

Students tend to select projects that have appropriate scope and well-defined, achievable goals. These projects should also offer sufficient challenge to be rewarding and allow students to apply their knowledge, while possibly learning new skills.

Evidence that the sponsor has sufficient knowledge to answer technical questions about the project also helps. When you complete the Submission Form, remember the following recommendations may increase the chances of selection:

• Clarify domain-specific terms or use “layman’s” terms. Describe the domain.
• Add some details and/or examples of what you are looking for. If possible, elaborate on any listed components, features or functions.
• Clarify the scope of the project; possibly separate the project into more than one project, and/or state willingness to work with the scope and to divide the project into smaller parts as appropriate once students begin.
• Specify the technologies to be used or suggest several options.
• Assure the students that one or more people with technological and domain knowledge will support them during the project.

Top

It is best to be conservative. If you suspect that the project is too big, it almost certainly is. If your project is selected, the primary objective of the initial meeting with the student(s) will be to discuss a feasible scope.

Top

We ask all sponsors to meet with your team once per week, generally for about an hour.* If you think it’s important to connect more or would like to be more involved in project supervision, please discuss it with your students.

*In the compressed May (five-week) project term, this is accelerated to multiple connections per week.

Generally yes. If it is well-documented and the students (possibly a different team) can be brought up to speed in a week, then a project continuation is feasible.

Top

While students do not receive payment for executing the projects, a $500 (+ tax) Participation Fee is due for each selected project. An invoice will be sent to the sponsor of each selected project.

In the event multiple projects by the same sponsor are selected, or a project is worked on in multiple terms, the Participation Fee will be charged per project, per term.

The fee will be waived for non-profit organizations (Charity registration number or official NPO status will be required).

Top

According to BCIT’s Intellectual Property Policy, creators (i.e. students in an ISSP project) are owners of the IP. BCIT does not require the students to enter any non-disclosure agreement (NDA) or sign away the IP in the ISSP program.

However, if the sponsors require so, they should indicate it in the project submission form (check the box “I want students to sign an NDA/IP” and download the NDA form) and discuss it with the students during the first meeting.

While many students are amenable to such an agreement, they have the option to select an alternative project if they disagree with the terms.

In general, the Confidentiality Intellectual Property Agreement should:

• Allow the student to present their work to faculty, sponsor and other students in a final presentation
• Allow the students to include their work in their portfolio
• Not exclude the students from employment in any industry

Top

Computer Information Technology (CIT) Internship Option: If your team or company needs individual contributors for project or operational roles, CIT students also have the option of doing an individual practicum in place of one of the team-based projects. The individual practicum is for students in the final term of CIT, and requires at least 100 hours of work (paid or unpaid) with a company for 10 weeks or more. If you have a position available for a student or would like to learn more, please email us.