Date: September 9, 2026

Topic: Site operations — new site setup, meeting communications, and the client experience from intake through preparation

Session Overview

• Open-floor “what’s on your mind” discussion, followed by a planned agenda item on site operations — how taxpayers move from intake through return preparation, and what resources preparers rely on along the way.
• Roughly a dozen participants spoke during the discussion; more may have attended without speaking.
• Notes are generated with AI assistance and anonymized before publishing — participant names and identifying program details are left out below. Organizations, software, and public resources mentioned by name are kept in for reference.

New Site Setup & the eFIN/SIDN Process

• A participant opening a new site asked what’s needed beyond the e-Services application. General guidance: submit the e-Services form, then follow up with your relationship manager, who can help assign an SIDN (Site Identification Number) — multiple participants noted the SIDN typically needs to come first, since it becomes part of the site name used when applying for an eFIN.
• Researched after the meeting (not part of the live discussion) to verify the guidance above — per IRS Publication 5683 (VITA/TCE Handbook for Partners and Site Coordinators), the official new-site sequence is:
• Request an SIDN from your local SPEC territory office.
• Once assigned, register a Responsible Official and apply for an EFIN through e-Services (at least two Responsible Officials are recommended, since only they can manage the online EFIN application).
• Complete Form 13533 (Partner Sponsor Agreement) — due by October.
• Complete Form 13715 (Site Information Sheet).
• Submit Form 15272 (Security Plan) to the local SPEC territory office — due by December 31.
• One participant’s program described periodically cleaning up its eFIN roster — renaming and consolidating years of acquired or inherited eFINs (including a couple owned by outside partners, who added the program as a secondary/backup contact) so at least two people have access to each one.
• A separate reminder surfaced from a recent spec call: eFINs may need to be restored or re-obtained through e-Services. Poor call audio made details hard to follow, and no one on this call had first-hand experience with the process yet.

Meeting Logistics: Reminders, Agendas & Zoom

• The facilitator is now posting meeting notes and agendas on VITAQuality.org and letting Zoom’s built-in registration/reminder system handle notifications, partly to avoid over-emailing people on the list who may not attend.
• Feedback was mixed: one participant received three unexpected email reminders covering all of September (traced to an email-list update rather than a new Zoom setting); a couple of others said calendar visibility alone is sufficient for them. A separate friction point: some registrants have to re-register to join a specific occurrence even though the series is already on their calendar.
• The facilitator is looking into Zoom’s agenda-posting feature and what happens to notifications when an agenda is updated on a recurring meeting, to decide whether to add automation or keep relying on VITAQuality.org for notes and agendas.

Vitacon — Travel & Lodging

• The facilitator is presenting at a Vitacon breakout session and asked who else is attending and where people are staying, since no hotel block or list appears to have been provided by organizers this year. A few participants shared their own hotel choices, but no shared block or discount was identified.
• Participants noted lingering interest in extending the conference to a day and a half or two days (no updates yet), and that many programs had to choose between Vitacon and Raise Texas this year given the scheduling overlap.

Site Operations: Intake, Prep & Handoff

• Main discussion question: how does a taxpayer get from check-in to a preparer, and does that process look the same across every site a program runs? Responses varied heavily by physical space — one program’s flow depends entirely on room layout, with an open gym setting working differently than a site split across a library or community center with a separate prep and waiting area.
• Another program described a multi-step model: clients sign in and receive intake paperwork (with varying levels of help filling it out); an experienced volunteer does a quick pre-review of documents; the preparer works directly with the client, and the reviewer joins mid-session as on-the-job training rather than as a separate step. Because computers aren’t always attached to a printer, the reviewer often steps away to print, and exit/signature steps happen at that point — a few sites have a dedicated exit station for a “second mini-review.”
• One site used to run efficiently across two large rooms but was moved into several smaller rooms with no waiting space; preparers now gather in an office area and clients are seated while preparers come to them — workable, but inefficient and harder to catch struggling new volunteers.
• General agreement that a lot depends on physical layout, making it hard to build one shared process across programs. There was also discussion of whether taxpayers prefer being personally escorted to a preparer versus volunteers calling names from a list, though no one was certain what clients actually prefer.
• On training: newer preparers are walked through an introduction script (confirming whether it’s the client’s first visit, explaining a second reviewer will check behind them), modeled by experienced volunteers. One gap identified: not setting client expectations well enough about how long the process will take. One program avoids the word “drop-off” in client communication — calling it an “appointment for your intake interview” instead — since clients otherwise expect to drop off and leave quickly.

Getting Preparers’ Questions Answered

