Analysis of changes from Bylaws v.1Bylaws v.2
Bylaws v.1 (original) ↗ Bylaws v.2 (revised) ↗ Proposed changes index ↗
Legal Working Document · RegenHub, LCA · May 11, 2026

Bylaws of RegenHub, LCA
Legal Analysis

Document reviewed
Bylaws of RegenHub, LCA · [March XX], 2026 draft · Jeff Pote / Pote Law Firm
Entity type
Colorado Public Benefit Limited Cooperative Association · Filed Feb 6, 2026 · Subchapter K tax treatment
Status
Working draft for board review and outside counsel. Not legal advice.
Analysis grounded in the Colorado Uniform Limited Cooperative Association Act (C.R.S. Title 7, Article 58), IRC § 704(b) and Treas. Reg. § 1.704-1(b), and cooperative governance principles. Tax treatment confirmed as Subchapter K (partnership). Proposed language is a starting point for Jeff's redraft — not final legal advice.
# Issue Priority Blocking board authorization?
1 Net Profit Allocation — equal share contradicts ULCAA and undermines IRC 704(b) High Yes — blocking
2 Suspension — no prior notice before stripping owner-member rights High Depends on bylaws dispute resolution
3 Quorum — "in person" requirement conflicts with hybrid membership and electronic meetings High Advisable
4 Schedule A — share price and dues are unfilled placeholders High Yes — blocking (bylaws cannot be effective)
5 Compensation — guaranteed payments not carved out from employee compensation prohibition Medium Yes if members will be compensated
6 Redemption window — five-year outer limit conflicts with Membership Agreement v.2 (90 days) Medium Yes — needs reconciliation
7 Confidentiality — no standard exceptions; sweeps too broad for a cooperative of practice Medium Advisable
8 Conflict hierarchy — implies ULCAA yields to bylaws; PBCA citation questionable Medium Advisable
Issue 01

Net Profit Allocation — Equal vs. Proportional to Patronage

For Jeff — Counsel Brief
v2 changes equal allocation to proportional-to-patronage because C.R.S. § 7-58-1004 makes proportionality the statutory default and the cooperative principle of members' economic participation requires that members who contribute more receive more. Equal allocation combined with proportional-to-capital-accounts loss allocation creates an IRC § 704(b) asymmetry that may fail the substantial economic effect test under Treas. Reg. § 1.704-1(b)(2).

The Patronage Plan link ensures the allocation methodology is adopted through a member-consent process rather than unilateral board revision. Both should use the same proportionality basis — patronage for profits, capital account balance for losses is the permissible combination under the regulations, but only if the same member who has a larger capital account also contributed more patronage. If patronage and capital account balance diverge, the allocation methodology should state explicitly which controls for which type of income/loss.

For the Board & Members
The original bylaws split profits equally among all members regardless of how much work each person contributed. This change ties profit distribution to actual contribution — the way cooperatives are designed to work.

If you bill 20 hours of client work through the co-op and another member bills 2 hours, you receive a larger share of the profits. Equal splits reward lower contributors disproportionately and penalize higher contributors. The specific way contributions are measured will be set in a Patronage Plan that the board adopts and members vote on — it can't be changed without majority member approval.

Current language — § 5.3.2
"Net Profits shall be allocated equally among the Patron Members at the end of each tax year... the Board shall have the authority to develop, review, and revise the methodology by which to calculate the Cooperative's, and each Member's respective allocable share of, Net Profits and Net Losses."
Current language — § 5.3.3
"Net Losses will be shared by the Patron Members in proportion to their respective Capital Accounts."
Problem — two layers

Layer 1 — ULCAA default allocation (C.R.S. § 7-58-1004). The statute provides that net margins shall be allocated to patron members "in proportion to the members' patronage of the association during the period." "Allocated equally" means each member receives the same dollar amount regardless of their actual contribution to the cooperative's revenue-generating activity. Equal allocation is not the same as proportional-to-patronage allocation. For a cooperative of practitioners where some members bill twenty hours of client work per month and others bill two, equal allocation rewards the lower contributor disproportionately and penalizes the higher contributor. This directly contradicts the cooperative principle of members' economic participation and the statute's default.

Layer 2 — IRC § 704(b) substantial economic effect. For Subchapter K, allocations must either (a) have substantial economic effect per Treas. Reg. § 1.704-1(b)(2), or (b) be consistent with the members' interests in the partnership per § 1.704-1(b)(3). The asymmetry between equal profit allocation and loss allocation proportional to capital accounts creates a capital account maintenance problem: if two members have different capital account balances (because one contributed more or received larger prior allocations), equal profit allocation means the member with the smaller account receives a disproportionately large share relative to their economic stake. This may fail the substantial economic effect test because it doesn't track actual economic arrangement.

Additionally, unconstrained Board discretion to "develop, review, and revise the methodology" without member consent violates C.R.S. § 7-58-1004's proportionality baseline and undermines the Patronage Plan the Membership Agreement requires the Board to adopt.

