Why does your society voting need an audit trail?
An audit trail is an append-only record of every vote, admin action, and status change in your society's voting process. When a levy, by-law change, or committee decision is challenged — by a member, the registrar, or a court — the audit trail is what proves the process was fair, quorate, and correctly counted.
What co-op bye-laws expect
Most Indian cooperative housing society bye-laws require:
- Quorum at general body meetings and votes
- Secret ballot for elections and sensitive resolutions
- Minutes and records retained for inspection
- One vote per member (flat) unless weighted shares apply
Digital voting on Plinth produces records that map directly to these requirements.
What Plinth logs automatically
- Poll creation, edits, publish, and close events
- Every vote cast (timestamp and flat, not the choice if secret)
- Claim approvals and rejections
- Credential upload, review, and purge events
- Result computation and export
Nothing in the audit log can be edited or deleted.
Dispute scenarios the audit trail resolves
"I never voted on the levy." — Show the flat's vote receipt and audit timestamp. "Quorum wasn't met." — Show eligible flats vs votes cast with the configured threshold. "The result was changed after close." — Audit log proves results were computed once, server-side. "Non-owners voted." — Every ballot tied to an approved flat claim.
Credential handling for compliance
When polls require ownership proof, documents are stored in a private bucket, accessed only via short-lived signed URLs, and auto-purged 30 days after the poll closes — balancing verification needs with privacy.
Protect your committee. Set up audit-ready voting on Plinth.