, home
Customer access Request an enterprise demo
Request an enterprise demo Customer access

Enterprise operations / APPLICATION BLUEPRINT

Enterprise Projects & Portfolio Delivery

Connect proposed initiatives, investment decisions, dependencies, milestones, controlled changes, deliverable acceptance and benefit review.

Start generatingExplore illustrative interface

12 workspace menus · 12 business workflows · 5 role profiles

Application blueprint only. This is a proposed design, not a deployed or production-tested system. Screens and sample figures are illustrative; workflows, business rules, approvals, permissions and integrations require confirmation before build.

Designed for Portfolio management office and project sponsors

Enterprise Projects & Portfolio Delivery workspace interface preview; illustrative records and figures.
Enterprise Projects & Portfolio Delivery — operational workspaceIllustrative interface · Sample dataView full interface →

Explore an illustrative interface.

Illustrative workspace and record review. Select a concept screen to inspect it in full.

Enterprise Projects & Portfolio Delivery workspace interface preview; illustrative records and figures.
Enterprise Projects & Portfolio Delivery — operational workspaceIllustrative interface · Sample dataView full interface →
Enterprise Projects & Portfolio Delivery record interface preview; illustrative records and figures.
Enterprise Projects & Portfolio Delivery — record and workflow reviewIllustrative interface · Sample dataView full interface →

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Business unitPeriodAssigned teamReview state

Dashboard measures

  • Active service movements
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Connect proposed initiatives, investment decisions, dependencies, milestones, controlled changes, deliverable acceptance and benefit review. A portfolio dashboard can show progress while hiding the approvals and dependencies that determine whether an outcome is deliverable. The system links the investment decision to delivery responsibilities, change control and acceptance, making unresolved issues visible alongside the promised benefits.

Operations

Operational overview

Review the work position and priority actions.

Initiative intake

Coordinate initiative intake with assigned responsibilities, linked records and review history.

Investment approval

Coordinate investment approval with assigned responsibilities, linked records and review history.

Dependency planning

Coordinate dependency planning with assigned responsibilities, linked records and review history.

Milestones and deliverables

Coordinate milestones and deliverables with assigned responsibilities, linked records and review history.

Issues and risks

Coordinate issues and risks with assigned responsibilities, linked records and review history.

Controlled scope changes

Coordinate controlled scope changes with assigned responsibilities, linked records and review history.

Acceptance and benefits review

Coordinate acceptance and benefits review with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Register the initiative

Register proposed initiatives with outcomes and ownership.

02

Approve delivery commitments

Approve funding, dependencies and delivery plans.

03

Manage work and changes

Manage milestones, issues and controlled changes.

04

Accept and review benefits

Accept deliverables and review realised benefits.

Business workflows

Select a workflow to review the steps, responsibilities, approval and exception handling.

01 · Coordinate initiative intake

Coordinate initiative intake within Enterprise project and portfolio delivery.

Trigger
Initiative intake requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register initiative intake and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

02 · Coordinate investment approval

Coordinate investment approval within Enterprise project and portfolio delivery.

Trigger
Investment approval requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register investment approval and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

03 · Coordinate dependency planning

Coordinate dependency planning within Enterprise project and portfolio delivery.

Trigger
Dependency planning requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register dependency planning and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

04 · Coordinate milestones and deliverables

Coordinate milestones and deliverables within Enterprise project and portfolio delivery.

Trigger
Milestones and deliverables requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register milestones and deliverables and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

05 · Coordinate issues and risks

Coordinate issues and risks within Enterprise project and portfolio delivery.

Trigger
Issues and risks requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register issues and risks and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

06 · Coordinate controlled scope changes

Coordinate controlled scope changes within Enterprise project and portfolio delivery.

Trigger
Controlled scope changes requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register controlled scope changes and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

07 · Coordinate acceptance and benefits review

Coordinate acceptance and benefits review within Enterprise project and portfolio delivery.

Trigger
Acceptance and benefits review requires a new record, an agreed review or a controlled change.