Proposed replacement — § 5.3.2
"Net Profits shall be allocated among the Patron Members in proportion to their patronage of the Cooperative during the applicable fiscal year, as measured by the Patronage Plan adopted pursuant to the Membership Agreement. Before allocation of Net Profits, the Board may set aside reasonable reserves as provided in Section 5.4.1. Notwithstanding the foregoing, where the Cooperative has not yet adopted a Patronage Plan or where all Patron Members have contributed equal and identical patronage during the applicable period, Net Profits may be allocated equally. The Board may amend the patronage measurement methodology only through the Patronage Plan amendment process requiring majority patron member approval."
Add note to § 5.3.3
"Net Losses will be allocated among the Patron Members in proportion to their respective positive Capital Account balances immediately prior to the allocation; provided that such allocation is consistent with the qualified income offset in Section 5.3.4."
For Jeff — Counsel Brief
v2 changes equal allocation to proportional-to-patronage because C.R.S. § 7-58-1004 makes proportionality the statutory default and the cooperative principle of members' economic participation requires that members who contribute more receive more. Equal allocation combined with proportional-to-capital-accounts loss allocation creates an IRC § 704(b) asymmetry that may fail the substantial economic effect test under Treas. Reg. § 1.704-1(b)(2).

The Patronage Plan link ensures the allocation methodology is adopted through a member-consent process rather than unilateral board revision. Both should use the same proportionality basis — patronage for profits, capital account balance for losses is the permissible combination under the regulations, but only if the same member who has a larger capital account also contributed more patronage. If patronage and capital account balance diverge, the allocation methodology should state explicitly which controls for which type of income/loss.

Issue 02

Suspension — Immediate Deprivation Without Notice

For Jeff — Counsel Brief
v2 adds written notice and a response period before suspension (except criminal/fraud) because suspension strips an owner-member of all participation rights for up to 180 days — a more sudden deprivation than termination, which already requires 14-day notice. The grounds "violated any resolution" and "frustrated the Cooperative's purpose or efforts" are broad enough to encompass legitimate member dissent; without a response opportunity, these grounds create a chilling effect on governance participation.

The exception for ground (b) (criminal/fraud conduct) preserves the board's emergency power. The 30-day post-suspension hearing and 10-business-day written determination requirements ensure the suspension remains a temporary measure subject to procedural review, not a de facto expulsion.

For the Board & Members
Currently the board can suspend a member immediately — cutting off access to all co-op services and governance participation — with no prior notice and no chance to respond. This changes that.

Except for criminal conduct, you get 5 business days' written notice and can submit a response before any suspension takes effect. If you are suspended, you're entitled to a hearing within 30 days. As an owner-member with equity in the co-op, you deserve at minimum the chance to tell your side before your membership rights are cut off.

Current language — § 1.10.1
"In the event that the Board, in its sole discretion, shall find by a simple majority vote that a Patron Member has (a) violated these Bylaws or any resolution, rule or policy of the Board, (b) committed any criminal act or other unlawful conduct involving fraud or dishonesty, or (c) otherwise been disruptive to the orderly operation of the Cooperative or frustrated the Cooperative's purpose or efforts, the Board may suspend, effective immediately, such Member for a period of time not to exceed one hundred and eighty (180) days..."
Compare — termination (§ 1.10.2)
Requires 14-day written notice + hearing before termination.
Problem

Patron members are owner-members of the Cooperative, not at-will participants. Suspension strips a member of all participation rights — access to cooperative services, voting, governance involvement — for up to 180 days, effective immediately, with no notice and no opportunity to respond. This is a more sudden deprivation than termination (which at least requires 14-day notice and a hearing).

For categories (a) "violated any resolution, rule or policy" and (c) "disruptive to orderly operation or frustrated the Cooperative's purpose or efforts" — these are broad, subjective standards. A cooperative of practitioners will regularly have members who disagree with board decisions. Immediate suspension for "frustrating the Cooperative's purpose or efforts" creates a chilling effect on legitimate member dissent.

C.R.S. § 7-58-1101 preserves the member's right to dissociate; C.R.S. § 7-58-1101(2) allows the operating agreement (including bylaws) to specify when dissociation is wrongful, but the statute does not authorize unlimited summary deprivation of member rights. Good cooperative governance practice requires at minimum: written notice of the specific conduct alleged, and some opportunity to respond before the deprivation takes effect (except for emergency circumstances such as actual criminal conduct).

Proposed addition — after "the Board may suspend... such Member"
"[...] provided that, except in cases of ground (b) (criminal act or unlawful conduct involving fraud or dishonesty), the Board shall first provide the affected Member with written notice specifying the conduct at issue and a five (5) business day period to submit a written response to the Board before any suspension takes effect. In cases of ground (b), immediate suspension without prior notice is permitted. Any Member suspended under this Section 1.10.1 shall be entitled to a hearing before the Board within thirty (30) days of the suspension's effective date at which the Member may present evidence and respond to the basis for suspension. The Board shall, within ten (10) business days of such hearing, issue a written determination either lifting, modifying, or confirming the suspension."
For Jeff — Counsel Brief
v2 adds written notice and a response period before suspension (except criminal/fraud) because suspension strips an owner-member of all participation rights for up to 180 days — a more sudden deprivation than termination, which already requires 14-day notice. The grounds "violated any resolution" and "frustrated the Cooperative's purpose or efforts" are broad enough to encompass legitimate member dissent; without a response opportunity, these grounds create a chilling effect on governance participation.

The exception for ground (b) (criminal/fraud conduct) preserves the board's emergency power. The 30-day post-suspension hearing and 10-business-day written determination requirements ensure the suspension remains a temporary measure subject to procedural review, not a de facto expulsion.

