15 — Reference
Help & support
Because so much of the work is a handoff, asking us for something is a normal part of using Quant Reports — not an escalation. Requests are raised where you are working, and tracked so your whole team can see what has been asked and what came back.
Raising a request
The Help & Support button sits at the bottom of the left sidebar on every page, marked with a headphones icon. The form opens over the page you are on, so you will not lose your work.
Pick the category that fits, then describe what you were doing, what you expected and what happened instead. Name the report or portfolio if it concerns a specific one. A screenshot is optional but usually saves a round of questions.
| Category | Use it when… |
|---|---|
| Bug | Something is broken or not behaving as expected. |
| Login | You or a teammate cannot sign in, or have access problems. |
| Data | A number, chart or report looks wrong, incomplete or out of date. |
| Feature | You want something added or improved — a new chart, a layout change, a different cut of the data. |
| Onboarding | You need help getting set up, or getting a new teammate started. |
| Account | Questions about your account, plan or billing. |
| Other | Anything that does not fit the categories above. |
What happens next
Your request becomes a ticket with its own reference number and appears on your dashboard within moments. The right person picks it up based on the category you chose. Replies arrive in the email inbox you use to sign in; reply to that email to continue the conversation.
Tracking requests
The Support Tickets card on your home page lists recent tickets for your whole team, so everyone can see what has already been raised and by whom — useful when three people notice the same thing. Each row shows the number, subject, who raised it, the date and a status. Click one to expand its summary.
| Status | Meaning |
|---|---|
| Open | We have received it and it is with our team. |
| Waiting | We have replied — check your email. We may be waiting on your answer. |
| Resolved | Closed. If the problem returns, reply to the email thread and it reopens. |
The badge on the card counts tickets updated since you last looked, and takes the colour of the most urgent one.
Common questions
- Who can see our tickets? — Everyone in your organisation sees your team’s tickets, along with who raised each one. Other organisations can never see them.
- I did not receive a reply — Replies go to the address you use to sign in. Check that inbox and its spam folder — the status turns to Waiting when a reply has been sent.
- Can I reopen a resolved ticket? — Yes. Reply to the original email thread and the conversation continues.
- A chart is rendering empty — Usually something it compares against is not configured. Check Why a chart is empty first — it resolves most cases without a ticket.
- How do I ask for something new? — Raise it as a Feature request and describe what you want to show rather than how to build it. If it can be a standard component we will build it that way, which means everyone gets it and it stays supported.
---
# Component library
74 components. Each entry: display name, system code, where it can be placed, API availability, what it needs configured, description, caveats and presentation options.
The same data is in docs/platform-documentation.components.json with keys: n name, c code, cat category, pl placement, api array, use adoption band, need array of requirements, d description, note caveat, o options, dep retired flag.
No formulas are included, by decision — see constraint 2 above.
Allocation (4)
Asset Allocation Chart — asset_allocation_chart _Report_
Pie or donut chart of the portfolio's allocation across asset classes. Each slice is that asset class's share of the total portfolio value, and the slices should always add to 100%. It is dynamic — the weights shown match the report date. Asset classes are tagged against investments and created once during setup; slice colours come from the entity theme's first palette.
Options: Decimal places. Default: 1.; Sort order — Weight (largest first) or Asset Class (alphabetical). Default: Weight.
Asset Allocation Table — asset_allocation_table _Report_
Detailed asset-allocation table with optional neutral, range and target columns. Current values match the Asset Allocation Chart. Target, Neutral and Min–Max come from the portfolio's own settings and are static — they do not move with the report date, because a strategic allocation should change infrequently.
Options: Decimal places. Default: 1.; Neutral column. Default: on.; Range column. Default: on.; Excess Neutral column. Default: off.; Excess Target column. Default: off.; Target column. Default: off.; Show zero-weight rows. Default: off.
Excess vs Neutral — excess_neutral_chart _Report_
Chart of actual allocation against the neutral position. Bars to the right mean the portfolio is holding more than neutral, bars to the left mean less. Asset classes with no neutral set are left out.
Options: Decimal places. Default: 1.; Always show every row. Default: off.; Sort order. Default: by asset class.
Neutral Allocation — neutral_allocation_chart _Report_
Chart of the neutral — strategic — asset allocation. These are configured values, and they are the reference point the Excess vs Neutral chart measures against.
Options: Decimal places. Default: 1.; Always show every row. Default: off.; Sort order. Default: by asset class.
Holdings (7)
Holdings Table — holdings_table _Report_
A flat, single-level list of every holding and its weight, with no return columns. Because it simply answers “what is held and how much”, it is the standard holdings disclosure for advice documents and for plain client or portfolio statements where fund performance is not the focus.
Options: Show zero-weight rows. Default: off.; Decimal places. Default: 1.; Sort order. Default: A–Z.
Holdings by Rank — holdings_rank_table _Report · REST API_
Holdings ranked by weight and limited to the top N. Same weights as the Holdings Table, sorted largest first and cut off. Because it is a top N cut, the shown weights add to less than 100% unless the total row is switched on.
Options: Decimal places. Default: 1.; Show the largest. Default: 10.
Underlying Investments Table — underlying_investment_table _Report_
Lists the portfolio's underlying investments with their weights alongside selected return periods, from 1 month through 10 years and inception. It pairs “what is held” with “how each line performed” in one table, which makes it the workhorse of quarterly portfolio reports and client reviews.
Options: Decimal places. Default: 1.; Sort order. Default: A–Z.; Hide weight column. Default: off.; Return columns — Auto-fit to the track record, or pick from 1m, 3m, 6m, 9m, 1y, 2y, 3y, 5y, 7y, 10y and Inception. Default: custom columns.
Underlying Comparison — underlying_comparison_table _Report · needs Benchmark_
Period-over-period change in underlying holdings, with each investment shown next to its own benchmark, so you can see whether it beat the index it is meant to beat.
Needs a benchmark set against each underlying investment. Investments without one show no comparison.
Options: Decimal places. Default: 1.; Sort order. Default: biggest change.; Compare over. Default: quarterly.; How many rows. Default: 15.; Minimum change — hides a holding unless it moved at least this much. Default: 1.
Top Equities — top_equities_all_table _Report_
Top directly-held equities across all markets. These are shares the portfolio owns in its own name, not shares held inside a managed fund — a holding counts as direct if it is in the listed-security universe and is not a managed fund. Kept separate from the look-through tables on purpose, so shares that were picked do not get mixed with shares a fund happens to own.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Add a total row. Default: off.; Keep the real weights. Default: off.; Columns to show. Default: weight, country and sector.
Top Australian Equities — top_equities_australia_table _Report_
Top directly-held domestic equities — shares owned in the portfolio's own name, not through a fund.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Add a total row. Default: off.; Keep the real weights. Default: off.; Columns to show. Default: weight, country and sector.
Top International Equities — top_equities_international_table _Report_
Top directly-held international equities — shares owned in the portfolio's own name, not through a fund.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Add a total row. Default: off.; Keep the real weights. Default: off.; Columns to show. Default: weight, country and sector.
Exposure (12)
Country — country_exposure_chart _Report · REST API · RETIRED_
Portfolio exposure by country, top N. Country exposure is taken from the domicile of each underlying holding, weighted by its size, then aggregated to fund and portfolio level. Everything outside the tracked list is grouped as “other”.
Deprecated. Use Country (Full Weight) instead, which handles unmapped and cash holdings differently. This one is kept only so existing templates keep rendering.
Options: Show the largest. Default: 10.; Decimal places. Default: 1.; Full Allocation mFunds — rescale slices to 100%. Default: off.
Credit Quality — credit_quality_chart _Report · REST API · needs Look-through data_
Fixed-income exposure by credit-quality band. Each bond's rating is converted into a historical default rate, those are weighted across the portfolio, and the average is mapped back to a letter grade and banded High, Medium or Low. Working in default-rate terms rather than averaging letter ratings means the figure reflects actual default risk, and correctly penalises portfolios that mix very high- and very low-rated bonds. Two bond portfolios can post the same return on very different credit risk — this is what shows it.
Options: Decimal places. Default: 1.
Market Cap — market_cap_chart _Report · REST API · needs Look-through data_
Equity exposure by market-capitalisation band. Each stock is placed into a size bucket — giant, large, mid, small or micro — based on where it sits within the total market cap of its region, not on fixed dollar thresholds. Giant is the top 40% of a region's cumulative market cap, large the next 30%, mid the next 20%, small the next 7%, micro the smallest 3%.
Options: Decimal places. Default: 1.
Sector — sector_exposure_chart _Report · REST API · needs Look-through data_
Breaks the portfolio's equity exposure down by sector on a look-through basis, showing the top N. It answers “where is the equity risk concentrated” — what advisers and asset consultants look for in quarterly reports, fact sheets and due-diligence packs. Three different domestic equity funds can all be full of the same banks, and this is where that shows up.
Options: Show the largest. Default: 10.; Decimal places. Default: 1.; Full Allocation Sectors — rescale slices to 100%. Default: off.; Chart style. Default: default style.
Sector vs Benchmark — sector_exposure_benchmark_chart _Report · needs Benchmark, Look-through data_
Sector exposure shown against the benchmark, with the gap between the two. Shows where the portfolio is deliberately different from the index.
Needs a benchmark with look-through sector data. Without one there is nothing to compare against and the widget will not render.
Options: Benchmark code. Default: none.; Decimal places. Default: 1.; Sort by. Default: weight.; Sector labels — Morningstar or GICS naming. Default: Morningstar.; Show zero-weight sectors. Default: off.; Group unrecognised as Others — puts cash and unclassified holdings in an Others bucket instead of dropping them. Default: off.
Industry (equities only) — equities_industry_chart _Report · REST API · needs Look-through data_
Industry exposure for the equity sleeve only, at a finer level than sectors. Percentages are shares of the equity sleeve, not of the whole portfolio.
Options: Applies to equity sleeves only — listed equities across all global markets.
Sector (equities only) — equities_sector_chart _Report · REST API · needs Look-through data_
Sector exposure for the equity sleeve only, so the numbers are not diluted by bonds and cash. This is the fairer comparison against an equity index — whole-of-portfolio sector weights on a balanced portfolio always look light next to a broad domestic equity index.
Options: Applies to equity sleeves only — listed equities across all global markets.
Top Holdings (look-through) — top_holdings_table _Report · REST API · needs Look-through data_
Top holdings on a look-through basis. Looks inside each fund to the individual companies it holds, so a client holding four funds that each own the same bank sees one combined line rather than four hidden ones.
Rescaled weights read as a share of the looked-through portfolio; unrescaled they are a share of the whole portfolio.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Country column. Default: on.; Sector column. Default: on.; Show total. Default: off.; Don't rescale weights — on gives a share of the whole portfolio, off a share of the equity sleeve. Default: off.; Weight column. Default: on.
Top Australian Shares — top_australian_shares_table _Report · REST API · needs Look-through data_
Top Australian shares on a look-through basis. Same calculation as Top Holdings, restricted to companies listed in the domestic market — Australia, in the standard configuration.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Country column. Default: on.; Sector column. Default: on.; Show total. Default: off.; Don't rescale weights. Default: off.; Enable direct equities — also lists directly held shares the look-through misses. Default: off.; Weight column. Default: on.
Top International Shares — top_international_shares_table _Report · REST API · needs Look-through data_
Top international shares on a look-through basis. The same calculation, restricted to companies listed outside the domestic market.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Country column. Default: on.; Sector column. Default: on.; Show total. Default: off.; Don't rescale weights. Default: off.; Enable direct equities. Default: off.; Weight column. Default: on.
Top Aggregated Equities — top_aggregated_equities_table _Report · REST API · needs Look-through data_
Top equities aggregated on a look-through basis, domestic and international together, with holdings in the same company combined into one line.
Options: Show the largest. Default: 10.; Decimal places. Default: 2.; Add a total row. Default: off.; Keep the real weights — on gives a share of the whole portfolio, off rescales to 100%. Default: off.; Columns to show. Default: weight, country and sector.; Include direct shares. Default: off.
Country (Full Weight) — full_weight_country_chart _Report · REST API · needs Look-through data_
Country exposure using full, un-rescaled weights, so the percentages are shares of the whole portfolio rather than of the part that could be mapped. Full-weight keeps unmapped and cash-like holdings in the denominator, so no single country is overstated. Use this rather than the deprecated Country chart.
Options: Show the largest. Default: 10.; Decimal places. Default: 1.
Performance (18)
VAMI — vami_chart _Report · REST API · Client API_
Plots the growth of a nominal investment — typically $100,000 — over time for the fund and its benchmark. The classic “value of $10k” line, and the most recognisable performance visual there is: it appears on almost every fact sheet and in quarterly and pitch materials to show cumulative track record at a glance. This static-render version is PDF-friendly and supports custom start dates and starting amounts.
Options: Lock to the report date. Default: off.; Starting amount. Default: $100,000.; Fund only. Default: off.; No hover pop-ups. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.
VAMI (interactive) — vami_js_chart _Sub-report · REST API_
Interactive growth-of-$X chart with hover read-outs. Benchmarks are drawn on the same axis from the same starting amount. A slider zooms the time axis.
Options: Not user-configurable. A slider zooms the x-axis range.
Cumulative Returns Chart — cumulative_returns_chart _Report_
Cumulative return line chart — the same shape as VAMI but in percentage terms from a zero start, rather than in dollars. Use it where quoting a dollar figure would imply an actual investment amount.
Options: Lock to the report date. Default: off.; Fund only. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.
Performance Summary Table — performance_summary_table _Both · REST API_
Table of returns over selected periods against the performance benchmarks assigned on the portfolio. The standard performance block for almost every report.
Growth and Income lines only render when income data is present, either from ETL processing where weights data exists, or from a custom data integration.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return columns.; Growth. Default: on.; Income. Default: on.; Excess returns. Default: off.; Require returns through the reporting period. Default: on.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.
Performance Summary Chart — performance_summary_chart _Report · REST API_
Bar chart of returns over standard periods, with the benchmark beside each bar. Periods of a year or more are annualised, which is why the labels read “3 Yrs p.a.” rather than “3 Yrs” — that makes a 3-year and a 5-year figure directly comparable.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return columns.; Growth. Default: off.; Income. Default: off.; Require returns through the reporting period. Default: on.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.
Monthly Performance — monthly_performance_table _Both · REST API_
A month-by-month grid of returns in a calendar layout, giving a granular view of consistency and of the best and worst months. It suits detailed quarterly reports, fund updates and IC papers where a single performance line is not enough.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Colour style. Default: standard.
Monthly Performance vs Benchmark — monthly_performance_benchmark_table _Report · needs Benchmark_
Monthly return grid including the benchmark, so every month can be read as a win or a loss against the index.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Colour style. Default: standard.
Monthly Returns Chart — monthly_returns_chart _Sub-report_
Bar chart of monthly returns, each month as its own bar in date order, with the benchmark alongside. Nothing is compounded or averaged — it is the raw monthly series.
Options: Not user-configurable. A slider zooms the x-axis range.
Annual Performance — annual_performance_chart _Both · REST API_
Annual return bar chart, one bar per calendar year, usually with the benchmark beside it.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; Colour theme. Default: main.
Annual Summary — annual_summary_table _Report_
Returns summary table with calendar-year columns alongside period columns. The current year is partial until December.
Options: Decimal places. Default: 1.; Years shown. Default: 5.; Period columns — Auto-fit, or pick from YTD, 1m, 3m, 6m, 9m, 1y, 2y, 3y, 5y, 7y, 10y, Incep p.a. and Since Inception. Default: auto-fit.; Growth. Default: off.; Income. Default: off.; Excess returns. Default: off.; Calendar Yrs Last — put calendar-year columns after the period columns. Default: off.; Calendar Yrs Ascending — oldest to newest, left to right. Default: off.; Calendar Yrs Only. Default: off.; Enable partial returns — show years without full returns. Default: off.; Require returns through the reporting period. Default: off.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.
Financial Summary — financial_summary_table _Report · Client API_
Returns summarised on the fiscal year configured for your market rather than the calendar year — a year running 1 July to 30 June, for example. Where clients are taxed and reported to on a fiscal year, calendar-year figures make them do a mental translation. An incomplete current year is labelled year-to-date.
Client API access to this widget is available on request.
Options: Decimal places. Default: 1.; Years shown. Default: 5.; Period columns — Auto-fit or custom. Default: auto-fit.; Growth. Default: off.; Income. Default: off.; Excess returns. Default: off.; Hide the widget heading. Default: on.; FY Last — put financial-year columns after the period columns. Default: off.; FY Only. Default: off.; Enable partial returns. Default: off.; Require returns through the reporting period. Default: off.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.
Financial Returns — financial_returns_table _Report · Client API · needs Benchmark_
Returns by fiscal year, with the benchmark and the excess return beside each year. An incomplete year is labelled year-to-date.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Fund only. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; Financial years shown. Default: 5.; Show extra return. Default: off.
Financial Years — financial_years_table _Report · Client API_
Fiscal-year performance table with an annualised summary row, so a long record reads both year by year and as a whole. The annualised row is the compound average yearly rate — the single rate that would have produced the same total.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Fund only. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; Financial years shown. Default: 5.; Show extra return. Default: off.
Financial Performance — financial_performance_table _Report · REST API_
Fiscal-year performance over time for a single series, newest first or oldest first. A partial current year shows as year-to-date.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Smallest first. Default: off.; Colour style. Default: standard.
Total Return Summary — total_return_summary_table _Sub-report · REST API_
Total-return summary since inception — the compounded return over the full history, not converted to a yearly rate. Use it where the cumulative figure is the point; annualised numbers understate the headline on a long track record.
Options: Not user-configurable.
Performance by Frequency — performance_by_frequency_chart _Report_
Returns aggregated by a chosen frequency — monthly, quarterly or yearly — so the same history can be shown at whatever level of detail suits the report. Incomplete periods at either end are marked and can be hidden.
Options: Decimal places. Default: 2.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Include the current period. Default: off.; Group by. Default: monthly.
Average Returns — average_returns_chart _Report · needs Benchmark_
Average returns by period. Three bars: the average month overall, the average month when the market rose, and the average month when the market fell. Up and down are set by the benchmark's month, not the portfolio's — so these really are “when the market rose and fell”.
Options: Decimal places. Default: 2.; Require returns through the reporting period. Default: off.; Disable hover — handy for PDFs. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.
Risk Summary Table — risk_summary_table _Report · needs Benchmark_
Table of returns over selected periods against risk benchmarks. The same calculation as the Performance Summary table; only the comparison series differ. Use it where the portfolio is judged against a CPI-plus or cash-plus objective rather than a market index.
Needs risk benchmarks configured on the model.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return columns.; Growth. Default: on.; Income. Default: on.; Excess returns. Default: off.; Require returns through the reporting period. Default: on.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: Default Start.
Risk (21)
Drawdown — drawdown_chart _Report · REST API_
Charts peak-to-trough declines over time for the fund against its benchmark and peers, so readers see how deep losses got and how long recovery took. A core downside-risk visual for quarterly reports, investment-committee and board packs, and consultant due diligence, where audiences care as much about losses as returns. The line sits at zero whenever the portfolio is at a new high, and dips whenever it is under water.
The peak is floored at the starting value here, so this chart measures losses from the higher of the start and the previous high. The Max Drawdown figure in the summary tables does not floor it, so the two can differ.
Options: Decimal places. Default: 1.; Require returns through the reporting period. Default: on.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: default start.; Colour theme. Default: main report.
Drawdown Wide Chart — drawdown_wide_chart _Sub-report_
Wide-format drawdown chart for the sub-report layout. Same calculation as the Drawdown chart, drawn full width so long histories stay readable.
Options: Not user-configurable. A slider zooms the x-axis range.
Drawdown Summary Table — drawdown_summary_table _Sub-report · REST API_
Table of the largest drawdown episodes — the worst peak-to-trough fall over each standard period, from 1 month out to since inception. Shown as a negative percentage. A window only produces a figure if there are enough months to fill it; otherwise it shows a dash.
Options: Not user-configurable.
Return Risk Report — return_risk_report_table _Both · REST API_
Return and risk statistics across return, standard deviation and drawdown windows, so performance is read next to the risk taken to get it. One row per series.
This table compounds through 12 months and only annualises from 24, which is why the column reads “2 Yrs Ave. Return”. Most other tables switch at 12.
Options: Decimal places. Default: 1.; Columns to show. Default: the standard set.; Lock to the report date. Default: off.; Start date. Default: the usual start.
Volatility Summary Table — volatility_summary_table _Sub-report · REST API_
Volatility statistics over each standard period from 3 months out to since inception, so you can see whether the fund is getting calmer or rougher. The square root of 12 converts a monthly figure to an annual one, which is the convention everyone quotes.
Whether the sample formula (divide by n-1) or the population formula (divide by n) is used is an account-level setting.
Options: Not user-configurable.
Volatility Chart — volatility_chart _Sub-report_
Volatility over time with 1 year, 3 years, 5 years and since inception all plotted on one chart. The 1-year line moves quickly, the 5-year line is smooth, and the inception line uses a window that grows with the history.
Options: Not user-configurable. A slider zooms the x-axis range.
Rolling Volatility 1 Chart — rolling_volatility_1_chart _Sub-report_
Volatility calculated over a moving window and drawn as a line, so risk rising and falling through time is visible rather than blended into one average. The line only starts once there are W full months of history, so a partly filled window shows nothing rather than a misleading figure.
Options: Not user-configurable.
Rolling Volatility 2 Chart — rolling_volatility_2_chart _Sub-report_
The same calculation as Rolling Volatility 1 with a different window length, so a short and a long horizon can sit on the same page. A short window reacts fast to current conditions and a long one shows the underlying trend — where they diverge is the interesting part.
Options: Not user-configurable.
Sharpe Ratio Summary Table — sharpe_ratio_summary_table _Sub-report · REST API · needs Risk-free rate_
Sharpe ratio over standard periods. Sharpe is return above cash per unit of bumpiness, so it asks whether the return justified the ride. Higher is better.
Needs a risk-free rate but not a benchmark, because Sharpe measures against cash rather than an index.
Options: Not user-configurable.
Performance Measure — performance_measure_table _Report · needs Risk-free rate, Benchmark_
Risk-adjusted performance statistics computed against a chosen risk-free rate, by default a central-bank cash rate. Aimed at more technical audiences: investment-committee and board packs, consultant due diligence and institutional mandate reviews. The measures are annualised standard deviation, Sharpe, Sortino and Beta.
It does not compute alpha, despite what the label suggests. Sortino here measures the downside against the benchmark while the numerator is measured against the risk-free rate, so read it as reward for the risk of trailing the index. Sharpe and Sortino need a risk-free rate; Sortino and Beta need a benchmark. With no benchmark set, only volatility and Sharpe appear. Periods under 12 months are not annualised.
Options: Decimal places. Default: 2.; Columns to show — 1m, 3m, 6m, 9m, 1y, 2y, 3y, 5y, 7y, 10y and Incp p.a.; Require returns through the reporting period. Default: off.; Start date — Default Start, Inception Start or Custom Start. Default: Default Start.
Performance Consistency & Risk Table — performance_consistency_and_risk_table _Report · needs Benchmark_
Consistency and risk metrics. This is the widget that calculates the real up-market and down-market capture ratios: up capture asks how much of the market's rise the portfolio got, down capture how much of the fall it took. The ideal is high up capture with low down capture — a fund at 90% up and 60% down gives up a little in rallies to lose much less in falls.
Capture, success rate and tracking error are all comparisons and show a dash without a benchmark, leaving only the positive and negative month counts. Months where either series is missing are dropped, and a capture ratio built on three down months is not evidence of much.
Options: Decimal places. Default: 1.; Performance consistency columns — up market capture, down market capture, positive monthly return, negative monthly return, success rate.; Risk columns — 3Y / 5Y / since-inception standard deviation, and 3Y / 5Y / since-inception max drawdown.; Require returns through the reporting period. Default: off.; Start date. Default: Default Start.
Capture Vs Benchmark Up Chart — capture_vs_benchmark_up_chart _Sub-report · needs Benchmark_
Despite the name, this is not the up-market capture ratio. It takes the portfolio's eight best months and plots what the benchmark did in each of those same months, side by side. No ratio is calculated. For the actual up-capture ratio, use the Performance Consistency & Risk table.
Options: Decimal places. Default: 2.; Up or down markets — up uses the best months, down the worst. Default: up.; Lock to the report date. Default: off.; Start date. Default: the usual start.
Capture Vs Benchmark Down Chart — capture_vs_benchmark_down_chart _Sub-report · needs Benchmark_
Despite the name, this is not the down-market capture ratio. It takes the portfolio's eight worst months and plots what the benchmark did in each of those same months. No ratio is calculated. A fund that has never had a down month produces an empty chart.
Options: Decimal places. Default: 2.; Up or down markets. Default: down.; Lock to the report date. Default: off.; Start date. Default: the usual start.
Distribution of Monthly Returns — returns_distribution_chart _Sub-report_
Histogram of periodic returns. Each month is dropped into a 1% band, from worse than -10% up to 10% and above, and the bar height is the count of months in that band. Empty bands at the ends are trimmed off. It shows the shape of the risk rather than its size — a single standard deviation figure hides a fat left tail, this does not.
Needs enough history to be meaningful — a two-year fund only has 24 months to spread across the bands.
Options: Not user-configurable. A slider zooms the x-axis range.
Risk Return 1 — risk_return_1_chart _Both_
A risk-versus-return scatter that plots the fund and its comparators by volatility (x) and return (y) over a rolling window, so relative efficiency is visible at a glance. Useful in quarterly reviews, manager research and consultant reports to argue that a fund earns its risk. Defaults to the since-inception period, so it is the long-run view.
Options: Decimal places. Default: 2.; Time window. Default: 99.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; No hover pop-ups. Default: off.; Smoothing. Default: 5.; Show labels. Default: off.; Chart style. Default: standard.; Swap the axes. Default: off.
Risk Return 2 — risk_return_2_chart _Both_
The same calculation as Risk Return 1, defaulting to the last 12 months rather than since inception. Pair it with Risk Return 1 to show whether recent behaviour is normal for this fund.
Options: Decimal places. Default: 2.; Time window. Default: 12.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; No hover pop-ups. Default: off.; Smoothing. Default: 5.; Show labels. Default: off.; Chart style. Default: standard.; Swap the axes. Default: off.
Risk Return Comparison Chart — risk_return_comparison_chart _Sub-report_
Risk versus return scatter: risk across the bottom, return up the side, one dot per series. Up and to the left is more return for less risk. Both axes use the same window, so the dots are directly comparable.
Needs comparison series to be worth showing.
Options: Not user-configurable.
Correlation VS Benchmark Chart — correlation_vs_benchmark_chart _Sub-report · needs Benchmark_
Rolling correlation of the fund against the first assigned benchmark, tracked over time. 1.0 means they move in lockstep, 0 means no relationship, negative means they tend to move in opposite directions. Useful for checking a fund is still doing its job: a diversifying manager whose correlation has crept up to 0.9 is not diversifying any more.
Options: Not user-configurable. A slider zooms the x-axis range.
Correlation Since Inception Table — correlation_matrix_table _Sub-report_
Correlation matrix across series. Reading down a column shows which holdings move together and which move independently; the diagonal is always 1. It regularly shows that funds bought for variety are near-duplicates.
Only months where every series has data are used, and any series with fewer than 12 months of history is left out entirely.
Options: Not user-configurable.
Statistics Performance Table — statistics_performance_table _Sub-report_
A one-column list of the portfolio's returns, volatility and worst losses over the standard windows, plus the total return since inception. Covers the portfolio only, not benchmarks.
Options: Not user-configurable.
Statistics Success Table — statistics_success_table _Sub-report_
Success and hit-rate statistics: how often the fund makes money, how much it typically makes when it wins, how much it loses when it loses, its best and worst periods, and its longest winning and losing streaks. Shown for months, and again for calendar years. No benchmark needed — every figure here is about the fund on its own.
A month of exactly 0.00% counts as a losing month, because the test is strictly greater than zero.
Options: Not user-configurable.
Peers (4)
Performance vs Percentile — performance_vs_percentile_table _Report · needs Benchmark_
Fund returns against percentile bands. Shows the comparison group's 5th, 25th, median, 75th and 95th percentile returns, then places the portfolio among them and reports its quartile.
Q1 is the best quartile. Percentiles are ranked on return alone, so a top-quartile fund is not necessarily a well-run one — it may just have taken more risk. Needs a comparison group and will not render with only one series.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return rows.; Require returns through the reporting period. Default: on.; Number of lines. Default: all series.; Start date. Default: Default Start.
Risk Return (Peers) 1 — risk_return_peers_1_chart _Report · needs Peer group_
Risk and return scatter against a peer group, so the portfolio's dot sits in a cloud of comparable funds rather than against an index. Peers face the same constraints and the same market, so it is a closer comparison than an index.
Options: Decimal places. Default: 2.; Time window. Default: 99.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Number of lines. Default: 0.; Pick exact lines. Default: none.; No hover pop-ups. Default: off.; Smoothing. Default: 5.; Show labels. Default: off.; Chart style. Default: standard.; Swap the axes. Default: off.
Peers Summary — peers_summary_table _Report · needs Peer group_
Table of returns over selected periods against peer group benchmarks. The same calculation as the Performance Summary table, with peer funds as the comparison rows.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return columns.; Growth. Default: on.; Income. Default: on.; Excess returns. Default: off.; Require returns through the reporting period. Default: on.; Portfolio only. Default: off.; Number of lines. Default: all series.; Start date. Default: Default Start.
Performance vs Peers Percentile — performance_vs_peers_percentile_table _Report · needs Peer group_
Fund returns against peer percentile bands, with the group's percentile spread alongside.
Needs a peer group with enough members for percentiles to mean anything — a quartile of six funds is not a robust ranking.
Options: Decimal places. Default: 1.; Auto-fit to available history.; Return rows.; Require returns through the reporting period. Default: on.; Number of lines. Default: all series.; Start date. Default: Default Start.
Attribution (6)
Contributors Table — underlying_investment_contributors_table _Report_
Top positive contributors to return for a chosen period — most often 1 month for factsheets, sometimes 3 months for quarterly reports. An investment appears here by doing well, by being a big position, or both: a small holding that soared can contribute less than a large holding that only did moderately well. For periods over 1 month only current investments are shown, so sold positions are excluded, as is any investment with late or lagged data.
Options: Decimal places. Default: 2.; Show the largest. Default: 5.; Ranking period. Default: 1 month.
Detractors Table — underlying_investment_detractors_table _Report_
The Contributors table in reverse — the holdings that cost the portfolio most over the period. A big losing position costs more than a small one. The same exclusions apply: for periods over 1 month, sold investments and any with lagged data are left out.
Options: Decimal places. Default: 2.; Show the largest. Default: 5.; Ranking period. Default: 1 month.
Asset Class Contributions Table — underlying_investment_asset_class_contributions_table _Report_
Weighted contributions of investments, aggregated to the asset sleeve. Shows how much of the portfolio each asset class was, what it returned, and how much of the portfolio's return came out of it.
Options: Decimal places. Default: 1.; Sort order. Default: Order.; Ascending — low to high instead of high to low. Default: off.
Contribution — contribution_table _Report_
Return contribution by holding, worked out from actual dollar movements rather than from weight times return. This is the more accurate version when money moved in or out during the month, because a weight-times-return estimate drifts when the portfolio changed size.
Needs dollar-level asset performance data, not just percentage returns.
Options: Decimal places. Default: 2.; Sort order. Default: by name.
Performance Attribution — performance_attribution_chart _Report_
Brinson performance-attribution chart: which asset classes drove the return, period by period. Bars above the line added to the return, bars below took away from it.
Needs attribution data with holdings mapped to an asset class or sub-category.
Options: Use staging data. Default: off.; Data source. Default: platform.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Group by. Default: sub-category.; Group by year — chains the monthly figures into yearly ones. Default: off.; Decimal places. Default: 2.
Investment Exposure — investment_exposure_chart _Report · Client API_
Investment exposure over time. Stacked bands showing how the asset-class mix has shifted, so you are watching the composition change rather than the value. Bands stack to 100%, and anything not covered by a recognised asset class is grouped into Other so the stack always adds up.
Options: Use staging data. Default: off.; Data source. Default: platform.; Lock to the report date. Default: off.; Start date. Default: the usual start.; Group by. Default: sub-category.; Decimal places. Default: 2.
Custom (2)
Custom Widget — widget_field_N _Dynamic field_
A widget you author yourself, storing values per period date with one or more render configurations, inserted into a report as a dynamic field. There is no fixed calculation — whatever it holds is what it shows. Use it for commentary, disclaimers, outlooks and anything else that has to be written by a person rather than calculated.
Options: No set options — it shows whatever its saved setup says.
SQL Widget — sql_widget_field_N _Dynamic field_
A widget backed by a query against your own data, using [model_code] and [period_date] shortcodes, with the render type chosen per configuration — pie chart, horizontal bar, table and others. The query decides the numbers, so any formula lives in the query rather than in the platform.
None of the return, risk or weighting rules described elsewhere in this catalogue apply unless the query implements them itself, and its numbers are not covered by the platform's calculation logic or tests. Treat a SQL widget as needing its own review.
Options: No set options — it shows whatever its query and chosen style say.