Office of Government-wide Policy (OGP): Mandate and Outputs

Somewhere in the General Services Administration, in a corner that produces no buildings and sells no laptops, sits the office that decides what the rest of the federal civilian government is allowed to do when it books a hotel room, sells a surplus forklift, or buys a new identity verification system. The Office of Government-wide Policy, known almost universally as OGP, is the part of GSA that writes rules instead of delivering services. Its outputs are dry — bulletins, circulars, sections of the Code of Federal Regulations — but they quietly determine the operating texture of nearly every civilian agency in the executive branch.

What OGP actually is

GSA, per its own organizational materials, is divided into three principal service organizations: the Federal Acquisition Service, which runs the Schedules and the rest of the buying machinery; the Public Buildings Service, which owns and leases the real estate; and the Office of Government-wide Policy, which sets the rules everyone else follows. The first two do things. The third decides how things are done.

The legal hook is older and more sweeping than the office itself. Title 40 of the U.S. Code, covering Public Buildings, Property, and Works, gives the Administrator of General Services a broad mandate to prescribe policies and methods for the economical and efficient management of federal property. Title 41, covering Public Contracts, adds further authority over acquisition policy in coordination with other bodies. OGP is the operational expression of those statutes — the place where the abstract grant of authority gets turned into something an agency travel officer can actually consult on a Tuesday morning.

It is worth distinguishing OGP from the Office of Management and Budget, because the two are easily confused and frequently overlap. OMB sits inside the Executive Office of the President and governs agencies through the budget process and through its own circulars — A-11, A-123, A-130, the familiar litany. OGP sits inside GSA, which is itself an independent agency, and governs through the Federal Travel Regulation, the Federal Management Regulation, and a long tail of bulletins. OMB issues the high-level policy direction; OGP writes the implementing detail for the administrative plumbing. When a contracting officer reads a rule about per diem, that rule almost certainly came from OGP. When the same officer reads a rule about how the agency must justify the underlying program, that rule almost certainly came from OMB.

The policy domains

OGP's portfolio is wider than most people realize, and the breadth is part of why the office is so easily overlooked. A rule about aircraft management and a rule about smart card credentials do not, on the surface, seem to belong to the same shop. They do.

Travel. The Federal Travel Regulation, codified at 41 CFR Chapters 300 through 304, is OGP's most visible product. It governs how federal civilian employees are reimbursed for official travel — lodging, meals and incidental expenses, mileage when driving a privately owned vehicle, the awkward category of relocation. The per diem rates that hotels and contracting officers argue about every fall are issued under this authority and published on GSA's per diem site. Adjacent programs, though operationally run elsewhere within GSA, sit on the regulatory foundation OGP maintains: the City Pair Program for negotiated government airfares, and SmartPay, the charge card program through which the bulk of federal travel and small purchases flow.

Real and personal property. The Federal Management Regulation, also in 41 CFR, replaced most of the older Federal Property Management Regulations during a long modernization effort and now governs how agencies manage motor vehicles, mail, transportation, and the disposal of personal property they no longer need. The disposal pipeline ends, for items that survive screening and donation, at GSA Auctions and the federal property disposal portal — but the rules describing what may be screened, donated, sold, or abandoned originate in OGP. The Federal Property Council resources hosted at fpc.gov collect the older 41 CFR text for reference.

Aircraft. Federal aircraft policy is a small but genuinely peculiar corner of the portfolio. OGP maintains the rules under which civilian agencies acquire, operate, and account for their aircraft, including the cost reporting that determines whether a given flight was a sensible use of a government plane or whether the trip should have been booked through City Pair like everyone else's. The fleet itself is small; the policy is detailed anyway, because aircraft are expensive and visible and tend to attract congressional attention.

Information technology. The implementation of FITARA — the Federal Information Technology Acquisition Reform Act — runs through OGP in coordination with OMB and agency CIOs. The statute strengthened the role of agency Chief Information Officers in IT acquisition and budgeting; the implementation guidance translates that into something agencies can actually follow. Identity policy lives in this neighborhood too, including the framework that ultimately produced services like Login.gov, run operationally by GSA's Technology Transformation Services rather than by OGP itself. The pattern repeats: OGP writes the rule, another part of GSA, or another agency entirely, runs the service.