Responsible role
Project manager

  • Register acceptance and benefits review and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

08 · Register the operating requirement

Coordinate operating requirement within Enterprise project and portfolio delivery.

Trigger
Operating requirement requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register operating requirement and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

09 · Resolve operating exceptions

Coordinate operating exceptions within Enterprise project and portfolio delivery.

Trigger
Operating exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register operating exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

10 · Verify completion and follow-up

Coordinate completion and follow-up within Enterprise project and portfolio delivery.

Trigger
Completion and follow-up requires a new record, an agreed review or a controlled change.

Responsible role
Project manager

  • Register completion and follow-up and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

11 · Review controlled operating changes

Coordinate controlled operating changes within Enterprise project and portfolio delivery.

Trigger
Controlled operating changes requires a new record, an agreed review or a controlled change.

Responsible role
Project manager

  • Register controlled operating changes and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

12 · Prepare scoped operational reports

Coordinate scoped operational reports within Enterprise project and portfolio delivery.

Trigger
Scoped operational reports requires a new record, an agreed review or a controlled change.

Responsible role
Project sponsor

  • Register scoped operational reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Deliverable owner records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

Governance and control

  • Projects require an accountable sponsor and owner.
  • Gate progression requires required evidence and approval.
  • Budget changes above tolerance require authorised approval.
  • Overdue milestones and unresolved high risks must escalate.
  • Closure requires agreed deliverables and outstanding actions to be accounted for.
Operating rules by business workflow
  • For initiative intake, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For investment approval, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For dependency planning, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For milestones and deliverables, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For issues and risks, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For controlled scope changes, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For acceptance and benefits review, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For operating requirement, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For operating exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For completion and follow-up, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For controlled operating changes, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For scoped operational reports, the record retains an accountable owner, its supporting evidence and accepted outcome.

Data, interfaces and operating requirements.

Core records

Programme / projectApplication / business caseMilestoneBudget / fundingRisk / issueDecisionDeliverableCloseout record
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Business unit — Business scope used for responsibility and reporting.
  • Operating subject — The request, commitment or work item being handled.
  • Accountable owner — Named responsibility for the next action.
  • Workflow stage — Current position in the agreed business journey.
  • Review requirement — Required review and outstanding decision.
  • Due or review date — Agreed action window or review trigger.
  • Linked evidence — Source records supporting the operating decision.
  • Decision authority — The delegated authority relevant to the accepted outcome.
  • Accepted outcome — Recorded decision and its business consequences.
  • Follow-up obligation — Remaining responsibilities after an accepted action.
  • Revision history — Trace of accepted changes and their evidence.
  • Initiative intake reference — Link the relevant initiative intake to the operating transaction and its decision evidence.
  • Investment approval reference — Link the relevant investment approval to the operating transaction and its decision evidence.
  • Dependency planning reference — Link the relevant dependency planning to the operating transaction and its decision evidence.
  • Milestones and deliverables reference — Link the relevant milestones and deliverables to the operating transaction and its decision evidence.
  • Issues and risks reference — Link the relevant issues and risks to the operating transaction and its decision evidence.

Systems and interfaces

  • Approved finance records
  • Delivery tools
  • Document and notification services

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Core application; organisational investment rules and optional finance or delivery tool integrations apply.

Mobile and tablet access

Review milestones, issues and delegated approvals through responsive portfolio views.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

Apple App Store ↗Google Play ↗

AI extensions

Prepare draft progress summaries from recorded delivery evidence for project manager review.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

AN EXAMPLE OPERATING SCENARIO

What to validate in a scoped demonstration.

A initiative is approved with funding and dependencies. A milestone is blocked by another workstream, a scope change is reviewed and the revised plan is authorised. The sponsor accepts the deliverable and the benefit-review obligation remains visible.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report
Discuss this solution

Questions before implementation.

How is this system adapted to our organisation?

Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.

How are approvals and responsibilities defined?

Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.

Can it connect with our existing systems?

Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.

What will we review in a solution walkthrough?

Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.