Supporters, volunteer shifts, canvass turf, donor asks, event logistics and the message of the day stop living in a shared spreadsheet, a group text and four inboxes. They live in one workspace that every organizer opens from a phone. If you want the door-level detail — walk lists, canvassing, GOTV, volunteer programs and playbooks by campaign type — that lives at /campaigns.
Candidate campaigns at every level, ballot measure and referendum committees, advocacy organizations running a legislative push, and nonprofits running a fundraising campaign against a hard end date.
It is nineteen days out. The volunteer roster is a spreadsheet with three cursors in it, the turf packets are printed and sitting in the back of somebody's car, the donor asks are in a staffer's inbox, and tomorrow's phone bank was confirmed in a group chat that has since scrolled past. Your field director knows which precincts got walked; nobody else does. So the first hour of every morning goes to reassembling yesterday from four places, and you still cannot say for certain whether the doors you counted were counted twice.
The campaign is the project. It holds the supporter and donor records, the volunteer roster, the turf and route assignments, the event calendar, the task board, the budget and the whole message history. Open the campaign and you see the campaign, instead of asking three people and adding up their answers.
Organizers work from the phone, because that is where the work happens. A volunteer captain opens the day, sees their assigned turf and shift roster, logs what happened at each stop, posts a field note with a photo, and sends a voice message when they are walking between houses. Atty files that voice message as an update on the right campaign, and pings the volunteers whose shift starts in two hours.
The reporting is a by-product, not a second job. Because the doors, the calls, the shifts and the asks were recorded where they happened, the daily field number, the volunteer follow-ups, the donor thank-yous and the Monday leadership update are already assembled. Atty drafts them and a human approves. For the deep field mechanics — building walk lists, cutting turf, structuring a GOTV weekend — go to /campaigns.
Doors knocked, calls made, shifts covered and asks outstanding are already recorded against the campaign by the people who did them. Atty drafts the daily field summary, the volunteer reminders and the donor follow-ups from that record, so the first hour of the morning goes to the plan instead of to reconstructing yesterday.
The volunteer tool, the shared drive, the forms tool, the supporter database, the task board and the team chat are built in and already connected. Campaigns are short and budgets are scrutinized line by line, so paying six vendors to hand data between them is a cost you can simply remove.
Assignments and completion are visible on the campaign, not implied in a thread. When leadership asks why a precinct is behind, the answer is a link: who owns it, which shifts were covered, what was logged at the door. The same record is what you hand to your compliance and finance people instead of a rebuilt narrative.
What caps most campaigns is coordination, not willing volunteers. When each region carries its own structure and Atty handles the reminders, the confirmations and the drafting, the same small staff can run more turf, more phone banks and more house meetings in the same week.
Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.
One record per person carries their contact details, what they signed up for, what they have given, which events they attended and every message you have exchanged, so the next ask starts from what actually happened.
Publish a public volunteer sign-up, pledge card or petition and share the link anywhere. Submissions land as records you can assign and follow up on, instead of a CSV somebody has to merge.
Volunteers, captains and staff carry roles and permissions, so a shift captain sees their people and their turf without getting the keys to the donor file.
Build the day's stops in order and hand them to the phone. The canvasser opens the route, works the list and marks each stop, so what was walked is a fact rather than a recollection. Walk-list mechanics are covered in depth at /campaigns.
Filing deadlines, mail drops, debate prep, event milestones and the GOTV plan sit as cards with an owner and a date. Moving a card is the status update, so the weekly meeting stops being a status meeting.
Plan the message calendar, draft the posts and the volunteer email with Atty, and keep the whole campaign saying the same thing on the same day without a group chat relay.
Atty works over WhatsApp, so a captain can send a voice note or a photo from the field and have it logged against the right campaign, and can ask what their shift is without opening anything else.
Canvassers and captains post what they saw, what worked and what stalled, with photos. Leadership reads one chronological record of the whole program instead of six group chats.
Go to /campaigns. This page frames the audience; /campaigns is the toolkit, with dedicated pages for canvassing, walk lists, volunteer programs, GOTV and the individual campaign types, including candidate races, ballot measures, advocacy pushes and nonprofit fundraising drives. Start there when you want the door-level mechanics rather than the overview.
No. Attain OS is a general-purpose operating system for organized work, and the campaign tooling is neutral by design: turf, shifts, supporters, asks and deadlines behave the same regardless of who is running or what the measure says. It is used by candidate committees, ballot measure committees, advocacy groups and nonprofits alike.
A volunteer's whole surface is a phone: open the day, see the turf, log the stop, post a note. There is no separate app to install for someone who will not be back next week, and Atty over WhatsApp covers the volunteers who never open anything new. Captains and staff are the only people who need more than the phone view.
It stays in the workspace with the campaign. The supporter records, the donor history, the field notes, the volunteer roster and the documents are still there and still searchable next cycle, which matters more for a recurring committee or a nonprofit than for anyone who thinks of a campaign as disposable.
Yes. Roles and access are set per person, so a regional coordinator runs their own turf, roster and board while the donor file and the central plan stay restricted. You can also bring in a consultant or a partner organization as an external collaborator with access to only their piece.
Registration, run of show, vendors and budget — works on site.
Calendar, campaigns, email, leads and the monthly report. Not nine tabs.
One intake door, the right department, and a record of what was done.
Dispatch, work orders on phones, and proof every job got done.
Who Attain OS Is For — One Operating System for the Team You Actually Run
