Government relations work is, mechanically, a memory problem. You're tracking many people across many institutions over many years, each with shifting positions, voting records, staff turnover, and a body of public statements that adds up over a career. The day-to-day work — briefing the principal, drafting a position paper, prepping for a meeting on the Hill — is mostly a fast retrieval task on top of that running record.
This guide is about putting the parts of GR and public affairs work that benefit from being together — stakeholder context, hearing transcripts, position papers, meeting notes, and the legislative tracker — into one vault where an agent can read across them.
What government relations notes actually do
The good GR shop doesn't run on the most expensive CRM. It runs on the principal walking into a meeting already knowing the staffer's name, the bill the member co-sponsored last session, and the position their boss took during the markup three years ago. That kind of context comes from a system that captures small details consistently and surfaces them on demand.
The four loads a GR notes vault has to carry:
- Stakeholder context — members, staff, agency officials, allied advocates, opposition. Histories, positions, relationships, what they've said publicly.
- Issue and position files — the policy substance, your client's or organization's position, the supporting research, the talking points.
- Meeting and hearing records — what was said, by whom, in what setting, with the actual exchanges searchable later.
- The legislative tracker — what's moving, where it is, who's in the room, what your asks are.
A vault that holds all four together, with an agent reading across them, is what makes the daily prep cycle compress. The same shape applies to anyone doing relationship-heavy work over long time horizons; see AI notes for executive assistants for a structurally similar setup with a different application.
Stakeholder pages that compound over years
The core asset is a page per person you care about. Not a CRM record — a page, in plain markdown, that grows over time.
A typical staffer page might hold: bio, role history, the offices they've worked in, their portfolio (the issues they handle), their boss's positions on those issues, who they tend to coordinate with on the other side, your prior interactions, and a running set of small notes — what they mentioned in passing, what their stated priority is this session, what they care about personally that came up.
The page is plain markdown, which means the agent can read it end-to-end. When you ask "what do I know about Sarah Mendez at Senator Pratt's office?", you get a real synthesis grounded in the page, not a generic search hit. Six months later, the page has more on it, and the agent's read is sharper.
For members and senior officials, the page can hold their public record — voting summaries, statements, op-eds, hearing comments — alongside your private observations. PDFs of speeches and committee transcripts auto-convert to markdown via docstrange, so a 40-page hearing record becomes searchable text the agent can quote from.
The position file — substance, not slogans
Every issue your organization works on deserves a position file. Not the talking points — the substance behind them. The history of how the position evolved. The data and studies you cite. The counterarguments you've encountered and how you've handled them. The places where your position is genuinely strong and the places where it's defensible but not airtight.
A good position file is a sub-vault. The top-level page is the current position summary. Underneath, sub-pages for: the policy background, the supporting research (PDFs and articles dropped in), the opposition arguments and your responses, the messaging variants you've tested, the coalition partners and where each one sits, and a running log of how the position has shifted over time.
When you draft new talking points or a position paper for a different audience, the agent reads the sub-vault first. "From the position file on the rural broadband bill, draft a one-page memo for a moderate Republican staffer focused on rural economic impact, not federal program design." You get a draft that respects the substance and adapts the framing, without inventing new positions.
For complex issues with many sub-positions, unlimited page nesting matters. A trade policy file might have sub-pages for each affected sector, each with their own sub-pages for major firms in the sector, each with their own running log of stakeholder interactions. The structure can be as deep as the issue is.
Hearing transcripts and meeting records that survive
Public hearings, markups, and committee briefings generate a lot of material that's notionally public but practically hard to use. The transcript exists as a 200-page PDF on a committee website. The video is on a streaming page nobody bookmarks. The exchange that mattered — the moment the chair signaled flexibility, the staffer's question that revealed the agency's real concern — is buried somewhere in there.
Drop the transcript PDF onto the relevant issue page. It auto-converts to markdown. Now ask the agent: "In the hearing transcript from the Energy and Commerce markup on April 12, find every exchange involving the chair and the ranking member. Pull the moments where either of them signaled openness to amendments." You get the relevant exchanges with speaker attribution, in seconds.
For your own meetings — Hill drops, agency calls, coalition strategy sessions — record them when appropriate, drop the audio onto the relevant page, and let the transcription run with speaker labels. The transcript sits next to your own notes from the meeting. Three weeks later when someone asks "did we get a clear read from Treasury on the implementation timeline?", the agent finds the moment, with the actual quote.
The same pattern handles the back-of-the-room conversation that often matters more than the meeting itself. Type three lines after the meeting — what was said in the elevator, what the body language signaled, what wasn't said. Those three lines become some of the most useful intel in the file when read months later.
The legislative tracker — embedded inline, not in a separate tool
Most GR shops run a legislative tracker. Often it lives in a spreadsheet that exists in a Drive folder nobody opens unless they have to. The tracker becomes useful when it lives in the same vault as everything else, embedded in a page you actually visit.
An inline database in a markdown page via the :::database::: directive is the right shape. Columns for bill or rule number, sponsor, current status, your organization's position, key contacts, next event, and a status field. The database lives in a planning page that has prose around it — your strategic thinking on the session, what you're prioritizing, where your coalition is strong or thin.
The agent can answer queries across the database alongside the rest of the vault: "Pull every bill where our position is 'oppose' and the current status is 'in committee'. For each, list our two top contacts on the committee and their last known position." You get a working list with the relationship context attached. That's a half-day of staff work compressed.
For the long-range view, a sub-page per major piece of legislation captures the arc — from introduction through committee through floor through enactment. Decisions made along the way, position shifts, the testimony you submitted, the amendment you fought for. Useful next session when the same bill comes back in a different form.
Briefings and prep documents that hold up
The principal's prep memo for a Hill drop is a high-stakes artifact. With everything in the vault, the assembly compresses. "Draft a one-page prep memo for tomorrow's meeting with Senator Pratt's chief of staff. Focus on the rural broadband bill. Pull the Senator's prior public statements, the chief of staff's relationship history with our team, our two-line ask, and the three counterarguments we should be ready for."
You get a draft. You spend twenty minutes editing it instead of two hours assembling it. The principal walks in with context grounded in the actual record. The drafting workflow itself overlaps with what we describe in drafting emails, proposals, and newsletters inside your notes app — same shape, higher-stakes content. For after-action reports, the same compression applies — three lines after the meeting, then a one-page memo the agent drafts from your three lines plus the transcript.
Coalition coordination and a compliance boundary
GR rarely happens alone. You're working with allied associations, member companies, paid advocates, and grassroots organizations. A "Coalition" sub-vault, with a page per partner organization, holds the running context — their position, their internal politics, the staffer who returns calls, the meetings you've had together. Update after each interaction. Over a session, the pages become the most useful intelligence asset for coalition work. For joint strategy sessions, the meeting page captures who said what. The transcript with speaker labels means you can later answer "did the trade association ever commit to that messaging?" without ambiguity.
A real practice note: GR work involves disclosure obligations, lobbying registration thresholds, gift rules, and ethics requirements that vary by jurisdiction. Your vault is a working tool — it's not a compliance system, and it doesn't replace legal counsel on any disclosure question. Operators are responsible for understanding their own jurisdictional obligations and matching their record-keeping practices to them. The vault makes the relevant material easier to find when an audit happens; it doesn't make the audit go away. The same commitment-capture pattern is the spine of how to capture action items so they actually get done.
A calmer way to run the work
The cognitive load of GR work compounds. Every new bill, every staff turnover, every coalition realignment adds another thing to track. The traditional answer is more spreadsheets, more CRM fields, more weekly meetings to share what people learned. The shape that actually scales is fewer tools, deeper context, and an agent that can read across the record on demand.
Try Docapybara free — sign up, build a stakeholder page for one staffer you brief into often, drop in the last hearing transcript that touched your issue, and ask the agent for a one-page prep memo for your next meeting with that office.