An Ontario project does not establish permission to serve every other province. Identify the intended player jurisdictions before projecting one national launch budget.
Keep the Ontario dependencies separate
| Dependency | What the project team needs to establish |
|---|---|
| AGCO | Relevant operator and supplier registration requirements |
| iGO | Required agreements, policies and onboarding conditions |
| Technology | Applicable testing and supplier evidence for the configuration |
| Operations | Ability to perform the responsibilities accepted by the operator |
The official process includes requirements concerning suppliers and independent testing. A platform sales statement should be checked against the actual entities, products and versions proposed.
Plan for the complete launch conditions
One completed registration does not mean every launch dependency is closed. Track outstanding contractual, technical and operational conditions. Identify who can provide the evidence needed to satisfy each one.
For another province, start a separate permission assessment rather than reuse Ontario's process by changing the location in the document.
Discuss the provincial scope with SuperBluOrange and share the current onboarding position. We can connect the software work to the appropriate operating arrangement, with an explicit boundary between completed approvals and remaining launch conditions.
Last source review: October 17, 2026. Recheck applicable rules before committing.