Plan a recorder setup

Decide who you want to hear from before you write anything else. A recorder aimed at existing listeners, customers, members, or event attendees will need different language and a different question.

Be specific enough that someone on your team could recognise the intended submitter immediately. "People interested in our work" is too broad, while "parents who attended our Saturday workshop" gives you a clear starting point.

Success looks like a short audience definition your team can repeat consistently in outreach, review, and reporting.

Pick one clear question or topic you want people to answer in their own voice. A single useful question usually produces stronger recordings than several loosely related asks.

Keep the question narrow enough that people know where to start. If you are unsure what to ask, choose the one answer that would be most useful to publish, review, or learn from first.

Success looks like a question your team can read aloud in one breath without needing extra explanation.

Write the words you will use to invite people to record. The invitation should explain who you want to hear from, what you are asking, and why their response matters.

Aim for language that sounds human and direct. If the invitation feels long, formal, or vague, people are more likely to stop before they record.

Include the basic expectation up front, such as the topic, the kind of response you want, and whether the recording is part of a campaign, story, or community project.

Success looks like invitation text that a new reader can understand quickly without asking follow-up questions.

Decide how the recorder should look and feel to your audience. The recorder is branded to your organisation, so the visual setup should match the context in which people discover it.

Use branding that helps people recognise they are in the right place. Consistency matters here, especially if you are sharing the recorder from your website, newsletter, or social channels.

Dafado and Magyar Minute are current recorder users. Their use shows that different organisations can adapt the recorder to their own audience and identity.

Success looks like a recorder experience that feels clearly connected to your organisation before someone starts recording.

Decide what submitters need to agree to when they record. Consent language should be clear enough that people understand what they are allowing and what happens after they submit.

Keep the wording plain and specific. If your team expects to review, edit, store, or potentially use recordings later, make sure the language reflects that accurately.

Success looks like consent language your team is comfortable standing behind and your submitters can understand without legal interpretation.

Decide who reviews submissions, how often they check the inbox, and what happens after review. This is where you prevent delays and confusion once responses start arriving.

Assign at least one clear reviewer before you go live. If more than one person is involved, agree on how you will flag, discuss, or hold submissions for later use.

Submissions arrive in a private Voice inbox, and no submission becomes public automatically. Your review workflow stays private to your team.

Success looks like a named reviewer and a simple internal process your team can follow from the first submission onward.

Decide what you want to learn or produce from the submissions. Some teams want story leads, some want audience insight, and some want recordings they may use later after review.

Reporting goals help you judge whether the recorder is working. They also make it easier to decide what to track, what counts as a useful submission, and when to adjust your invitation or question.

Success looks like a small set of outcomes your team can review after launch, such as submission volume, relevance, recurring themes, or production opportunities.