Volunteer, share an idea, or ask Ethan a question. He is building a movement and developing proposals, and your perspective can help shape the work.
Your information is used to respond to this request. Asking for updates does not automatically enroll you in a mailing list. Please do not include sensitive personal information.
PRACTICAL WAYS TO TAKE PART
Choose a manageable task, share a concrete concern, or propose a focused conversation. Select a topic to read the guide. Each explains what to send and what to agree before acting on the campaign’s behalf.
Choose one bounded task that fits your skill and availability. A one-time contribution is welcome; no unlimited or long-term commitment is needed. Describe the output and a realistic deadline so its usefulness can be agreed before you begin.
Possible starting points include research on one Real Deal proposal, an edit to one confusing passage, an accessibility check, or a topic and suitable place for a local conversation. Use the output guides below for the details to include rather than attempting every kind of contribution at once.
For a one-time offer, begin your message with “Volunteer — one task.” For recurring help, describe an approximate weekly commitment and any dates when you are unavailable. These are examples of offers, not advertised vacancies or guaranteed assignments.
Before work begins, agree on the task, its purpose, the person handling questions, the expected output, and the deadline. A research note, corrected paragraph, accessible graphic, or event checklist is more useful than an open-ended instruction to “help with the campaign.”
Agree on a reviewable format. For editing, identify the page and show the exact passage and proposed change. For design, use materials you have permission to use, with readable text and alternative text where appropriate. The research and website-report guides below specify their evidence requirements.
Submitting work does not automatically make it approved campaign material. Publication, credit, permissions, and any later revisions should be discussed before the work is distributed. Do not send passwords, account access, private contact lists, or confidential employer documents through the contact form.
Start by asking which issue matters most to the person or group: housing, healthcare, work, education, or another concern. Listen for the practical problem before offering the campaign’s response. People do not need to support Ethan or agree with the platform to describe a problem worth understanding.
Use the current website to explain a stated position. If an amount, date, eligibility rule, or funding detail is still unresolved, say so. Do not invent an answer, promise access to a benefit, or present a proposal as an enacted program. Bring unanswered questions back through the form with a link to the relevant section.
Respect a person’s decision not to continue. Ask before taking photographs, recording a conversation, quoting someone publicly, or passing along their contact details. A general description of a local issue is enough; the campaign does not need private medical histories or financial records to begin discussing it.
A useful event suggestion begins with a purpose: a listening session about rent burdens, a student discussion of the platform, a healthcare conversation, or a general question-and-answer meeting. Give a city or general area, the intended audience, and a realistic format. A small focused conversation can be useful without claiming a large turnout.
Include possible dates and time zones, expected duration, proposed venue or online platform, accessibility needs, approximate attendance, and whether media or recording would be involved. Explain who would handle invitations, venue permission, setup, welcoming participants, moderation, and cleanup. Identify any costs before making commitments.
Do not reserve a venue, spend money on the campaign’s behalf, announce Ethan’s attendance, or describe an organization as a partner without explicit agreement. An invitation starts a discussion. Confirmed events belong on the Events page after the necessary arrangements have been agreed.
You can support a proposal, oppose it, or suggest a different approach. Identify the exact section of The Real Deal and explain the practical question. A useful submission might ask how a healthcare transition protects ongoing treatment, how rent protections interact with repairs, or how a wage change would affect a small employer.
For a proposed improvement, describe the problem, the people affected, the change you recommend, the agency or level of government that could act, and a way to judge the result. Include public evidence and distinguish known facts from assumptions. If costs are uncertain, explain what would need to be estimated rather than supply an unsupported number.
Corrections should quote the wording and provide a reliable public source where available. Disagreement alone is not a factual correction, but both are welcome forms of feedback. For a personal example, share only what you are comfortable sending and leave other people unnamed unless you have permission.
First, send a focused message through the existing form. Choose “Volunteer” for an offer of help. For an invitation, interview request, question, or correction, choose “Share an idea or ask a question” and identify the purpose in the first line. The form does not include a separate subject field, so put a short heading at the start of your message.
If the conversation moves forward, agree on scope, availability, delivery format, and the next check-in. Start with a manageable task where practical. If circumstances change, say so rather than taking on a commitment you cannot keep. Work that involves public appearances, spending, other people’s information, or account access needs separate agreement.
There is no guaranteed response time, automatic assignment, or confirmed role when a form is sent. The visible submission confirmation shows that the website accepted the message; it does not confirm a booking or policy decision. Do not submit private records while waiting for a reply.
Volunteer: “I can help with [specific task], remotely or in [general area]. I can offer [rough amount of time] and deliver [output] by [suggested date]. Please let me know whether this would be useful before I begin.”
Policy question or correction: “On [page link], the section [heading or short quotation] raises this question: [specific issue]. My suggested change is [suggestion], supported by [public source].” Event or media request: “I am contacting you for [organization or outlet] about [purpose]. Proposed dates, time zone, format, audience, deadline, and recording arrangements are [details].”
Keep the message relevant and include an email address you can check. Do not put identification numbers, payment information, medical documents, passwords, or other people’s private details in the message. Requests for updates remain requests; the form does not automatically enroll you in a mailing list.
For a small contribution, agree on an output before starting: one sourced policy question, one reproducible website issue, or one event outline. Time estimates are only planning estimates; availability does not create an assignment.
Download a task handoff template (TXT)
PROPOSED VOLUNTEER TASK / HANDOFF
Task title:
Purpose:
Agreed output and length:
Estimated time / availability:
Scope agreed with:
Sources and dates:
Completed work:
Unresolved question:
Next step and responsible person (if agreed):
Permission to publish any contribution:
Do not include private records or other people’s contact details. This template is an offer of help, not an approved role.
ILLUSTRATIVE VOLUNTEER HANDOFF — NOT A CURRENT WEBSITE BUG OR APPROVED ROLE
Task title: Check one public page’s keyboard navigation.
Purpose: Offer a small, reproducible accessibility review.
Proposed output: A one-page note covering one URL, the browser and viewport used, steps attempted, expected behavior, and observed behavior.
Estimated time: About 30–45 minutes for an initial check; an estimate, not an assigned commitment.
Scope agreement: Confirm that the review would be useful before representing it as campaign work. No account access, spending, form submissions, or changes to the website are included.
FICTIONAL FINISHED NOTE
Page reviewed: [the agreed public URL]
Test: Use Tab to reach a link, then Enter to activate it.
Expected: Focus is visible and the destination opens.
Observed in this fictional example: Focus was difficult to distinguish against the background.
Evidence to include in a real note: The exact link label, browser/version, viewport, numbered steps, and a screenshot without personal information.
Unresolved question: Does the same behavior occur in another browser or at a different viewport?
Suggested next step: Ask the page maintainer to reproduce it. Do not describe a suggested fix as tested or approved.
COMPLETION CHECKLIST
Keep the note to the agreed scope. Distinguish what you observed from what you suspect. Include enough detail for another person to repeat the check. Remove personal data and credentials. State whether the campaign may reuse your contribution and identify any third-party material requiring permission.
HOW TO OFFER IT
In the participation form, choose Volunteer and describe the proposed output, relevant skill, and availability. Agree scope and any follow-up before beginning work on the campaign’s behalf. A submitted offer does not create a role or promise a response time.
These are possible contributions to propose through the existing form, not confirmed assignments. Choose the output that fits your skills; agree scope and review before doing work on the campaign’s behalf.
Choose a narrow claim and collect two relevant public sources. Note who produced each, when it was published, what population or program it covers, and what it cannot establish. Explain whether a difference comes from a real disagreement or from definitions, geography, or time periods.
A useful finished note ends with the decision the evidence could inform and the uncertainty that remains. Avoid a large attachment dump or a summary that treats every source as equally authoritative. Link the originals so the reviewer can inspect the reasoning.
Select a passage that a new reader might struggle to understand. Provide the current wording, your proposed explanation, and a short note showing that the meaning is preserved. Keep conditions about eligibility, funding, authority, and timing when they affect the promise.
Test the explanation against a simple question: could someone reasonably mistake it for an existing benefit, a guaranteed outcome, or an approved application? If so, revise it. A plain-language draft is an editing suggestion, not authority to change campaign policy.
Pick a realistic task, such as finding the healthcare proposal from a campaign tab or locating a downloadable resource. Record the starting URL, steps, device and browser, and where the path succeeds or fails. A screenshot can help if it contains no private information.
Separate a broken link, a confusing label, and a preference about appearance. Give a reproducible issue and expected result rather than proposing a redesign when a small correction would solve it. Do not submit test messages, alter accounts, or change pages as part of an unagreed review.
State the language or access skill you can contribute and the specific public passage you want to review. Preserve policy qualifications and flag any wording that has no clear equivalent rather than quietly substituting a different promise.
Agree how specialist terms, proofreading, credit, and publication would be handled before presenting the work as an official translation. An informal volunteer draft is not a certified interpretation or proof that a service is available in that language.
A local note could identify a public service, its published access instructions, the obstacle people report, and the authority responsible. Use public documents and anonymized descriptions instead of collecting case files, tenant records, or medical details.
Distinguish what you observed from what someone told you and from what you infer. End with one question the campaign can examine, such as which level of government controls a delay. The campaign form is not a government service request or a route for resolving an individual emergency.
Provide a short cover note with the purpose, completed output, source list, unresolved issue, and requested review. Label draft versions clearly so an earlier copy is not mistaken for the final submission. Mention any reuse permissions or restrictions that matter.
If you need to stop, explain what is finished and what remains; do not promise a replacement volunteer. A handoff should reduce another person’s work without implying that the contribution has already been approved, published, or assigned for continuing maintenance.
A short, organized contribution is easier to assess than a large unsorted collection of links. These examples are possible outputs to offer, not approved assignments or confirmed volunteer roles.
Choose one question, such as a housing bottleneck or a healthcare access problem. State it at the top, then provide three strong public sources with dates and a short explanation of what each supports. Distinguish direct quotations from your interpretation and identify uncertainty. State whether the evidence concerns your city, a region, or the country; a local example does not prove a national result.
Finish with two or three decisions the research could inform. Separate your suggested answer from the source’s actual findings. Ask whether the brief would be useful before taking on a large project.
Describe the page, device or browser, the action you attempted, what happened, and what you expected. If the issue concerns wording, quote the smallest passage that demonstrates it. If it concerns layout, identify the screen size or orientation where it occurs.
Describe the difficulty rather than assuming its cause. A button that cannot be reached, unreadable text, missing captions, and a slow connection are different issues. Do not send screenshots containing private information.
Describe one issue in a general location, what people say is difficult, and any public information that helps explain the setting. Avoid naming private participants. Record disagreement and uncertainty instead of turning every concern into a consensus claim.
Explain the next question worth investigating. The note can inform a discussion without claiming the campaign has adopted a new position, selected a partner, or promised a local project.
Package an agreed task’s final output with its source links, unresolved questions, reuse permissions, and a brief revision note. Identify what changed and what still needs review. The downloadable handoff template above provides fields for this record.
Check that a reviewer can open the files and understand the result without reconstructing the work. Mark a draft as a draft; agree on publication or an official announcement separately.
This is an example of a manageable research or feedback task, not an assigned role. Ask whether the output would be useful before doing work on the campaign’s behalf.
If the question needs more research than that, say so. An incomplete but clearly bounded note is better than an answer presented with more certainty than its evidence supports.
Before reuse, compare the finished contribution with the agreed scope. Follow the output guide’s source and permission checks, and confirm that every remaining uncertainty is visible to the reviewer.
Record the reviewer’s requested changes and the next agreed step. Keep the draft or personal-submission label until publication is approved; submitting work does not create authority to represent Ethan.
Send your offer or question → · Browse the Supporter Toolkit →
