Best practice for aligning Demands, Projects, Programs, Portfolios, and Strategic Goals in SPM

[SoureshD6782072]

Hi Community,

We are implementing ServiceNow Strategic Portfolio Management and are currently designing the end-to-end process from Demand Intake → Evaluation → Portfolio Prioritization → Project Creation → Execution → Benefits Tracking.
Our business wants to use SPM not just for project execution, but also for strategic alignment and funding governance. The expected process is:

Business users submit a Demand.
Demand should be evaluated against multiple dimensions such as:

Strategic alignment
Risk
Cost estimate
Business value
Regulatory impact
Resource availability

Approved Demands should be prioritized at the Portfolio level.
Once selected, the Demand should generate a Project.
The Project should roll up to a Program where applicable.
Cost, resource plans, and benefits should roll up from Project to Program and Portfolio.
Leadership wants dashboards showing:

Portfolio investment by strategic goal
Planned vs actual cost
Benefit realization
Demand-to-project conversion rate
Resource capacity vs demand
Projects not aligned to any strategic objective

The challenge is that the business also wants a custom approval model based on estimated cost and strategic priority. For example:

If estimated cost is below $50K, approval should be done by Portfolio Manager.
If estimated cost is between $50K and $250K, approval should go to Finance and Business Sponsor.
If estimated cost is above $250K or marked as regulatory, approval should go to Steering Committee.
If the Demand is not aligned to an active strategic goal, it should not proceed to project creation.

My questions are:

What is the recommended SPM data model for linking Demands, Projects, Programs, Portfolios, Goals, and Funding without creating unnecessary custom reference fields?
Should strategic alignment be handled through Goals / Planning Items / Portfolio Plans, or is it acceptable to add a custom “Strategic Objective” reference directly on Demand and Project?
What is the best practice for implementing this type of approval governance — Flow Designer, legacy workflow, Decision Tables, or Portfolio Planning configuration?
How should we ensure that financial rollups from Project to Program and Portfolio remain accurate if we introduce custom funding approval stages?
Is it better to convert approved Demands into Projects only after final funding approval, or should Project records be created earlier in a “proposed” state?
How are others handling benefits tracking when benefits are estimated at Demand stage but realized at Project or Program level?
Are there any known pitfalls when customizing Demand scoring and approval logic in SPM that could impact Portfolio Planning, Investment Funding, or reporting?

We want to stay as close to the out-of-box SPM model as possible and avoid creating custom fields/processes that will create upgrade or reporting issues later.
Any architectural guidance, design patterns, or lessons learned from similar SPM implementations would be greatly appreciated.
Thanks in advance!

[romiilsikka]

Use the OOTB SPM model:

Demand → Project → Program → Portfolio

Use Goals/Strategic Objectives for alignment; avoid custom strategic reference fields.

Use Demand Scoring + Assessment Designer for evaluation.

Use Portfolio Planning for prioritization.

Use Flow Designer + Decision Tables for approval routing based on cost, risk, and regulatory criteria.

Block approval/project creation if no active strategic goal is linked.

Create Projects only after final funding approval.

Use OOTB Cost Plans, Resource Plans, Benefit Plans, and Funding to preserve rollups.

Track estimated benefits on Demand and realized benefits on Project/Program.

Avoid custom financial tables, custom rollups, and legacy workflows.

This keeps the solution upgrade-safe, reporting-friendly, and aligned with SPM best practices.