Start a proposed pilot with the project records you already maintain

Why spreadsheets stop scaling

When project records are maintained in several locations, an agency may want to review how status updates, source values, and leadership reporting are coordinated. The actual questions and any existing controls depend on that agency's own records and operating process.

Identify agency-approved source records

A proposed pilot can begin by identifying existing project names, budget records, schedule information, and approved reviewers. Any data permissions, field mapping, import, or operational application requires separate agency approval and implementation.

Potential requirements to scope

• Project records. Identify the existing agency-approved fields and reviewers relevant to the proposed scope.
• Budget and schedule review. Agree which source values and reporting periods would be considered.
• Leadership review. Define the reporting questions and approval process that agency staff require.
• Implementation boundaries. Validate any proposed data mapping, access controls, reporting, and retention requirements separately.

Existing systems remain the agency's decision

The agency determines which existing tools remain in place and whether any proposed source access is appropriate. No deployed import pipeline, production connector, operational portfolio application, or customer outcome is represented. See the technical scoping guide.