A portfolio manager tracking performance and a COO auditing exposures need to see very different things. Role-based dashboards let each person open the platform to the view that matters to them. This how-to covers what each role’s dashboard should contain and how to build one.
Why role-based dashboards
A single “everything” screen serves no one well. The PM wants performance and positioning; operations wants reconciliation and cash; risk and compliance want limits and exposures. Building a focused view per role means less noise, faster decisions, and fewer mistakes from hunting for the right number.
The PM dashboard
Center it on decisions: real-time P&L, current positions and weights, exposure by strategy and asset class, and performance against benchmark. For a multi-asset book, show traditional and digital exposure side by side so the PM sees the whole portfolio at a glance.
The operations / COO dashboard
Center it on control: reconciliation status and open breaks, cash by account and custodian, NAV progress, and anything requiring action today. This is the view that answers “is the book clean and can we strike NAV?” without opening five screens.
The risk & compliance dashboard
Center it on limits: exposure and concentration against mandate, leverage, and any limit breaches or approaching thresholds, with a clear audit trail. The goal is to see a breach the moment it happens, not at the end of the day.
How to build a dashboard
Start from the role — decide the two or three questions this view must answer.
Add the widgets that answer them (positions, P&L, reconciliation, exposure, limits).
Select the data scope — fund, strategy, book, or asset class.
Arrange most-important-first, top-left, and remove anything that isn’t decision-relevant.
Save the view and share it with the role, so everyone in that seat opens to the same screen.
Tips
Keep one primary view per role rather than one crowded dashboard for all. Favor the numbers that drive a decision over the ones that are merely interesting. And revisit views quarterly — the questions that matter change as the fund grows.
Frequently asked questions
Do I need technical skills to build a dashboard?
No. Dashboards are configured by selecting views and widgets — no code — so PMs, ops, and risk can build their own.
Can different roles have different dashboards?
Yes — that’s the point. Build a focused view per role (PM, operations, risk/compliance) so each opens to what matters to them.
Can a dashboard show crypto and traditional assets together?
Yes. Because HedgeGuard runs both in one book, a single view can show traditional and digital exposure side by side.
Can I share a dashboard with my team?
Yes. Save a view and share it to a role so everyone in that seat sees the same screen.
Multi-Asset Fund Setup: TradFi + Crypto
Launching a fund that holds both traditional and digital assets means solving two operating models at once. This tactical guide walks through the moving parts — structure, custody, valuation, reporting, and daily workflows — and where the TradFi and crypto sides diverge.
Note: fund structuring and regulatory questions below are operational orientation, not legal advice — confirm specifics with your counsel and administrator.
Fund structure & legal foundation
Structure comes first because it shapes everything downstream: domicile, vehicle, share classes, and the service-provider stack (administrator, auditor, legal, prime/custody). For hybrid funds, confirm early that your chosen administrator and auditor can actually service digital assets — not every traditional provider does, and that constraint can decide your structure.
Custody across both worlds
Custody is where the two worlds differ most. On the traditional side you have prime brokers and custodians; on the digital side you’ll typically combine qualified crypto custodians, MPC or multi-sig arrangements, exchange accounts for liquidity, and on-chain wallets. Your operating model — and your reconciliation load — is defined by how many venues you hold the same asset across, so keep the custody map deliberate and documented.
Valuation & NAV
Traditional assets have a clean close; crypto markets never close. Decide when you strike NAV (most funds mirror a TradFi cutoff such as 4pm ET or 5pm London), which price sources you use for digital assets (index providers are the institutional convention), and document both. Consistency and documentation matter more than the exact choice — that’s what auditors and allocators check.
Reporting & compliance
Investor reporting has to present both asset classes as one coherent NAV and exposure picture. On compliance, the baseline doesn’t pause because assets are digital: KYC/AML on flows, sanctions and (where applicable) travel-rule handling for on-chain transfers, and a defensible, exportable audit trail across everything.
Operational workflows
Day to day, the goal is one book, not two. Trade capture, position management, cash and reconciliation should span TradFi and crypto in a single flow — otherwise someone reconciles two systems by hand every day, which is where errors and key-person risk creep in.
Bringing it together on one platform
This is exactly what a dual-native PMS is for. HedgeGuard runs traditional and digital assets through the same valuation, reconciliation, and reporting engine, so a hybrid fund operates from one consolidated book from day one rather than stitching a crypto tool to a TradFi system.
Frequently asked questions
What’s hardest about running a TradFi + crypto fund?
Custody and reconciliation across many venues, and striking a consistent NAV when crypto markets never close. Solving both in one book is the core challenge.
Do I need separate systems for crypto and traditional assets?
No — and you shouldn’t. A dual-native PMS runs both in one book, avoiding the manual reconciliation of two parallel systems.
How do hybrid funds value crypto for NAV?
Most strike NAV at a TradFi cutoff and use index-provider prices for digital assets, then document the methodology for auditors and investors.
Can a traditional administrator service digital assets?
Not always. Confirm your administrator and auditor support crypto before finalizing structure — it’s a common late-stage blocker.
How to deploy a PMS in 60 days.
A portfolio management system doesn’t need a multi-quarter rollout. With disciplined preparation, a growing manager can deploy a full PMS in about 60 days. This playbook breaks the timeline into three phases, covers the data preparation that makes or breaks it, and gives you a go-live checklist you can run against.
The 60-day timeline at a glance
Phase 1 — Weeks 1–2: Discovery & data. Scope workflows, connect data sources, and prepare historical data.
Phase 2 — Weeks 3–5: Configuration & parallel run. Configure the platform to your workflows and run it alongside your existing system.
Phase 3 — Weeks 6–8: Validation & go-live. Reconcile in parallel, sign off, and cut over.
Phase 1: Data preparation is the make-or-break
Most implementations don’t slip because of software — they slip because of data. Start by exporting positions, transactions, and reference data from your current system, then assess quality: gaps, duplicates, inconsistent identifiers, and unmatched cash. Clean data reconstructs cleanly; messy data is where timelines stretch. Map your instruments, accounts, and custodians early, and decide up front whether you’re rebuilding full history from inception (clean data) or starting from a recent verified NAV.
Phase 2: Configuration & parallel run
Configure the platform to mirror how your fund actually operates — strategies, share classes, books, and reporting views — then run it in parallel with your existing system. The parallel run is non-negotiable: it’s how you catch discrepancies before they matter, by comparing NAV, positions, and reconciliation output side by side against your source of truth.
Phase 3: Validation & go-live
Go-live is a decision, not a date. When the parallel run produces matching NAV and clean reconciliation across a full cycle, you have the evidence to sign off. Cut over on a clean period boundary (typically month-end), keep the old system read-only for a defined window, and confirm the first live NAV and investor report before standing down.
Stakeholder alignment
A 60-day timeline only holds if the right people are engaged from week one: the PM on strategy and views, operations on reconciliation and cash, compliance on controls and reporting, and your fund administrator and custodians on data feeds. Name a single decision-maker for sign-off — scattered ownership is the most common cause of slippage.
Go-live checklist
Historical data exported, cleaned, and mapped
Instruments, accounts, and custodians configured
Data feeds live (prices, custodians, exchanges)
Parallel run reconciled — NAV and positions matched across a full cycle
Reporting views validated for each role
Compliance controls and audit trail confirmed
Cutover date set on a period boundary; old system read-only
First live NAV and investor report signed off
Common pitfalls
Three derail most timelines: underestimating data cleanup, skipping or shortening the parallel run, and scope creep (trying to redesign every workflow during migration instead of matching what you have, then improving later). Avoid all three and 60 days is realistic.
Frequently asked questions
How long does it really take to deploy a PMS?
With clean data and engaged stakeholders, around 60 days. The variable is almost always data quality and decision-making speed, not the software.
What’s the most important success factor?
Data preparation and a genuine parallel run. Clean, mapped data plus side-by-side reconciliation against your current system is what makes go-live low-risk.
Can we migrate our full history in that window?
Yes, when source data is clean. Where legacy data needs significant cleanup, you either budget time to reconcile it or start from a recent verified NAV.
Do we need to freeze operations during cutover?
No. HedgeGuard runs in parallel with your existing system, so you cut over on a clean period boundary without a freeze.