Attain OS for public administration

One place for every request, one owner per request, one record of what was done.

Constituent requests, complaints, work orders and inter-department referrals stop sitting in a counter logbook, a shared inbox and three department spreadsheets. They become cases in one system, each with an owner, a status and a record that survives a staff change. Attain OS is an internal case desk: residents do not log in, and it does not send them status updates by itself.

14 days free · No card needed · Cancel anytime

Government Software for Small Offices: Constituent Requests, Cases and Field Work

Who this is for

What this looks like today

Municipal offices, agencies, public-works and sanitation departments, constituent services teams and community programs that take in requests from the public and have to deliver a service and an answer for each one.

The counter logbook has eleven entries from this morning, four of them about the same collapsed drain. A resident is on the phone about a streetlight she reported three weeks ago, and the only person who would know is on leave. Public works has a crew out but the office will not see what they did until the supervisor comes back with a sheet of paper. Two departments are each waiting for the other to act on a referral that was made verbally. Nobody in the building is doing anything wrong. There is simply no shared place where a request lives from the moment it arrives until the moment it is closed.

  • The same complaint arrives by phone, by counter visit and on social media, and becomes three separate half-tracked items
  • A request handed to another department disappears, and nobody can say where it stopped
  • Residents call back for status because nobody knows where to look for the answer
  • Field crews report what they did on paper that reaches the office days later, if at all
  • When someone asks what was done about an issue last year, finding out is an afternoon of asking around

What changes

Intake stops depending on which door someone walks through. A public request form can open a case for each submission shortly after it arrives, and staff log counter visits and phone calls as cases by hand, or describe them to Atty and approve the draft. Each case carries a category, a priority, the resident's record and a due date. Four reports about one collapsed drain still arrive as four cases, but staff see them side by side and close three against the first.

Routing becomes visible instead of verbal. A case is assigned to one or more people with a due date and a status anyone in the project can see, and each assignee is notified. Work that goes to a crew can become a Work Board work-order ticket with the address, on a board with the statuses you define. The crew opens the day as a route on a phone, marks each stop done, which saves when and by whom, and posts a photo of the result to the feed.

Closing the loop is still done by people. Atty can draft the resolution summary or the text of a reply from what was recorded on the case, and a person reviews it and sends it from the resident's record as a one-off email. Community notices go out as email campaigns from the Emails app. The record of what was requested, who handled it and what was done stays on the case after the people involved move on.

The status answer stops being a research project

Because the request, the assignees, the internal notes, the attachments and the resolution sit on one case, answering a resident takes a lookup rather than three phone calls. Atty can draft a resolution summary or a weekly note from what the cases already contain, so writing up the week is review work instead of reconstruction.

One system instead of separate tools per department

Intake forms, cases, work boards, crew routes, documents, email notices and team chat are built into one workspace, so departments stop maintaining their own disconnected tools. Attain OS does not connect to permitting, mapping or finance systems, so anything that must live there stays there.

Every request has a name, a date and a visible state

Nothing sits in an unowned pile. A department head can open the cases and see what is open, who owns it and what is past its due date. Each case keeps a history of field changes, so when a council member asks what happened with an issue, the answer is a record with dates on it rather than a recollection.

Serve more residents with the same staff

Constituent volume rises faster than staffing does. When web requests arrive as cases, every handoff has a named owner and routine write-ups are drafted by Atty for approval, the same office spends less time chasing status and more on the requests that need judgment. Nothing is routed or answered without a person.

The apps that carry the work

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.

Forms

Community intake through a public form

Build request forms for service issues, complaints and program interest, with a dropdown for the category and text fields for the address and details. Share the link on your site, on printed notices or as a QR code from the Sharing Hub. Each submission can open a Customer Care case shortly after it arrives. Forms have no file-upload or photo field, so applications that need documents are handled another way.

  • Public service-request form for issues like drainage, lighting and collection
  • Program interest forms that capture the resident's name, email and phone
  • A case opened for each submission, with the priority and tags you set
Forms
Customer Care

Constituent cases, from report to resolution

Each request is a case with a status from New to Closed, a priority, a category, assignees, a due date, internal notes, image attachments and a resolution summary with the root cause. A history of field changes shows who changed what and when. Residents cannot see or reply to cases: it is an internal case desk.

  • Cases linked to the resident's record
  • Duplicate reports closed against the first case with a note
  • A reopened issue handled on the original case
