Creig Phiri

Govora

Participant information and consent management for Canadian youth-serving nonprofits and community organizations. A live BTS product and an example of my systems implementation work.

The problem and my motivation

Youth-serving teams need to keep participant information, programs, contacts and consent organized as staff and responsibilities change. Govora brings those operational records into one system.

My Kidoodle.TV work and commitment to children’s online safety inform my motivation for pursuing Govora.

My contribution and team delivery

I implemented reuse of a staff consent-warning acknowledgement for the same user, organization, participant and consent revision, with a fixed ten-minute expiry. A consent change invalidates that acknowledgement; acknowledging the warning does not grant consent. I also contributed authenticated issue reporting with administrator-only review, persistence and integration tests.

I also bring technical systems leadership and backend and cloud engineering experience to the product. Govora is delivered by BTS with shared product and engineering responsibilities; these contributions are part of that wider work.

Implemented capabilities

Govora brings together programs and cohorts, participant and contact records, attachments, daily records and consent workflows. The implementation includes versioned consent forms, requests and status summaries, organization-scoped roles, audit events and retention workflows.

Approach, trade-offs and safeguards

The architecture combines a Vue frontend, FastAPI services, PostgreSQL and AWS infrastructure. Important engineering boundaries include organization scope, role-based permissions and preserving which form version a consent record refers to.

Versioned forms favor traceability over silent updates: a new published version should not automatically replace a cohort’s existing requirement. That makes changes more deliberate and creates an explicit adoption step for the organization.

Keeping workflow awareness distinct from authorization matters. A staff member acknowledging a consent warning must not be confused with a participant or contact granting consent. Technical checks also do not determine legal guardianship or establish compliance.

Maturity and supported results

Govora is a live BTS product for participant information and consent management. Reporting, integrations and workflow changes may require separately scoped work.

Software supports an organization’s governance responsibilities; it does not establish legal compliance or determine guardianship. Govora does not offer compliance certification or a guarantee that every copy of data has been removed.

contact.sh

Bring the problem.
Let’s talk implementation.

For practical AI and software implementation, contact Boring Tech Solutions with your workflow, constraints and what you need to demonstrate.

Contact Boring Tech Solutions