Bylaws generated from your state's template, and approved through it
In the PTA Edition only
From the state's template to an approved document, on a schedule
The state turns its bylaws into a template
The state's bylaws document, with fill-in fields where a unit's answers go: unit name, meeting day, dues amount, number of officers. Addenda that only apply to some units are inserted when the answers call for them. Separate templates for units and councils, and for in-council and out-of-council units.
The review comes due
A trigger creates the bylaws task on the anniversary of the last approval, every few years as the state decides. A unit that needs a mid-cycle change starts the task itself.
The unit answers the questionnaire
The previous answers are already filled in, so a renewal changes only what changed: a new meeting night, a new dues amount, one more officer. The unit answers in Connect, not in a document.
Connect generates the PDF
The state's template with the unit's answers in it, the right addenda attached, and a signature page, in English or Spanish. It is filed as a document on the unit's record.
The council reviews first
For an in-council unit the task goes to the council. The council reads the generated PDF and approves it, or sends it back with comments and the unit revises its answers.
Then the district, then the state
Each approver in turn reads the same PDF and approves or sends it back. An out-of-council unit's bylaws go district then state. A council's own bylaws go district then state.
Approval stamps the document
When the state approves, the bylaws document is stamped with its approval date. That date is what the next anniversary counts from.
Everyone can see where it stands
The unit's dashboard shows bylaws status and the next review date. The Bylaw Submission report shows every unit's status at council, district and state, and the Compliance report's Bylaws column reads it.
Bylaws are the one document every unit has to get exactly right
The state publishes its bylaws as a document. A thousand units open it, and each one changes something it should not, misses a section it needs, or is still on the version from four years ago.
Bylaws come up for review every few years, on a different date for every unit. Tracking that in a spreadsheet means somebody at the state office is reading approval dates in March.
The council approved it by email, the district by a signed page that was scanned, and the state is not sure it ever saw the final version.
How a state's bylaws become every unit's bylaws
Approval then runs up the same chain the rest of Connect uses, and the approval date sets the next review.
Bylaws that match the state's template, every time
Built for state PTAs and school districts. We set it up with you.
What every unit and council gets
The unit answers questions in Connect. The state's wording is never edited by hand.
On a renewal the last answers are already there, so the unit changes only what changed.
Generated from the template with the right addenda and a signature page, filed on the unit's record.
The task arrives on the anniversary the state sets, or when the unit starts one for a mid-cycle change.
Council, district and state each review the same PDF and approve it or send it back with comments.
Bylaws status and next review date on the unit's dashboard, and in the reports the council, district and state read.
And so much more
Frequently Asked Questions
Keep looking around
Messaging
Send to board members by position and level, using recipient groups you save once. Attach files, schedule the send, and see who received, opened and bounced. Every recipient also gets an in-app inbox.
Team & Permissions
Invite people at the level they work at and they see that level and everything under it. Viewers can look without changing anything. One FutureFund login carries across every product.
Memberships & Dues
Units keep their member lists, or have them filled in nightly from FutureFund. The state sees counts by unit, council and district, and per-capita dues are apportioned and paid out to every level automatically.