As a user, I want to incorporate a co-op

[sienna-oldaccountdontuse]

Story

As a user
I want to incorporate a cooperative association
So that i am recognized as a legal entity in BC

Background

In this flowchart
Spreadsheet

Differences from Benefit Companies

Step 1

• Can only create named company (using NR)
• Only needs registered office mailing and deliver (no records office)
• No name translation
• Must indicate if special cooperative type
  • Community Service
  • Housing

Step 2

• Min 3 directors, - At least 1 in BC; Majority in Canada
• Need subscribers, 3 minimum, from anywhere

Step 3

• Don't input share structure data in app - it is included in the form they upload
• Need to upload "Memorandum"

Step 4

• Link to guide to download (instead of "Benefit Company Sample articles")
• Need to upload rules
• Don't need to indicate if they "made their own, or used the sample" like bcomps do

Step 5

• Can only be effective immediately
• Different section and act
• Different filing fee

After payment

• Staff need to review the rules and memorandum that were uploaded before incorporation can happen
• Staff need to approve the filing
• System needs to mark the filing as complete
• Staff could interact with client, questions about approval process?????? ⚠️
• System needs to mark the rules and memorandum as certified, and include the new name and incorporation number of the co-op. How do we want to "certify" it, add a cover page? Add an overlay? Do they upload just PDFs? What does Societies do? ⚠️
• System needs to provide outputs: Incorporation certificate, Incorporation output ( @lmcclung needs to ask policy if we can do an incorporation output instead of list of first directors and list of addresses) Policy said yes, we can have an incorporation output
• NO BN Messaging
• NO MRAS messaging
• Does not need to get displayed BC OnLine Yes it does need to get displayed in BCOL
• Does not need to go back to any legacy systems (yay)
• VON/Orgbook (?) yes, it does need to go back to orgbook
• Gazette messaging (we might need to build our own, because we are currently using COLIN's jobs)

Requirements

Scenario 1 -

Definition of Ready

• Are the Acceptance Criteria defined?
• Does the user story speak to the value being created, and is understood by the team?
• Are the dependencies known/ understood? (to the our best knowledge)
• Is this user story small enough to be completed in one Sprint?
• Dev team accepts UI artifacts? (visual UX designs ready to go)
• Is it clear whether this work is intended for deploy or limited/staged-release?

[sienna-oldaccountdontuse]

Questions for Devs about story structure:

• Do you guys like the list of differences from BComps at the story level?
• Can we put AC at the relevant task level?
• Because we won't have a lot of designs for each of these stories, what do the BAs need to do to give you everything you need?