Run the association from one platform.

01Forms

Every form keeps its history.

Build forms from twelve field types, from short text and dates to file uploads and section headers. Each published change becomes a new form version, so a submission always stays tied to the questions it answered.

• draft
• published
• closed
• archived

02Submissions

A clear path from submitted to approved.

Submissions move from draft to submitted to under review, then out as approved or rejected — and members can withdraw. Reviewers act through permissions like submission::review and submission::approve, and the audit log records each step.

• submitted
• under_review
• approved
• rejected
• withdrawn

03Relationships

Members, events, and forms — connected.

Beneath the records sits a relationship graph: who is a member of what, who attended which event, who submitted which form. Records are also indexed as embeddings, the groundwork for finding them by meaning.

• member_of
• attended
• submitted

AI search over this index is on the roadmap.

04One platform

One workspace for the whole association.

Chapters, roles, and the people who belong, kept together with events, attendance, and the notices that keep members in the loop — plus a public home on the association's own subdomain.

• members
• units
• events
• attendance