A form can collect answers, but a questionnaire program must preserve the decisions around those answers. Questions are reused and refined, different audiences receive different campaigns, access and identity rules matter, and results only make sense when the definition and eligible population remain visible. RhoQuestionnaire begins with a private question pool. Teams manage reusable questions, answer controls, hierarchy, dependencies, terms, language, and visual choices once, then compose them into questionnaires and focused surveys. A change improves every draft that uses the question, while an active sending keeps its immutable snapshot. The same governance continues into delivery. Recipients, categories, mailing lists, imports, and custom fields define the audience; email, SMS, recipient account, public link, QR, embed, and automated triggers activate prepared sendings through the same capacity and access rules. Each visit, reminder, staff-completion path, and response remains attached to the campaign that authorized it. Completion is a workflow rather than a submit button. Secure invitations, context-bound access, autosaved drafts, terms gates, conditional questions, multilingual system text, shared review, required-answer checks, and locked submissions give participants a clear journey without weakening the administrator's evidence trail. Analytics can then compare one sending or every repeated sending of a questionnaire without pretending every question was eligible everywhere. Hierarchy paths, hidden-state evidence, eligible and unanswered denominators, numeric and choice summaries, saved research definitions, exports, and anonymous-result suppression preserve meaning from collection through decision-making. That is the difference between publishing a form and operating a questionnaire program: the questions, participants, delivery, history, and analysis remain connected long after the first link is sent.