Issue 03

Quorum — "Present and in Person" Conflicts with Hybrid Membership

For Jeff — Counsel Brief
v2 adds "or participating by electronic or telecommunications means permitted under Section 2.1" because the original "present and in person" language, read plainly, excludes electronic attendees from quorum — directly contradicting § 2.1's explicit authorization of hybrid and electronic meetings. This is a technical correction, not a substantive change to quorum threshold.

Jeff should confirm that the companion voting provisions (§ 2.6, § 2.8) consistently treat electronic participation as valid, since a quorum fix that is not matched by voting-provision fixes would create a new inconsistency.

For the Board & Members
The bylaws say a meeting requires "a simple majority present and in person" to conduct official business. But the same bylaws also say meetings can be held by video call or phone. Under a strict reading, people attending by Zoom don't count toward quorum — meaning a meeting with 9 people on video and 1 in person technically couldn't conduct business.

This is a straightforward fix: people attending electronically count toward quorum, the same as those in the room. It aligns the quorum rule with the meeting format the bylaws already permit.

Current language — § 2.7.1
"a quorum for the transaction of business at any meeting of the Members shall be a simple majority of the Patron Members, present and in person"
Compare — § 2.1
"All meetings of Members of the Cooperative may take place in person, by telephone or video conference, or by any other electronic or telecommunications means..."
Problem

The quorum provision requires members to be "present and in person." Under a plain reading, members attending by video or telephone conference would not count toward quorum, because they are not "in person." This means a meeting of 10 members with 6 attending electronically and 3 attending in person would not have a quorum — even though 9 of 10 members are effectively present.

The Cooperative's governing documents explicitly contemplate hybrid and fully electronic meetings (§ 2.1). The quorum provision should match. The phrase "present and in person" appears to be standard boilerplate for an in-person entity — it was not updated for an LCA that expressly permits electronic attendance.

Proposed replacement — § 2.7.1
"Except for transactions of business specifically requiring a different quorum by law, a quorum for the transaction of business at any meeting of the Members shall be a simple majority of the Patron Members entitled to vote, present in person or by electronic or telecommunications means permitted under Section 2.1."
For Jeff — Counsel Brief
v2 adds "or participating by electronic or telecommunications means permitted under Section 2.1" because the original "present and in person" language, read plainly, excludes electronic attendees from quorum — directly contradicting § 2.1's explicit authorization of hybrid and electronic meetings. This is a technical correction, not a substantive change to quorum threshold.

Jeff should confirm that the companion voting provisions (§ 2.6, § 2.8) consistently treat electronic participation as valid, since a quorum fix that is not matched by voting-provision fixes would create a new inconsistency.

Issue 04

Schedule A — Unfilled Placeholders

For Jeff — Counsel Brief
v2 flags Schedule A placeholders as completion items because bylaws with blank financial terms cannot be effective. The $100 Patron Share price, initial annual dues, effective date, initial board composition, and secretary signature must all be confirmed and filled before the bylaws are presented for board authorization.

The $100 share price must match the Membership Agreement; if they differ, the governing document for redemption mechanics must be identified. Any founding member dues waiver should be documented separately rather than left to implication in Schedule A.

For the Board & Members
Schedule A — the part of the bylaws that sets share price and annual dues — has blank placeholders. The bylaws can't take legal effect with blank financial terms. This flags what needs to be filled in before the board votes to adopt them: the share price (expected $100), any annual dues, the effective date, initial board member names, and the secretary's signature.

These are administrative items for the board to confirm. The share price must match the Membership Agreement. Any founding member dues waiver should be documented separately.

Current language — Schedule A
Share Price: $[…]
Membership Dues (yearly): $[…]
Problem

The bylaws cannot be effective with material financial terms left blank. The Membership Agreement v.2 references $100 per share of Patron Stock. Schedule A must be completed before the bylaws are authorized.

The Board retains discretion to revise these amounts, so the specific values in Schedule A will be the initial values subject to future Board adjustment.

Additional completion items

Three other blanks must be filled before execution:

- Effective date in title block and Certificate: "[MARCH XX], 2026"
- Initial Board composition (§ 3.2.2): "[…]"
- Secretary signature on Certificate: "[…], Secretary"

For Jeff — Counsel Brief
v2 flags Schedule A placeholders as completion items because bylaws with blank financial terms cannot be effective. The $100 Patron Share price, initial annual dues, effective date, initial board composition, and secretary signature must all be confirmed and filled before the bylaws are presented for board authorization.

The $100 share price must match the Membership Agreement; if they differ, the governing document for redemption mechanics must be identified. Any founding member dues waiver should be documented separately rather than left to implication in Schedule A.

Confirm before execution
(a) $100 per Patron Share matches the Membership Agreement; (b) the Cooperative has determined whether to charge annual dues at this time; and (c) the Schedule A reflects any initial dues waiver for founding members.
Issue 05

Compensation — Guaranteed Payments Not Carved Out

For Jeff — Counsel Brief
v2 adds the IRC § 707(c) guaranteed payments carve-out because the original prohibition on "salary or other compensation as an employee" is correct as to employment — W-2 wages cannot be paid to partners under Treas. Reg. § 31.3121(d)-1(b) and Rev. Rul. 69-184 — but overbroad as to mechanism. A broad reading would prohibit guaranteed payments, which are the legally correct substitute for member compensation under Subchapter K.

