Decision log
Record each national and regional decision with a date and an owner so later teams can see why it was made.
Distributed regional campaign operations
Connect national strategy to regional execution.
Federal campaigns need disciplined coordination across offices, regions, teams, events, finance, forms, content, and public communications. Attain OS gives each layer a shared operating model.
Regional teamsAttain OS workflow
County routesAttain OS workflow
National eventsAttain OS workflow
Contribution emailsAttain OS workflow
Coordinate team work with tasks, forms shared by link, and HTML pages. Assign owners and review unfinished work before each campaign day.
See the shared campaign toolsWorking guide
For a federal campaign, the software has to connect national decisions with regional teams, offices and events without making every region rebuild the plan. The workable setup names one owner for each region, keeps the approved reference set in one place, and gives each regional lead a calendar and a stop list. Those ownership rules matter more than the number of tools.
Timeline
A regional calendar from national setup to debrief
- 12 to 10 weeks before launch
Set the national operating model
- Name a national lead and one lead for each state or region, each with a deputy.
- Decide which pages and documents regions copy from the national source and which they must use as written.
- Agree on naming for pages and events so regional teams can find each other's work.
- 8 to 6 weeks out
Publish the approved reference set
- Store approved talking points, policy explainers and asset guidelines in the Documents app.
- Put an owner and an approval date in the title or first line of every approved document.
- Brief regional leads on which materials they may adapt and which must stay unchanged.
- 6 to 4 weeks out
Open regional intake
- Publish one volunteer form with a region question, so every submission arrives with its area.
- Export submissions to CSV so each regional lead can review their own area.
- Publish the period in which each regional request will get an answer, and keep to it.
- 4 to 2 weeks out
Plan national and regional events
- Put national days of action and regional rallies on one calendar, each with a named host.
- Request each venue through a booking form and confirm the headcount before the event.
- Set regional event dates before any public announcement goes out.
- Event weeks and after
Run, review and report
- Give each regional lead a stop order in Routes before the day.
- Collect each debrief in one decision log entry, with an owner for every follow-up.
- Send compliance questions to each region's treasurer or counsel, since Attain OS does not provide compliance reporting.
Workflow map
Where national and regional work meets
| Job | App | What it does here |
|---|---|---|
| Coordinate regional leads | Tasks | Create one task for each regional lead, with the deputy named in the first checklist step and a label for each region. Use the assignee field so the owner is clear, and archive the task once the region's first phase is finished. A task tracks the work; it does not set the regional strategy. |
| Keep approved references | Documents | Store the national talking points, policy explainers and asset guidelines in Documents, with the owner and approval date in each title. Regions link to the source instead of retyping it. When national text changes, the owner tells each region which section moved and what to do next. |
| Collect regional volunteers | Forms | Use one volunteer form with a region question, so each submission carries its area into review. Submissions are stored and a scheduled job processes them hourly in production, notifying the form's creator. Regional leads then confirm roles and shifts with each volunteer through their own process. |
| Align regional events | Calendar | Put national days of action, regional rallies and local events on one calendar, each with a named host and location. Calendar invitations and RSVPs reach workspace members. Partners outside the workspace need their own invitation, and the event entry is the reference they should match. |
| Order regional stops | Routes | Set each county's stops in the order the regional lead chooses, then open the directions link for the team. Routes does not optimize that sequence, so a long regional day needs someone who checks timing and access before the team leaves. Keep the stop list as the agreed plan. |
| Record regional debriefs | Notes | Write each regional debrief in Notes with the date, the region and the decisions reached. Keep the discussion short, then move agreed decisions into a decision log page every region can read. Name an owner for each follow-up before the notes are closed. |
Start here
Reference pages and requests for regional teams
Internal wiki page
Give regional teams one page per process, with an owner and a last-checked date, instead of a single shared manual.
Partnership inquiry form
Screen organizations before national or regional teams make commitments on the campaign's behalf.
Venue booking request
Ask a venue for the date, times, headcount and room setup before a regional event is announced.
Shipping request form
Request courier pickup for printed materials moving between offices, with package counts and addresses.
Mistakes to avoid
Four ways a distributed campaign drifts apart
Letting regions edit the national source
When each region edits the national talking points, one message turns into many local versions. Keep a single source owned nationally, and let regions copy it into local pages with their changes marked. Without that rule, nobody can tell which wording is the approved one.
Sending every region every local detail
Regional leads need the national dates that touch them and their own events, not every detail from every state. Put national dates on one calendar, give each region its own event entries with a named host, and keep the shared timeline short. Otherwise conflicts appear on the day instead of weeks before.
Assuming a route plan is optimized
Routes keeps the stops in the order your regional lead chooses and opens a Google Maps directions link. It does not calculate a faster order, so a long multi-county day needs someone to check timing, access and travel between stops before the team leaves.
Treating reporting as an event task
Federal finance and reporting rules are detailed and change over time. Attain OS does not provide FEC or compliance reporting, so give those deadlines to your treasurer and counsel. Keep them out of general event checklists, where they are easy to miss or misread.
Working checklist
Before a regional lead takes over and before each national day
Before a regional lead takes over
- Confirm the deputy is named in the workspace.
- Check which approved references the region must use as written.
- Confirm the region's first month of events is on the shared calendar.
Before each national day of action
- Confirm each regional host, address and headcount.
- Check that every regional stop list is saved in Routes.
- Confirm the treasurer and counsel have the compliance questions for that day.
What this agreement means
Keep national and regional roles clear
- A distributed campaign works when each region has one named lead, one deputy and a rule for copying national material.
- Keep one approved reference set with owners and approval dates, and link regions to it.
- Use Forms for regional intake, Calendar for shared events and Routes for stop order, and have each lead confirm people directly.
- Keep finance, filing and compliance decisions with the treasurer and counsel, outside the event workspace.
The timing is a planning example, not measured campaign seasonality. Confirm federal reporting and disclosure requirements with qualified advisers.
Frequently asked questions
What is federal campaign software?
It is software that helps a federal campaign coordinate its offices, regional teams, events and approved materials in one workspace. Specialist needs, such as data sourcing, money handling and filing, need separate systems and qualified advisers.
Can a federal campaign plan regional routes in one tool?
You can keep each regional stop list and its directions link together. Attain OS does not optimize the order of stops and does not provide voter files or a canvass results database, so regional leads should check timing and access themselves.
What is a team wiki for a campaign?
A team wiki is a reference area that holds terms, contacts and processes everyone needs. For a campaign, keep approved talking points and regional contact rules there, with an owner and an approval date on each page.
How should file sharing work for a distributed team?
Shared files work best when each document has one owner and a clear status. Store the source copy in one place, let regions link to it, and make a local copy only when a region has approved changes.
More references for this work
Training Playbook
Prepare the content and structure for training playbook.
Culture Deck
Prepare the content and structure for culture deck.
Payroll Schedule
Prepare the content and structure for payroll schedule.
Benefit Summary
Prepare the content and structure for benefit summary.
Campaign types
Progressive political
Run progressive political campaigns with Attain OS: volunteer teams, route planning, forms, events, contribution emails, and campaign content in one operating system.
Conservative political
Coordinate conservative political campaigns with Attain OS for precinct teams, canvassing routes, event operations, donor emails, forms, and message discipline.
Local campaign
Manage city, county, school board, and neighborhood campaigns with local route planning, volunteers, events, forms, email outreach, and web flyers.
Federal campaign
Organize distributed federal campaign teams with Attain OS for regional routes, national events, contribution email operations, forms, documents, and content.
Judicial campaign
Run judicial campaigns with disciplined public education, event coordination, route planning, supporter forms, team assignments, and professional content workflows.
Ballot initiative
Coordinate ballot measures, referendums, and petition campaigns with routes, signature intake forms, volunteer teams, events, and voter education content.
Grassroots activism
Mobilize grassroots activism with Attain OS for canvassing routes, volunteer onboarding, event coordination, forms, content, and sustained supporter communication.
Nonprofit fundraising
Plan nonprofit fundraising campaigns with donor emails, event coordination, pledge forms, team assignments, content creation, and campaign analytics.
Union organizing
Coordinate union organizing campaigns with shift-based routes, confidential forms, steward teams, events, documents, and consistent member communications.
Public health outreach
Run public health outreach campaigns with neighborhood routes, intake forms, events, multilingual content, email updates, and partner coordination.
Community event
Coordinate community event campaigns with volunteers, route plans, RSVP forms, web flyers, email invitations, schedules, and shared event assets.
Disaster relief
Mobilize disaster relief campaigns with supply routes, intake forms, volunteer teams, event staging, public updates, documents, and contribution emails.
