USE CASE · DEVELOP & POSITION
Track Projects From Early Signal to Procurement
Track projects from early planning toward procurement, keeping relevant opportunities in view with source-backed context that supports the next commercial decision.
Talk to SalesExplore Project Intelligence
THE CHALLENGE
Why public-infrastructure projects are difficult to track over time
Infrastructure projects can develop across years and across many public documents. A need may first appear in a capital plan, then surface in funding discussions, consultant activity, design work, council approvals, procurement preparation, and finally a formal solicitation.
A continuous project history shows how scope, budget, timing, stakeholders and procurement status change across successive records. Commercial actions can then follow the latest available context. GFOA's capital planning guidance describes multi-year plans that define expected needs, scope, funding and future costs, all useful context as projects evolve.
The operating shift
Connected project history across public records
Stage changes supported by evidence
Current account and pursuit context as the project develops
PROJECT MOVEMENT
Which changes show that an infrastructure project is moving?
To track projects effectively, watch the changes that alter confidence, scope, timing, access, funding, delivery, or the transition toward procurement.
Scope development
Studies, design activity, phase definitions, technical details, and owner discussions show how the need is becoming a project.
Funding change
Budget actions, grants, financing, and allocations can materially change execution confidence and timing.
Stakeholder change
New owner staff, consultants, project managers or company relationships can change account access and pursuit planning.
Approval milestones
Council, board, agency, or internal approvals can move a project into a more committed stage.
Procurement preparation
Drafting, vendor engagement, pre-bid activity, procurement type, and release milestones show when the project is entering the buying window.
PROJECT LIFECYCLE FLOW
Keep the project, the evidence, and the next move connected
A priority project stays useful when each new piece of evidence can change the commercial plan.
1
Baseline
Capture the owner, need, timing, value, market, and source behind the early opportunity.
2
Working priority
Keep the project visible in the appropriate list or customer workflow based on timing.
3
New intelligence
Review new project and market signals as they become available.
4
REX AI research
Investigate the specific question that could change project confidence or the next action.
5
Commercial update
Carry the new context into CRM, account planning, positioning, or capture work.
Lifecycle control
A project the team can revisit with the latest relevant context.
WORKFLOW
A grounded monitoring workflow for a priority project
Citylitics enables teams to continue monitoring relevant opportunities and emerging signals over time. The concrete workflow is to keep the opportunity organized, review new intelligence, research material changes, and update the customer's sales process.
1
Establish the project baseline
Record the owner, project need, timing, value, market, and public source that made the opportunity relevant.
2
Keep the opportunity visible
Use the appropriate Citylitics list or customer workflow so the project stays in view according to its commercial timing.
3
Review new intelligence
Revisit the opportunity as new project and market signals become available in the configured intelligence workflow.
4
Use REX AI for the open question
Investigate a specific opportunity when funding, engineering involvement, timing, scope, or source detail could change the commercial plan.
5
Update the next action
Carry the new evidence into the customer's CRM, account plan, capture review, or outreach decision.
OUTCOMES
Keep the project context useful as the opportunity develops
Give account and pursuit teams a consistent way to revisit the project, research what changed, and update the commercial plan as new intelligence appears.
01
Start with the earliest credible record
Capture the owner, project need, timing, value, source, and market context when the opportunity first becomes relevant.
02
Keep priority opportunities organized
Use Action or Future Lists and the customer's existing workflow to keep important projects visible according to their timing.
03
Research what changed
Use REX AI on the specific opportunity when the team needs current funding, engineering, timing, scope, or source-document context.
04
Carry the new context forward
Update account, CRM, and pursuit decisions as the project produces new evidence and moves closer to procurement.
CITYLITICS SUPPORT
Keep project intelligence connected to the next commercial move
Citylitics supports an Always-On Market Development approach by keeping relevant opportunities and emerging signals in the team's working view while source-backed research helps answer project-specific questions.
What your team needs to do
Citylitics capability
How it helps
Establish planned project context
Capital Projects Dashboard
Review owner, project, timing, value, status, geography, and source context from published capital plans and budgets.
See emerging project movement
Intelligence Feeds
Review analyst-verified project and market signals aligned to the team's configured markets and territories.
Keep priority projects organized
Action List and Future List
Separate opportunities that need near-term attention from longer-horizon projects that remain commercially relevant.
Research current status
REX AI
Investigate funding, timing, engineering involvement, scope, or source-document evidence on the specific opportunity.
Carry updates into the operating process
CRM sync and exports
Move relevant opportunity context into supported sales workflows where account and pursuit decisions are managed.
PROJECT HISTORY METHOD
Track projects by connecting each new record to the existing opportunity history
Add each new signal to the existing project history so the record reflects how the opportunity is changing. Preserving the source trail across stages gives the team a defensible history of what changed, when it changed and which capture action followed.
01
Identify the project in public records
Planning, budgets, agendas and project documents establish the initial record.
02
Connect later activity to the same owner and project
Funding, consultant, scope and procurement signals are associated with the existing context.
03
Preserve source evidence
Keep the underlying records available for direct inspection of each update.
04
Assess freshness and stage movement
New activity is evaluated for whether it materially changes project maturity or timing.
05
Carry the update into account and pursuit decisions
The sales team decides whether the change requires outreach, research, monitoring or capture action.
How to read the lifecycle example
LA Metro’s project history shows how public evidence accumulates as a major pursuit develops. Citylitics enables teams to continue monitoring relevant opportunities and emerging signals over time; customer teams own pursuit timing, relationship strategy, and resource commitment. Citylitics Marketing reviewed this page on 15 October 2026 against LA Metro’s project history, GFOA guidance, and current product materials. The published data-process overview covers collection and quality review.
OFFICIAL PUBLIC-SOURCE EXAMPLE
The Sepulveda Transit Corridor shows years of project movement in the public record
LA Metro's project documents trace the Sepulveda Transit Corridor through feasibility work, a 2019 pre-development RFP, public environmental review, alternative refinement and a 2025 Draft Environmental Impact Report.
Signal
A major transit concept moves from feasibility into formal project development and environmental review.
Evidence
Metro's 2025 Draft EIR records the earlier feasibility study, the 2019 pre-development procurement, the 2021 public-comment period and later alternative refinements.
Interpretation
Each record changes what is known about project scope, delivery approach, stakeholders and timing, so the account picture should evolve with the project.
Action
A commercial team can maintain one opportunity record, update the capture plan as evidence changes and prepare for later procurement with the history intact.
DECISION FRAMEWORK
Which project updates should change the commercial plan?
Pay attention to new evidence that changes project confidence, timing, stakeholder context, solution fit, or the next account action.
01
Project definition
New planning, scope, or owner information changes what the project appears to require.
02
Funding context
New financing or budget evidence changes confidence in the opportunity or the timing of account work.
03
Engineering and stakeholder context
New information changes who is involved or who the account team needs to understand.
04
Timing
The available evidence changes when the project is likely to require research, outreach, positioning, or pursuit resources.
05
Commercial fit
New scope or project detail changes the relevance of the opportunity to the team's offering.
06
Next action
The update creates a clear reason to research, engage, reprioritize, or carry the opportunity into the next pursuit stage.
RESULT
A project record that stays useful from early signal through procurement
WHO IT'S FOR
For teams carrying project context across the lifecycle
Sales & account teams
Track projects across planning, funding, design and procurement so account activity stays tied to the same opportunity history.
Business-development & capture teams
Use each new project event to update timing, relationships, qualification and the next pursuit action.
Market & strategy teams
Review how project portfolios are progressing across owners, territories and infrastructure markets.
Revenue operations
Carry project context into assignment, action lists, exports and CRM workflows as opportunities advance.
WHY CITYLITICS
Support an Always-On project-development workflow
Citylitics brings capital-plan records, current project signals, source-backed research, and sales-workflow tools into the same market-development process. The goal is to help teams keep relevant opportunities in view and refresh the commercial context as new evidence becomes available.
Early project context
Capital Projects Dashboard and Intelligence Feeds establish the owner, project, timing, market, and source context.
Working prioritization
Action and Future Lists help teams organize priority opportunities around the timing of follow-up.
Opportunity-level research
REX AI helps answer specific questions about funding, engineering involvement, timing, scope, and source documents.
Sales-process continuity
CRM sync and exports help updated opportunity context move into the systems where account and pursuit work continues.
FAQ
Questions for project lifecycle tracking
Does Citylitics automatically track every project change?
Citylitics enables teams to continue monitoring relevant opportunities and emerging signals over time. Concrete workflow descriptions should stay with the available intelligence, lists, REX AI research, and CRM handoff while monitoring mechanics remain high level.
How should teams organize longer-horizon projects?
Use a Future List or the customer's existing account workflow to keep strategically relevant opportunities visible until the timing supports more active work.
What can REX AI check on a tracked opportunity?
REX AI can investigate a specific opportunity through structured web questions or source-document Q&A on topics such as funding, engineering involvement, timing, phase, scope, or other source-backed context.
Where should formal project stage progression live?
Citylitics supplies the market and project evidence. The customer owns formal qualification, stage progression, capture, and CRM management in its existing process.
Keep priority projects in view as the market moves
Organize relevant opportunities, review new intelligence, use REX AI for project-specific research, and carry updated context into your account and pursuit workflow.
Talk to SalesExplore Project Intelligence