Guaranteed payments are deductible by the entity, ordinary income to the member, and reported on Schedule K-1 — the standard compensation mechanism for working partners. Without this carve-out, the bylaws arguably prohibit compensating working members at all while the partnership election is in effect. Before the first fiscal year, the board should adopt a resolution clarifying the form and process for member compensation under § 707(c).

For the Board & Members
The bylaws correctly say members can't receive W-2 employee paychecks while the co-op is taxed as a partnership — that's an IRS rule. But the original language was broad enough that it could be read to mean members can't be compensated at all for their work.

This change clarifies: the co-op can pay members for services through a "guaranteed payment" — the tax-law-approved way to compensate working partners. You'd receive it as ordinary income and it shows up on your Schedule K-1 each year. Without this clarification, the bylaws could be read to prohibit paying members for any services while the partnership tax election is in effect.

Current language — § 4.8
"at any time while the Cooperative is taxed as a partnership, no Director or officer of the Cooperative who is also a Member may receive any salary or other compensation as an employee of the Cooperative in consideration for their performance of services on behalf of the Cooperative."
Problem

This provision correctly recognizes that member-partners cannot be W-2 employees while the entity is taxed as a partnership. Under Treas. Reg. § 31.3121(d)-1(b) and IRS Rev. Rul. 69-184, partners cannot be employees of their own partnership. However, IRC § 707(c) provides the correct mechanism for compensating members for services: guaranteed payments. Guaranteed payments are deductible by the Cooperative (as business expenses), included in the member's ordinary income, and reported on Schedule K-1.

The current provision says "no salary or other compensation as an employee." This is accurate as to employment compensation, but if read broadly, it could be interpreted to prohibit guaranteed payments — which are not employee compensation but are the correct and legally required substitute. For a cooperative of practitioners whose members may be performing services for the Cooperative, this ambiguity creates real operational risk: members may believe they cannot be compensated at all while the partnership election is in effect.

Statutory and regulatory basis
  • IRC § 707(c): Guaranteed payments for services or use of capital are treated as made to a person who is not a member of the partnership — deductible by the entity, ordinary income to the recipient.
  • IRC § 707(a): Transactions between the partnership and a member acting outside their capacity as a member are treated as arm's-length transactions with a non-member.
  • Treas. Reg. § 31.3121(d)-1(b); Rev. Rul. 69-184: Partners are not employees of their own partnership — W-2 wages cannot be paid to a member while taxed as a partnership.
Proposed replacement — § 4.8, first sentence
"At any time while the Cooperative is taxed as a partnership, no Director or officer of the Cooperative who is also a Member may receive any salary or other compensation in their capacity as an employee of the Cooperative. Notwithstanding the foregoing, Members may receive guaranteed payments for services or use of capital within the meaning of IRC § 707(c), as authorized by the Board, which shall be treated as ordinary income to the recipient and reported on Schedule K-1. Nothing in this provision prohibits a Member from receiving compensation for services rendered to the Cooperative in a capacity other than as a Member, provided such arrangement is treated as a transaction between the Cooperative and a person acting outside their capacity as a Member under IRC § 707(a), and disclosed to and approved by the Board."
For Jeff — Counsel Brief
v2 adds the IRC § 707(c) guaranteed payments carve-out because the original prohibition on "salary or other compensation as an employee" is correct as to employment — W-2 wages cannot be paid to partners under Treas. Reg. § 31.3121(d)-1(b) and Rev. Rul. 69-184 — but overbroad as to mechanism. A broad reading would prohibit guaranteed payments, which are the legally correct substitute for member compensation under Subchapter K.

Guaranteed payments are deductible by the entity, ordinary income to the member, and reported on Schedule K-1 — the standard compensation mechanism for working partners. Without this carve-out, the bylaws arguably prohibit compensating working members at all while the partnership election is in effect. Before the first fiscal year, the board should adopt a resolution clarifying the form and process for member compensation under § 707(c).

Issue 06

Redemption Window — Five Years to Three Years

For Jeff — Counsel Brief
v2 reduces the outer redemption limit from five years to three years because the five-year provision is calibrated for agricultural cooperatives with large illiquid retained patronage — not a $100 initial share. More critically, five years directly conflicts with the Membership Agreement v2's 90-day redemption provision; without reconciliation, a departing member cannot determine which timeline governs.

Three years preserves Board flexibility as an outer backstop while reducing the mismatch with the entity's actual capital profile and the solvency protection under C.R.S. § 7-58-1007. The bylaws and Membership Agreement must be explicit about which document controls redemption mechanics — Jeff should identify the controlling document before either is authorized.

For the Board & Members
The bylaws currently give the board up to 5 years to return your $100 share after you leave. Five years is a long time to wait for $100 — it's a provision written for farm cooperatives with tens of thousands in retained profits, not a $100 membership share.

This change reduces the outer limit to 3 years. The target is still to pay within 90 days (as stated in the Membership Agreement), but 3 years is the backstop if circumstances delay it. The two documents — bylaws and Membership Agreement — need to agree on the timeline.