Records and information management. Records policy is jointly held with the National Archives, but OGP contributes the administrative-services side — how agencies handle the operational records produced by travel, property, and acquisition functions. The work is not glamorous. It is, however, what determines whether anyone can reconstruct, five years on, why a particular building was leased or a particular vehicle sold.

Identity, credentialing, and access management. Often abbreviated ICAM in the policy literature, this is the framework governing how federal employees and contractors prove who they are to government systems. The policy underpins the Personal Identity Verification card carried by federal personnel and the digital identity services that have grown up alongside it. Login.gov, again, is the consumer-facing manifestation; the policy scaffolding behind it is OGP's.

The forms the outputs take

OGP's outputs come in a handful of recognizable formats, and the format usually tells a reader something about the weight of the document.

The most binding outputs are the regulations themselves — sections of 41 CFR, principally — which carry the force of law for civilian agencies. These are amended through notice-and-comment rulemaking and appear in the Federal Register before settling into the CFR. Agencies have to follow them. The Department of Defense generally does not, since DoD operates under its own parallel framework, the Joint Travel Regulations chief among them. This is one of the small absurdities of the system: a civilian employee and a DoD civilian employee on the same trip to the same conference may be reimbursed under different rule sets.

Below the regulations sit the bulletins. FTR Bulletins and FMR Bulletins are issued periodically to clarify, interpret, or temporarily adjust the regulations — to announce a new mileage rate, for instance, or to address a specific class of relocation expense, or to remind agencies of an obligation that has been widely ignored. Bulletins are binding in the sense that they represent the Administrator's authoritative interpretation, but they sit a step below the regulation itself and can be revised more nimbly.

OGP also issues circulars and policy memoranda on subjects that do not lend themselves to formal regulation — best-practice guidance on fleet management, say, or analytical work on the cost of federal real estate. These are not binding in the same legal sense but tend to be followed because OGP is, in the relevant domain, the only authoritative voice in the civilian executive branch.

Finally, there is a steady output of data and reference material: per diem tables, mileage rates, aircraft cost factors, real property inventories. Some of this is statutorily required reporting; some of it exists because someone, decades ago, decided the government needed it and no one has yet decided it does not.

Where OGP fits relative to other rule writers

The federal civilian rulebook has several authors, and the divisions between them matter to anyone trying to find a particular rule.

The Federal Acquisition Regulation, hosted at acquisition.gov, governs how the government buys things. It is jointly maintained by GSA, the Department of Defense, and NASA through the FAR Council, with substantial input from OMB's Office of Federal Procurement Policy. OGP participates but does not own the FAR. By contrast, OGP does own the FTR and the FMR more or less outright.

OMB, as noted, governs from the White House through its circulars and through the budget process. The relationship with OGP is generally cooperative rather than competitive: OMB sets direction on, for example, IT modernization or shared services, and OGP works out the administrative-policy implications for travel, property, and acquisition systems. When the two issue joint guidance, which happens often enough, the joint document usually addresses both the strategic intent — OMB's territory — and the operational mechanics — OGP's.

The agencies themselves retain their own internal policy shops, which translate FTR and FMR requirements into agency-specific handbooks and orders. An employee at a given department reading a travel policy is usually reading an agency document that incorporates the FTR by reference and adds further internal restrictions. The base layer, though, is OGP's.

A small edge case worth flagging: certain agencies and components are statutorily exempt from parts of the framework, or operate under specialized regimes — the Postal Service, the intelligence community in various respects, the legislative and judicial branches almost entirely. The FTR applies to civilian executive branch agencies. The reach is broad but not universal, and the exemptions are scattered across statutes rather than collected in any single convenient list.

Why the office is easy to miss

OGP does not sell anything, does not own buildings, and does not run a public-facing service that anyone outside government would recognize. Its work product reaches the public mainly through second-order effects: the rate a federal employee can spend on a hotel room in Boise in November, the price the government pays for a flight from Washington to Atlanta, the conditions under which a surplus desk ends up on GSA Auctions instead of in a landfill. The office is, in a quiet and slightly stubborn way, the operating system on which a great deal of routine federal administration runs. That it is largely invisible is, on close inspection, a sign that it is working.