• The facilitator asked what happens when a new preparer hits a question mid-return, and what escalation paths exist. Approaches described: a physical “cup on the monitor” signal system used historically; Discord, used by one small program; and, most commonly, just raising a hand or flagging a reviewer directly, without a strict handoff process. One program is discussing an internal Slack- or email-list-style option for off-site volunteers, but is weighing the login burden against keeping client PII out of the channel.
• One participant described piloting an IRS-built AI assistant a couple of seasons ago — trained only on IRS-approved references, with results linking back to source documents — which reportedly worked well but was discontinued, said to be tied to a budget-related IRS funding disruption. A college was separately mentioned as building something similar for its own student volunteers, and another participant is connected to a Treasury team exploring technology support for VITA programs.
• Common thread: even where a documented resource exists, volunteers’ default behavior is still to just ask someone in the room.

Reference Resources: The 4012 & Program Wikis

• Frustration was shared about volunteers not consistently using IRS Publication 4012, despite training efforts (desktop links, paper copies, teaching Ctrl+F search, modeling its use). One participant raised a structural issue: the 4012 has absorbed clarifications that arguably belong in the 1040 instructions or Pub 17, prior-year versions can carry errors, and pandemic-era changes were inconsistently rolled into the 4491X update process.
• One larger program maintains its own internal wiki (built in Notion, after WordPress and Squarespace proved too hard to manage single-handedly) covering topics the 4012 handles poorly — e.g., HSAs, retirement-account detail — plus operational how-to content for site managers. It’s maintained year-round by a small internal team, updated in the off-season, and expanded from questions logged in the program’s Slack channel during the season. Editing access is limited to a couple of people; the wiki itself is public aside from anything kept on internal SharePoint.
• Notion was praised for letting pages nest arbitrarily deep with inline links, and for how easily a linked file can be swapped without breaking existing links (a nonprofit called Get Your Refund reportedly runs a similar setup). Another participant’s program, currently building a separate Google Sites resource, expressed interest in modeling their wiki after what was shared and asked to connect after the call.
• Open question, not resolved: whether a shared, national VITA wiki would be valuable versus impractical, given how much programs’ training differs and unclear ownership over keeping shared content accurate. A related thread touched on the tension between programs investing unpaid time in training materials and wanting compensation if shared — general sentiment favored keeping materials open/public domain over monetizing them.

State & Local Tax Complexity

• Several participants described state and local returns as disproportionately time-consuming relative to federal, especially where municipality-level taxes aren’t well supported in TaxSlayer’s professional interface. One workaround: for out-of-expertise state/local situations, some programs sit the client down with a volunteer to start the return on MyFreeTaxes.com (the public self-file version), since it prompts for more state detail than the professional software, then have a volunteer review before submission.
• Programs are also spending meaningful time on work beyond the return itself — taxpayer education for non-filers, and helping clients create ID.me and payroll-portal logins — enough that one program is considering a social-work-adjacent hire and a QR-code system to track this unbilled support work per shift.
• A comparison of well-regarded larger urban programs came up, including ones running a combined-staff summer model with joint clinics involving the IRS, state agencies, and Low-Income Taxpayer Clinics; participants speculated informally that operating in a state without its own income tax may help some of those programs scale.

ID.me Verification Tips

• General consensus that clients prefer avoiding ID.me’s video-verification step when possible, and that wait times for the video-assisted path vary widely (a few minutes to much longer during peak season).
• Tips shared: starting on a volunteer’s laptop (for its camera) and sending photo capture to the client’s phone works for some; others found it more reliable to run the whole process on the client’s own device, since clients already know their own login details. A phone flashlight held above the client can help with poor lighting.
• One participant flagged a broader gap: volunteers don’t consistently ask clients where they’re storing new account passwords (relevant beyond taxes, since ID.me also unlocks Social Security and other federal accounts) — suggested building that check into the process, along with having clients finish account setup independently in the waiting area.

AARP Foundation Tax-Aide Collaboration

• Participants discussed a recurring gap between AARP’s supportive national messaging on VITA/Tax-Aide collaboration and a more mixed local reality, attributed to volunteer-driven state leadership and copyrighted training materials.
• Where collaboration does happen locally it was described positively — one state’s Tax-Aide network stepped in during a VITA program disruption and has since built a well-regarded joint approach. Formally joining the Tax-Aide network can bring added resources but trades off VITA’s paid-staff grant funding for Tax-Aide’s all-volunteer, 60-and-older-focused model (which draws on both TCE and VITA funding).
• No action items — flagged as a good discussion, worth revisiting if the facilitator follows up with regional AARP contacts.

Looking Ahead: Quality Review

• The facilitator framed the day around one core question: once a program identifies the resources preparers need, is the right delivery mechanism electronic, print, or some mix — likely a mix, with quick-reference material close at hand and deeper documentation for less common issues.
• A session on volunteer-management software is still being planned but not yet scheduled, pending input from at least one other program.
• Next session: site operations at the point of quality review — support for reviewers, and how the process looks and feels from the taxpayer’s side.