Current language — § 1.9.3
"the Board shall redeem the Member's equity within five (5) years of withdrawal, in cash, by issuing a promissory note, or some combination thereof."
Current language — § 1.11.1
"Within one-hundred and twenty (120) days after the effective date of a Patron Member's withdrawal or termination, the Cooperative shall consider distributing to the Patron Member its equity interest... Notwithstanding the foregoing, the Board shall have the sole discretion to delay... provided that the Board shall redeem the Member's equity within five (5) years of withdrawal or termination."
Membership Agreement v.2 proposes
90-day redemption at par ($100), subject to C.R.S. § 7-58-1007 solvency limitations.
Problem

The bylaws provide a five-year outer limit with full Board discretion on timing. The Membership Agreement v.2 proposes a 90-day obligation at par value. These provisions directly conflict. A member reading the Membership Agreement would expect redemption within 90 days; the bylaws give the Board up to five years.

For a $100 share, a five-year redemption delay is disproportionate to the Cooperative's likely exposure. The five-year outer limit is appropriate for organizations with large, illiquid capital accounts (e.g., agricultural cooperatives with hundreds of thousands in retained patronage). For an LCA with a $100 initial membership share, 120 days or 90 days is more appropriate.

The two documents should be reconciled. Recommended approach: retain the 120-day "shall consider distributing" language from § 1.11.1 as the target, but set a three-year (rather than five-year) outer limit, subject to C.R.S. § 7-58-1007. The Membership Agreement's 90-day language can reference the bylaws for the controlling mechanics.

For Jeff — Counsel Brief
v2 reduces the outer redemption limit from five years to three years because the five-year provision is calibrated for agricultural cooperatives with large illiquid retained patronage — not a $100 initial share. More critically, five years directly conflicts with the Membership Agreement v2's 90-day redemption provision; without reconciliation, a departing member cannot determine which timeline governs.

Three years preserves Board flexibility as an outer backstop while reducing the mismatch with the entity's actual capital profile and the solvency protection under C.R.S. § 7-58-1007. The bylaws and Membership Agreement must be explicit about which document controls redemption mechanics — Jeff should identify the controlling document before either is authorized.

Questions for Jeff
(a) What is the intended redemption timeline for the $100 Patron Share? (b) Should the Membership Agreement or the bylaws be the controlling document for redemption mechanics? (c) Is the five-year outer limit intended as a safety valve for solvency situations, or as an actual operational timeline?
Issue 07

Confidentiality — No Standard Exceptions

For Jeff — Counsel Brief
v2 replaces the confidentiality provision with a scoped definition plus four standard exceptions because the original swept all Cooperative information into indefinite strict confidence with no carve-outs. For a Public Benefit LCA that voluntarily publishes an annual benefit report, sweeping confidentiality over "all information pertaining to… operations, activities or transactions" creates direct tension with the transparency obligations the Cooperative has undertaken.

The replacement is standard commercial confidentiality language — it protects genuine trade secrets and member information while allowing members to describe their cooperative involvement publicly, consult legal counsel, and comply with legal obligations. The "reasonable person" scope standard replaces the undefined "any and all information received by or through the Cooperative."

For the Board & Members
The original confidentiality section says you can never share "any and all information received by or through the Cooperative" with anyone. Taken literally, that would prohibit you from telling a colleague you're a member of Techne, or discussing co-op matters with your accountant during tax season.

This change is standard: it protects genuinely private information — trade secrets, client details, member financial information — while allowing you to describe your membership publicly, talk to your lawyer or accountant, and share information that's already publicly available. It also adds a clear path for situations where you're legally required to disclose (a subpoena, for example).

Current language — § 18.2
"Members and former Members, shall at all times maintain in strict confidence and promise not disclose to any person or entity not otherwise entitled to receive such information any and all information received by or through the Cooperative, pertaining to the records of the Cooperative, its Members, and the operations, activities or transactions of the same."
Problem

The confidentiality obligation has no carve-outs. For a cooperative of practitioners operating in public professional communities, the following omissions create operational and legal risk:

(a) No public domain exception — information that becomes publicly known through no fault of the member is still covered by the obligation.
(b) No prior knowledge exception — information the member knew before joining the Cooperative is still covered.
(c) No independent development exception.
(d) No required disclosure exception — if a member receives a subpoena or is required by law to disclose.
(e) No general membership description exception — members cannot describe their cooperative membership or involvement in public professional contexts without risking breach.
(f) No legal counsel exception — members presumably can consult attorneys, but the current language requires their counsel to maintain confidence "to the same degree and extent" as the member, which is an unusual expansion of the restriction.

For a Public Benefit LCA that publishes an annual benefit report (Article XV), sweeping confidentiality over "all information received by or through the Cooperative pertaining to... operations, activities or transactions" creates tension with the transparency obligations the Cooperative has voluntarily undertaken.

