Keep an association as a going concern
What each owners association on the project holds: membership as recorded, the current governing document, staged turnover, and what it maintains.
An association's own facts lived in the schema with nothing to read them: which lots belong to it, which covenants and rules are current, how far turnover has gone, and what it maintains. This page is that read, one card per association, master before its subs.
A card's lot count is exactly what is on record, so a lot in a sub and its master is two rows and both counts include it. This page never walks the hierarchy to reconcile that down to one membership; expanding a card lists every member lot, with any other association it also belongs to, so the two-row shape is visible rather than something a reader has to trust the count on.
The current covenants and rules are the latest effective document not after today. A document dated in the future, or one a later document has superseded, is never shown as current.
Why it also lives here
Nothing else in the product reads this module. It was built with its schema, its RLS and its seed rows well ahead of a screen. This page is that screen.
Keeping the register
Add an association records a master, or a sub-association under the master it was formed under. Each card's Edit opens the association's own sections, and somebody with documents access at edit writes any of them:
Membership takes lots by number the way the plat names them, as a list or a range (1-6, 9, 14-16), or every lot on a plat in one phase. One row per lot; a lot already on the association is left as it is, and a lot number this project does not have refuses the whole range. A lot is taken off from the list on the card.
A governing document is covenants or rules, dated from when it took effect, pointing at a document already on this project's register. Nothing is uploaded here. Dated after the current document of its type it becomes current; dated earlier it files as history and the current one stays.
Turnover is recorded one stage at a time, with the date it happened and a note. Clearing the date records the stage as not yet, which is also how a stage recorded in error, or reversed, is taken back: turnover moves both ways, the way the billing stage does, because a turnover a court unwound is as real an event as the one that recorded it.
Remove takes off an association with nothing on record. One with a member lot, a governing document, a turnover stage, a maintenance area or a sub-association is kept, not removed.
Who can
- Documents at view or better: anyone who can read documents.
- Documents at edit or better: anyone who can upload and file documents.
How to
You open this when a lot's association standing or a turnover stage has to be checked or recorded.
- Switch project carries this deal. Associations is a project page: All projects has no version of it.
- One card per association, master before its subs. Membership is exactly what is recorded, so a lot in a sub and its master counts in both.
- Turnover happens in stages, sometimes years apart. Completed and pending are both listed, and neither is inferred from the other.
- The current covenants and rules are the latest effective document not after today, read off this project's document register.
- Add an association opens its form. Each card's Edit opens membership by lot range or phase, a governing document, and every turnover stage with its date.
- What an association standing requires is a surface on the obligations register, so the gates are read there rather than on this card.
Related pages
Known limits
A turnover stage records the date and the note, not who recorded it or when the row itself changed. Maintenance areas are read here and not written.
