Check us out on YouTube!
Looking for a quick guide to PBS resources and programs?
-
View details from our past and upcoming National Customer Forums
CES Classroom Platform
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock
( )
or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
The PBS occupancy planning process standardizes milestone dates, requirements terminology, and responsibilities as customer agency Occupancy Agreements (OA) approach expiration.
Following the planning process is critical to achieving PBS and our customers' mutual goals of:
View the PBS Planning And Requirements Process Customer Fact Sheet [PDF - 332 KB]
Occupancy Planning and Requirements Gathering Topics
The Client Project Agreement (CPA) is a collaborative document that helps define a project's strategic requirements and other occupancy considerations. The Regional Planning Manager and other GSA team members will work with you on completing the CPA.
To learn more about the CPA you can view Part 1 [PDF - 58 KB]and Part 2 [PDF - 81 KB].
Strategic Requirements represent high level information that establish basic project parameters. This information includes existing occupancy information, total square feet, approximate headcount, location, use of space, parking, and utilization rate (UR) for the follow on project. Identifying strategic requirements on time is critical to a project's overall success.
Functional Requirements are developed from the strategic requirements by the GSA Project Manager and project team. This refined data set defines the new space's parameters, operations, expectations, schedule, and cost goals. Functional requirements include, but are not limited to, a verified total square footage, headcount, and geographic location. The Project Manager reviews the functional requirements and the initial project management plan/schedule with the customer at the project kick-off meeting.
Technical Requirements refine the strategic requirements into the specific details needed to deliver the project. Technical requirements include agency-specific requirements, agency-specific security information, basic space plans and adjacency plans. This is the final step in the requirements-gathering process before a Request for Lease Proposals (RLP) can be issued or a construction project can begin in owned locations. These details will inform the Project Management Plan.Note: Initial schedule, costs, and an OA will be shared prior to lease award.
(milestone dates are for non-prospectus projects. Prospectus project milestones noted separately)
Identification Phase - 36-30 Prior to OA Expiration*
18-12 months prior to OMB submission (prospectus projects)
Initiation Phase - 30-29 months prior to OA Expiration
12-11 months prior to OMB submission (prospectus projects)
Planning Phase - 29-24 Months Prior to OA Expiration
53-36 months prior to OA expiration (aligns with CILP+ date)++ (prospectus projects)
Execution Phase - 24-0 Months Prior To OA Expiration
36-0 months prior to OA expiration+++ (prospectus projects)
Close Out Phase - Substantial Completion
* In some cases, factors beyond expiration can trigger engagement and strategic requirements development.
** Certain PBS personnel, such as the Lease Contracting Officer, will remain involved at multiple phases
*** Or other form of written documentation showing acceptance of the strategy in the CPA
+ Capital Investment and Leasing Program Prospectus (CILP)
++ Once strategic requirements are identified, project manager secures technical requirements over next 24 months
+++ Typical duration, actual schedule may vary
Check us out on YouTube!
Looking for a quick guide to PBS resources and programs?
View details from our past and upcoming National Customer Forums
CES Classroom Platform