Proposed replacement — § 18.2
"Members and former Members shall maintain in confidence non-public information received from or through the Cooperative that is designated as confidential or that a reasonable person would understand to be confidential given the nature of the information and circumstances of disclosure ('Confidential Information'). The foregoing obligation does not apply to information that: (a) is or becomes generally available to the public other than as a result of disclosure by the Member in breach of this Section; (b) was known to the Member prior to receiving it from the Cooperative, as evidenced by records in existence before receipt; (c) is independently developed by the Member without reference to Confidential Information; or (d) is required to be disclosed by law, regulation, or court order, provided the Member provides the Cooperative prompt written notice before disclosure (where legally permitted) and cooperates with the Cooperative's efforts to seek a protective order. Members may disclose the existence of their membership and the general nature of the Cooperative's activities in professional contexts. Members may share Confidential Information with attorneys, accountants, and advisors bound by professional confidentiality obligations."
For Jeff — Counsel Brief
v2 replaces the confidentiality provision with a scoped definition plus four standard exceptions because the original swept all Cooperative information into indefinite strict confidence with no carve-outs. For a Public Benefit LCA that voluntarily publishes an annual benefit report, sweeping confidentiality over "all information pertaining to… operations, activities or transactions" creates direct tension with the transparency obligations the Cooperative has undertaken.

The replacement is standard commercial confidentiality language — it protects genuine trade secrets and member information while allowing members to describe their cooperative involvement publicly, consult legal counsel, and comply with legal obligations. The "reasonable person" scope standard replaces the undefined "any and all information received by or through the Cooperative."

Issue 08

Conflict Resolution Hierarchy — ULCAA Cannot Yield to Bylaws

For Jeff — Counsel Brief
v2 reorders the conflict hierarchy to place mandatory non-waivable ULCAA provisions first because C.R.S. § 7-58-110 specifies ULCAA provisions that bylaws cannot override — including the member's right to dissociate (§ 7-58-1101(1)). Placing bylaws above the ULCAA in the hierarchy incorrectly implies that bylaw provisions can override non-waivable statutory rights.

The PBCA reference is replaced with C.R.S. § 7-58-104 because the PBCA governs public benefit corporations; RegenHub's public benefit LCA status is governed by § 7-58-104 within the ULCAA itself, not the corporate act. Jeff should confirm whether the PBCA reference was intentional (if so, the rationale should be stated explicitly) or a template artifact from a public benefit corporation form.

For the Board & Members
The bylaws currently say: if the bylaws conflict with Colorado law, the bylaws win. For certain provisions, that's legally backwards. Colorado law sets minimum protections for members that bylaws cannot override — including your right to leave the co-op.

This change puts mandatory state law above the bylaws in the conflict hierarchy. It also corrects a citation error: the bylaws referred to the Colorado Public Benefit Corporation Act, which governs corporations. Techne is a cooperative, not a corporation. The correct law is the LCA (Limited Cooperative Association) section of Colorado statute.

Current language — Preamble
"In the event of any conflict... such conflict shall be resolved first in accordance with the Articles of Organization, then these bylaws... then the ULCAA, and finally the PBCA"

Also: "the Articles of Organization, the ULCAA, and the PBCA, each as amended, and any provisions of any successor act, are incorporated by reference as if fully set forth herein."
Problem — two points

First — non-waivable ULCAA provisions. The priority hierarchy places the ULCAA below the Articles and Bylaws. Under Colorado law, certain provisions of the ULCAA are non-waivable even by Articles or Bylaws — see C.R.S. § 7-58-110 (specifying which ULCAA provisions can and cannot be varied). For example, the member's right to dissociate (C.R.S. § 7-58-1101(1)) cannot be eliminated by the bylaws. The current hierarchy implies that Articles and Bylaws always prevail over the ULCAA, which would be incorrect for mandatory statutory provisions.

Second — PBCA citation appears inapplicable. The PBCA (C.R.S. Title 7, Article 101, Part 5) is the Colorado Public Benefit Corporation Act, which governs corporations. RegenHub is an LCA, not a corporation. The public benefit provisions applicable to a Colorado Public Benefit LCA are found in C.R.S. § 7-58-104 (public benefit LCA provisions within the ULCAA itself), not in the Public Benefit Corporation Act. The PBCA citation appears to be boilerplate from a public benefit corporation template and may be inapplicable. If Jeff intended to incorporate public benefit corporation principles by analogy, that intent should be stated explicitly; if the citation is simply incorrect, it should be replaced with C.R.S. § 7-58-104 and related ULCAA public benefit provisions.

Statutory basis
  • C.R.S. § 7-58-110: Specifies which ULCAA provisions may and may not be varied by the operating agreement or articles. Non-waivable provisions include member dissociation rights and certain fiduciary duties.
  • C.R.S. § 7-58-104: Contains the public benefit provisions applicable to a Limited Cooperative Association organized for public benefit — the operative statute for RegenHub's PB status, not the PBCA.
  • C.R.S. § 7-58-1101(1): Member's right to dissociate is a non-waivable statutory right the bylaws cannot eliminate.
Proposed replacement — conflict hierarchy sentence
"In the event of any conflict, it is the intention of the Cooperative that such conflict shall be resolved first in accordance with any mandatory, non-waivable provisions of the ULCAA, then in accordance with the Articles of Organization, then these Bylaws, and then any other applicable provisions of the ULCAA, unless otherwise expressly specified by these Bylaws."
For Jeff — Counsel Brief
v2 reorders the conflict hierarchy to place mandatory non-waivable ULCAA provisions first because C.R.S. § 7-58-110 specifies ULCAA provisions that bylaws cannot override — including the member's right to dissociate (§ 7-58-1101(1)). Placing bylaws above the ULCAA in the hierarchy incorrectly implies that bylaw provisions can override non-waivable statutory rights.