Customer Care
Customer Management

Residents, businesses and community organizations

A contact record holds the address, phone, email, preferred contact method and language, labels and custom fields, and shows the cases linked to that person. Staff can send a one-off email from the record, and it is kept in the record's Communications tab. It is not a complete log of every call or visit.

  • Resident and business records with their linked cases
  • Neighborhood associations and community contacts under one label
  • Preferred language on each record, so a reply goes out in the right one
Customer Management
Work Board

Field work and referrals you can see

Create a Work Board ticket of the work-order type for work that goes to a crew, with the address, a priority from P0 to P5, assignees, labels and a due date. The board's statuses are yours to define and labels can mark the department. Moving the card is the status update, visible to everyone in the project.

  • Labels per department, program or district
  • Referrals with the receiving owner named on the ticket
  • Overdue work visible on the board before someone complains
Work Board
Routes

Crews, inspections and service runs

Build the day's stops for a public-works crew, a collection run or an inspector in the order you choose, and open the route as Google Maps directions. The field marks each stop done from a phone, which saves when and by whom. You set the order: there is no route optimization and no vehicle tracking.

  • Daily crew routes built from open requests
  • Inspection runs grouped by district
  • Completion saved from the field the same day, with who marked it
Routes
Documents

Files and the record of what was decided

Upload permits, applications, correspondence and reports as documents, link each to the resident or business it belongs to, and give it labels, assignees and a due date. Documents can be searched and filtered, and a person can run an analysis for a summary, text extraction or translation. There are no folders and no version history.

  • Permit and application files linked to the resident's record
  • Scanned letters summarized or translated on request
  • Documents labeled by department or program
Documents
Emails

Notices to residents by email

Send a service notice or program update as an email campaign to residents in your records, or to a list imported by CSV, with a visual or AI-generated layout and each recipient's first name. Sending is queued and goes out shortly after you send it; each recipient shows as sent, viewed or failed, and people who unsubscribed are skipped. There is no scheduling for later and no inbox for replies.

  • Service interruption notices to affected residents
  • Program announcements to a CSV list
  • A test send to one address before the real one
Emails
Content Creator

Public explainer and event pages

Build a simple web page for a program, an event or a process residents keep asking about with a guided wizard: pick a type, answer the questions Atty asks, approve the plan and review the page before you share it by link. Nothing is posted to social networks, and each page is reviewed by a person before anyone sees it.

  • An explainer page for a process residents keep asking about
  • A community event page shared by link and QR code
  • A program page linked from an email notice
Content Creator
WhatsApp + Atty

Field reports from staff over WhatsApp

Where your organization has WhatsApp enabled, a field officer can send Atty a voice note, a text or a photo. Atty drafts a case or an update for approval, and a photo is saved to the project's documents and can be attached to the case once approved. Location pins are ignored, so the address goes in the message. Atty does not talk to residents.

  • A field report drafted as a case from a voice note
  • A photo attached to the right case once approved
  • Open cases listed without opening the app
WhatsApp + Atty
Working guide

Case management software for a public office should record each resident request as one case, with a category, an owner, a status and the facts a reviewer needs to act. The case should stay with the request when staff change, and a referral to another department should show who now holds the work. Check how a tool handles public intake, assignment and the history of each case, because those decide whether a request gets answered.

In practice

Requests from the counter, the phone and the crew

  1. Morning · counter and phone log

    The front desk logs counter visits and phone calls as cases, each with a category and an address. Public form submissions can open a case when the scheduled processing runs. Four reports about one collapsed drain become four cases that staff can see side by side, so the crew is sent once and the other three are closed against that work.

    Customer Care
  2. Late morning · duplicate reports

    A supervisor finds two cases about the same streetlight. One becomes the working case with an assignee. The other gets an internal note that names it and closes with a resolution summary. The resident's record shows both contacts, so nobody calls the resident twice.

    Customer Management
  3. Midday · a referral to public works

    A report about a damaged sign belongs to another department. The case moves to that department's owner with a due date and a note saying what is needed. Public works sees the work as a ticket on its board, so the referral does not depend on someone remembering a hallway conversation.

    Work Board
  4. Afternoon · the crew route

    The public works crew opens the day's route on a phone, works the stops in order and marks each one done. The office can see each result in the route or the feed once the crew marks it, rather than on paper days later. Nothing tracks the crew's location.

    Routes
  5. Late afternoon · a program notice

    Staff write a notice about a program change from the case notes, and a person checks it before it goes out. Staff record which residents were told and when, so the next question about the same change starts from a known answer.

  6. Friday · a records question

    A resident asks what happened to a drainage complaint last year. Staff open the old case and read its notes, status history and resolution summary, rather than asking around the office for someone who remembers it.

    Customer Care
