Funds from the rental-of-space account in FBF pay for all leased space in GSA’s inventory. During fiscal years 1997 and 1998, GSA received appropriations of about $4.6 billion in NOA for this account, about $2.3 billion in each fiscal year. GSA submitted two requests, totaling $324 million in NOA, to reprogram funds from other FBF accounts into the rental-of-space account. On August 8, 1997, GSA requested approval to reprogram $110 million of the fiscal year 1997 appropriated funds, and on January 9, 1998, it requested approval to reprogram another $214 million of fiscal year 1998 appropriated funds. Both requests were approved. The amounts requested equaled about 4.7 percent of the amount initially requested by GSA in its budget requests for the rental-of-space account for fiscal year 1997, and 9.4 percent of the amount requested for fiscal year 1998. In its August 8, 1997, reprogramming request for fiscal year 1997, GSA attributed the need for the reprogramming to three causes. First, it had estimated that the overall average rents would increase by 2 percent, but actual rent increases ranged from 3 to 5 percent. This resulted in the cost to the account being underestimated by about $30.9 million. Second, on the basis of regional expectations, GSA had overestimated the amounts that would be saved through lease cancellations by about $74.1 million. Third, GSA had not been able to absorb a $5.1 million congressional reduction in appropriations requested for rental-of-space expenditures in fiscal year 1997. According to a GSA official, the agency could not absorb this cut because GSA was already short of NOA in this account. GSA alerted its oversight committees in its reprogramming request letter that these problems would also affect the rental-of-space account in fiscal year 1998. In its January 9, 1998, reprogramming request for fiscal year 1998, GSA attributed the need for the reprogramming to four causes. First, GSA needed $143.6 million to cover the $110 million underestimation in fiscal year 1997 and to annualize this error for fiscal year 1998. Second, as in fiscal year 1997, GSA had estimated the overall average rental rate increase at 2 percent, but actual increases ranged from 3 to 5 percent. This resulted in the cost to the account being underestimated by about $22.5 million. Third, as in fiscal year 1997, it had overestimated savings from lease cancellations, this time by about $41.8 million. Finally, on the basis of what regional staff believed was going to happen, GSA had underestimated the need for expansion space. This resulted in a need for an additional $6.1 million. The process of formulating the budget is to begin no later than the spring of each year, about 9 months before it is transmitted to Congress and 18 months before the beginning of the fiscal year in which the budget becomes effective. During the first 6 months of this period (from about April through September), PBS compiles information on the various budget elements, including the rental-of-space account; reviews the information for reasonableness and accuracy; and prepares its budget estimates. During the next 3 months (October through December) these estimates are to be submitted as a portion of GSA’s budget request to the Office of Management and Budget (OMB) for review. OMB reviews the budget request and passes it back to GSA with any changes, and GSA may appeal OMB ‘s changes before the budget is finalized. Early the following year (between the first Monday in January and the first Monday in February), the budget is to be submitted to Congress for its review and appropriation of funds. Because of the timing of the budget process, when GSA realizes that an estimation error has been included in its budget request for that fiscal year (in fiscal year 1997 in this case), the error usually cannot be corrected in a future budget estimate until the second fiscal year after the error occurred (in this case, fiscal year 1999). To accomplish our objectives, we observed the Galaxy program in operation, reviewed training materials on its operation, reviewed documentation on the reprogramming requests, and interviewed PBS officials and budget and/or program analysts responsible for maintaining Galaxy in 10 of GSA’s 11 regions. We discussed with the PBS Deputy Controller what elements were needed to track and forecast rent expenditures. We checked to see that the elements discussed were included in the Galaxy program. We did not verify the accuracy of the data in Galaxy, but we did obtain information from PBS on how it planned to ensure that the data would be accurate, reliable, and consistent. We also did not contact customer agencies to verify the extent to which they were being contacted by GSA regarding their future space needs. We did our work in Washington, D.C., between August 1998 and May 1999 in accordance with generally accepted government auditing standards. We requested comments on a draft of this report from the Administrator of GSA. GSA’s comments are discussed at the end of this letter. GSA has taken corrective actions to specifically improve its tracking of the rental-of-space account and to improve its budget estimating for this account. The major step taken to improve both the tracking and estimating of the rental-of-space account was GSA’s development of the Galaxy program to be the primary tool to manage the rental-of-space account for fiscal year 1999 and to help manage project expenditures for fiscal year 2001. The reason Galaxy was developed was to provide a means to have all the regions use a consistent format, the same set of tools, and the same assumptions to monitor, reconcile, and estimate future expenditures from the rental-of-space account. Rent account analysts responsible for the rental-of-space account had not had a financial management tool for tracking and analyzing the account since September 1997. The previous automated system was discontinued when STAR was being put on-line. Rent account analysts had been using manual spreadsheets to monitor the account since that time. The Galaxy program software was developed under an existing support services contract, at no additional cost to GSA except for some travel to a region, as an interim program until a module could be developed for STAR. Current plans are to enhance Galaxy so that it will interface with STAR. A statement of work to accomplish this objective is currently being developed. To implement Galaxy, GSA provided each region with training on its use and a copy of the software already loaded with the region’s data for active lease contracts and active lease projects as of October 1, 1998. Galaxy has seven basic components, which include the elements PBS has identified as needed for tracking actual expenditures and estimating the funding requirements for future expenditures from the rental-of-space account. These components are described in table 1. The program can also generate various reports on both leases and projects, such as base rent by month, RWAs by lease number, IBAAs by lease number, lump sums by lease, operating cost escalation/CPI by lease, NOA by base lease, and estimate of rent increases tied to projects. Rent account analysts are responsible for ensuring that Galaxy’s data are accurate, reliable, and consistent. The training manual states that all active leases and projects loaded in Galaxy “must be validated.” The manual lists five steps that the analyst must follow to validate the information. Table 2 lists these steps. Also, other guidance in the manual indicates that Galaxy must be reconciled to NEAR on a monthly basis to ensure that accurate obligations are stated in NEAR. Further, the manual states that the effectiveness of any system is contingent upon the information it is supplied. Therefore, each region is responsible for ensuring the accuracy of the data input into Galaxy. Without accurate data, a credible status report for the rental-of- space account cannot be produced. Further, the regional rent account analysts we interviewed all agreed that communications between themselves and the realty specialists will be key in maintaining the accuracy of Galaxy. The analysts believed that communications would be of particular importance in estimating the rent account for a future budget year because, in order to estimate future expenditures, they rely not only on information about active leases, but also on information on projects in process. Project information is dependent upon the realty specialists’ communications with the customer agencies. The analysts we interviewed all believed that, with proper communications, Galaxy should help avoid past problems and improve the estimating process. We were told that all GSA regions are to create a branch that will have as one of its responsibilities the initiating and inputting of all project data into STAR. This process should help ensure that the projects are entered into STAR. In May 1999, at least one region had already begun interviewing applicants for positions in the new branch. We agree that good communication between the analysts maintaining Galaxy and the realty specialists maintaining STAR is critical to the accuracy of the data in Galaxy. To project the rent expenditure account, it is particularly important to obtain data on lease projects, which reflect potential changes in the inventory. This information is not as readily available as data on existing leases, but must be obtained from customer agencies. Further, we agree that good communication between GSA and its customer agencies is essential to improving the accuracy of the rental- of-space estimate. However, this may not be easily accomplished, even with good communications, given that for budget purposes GSA needs to estimate changes in space requirements approximately 18 months in advance. In his testimony on April 24, 1997, the PBS Commissioner testified that, when he asked federal agency facility managers in a quarterly meeting whether they could identify the space reductions from downsizing a year in advance, they all said that they could not. This shows how difficult it may be for GSA to get accurate information on changes in the inventory.