The PBCA reference is replaced with C.R.S. § 7-58-104 because the PBCA governs public benefit corporations; RegenHub's public benefit LCA status is governed by § 7-58-104 within the ULCAA itself, not the corporate act. Jeff should confirm whether the PBCA reference was intentional (if so, the rationale should be stated explicitly) or a template artifact from a public benefit corporation form.

Rec

Cross-Cutting Recommendations

01
Bylaws + Membership Agreement reconciliation The two documents need to be reviewed as a system before either is authorized. Key conflicts: redemption window (90 days vs. 5 years), IP scope (bylaw confidentiality may conflict with Membership Agreement IP carve-outs), and patronage allocation methodology.
02
Patronage Plan cross-reference The bylaws should explicitly require the Board to adopt a Patronage Plan (as the Membership Agreement requires) and reference it as the operative document for profit allocation methodology.
03
Schedule A completion Before the bylaws are effective, confirm: Patron Share price ($100), initial annual dues (if any), and whether any founding member dues waiver will be documented separately.
04
Electronic meeting conformity Beyond quorum, confirm that all voting provisions (§ 2.6, § 2.8) consistently treat electronic participation as valid participation.
05
Guaranteed payments resolution Before the first fiscal year, the Board should adopt a resolution clarifying the form and process for member compensation under IRC § 707(c), consistent with the Subchapter K election.
Q&A

Questions for Jeff Pote

Question 01
Net Profit methodology
Should profit allocation be proportional to patronage (ULCAA default and cooperative principle) or equal per member? If equal, what is the rationale and how will it satisfy IRC 704(b)?
Question 02
Suspension notice
Was immediate suspension without notice intentional? If so, for which categories? Category (b) (fraud/criminal) is defensible; categories (a) and (c) (rules violations, disruption) would benefit from even a short notice period.
Question 03
Quorum
Should "present and in person" be updated to include electronic attendance, consistent with § 2.1?
Question 04
Redemption window
Which controls: the Membership Agreement's 90-day target or the bylaws' 5-year outer limit? Or does the bylaws' 120-day "shall consider" + 5-year outer limit supersede the Membership Agreement?
Question 05
PBCA citation
Is the Public Benefit Corporation Act citation intentional or a template artifact? Should it be replaced with C.R.S. § 7-58-104?
Question 06
Guaranteed payments
Is the intent to prohibit all member compensation while taxed as a partnership, or to prohibit only employment-style compensation while permitting IRC § 707(c) guaranteed payments?
Addendum — May 2026
Additional Research Read

The following findings are drawn from an independent Colorado legal research read of both v.2 documents, oriented to the ratification window. The read reviewed Bylaws v.2 and Membership Agreement v.2 together against Colorado ULCAA, IRC Subchapter K, and cooperative governance standards. Where findings extend existing issues above, cross-references are noted. Where they diverge from the analysis above, the divergence is made explicit. Research posture, not legal advice.

Extends Issue 01

Profit Allocation Default is Permissive Where It Must Be Determinate

Concurs & Adds Specificity

The existing analysis flags equal allocation as contrary to the ULCAA default and IRC § 704(b). This read adds a specific mechanism problem: § 5.3.2 uses may be allocated equally as a fallback for the period before a Patronage Plan exists. For an allocation to carry substantial economic effect under IRC § 704(b), the method must be fixed in advance, not left optional. A permissive default leaves the opening fiscal period without a determinate allocation rule.

Specific problem — the "may" fallback

MA § 2.4 defers the Patronage Plan until ninety days after the first patron member is admitted. For the opening fiscal period there will likely be no Plan, and the fallback in § 5.3.2 reads that profit may be allocated equally. For the alternative test for economic effect, the allocation method must be specified before any income or loss is allocated. A "may" leaves a gap between when members are admitted and when the Plan is adopted.

The fix is one word: replace "may be allocated equally" with "shall be allocated equally per capita among patron members in good standing until the Board ratifies a Patronage Plan." This closes the opening-period gap and removes the daylight between the patronage rule and its fallback.

Path
Replace "Net Profits may be allocated equally" in the pre-Plan fallback with a binding default: "Until a Patronage Plan is adopted, Net Profits shall be allocated equally per capita among patron members in good standing at the close of the fiscal year." This makes the first-period allocation determinate for IRC § 704(b) purposes.
Extends Issue 05

Section 4.8 Contradicts Itself — Second Paragraph Undercuts the First

Adds New Dimension to Issue 05

The existing analysis flags § 4.8 for needing a § 707(c) guaranteed-payments carve-out. This read identifies a second problem within the same section: the two paragraphs directly contradict each other, meaning the fix is not just an addition but a conforming revision.

Internal contradiction

The first paragraph correctly bars a member from drawing a W-2 salary while the entity is a partnership — the long-settled rule of Rev. Rul. 69-184 — and routes pay through guaranteed payments under IRC § 707(c). The second paragraph then says no officer is prevented from receiving a salary by reason of being a member. This re-opens precisely the exception the first paragraph just foreclosed. As currently drafted, the two paragraphs cannot both be followed.