Workflow map

Which app carries each part of intake

JobAppWhat it does here
Public intakeFormsBuild a request form with a category dropdown and address and detail fields, then share its link on your site or in print. Each submission saves in a table, and a case can open when the scheduled processing runs. Forms have no file-upload or photo field.
Case ownershipCustomer CareEach request is a case with a status, a priority, a category, assignees, a due date and internal notes. Residents cannot see or reply to cases, so staff answer residents through their own channels and keep the case as the internal record.
Residents and organizationsCustomer ManagementA contact record holds the address, phone, email, preferred contact method and language, labels and the cases linked to that person. It is not a complete log of every call or visit, so staff still write up conversations in the case.
Department work ordersWork BoardCreate a work-order ticket for work that goes to a crew, with the address, a priority from P0 to P5, assignees and labels for the department. Statuses are the ones you define, and moving the card is the status update everyone sees.
Field crewsRoutesBuild the day's stops for a crew or inspector in the order you choose, and open the route as Google Maps directions. Stops save when they are marked done and by whom. There is no route optimization and no vehicle tracking.
Program documentsDocumentsStore permits, applications, correspondence and reports, link each one to the resident or business it belongs to, and set labels and a due date. Documents have no folders and no version history, so put the date and status in each file name.
Start here

Forms and pages for public requests

Customer complaint form

Ask when and where the problem happened, who was involved and the outcome requested, so the review starts from facts.

Contact us form

Collect a name, a way to reply and the question, so the right department can answer from the first message.

Volunteer sign-up form

Match people to a specific shift or role, rather than collecting a general list of interest.

FAQ page

Answer the questions residents ask most often, taken from the requests you already receive, with the direct answer first.

Mistakes to avoid

Three things that make a case hard to answer

One case per phone call

Four people reporting the same drain create four records, and each one looks like a new problem. Keep the first case as the working record, add a note to the others that names it, and close them against the same resolution. Otherwise the crew is sent four times and the office cannot see the pattern.

A referral made in a hallway

A request passed to another department has no owner until someone writes it down. Assign the case to that department's owner with a due date and a note saying what is needed. The assignee change is the record of the referral, so keep it current.

A status promise the office cannot keep

Residents cannot log in, and the system does not send them status updates by itself. Decide who answers residents, how often and through which channel, and set that expectation in the form's wording so residents know what happens next.

Working checklist

Setup for intake and a working day

Setting up intake

  • Name one owner for each public form and its cases.
  • Keep the category list short enough to sort by at a glance.
  • Write what residents can expect next, and when.

Each working day

  • Read new cases and set a priority and a due date.
  • Assign each case to one named owner.
  • Record the referral or resolution in a note before closing.
What this agreement means

What a public office settles first

  • Decide the categories residents choose from and who owns each one.
  • Decide what a referral to another department must include before it is accepted.
  • Decide how and when staff tell residents what happened to their request.

This describes an internal case routine. It does not replace public records rules, privacy obligations or your department's procedures, so check those before you store sensitive information.

Frequently asked questions

Is case management software the same as permit or licensing software?

No. Permits, licensing, payments and benefits are separate systems with their own rules. This kind of software holds the requests and cases that staff work on, with owners, statuses and history. Keep permits and payments in the systems built for them.

Can residents submit a request without an account?

Yes. A public form needs no login and has a bot check; a terms checkbox is optional. Residents do not get status updates automatically, so decide how staff will reply and say so on the form.

Can we limit who sees sensitive resident information?

Partly. Access is set per project, so members see the apps switched on there, and outside collaborators can be limited to the apps you grant. There are no field-level controls and no single sign-on, so check your privacy and records requirements before you store sensitive data.

Does Attain OS take payments or give residents a status page?

No. There are no payments, no permit module and no resident portal or status page. Attain OS is an internal case desk with public intake forms, and you can share one case as a read-only link when you choose.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA