Research and Communications Support

Research and communications can look low risk because the output is only a draft. A draft can still create harm: it may misstate a service, expose a personal story, repeat a false statistic, promise a result, or present an imagined partnership as fact.

This guide treats the work as an editorial support role. The volunteer may gather and organize evidence, but the organization's editor or authorized lead owns publication. Line ownership matters when a public statement reaches people who make decisions based on it.

Realistic duties

A defined project may involve:

• Clarifying the audience, question, scope, and prohibited claims.
• Searching approved public sources for current information.
• Recording citation title, publisher, date, and the exact passage used.
• Comparing sources and labeling conflicts or uncertainty.
• Drafting a plain-language summary or caption from verified material.
• Preparing an accessible document structure and checking links.
• Submitting the draft for human review and correction.

The role should not include invented interviews, unauthorized quotations, hidden advocacy, or publication without approval. Fundraising messages, medical claims, legal interpretation, and community representation need additional review.

Suitability and access

This activity may suit someone who is curious, skeptical, well organized, and comfortable marking a claim unresolved. It can be remote and self-paced, but deadlines and revisions still create load. It may not fit a person who wants creative freedom beyond the evidence or feels criticized by edits.

Check the full working setup:

• Can you read long documents comfortably on the available screen?
• Are screen reader, caption, dictation, keyboard, or magnification tools available?
• Is audio or video source material captioned and transcribed?
• Can deadlines be divided into smaller milestones?
• Are files provided in accessible formats?
• Is there a quiet space for interview or review calls?
• Can you use an organization account for approved AI features?

Research is not automatically accessible because it is desk work. Reading dense PDFs, scanning charts, and checking file formats can require substantial visual and cognitive effort.

Training and supervised practice

Ask for orientation to the organization's mission, style guide, source standard, privacy and consent rules, accessibility requirements, and correction process. Practice on a fictional public claim that has two sources with different dates. The reviewer should see whether the volunteer separates fact, inference, and recommendation.

Training should also explain how to describe uncertainty. "The organization says" is different from an independently verified fact. "A local report found" needs a date, population, and link. A quote needs an exact source and permission when required.

Screening questions for the organization

1. What decision or audience will this communication support?
2. Who is the editor, fact-checker, and final approver?
3. Which sources are acceptable, and how current must they be?
4. What claims, topics, or words are prohibited?
5. May the volunteer contact sources or participants, and under what script?
6. What consent and permission are required for quotations and images?
7. Which style, accessibility, and file-format standards apply?
8. What systems may hold drafts, source notes, and personal information?
9. May any AI tool be used, and with what data and disclosure rules?
10. How are corrections, complaints, and takedown requests handled?
11. What is the milestone and review schedule?
12. How will the trial end and ownership of files transfer?

Ask for the approval workflow in writing. A general permission to "write something" is not a scope.

Activity safeguards

Keep a source trail for every factual claim. Use direct links where stable and record access dates. Do not cite a search snippet as if it were the full source. If a source cannot be opened or verified, remove the claim or mark it unresolved.

Do not invent a partnership, sponsor, participant voice, outcome, or urgency. Do not use a person's story, photograph, or organization logo without the required permission. Separate an organization's view from independent evidence.

Protect unpublished drafts and source notes. Use approved storage rather than personal email or unapproved AI. If a mistake is published, report it promptly and follow the correction process. Do not quietly rewrite the meaning of an earlier statement.

Accessibility

Accessible communication starts before final formatting. Use descriptive headings, meaningful link text, alt text for informative images, captions and transcripts for audio or video, and sufficient contrast. Avoid image-only text when the same information can be provided as text.

Plain language does not mean removing necessary uncertainty. Explain technical terms, keep sentences manageable, and provide the detailed source route for readers who need it. Test keyboard navigation and screen-reader order in the final format when the system allows.

Limited AI use

AI may suggest an outline, identify inconsistent phrasing in a public draft, or create a synthetic example for practice. Every factual claim, quotation, statistic, link, date, image description, and permission must be checked by a human.

Do not place confidential drafts, identifiable interviews, unpublished community information, or restricted source material in an unapproved AI service. AI cannot approve a public claim, decide whether a person's story is safe to publish, or take responsibility for a correction.

Sample outreach

Subject: Volunteer editorial-support project

Hello [organization name],

I am interested in a bounded research or communications project for one approved public resource. Could you share the audience, source standard, review workflow, style and accessibility requirements, and the person who approves publication?

I can prepare a source log, draft, and verification notes for an editorial review. I would like to understand the policy for confidential materials and any permitted AI use before starting.

Thank you, [name]

This is illustrative. Send it through the organization's published volunteer channel and do not attach confidential material.

30-Day trial plan

• Days 1 to 3: Review the brief, style, source, privacy, accessibility, and approval rules.
• Days 4 to 6: Complete a small fictional source comparison and get feedback.
• Day 7: Confirm the project question, audience, milestones, editor, and file location.
• Days 8 to 14: Build a source log and draft only the approved section.
• Days 15 to 21: Submit for fact-check. Correct errors and record unanswered claims.
• Days 22 to 27: Prepare the accessible version and complete a second review.
• Days 28 to 30: Review approvals, corrections, time, learning, and ownership. Decide whether to continue, narrow the role, or exit.

Exit criteria

Do not publish if sources are missing, permissions are unclear, an editor cannot be named, or a claim would require professional legal, medical, or financial judgment outside the project. Stop if you are asked to invent an endorsement, conceal a conflict, or present a partnership that does not exist.

Exit at review if deadlines cannot be met, review feedback is unsafe or disrespectful, or the project keeps expanding without scope. Transfer final files and source logs to the approved owner, remove personal working copies, and document unresolved claims without publishing them.

Decision worksheet

Record the audience, public question, approved sources, prohibited claims, editor, milestones, review dates, accessibility requirements, file storage, and AI policy. During the trial, track verified claims, unresolved claims, corrections, review cycles, permissions, and completed accessible checks.

The useful measure is not word count. It is whether the approved output is accurate, attributable, accessible, and honestly limited.