Page tree
Skip to end of metadata
Go to start of metadata

What To Ask If You Are Hiring a Non-ITServices Third Party Developer

If you wish to hire a third-party developer but choose not to go with ITServices, here are some questions you may want to pose before signing on the dotted line:

  • Can you build an application that will meet our requirements?
  • What is your availability? Will you be able to complete the work within our timeline?
  • Who else have you worked for? Can you provide references?
  • Do you provide project management services? Who will be responsible for tracking and ensuring timelines, scope, effort, and budget?
  • Who will own the work product? Will we have access to the code?
  • Will there be touchpoints during the development process where I can give feedback?
  • What documentation will you provide? Technical? End user?
  • What environment is required to support the application? Do you offer hosting services, or do I need to find that elsewhere?
  • Will the application meet web accessibility standards?
  • Will you be performing a security audit?
  • Will training be required to use the application? If so, will you provide it?
  • How will the application be maintained after initial delivery? Do you offer a support contract?
  • How are costs assessed? Do you use an hourly or flat rate?
  • At what point will we receive a project estimate? Do we have to pay for the estimate?
  • Will there be any hidden or additional costs? For example: for project management, documentation, training, testing, maintenance and support, etc.

Procurement Policy

There are a number of new procurement-related policies mandated by Queen's University so that the institution is in compliance with Federal and Provincial acts and agreements pertaining to Broad Public Sector (BPS) procurement. Some of these include requirements to get quotes from multiple vendors for contracts that exceed a specific dollar value.

For more information about Queen's procurement policies, please visit Queen's Strategic Procurement website .

Confidentiality and Non-Disclosure Agreements

Depending on the nature of the information your developer will have access to, they may need to sign a Confidentiality Agreement. Please see the webpage on Confidentiality and Non Disclosure Agreements for more information and copies of the agreements.


  • No labels