A working guide to managing appropriations requests for many clients at once: the kinds of request, how each one moves from a client’s need to a final bill, the evidence it needs, where firms lose track, and what AI can carry.
An appropriations request is one client need turned into a specific ask (a funding level, a few sentences of report language, or a community project) that member offices carry to the subcommittee writing the bill. Across a client book that becomes dozens of request and office pairings, each with its own form, deadline, version and result in the House and the Senate. Firms that do not lose track keep one record per request, per office, from draft to final outcome. AI helps by drafting from the client’s history, suggesting the account and subcommittee for a person to confirm, keeping each office’s status current and turning final bills into client reports.
Drop the request here
Drop the request here
Drop the request here
One ask, approved once. Drag it onto each office, or use the buttons.
Member offices that collect appropriations requests generally sort them into three kinds, and the committees handle each kind differently. A firm with a full client book runs all three at once, often for the same client: a funding level for the program, language telling the agency how to run it, and a project for a city or university partner.
Names, forms, eligibility and the accounts open to each kind change from year to year and differ by chamber, subcommittee and office. Read each office’s current request guidance and the committees’ own guidance at appropriations.house.gov and appropriations.senate.gov before planning a cycle.
Every request follows roughly the same route, but the dates and the details belong to each office and each subcommittee. What makes it hard at scale is that the route forks: the House and the Senate write separate bills and reports, and a request can succeed in one and not the other.
Start with what the client needs from the federal government this year, in its own words, and what happened last cycle. One need can produce several requests: a funding level, supporting language and, for an eligible partner, a project.
Map the need to the bill: which subcommittee, which account, which program line, and what the President’s budget request proposed for it. Agency budget justifications are the usual source (for defense, the DoD Comptroller publishes them). A good request sent to the wrong account reaches staff who cannot act on it.
Each House and Senate office that agrees to carry a request runs its own intake: a web form, a portal or a questionnaire, with its own questions, word limits and sometimes a cap on requests or a ranking for organizations that submit several. Office deadlines generally fall well before the committee’s.
Offices submit the requests they choose to each subcommittee through the committee’s own process, by dates the committees set every year, often in different weeks for different subcommittees and chambers.
Subcommittee and full committee markups produce the House bill and the committee report that explains it. Check the tables and the report for every request.
The Senate works on its own schedule, often later, and writes its own text. In some years not every Senate bill is reported. Check each request again.
Differences are resolved in a final bill, often packaged with others, with an explanatory statement that sets out what was agreed. A continuing resolution can hold funding at existing levels for part or all of the year and delay every outcome.
Compare the final bill, the tables and the explanatory statement with every request, report the result to each client, and record what carries into next year. Bill text and committee reports are published on congress.gov.
Office staff choose among many requests in little time. The request that is easy to say yes to answers their questions before they ask them, in the order their form asks them. Build the file once per request and every office copy draws from it.
| Evidence | ProgrammaticProg. | LanguageLang. | ProjectProject |
|---|---|---|---|
| Account, program line and budget request context | Needed | Needed | Needed |
| A justification in plain words, a paragraph or less | Needed | Needed | Needed |
| Local connection: facilities, jobs, people served in the member’s district or state | Needed | Needed | Needed |
| Last cycle’s history: what was asked, what was funded or written | Needed | Needed | Helpful |
| The proposed language, word for word | Not usually | Needed | Not usually |
| Letters of support from the community | Helpful | Not usually | Needed |
| Recipient eligibility and the committee’s disclosure items | Not usually | Not usually | Needed |
| Project description, timeline and use of funds | Not usually | Not usually | Needed |
| Client sign-off on the exact version sent | Needed | Needed | Needed |
Five fictional clients and eleven requests, from drafting to final outcome. Open a card to see what a request has to carry: its offices and the version each received, the evidence still open, its result in each chamber, and what happens next. Move it a stage and see what the board flags.
With three clients, a careful lobbyist can hold every request in their head. With fifteen, the same six problems turn up in almost every firm, and none of them is a judgment problem. They are record-keeping problems that cost judgment its chance.
The client approved the third draft. One office portal has the second, because a late edit went to two offices and not the third.
WHAT PREVENTS ITOne master version per request. Every office copy is made from it, and every submission is recorded with the version sent.
Ten offices, ten dates, different subcommittees on different schedules, and a client who needs a week to approve anything. The committee’s date is the wrong one to plan around.
WHAT PREVENTS ITA deadline per office, with the client’s approval time worked back from the earliest one.
“Did Sen. Okafor’s office submit it?” gets answered from memory or from a spreadsheet last touched three weeks ago.
WHAT PREVENTS ITStatus kept per office and changed only when the office confirms, with the confirmation attached.
Two clients want different things from the same account, or one client’s request reaches two offices in two different forms.
WHAT PREVENTS ITA view of the book by subcommittee and account, not only by client, so a partner sees the overlap before an office does.
The final bill arrives months later, sometimes after a continuing resolution, and nobody compares it with the open requests. The client hears the result from someone else.
WHAT PREVENTS ITAn outcome check against every open request when bill text, reports and the explanatory statement are released.
Next year’s request is drafted from a blank page because last year’s outcome and staff feedback were never written down.
WHAT PREVENTS ITEach outcome becomes the starting record for next year’s request, with what the office and the committee said.
The judgment in appropriations work is choosing the ask, the offices and the argument, and making the case in person. The volume is everything around it. That is where AI earns its place, with a person approving anything that leaves the firm and every finding carrying its source.
A first draft in each office’s format, built from the client’s record, last cycle’s request and its outcome. Facts it cannot source stay as visible blanks.
THE PERSONThe lobbyist chooses the ask and the argument. The client approves the version.
Suggests the likely subcommittee, account and program line, quoting the budget document it found them in.
THE PERSONA person confirms the account against the agency’s budget justification before anything is written around it.
Keeps one line per office current from confirmations and correspondence, flags version mismatches, and warns as each office deadline approaches.
THE PERSONThe lobbyist works the offices. Status changes only on a real confirmation.
When the House, Senate or final text is released, finds each request’s result with page references and drafts the client update.
THE PERSONA person checks every finding against the text and sends the update.
A programmatic request asks the committee to fund an existing account or program at a certain level, and anyone with a stake in that program can make one. Community Project Funding (the House term) and Congressionally Directed Spending (the Senate term) fund a specific project for a specific recipient in a member’s district or state. Project requests have their own eligibility, disclosure and certification rules, set each year, and recipients have generally been public entities and nonprofits rather than companies.
The request belongs to the client, and the member office is the one that submits it to the subcommittee. Firms usually prepare the request, coordinate with each office and keep the file. Office forms generally ask for the requesting organization’s details and a contact there, and some offices expect the organization itself to fill in the form, so check each office’s instructions.
Offices receive far more requests than they can carry. Staff need time to review them, decide which to submit, rank them where the committee asks for that, and enter them into the committee’s own system. The date that binds a firm is each office’s deadline, minus the time the client needs to approve the final version.
A continuing resolution generally keeps agencies funded at existing levels and terms for a set period, so requests stay unresolved until a full-year bill passes. If the year ends with a full-year continuing resolution instead, requests made for that bill may never be acted on, and the firm should plan with each client whether to submit them again next cycle.
Keep one record per request, and inside it one line per office: the version that office received, its deadline, its confirmation, and the result in the House and the Senate. Look across the book by subcommittee and account as well as by client, so overlapping asks surface before submission and outcomes can be checked against every request when the final bill appears.
Capiro is the AI back office for lobbyists. It keeps each client’s appropriations requests, offices, evidence and outcomes in one place, and Meri, the AI Chief of Staff inside the back office, keeps the drafting, tracking and reporting moving for a person to approve. AI should not replace the relationship. It should carry the work around it. More capacity for every client.
The category, explained: What is an AI back office for lobbyists?
“This is essentially a back-office platform that merges several softwares we currently use.”
Partner, Government Affairs FirmSo we can tailor the demo. Takes 20 seconds.
Choose a time for your 30-minute discovery call with Jordan Clayton. We will also be in touch within one business day.
