"All our survey operations live in one person's account, and we can't hand it off if they leave." "Different departments are building near-identical forms over and over." These are common organizational survey problems.
This article covers the team-operations best practices for running surveys efficiently across an org.
Three problems with individual operation
Problem 1: Tribal knowledge
Forms living in individual accounts make handoff impossible when that person leaves or rotates out. Their successor can't even see prior data.
Problem 2: Duplicate work
Marketing, Sales, Support each build similar surveys independently. Best practices don't propagate, question quality is uneven.
Problem 3: No governance
No visibility into who runs which surveys or how data is stored. Information security and compliance risks compound.
The organizational account model
Organization
The company-wide unit. Billing and global admin attach here.
Members
Individual users within the org. Roles (Admin / Member) separate permissions.
Folders
Departments and projects group forms.
Forms / Reports
Individual deliverables inside folders.
Repoan's team features
Repoan's Pro plan includes team functionality.
Creating an org
1. Account settings → Organization
2. Create org → name and industry
3. Invite members by email
Permissions
- Admin — global management, billing
- Member — create / edit forms
Folder-level permissions are on the roadmap.
Billing unit
Billed at the org level — every member gets Pro features.
Folder best practices
Per-department folders
📁 Marketing
├─ Webinar surveys (monthly)
├─ Newsletter signup form
└─ Asset request form
📁 Sales
├─ Post-meeting survey
├─ Lost-deal interview
└─ Existing-customer satisfaction
📁 People Ops
├─ Interview feedback
├─ Exit interview
└─ Engagement survey (quarterly)
Per-project folders
For time-bound campaigns or specific research projects:
📁 Spring 2026 Campaign
├─ Pre-launch awareness
├─ Mid-campaign satisfaction
└─ Post-campaign measurement
Templates folder
A single place for master templates the whole org reuses:
📁 Shared templates
├─ Standard NPS survey
├─ Standard CSAT survey
└─ Standard seminar survey
Guest access
When external partners (clients, agencies, contractors) need limited visibility:
What guest access does
- Grant limited access to a specific form or report
- Password protection / time-limited URLs
- Permissions tunable: view-only, comment, etc.
Use cases
- Co-marketing with an agency — share the report with the agency
- Client reporting — distribute results via link
- Outsourced operations — partner builds the form, data viewing internal-only
Team operating rules
Rule 1: Naming convention
[Dept]_[Purpose]_[Date]
e.g., MKT_Webinar Survey_2026-05
Massive lift in searchability.
Rule 2: Share master templates
Frequent surveys like NPS should exist as org-shared templates that get copied. No re-building from scratch each time.
Rule 3: Archive policy
Define when to delete or move old forms:
- 3 months after close: move to "archive" folder
- 1 year: archive and exclude from search
- 3 years: data deletion (privacy)
Rule 4: Monthly operations review
Once a month, review all running org surveys:
- Any duplicates?
- Any with zero impact?
- Any questions due for improvement?
Standardizing quality
AI question check
Ask Repoan's AI to "review this question set" and it surfaces:
- Leading questions
- Double-barreled questions
- Biased options
- Unnecessarily heavy items
An effective way to standardize quality org-wide.
Master template approach
Veterans build "the org-standard survey" as a template; new joiners and other departments copy and lightly customize.
Customizing Repoan's templates and saving as org templates eliminates from-scratch rebuilds.
Governance
State retention periods
Define data retention up front: "retention period: 3 months" — with an auto-delete mechanism.
Personal data handling
"Surveys collecting emails must include a privacy notice." Enforce as org policy.
Access logs
Audit logs of "who viewed what when" for compliance.
Failure modes
❌ Everyone is Admin
People-ops surveys shouldn't be accessible to sales. Least privilege.
❌ No folder structure
Over time, orphaned forms with unknown owners accumulate.
❌ No naming convention
"Survey 1," "Copy (2)" — unsearchable in 6 months.
❌ No review
"Just ran a survey" becomes the default — quality decays.
Summary
Team operations best practices:
- Team feature ends tribal knowledge
- Folders + naming for organization
- Master templates for quality
- Guest access for external sharing
- Monthly review for operating discipline
Repoan's team feature (Pro) handles member invites, folders, guest access, and report sharing. Billing at the org level means every member has full access to AI question generation, AI report analysis, calendar integration, and the rest.