Path
Strike or conform the second paragraph so the § 707(c) treatment stands without qualification. If the intent of the second paragraph was to preserve a carve-out for officers acting in a non-member capacity (e.g., under a § 707(a) arm's-length arrangement), that intent should be stated explicitly rather than as a general salary permission.
New — A03

Liquidation Waterfall Has Two Endings

Problem

§ 5.1.5 correctly says liquidating distributions follow positive capital-account balances, consistent with what IRC § 704(b) requires for the alternate test for economic effect. Article XIV § 14.3 then sends any residual equally to current and three-year former members.

If capital accounts have already absorbed the final gain or loss allocation — as they should under § 5.1.5 — there should be nothing left to distribute equally. A separate equal-distribution tier that does not track capital accounts can break substantial economic effect because it produces an outcome not consistent with the members' actual economic arrangement.

Statutory basis
  • IRC § 704(b); Treas. Reg. § 1.704-1(b)(2)(ii)(b)(2): Liquidating distributions must be made in accordance with positive capital account balances for the alternate test for economic effect to apply.
  • C.R.S. § 7-58-104: Public benefit asset assignment on dissolution — a potentially applicable path for residual assets that avoids the capital-account consistency problem.
Path
Reconcile Article XIV with § 5.1.5 by removing the equal-distribution tier, or recharacterize the § 14.3 residual explicitly as a public-benefit asset assignment rather than a member distribution — a path Article XIV itself already contemplates for illiquid assets. If the equal residual distribution is intentional, the document should explain how it interacts with § 5.1.5 without breaking the capital-account-based liquidation rule.
New — A04

Community Participant Class Is Difficult to Place in the Statute

Problem

ULCAA recognizes two member classes: patron members (who patronize the cooperative) and investor members (who provide capital). A Community Participant described as "a member with access to programming" who neither patronizes as a patron member nor invests as an investor member does not fit cleanly into either statutory category.

§ 1.1(c) leaves governance rights for this class to Board discretion, which creates ambiguity across voting rights, capital account treatment, and Schedule A (where Community Participant share price and dues are placeholders alongside the other classes).

Statutory basis
  • C.R.S. § 7-58-103(14), (15): Patron member and investor member definitions — the two statutory categories available to a ULCAA entity.
  • C.R.S. § 7-58-401: Governance rights of patron vs. investor members — Board discretion to define governance rights works within, not around, the statutory framework.
Path
Make a deliberate choice: is the Community Participant a sub-type of patron member (with reduced patronage activity), a form of investor member, or a non-member participant in cooperative programming? Once the classification is settled, align §§ 1.1, 1.4, and Schedule A to that choice. If the class is intended to be non-member, the voting and capital-account provisions that currently apply to members should not attach to it.
New — A05

Court-Access Waiver Is Broader Than a Jury Waiver

Problem

Waiving the right to a jury trial is routine and the Membership Agreement's own § 9.9 jury waiver is clean. Bylaws § 11.5 goes further and waives all rights to seek remedies in any court. This is a qualitatively different waiver — it forecloses judicial access entirely, not just the jury.

Paired with a Board hearing in which the Board may itself be a party to the dispute (disputes between members and the Board over governance decisions), the breadth of § 11.5 invites a fairness challenge to enforceability. A member who cannot get a neutral adjudicator when the cooperative is the adverse party has no meaningful dispute resolution path.

Path
Consider narrowing § 11.5 to a jury waiver (consistent with MA § 9.9) plus mandatory arbitration before a neutral arbitrator, and add an explicit neutral adjudication path for cases where the Board itself is the adverse party. Wholesale court-access waivers in membership agreements have been subject to challenge in other cooperative and club contexts; narrowing to arbitration + jury waiver is both more standard and more likely to be enforced.
New — A06

Article XII Sets a Threshold for Amending the Articles of Organization

Problem

Bylaws can govern their own amendment. Article XII, however, also sets a voting threshold for amending the Articles of Organization. Article amendments are a state-law matter: they follow the ULCAA's statutory procedure and require a filing with the Colorado Secretary of State. A bylaw-set threshold for article amendments could be misread as the controlling rule, potentially creating confusion about whether a bylaw amendment is also needed whenever the Articles are amended.

Statutory basis
  • C.R.S. § 7-58-201 et seq.: Article amendment procedure under the ULCAA — governs the form and filing requirements for amending a limited cooperative association's articles of organization.
Path
Add a clarifying clause to Article XII stating that article amendments proceed under the ULCAA's statutory procedure (including any required state filing), and that the threshold stated in Article XII governs bylaw amendments only. If the Board intends the Article XII threshold to apply to Article amendments as an internal governance matter (above the statutory floor), that intent should be stated explicitly with a note that it does not substitute for the statutory procedure.
Affirmed

Capital-Account Machinery and the Partnership Tax Spine Are Well-Drafted

Solid as Drafted

The research read affirms the following provisions as well-constructed and not requiring revision: the capital-account rules in § 5.1, the qualified income offset in § 5.3.4, and the no-deficit-restoration posture in § 5.6. Together these form the standard alternate test for economic effect used by a partnership that does not impose a deficit restoration obligation — an appropriate posture for an early-stage cooperative.

The guaranteed-payment handling under § 707(c) is correct in principle (the internal contradiction in the second paragraph of § 4.8, addressed above, is a drafting problem, not a structural error). The consent-to-tax provisions in §§ 1.10 and 6.1 are clear and consistent with the Subchapter K election.

Proposed Changes Index
All 15 proposed changes serialized with stable IDs for reference in board discussion and amendment motions.
View Changes Index →