Quant Reports

08Guides

How we work together

The most useful thing to understand about Quant Reports is that it is not software you are left alone with. It is a service with software in it. The heavy, structural work is ours; the judgement is yours; and the reporting cycle is a series of handoffs between the two.

This is deliberate. The parts we keep — template construction, data connection, calculation, new components — are the parts where a mistake propagates across every report at once. The parts you keep are the parts only you can do: what this period meant, which portfolios go out, and whether it is right to send.

Setting up

Onboarding is a collaboration, not a self-service form. Working from your existing reports, we build the thing you already send — then improve it.

  1. Take your current reports apart _(We do this)_ — You send the pack you produce today. We work out what every page, chart and figure is, which are calculated and which are written, and what has been carried forward by habit rather than need.
  2. Connect your data _(We do this)_ — We establish how holdings and returns will reach us each period and confirm the figures reconcile against what you produce today, before anything is reported on.
  3. Build the template _(We do this)_ — We construct the layout, apply your branding, and select the charts and tables that reproduce your report — then show you where the automated version can go further than the manual one did.
  4. Review and sign off _(You do this)_ — You check the output against your own, line by line, on real portfolios and real history. Discrepancies get explained or corrected before go-live, not after.
  5. Roll it out _(We do this)_ — The approved template is applied across every portfolio it fits. This is where the effort of getting one report right pays for itself.

The recurring cycle

Once you are live, each period follows the same shape.

  1. Data lands and reports rebuild _(We do this)_ — New holdings and returns arrive, are checked, and every report regenerates against them. You do not trigger this and you do not wait on anyone internally for it.
  2. Add the commentary _(You do this)_ — Market commentary, portfolio commentary, outlooks, anything that needs a person. This is the substantive work left in a reporting cycle, and it is the point of automating everything else.
  3. Review _(You do this)_ — Read the pack as your client will. Check the commentary reads correctly against the figures beside it, and that nothing looks wrong.
  4. Approve and distribute _(You do this)_ — Approve the reports and send them, or publish them where your clients read them.
  5. Handle anything structural _(We do this)_ — A new portfolio, a changed benchmark, a layout change, a chart you want that does not exist yet — it comes to us and we make it, usually well within the cycle.

Where the line sits

A rough division, though it is not rigid — if you want more control over any of the right-hand column, ask.

Yours to change, any time

  • Commentary, outlooks and written content
  • Images and photography in a report
  • Text fields shared across reports — disclaimers, contact details, standing notes
  • Which reports are produced and when they go out
  • Approving and distributing
  • Per-report presentation options, if you want them

Ours to build and maintain

  • Templates, layout and branding
  • Data connection, validation and reconciliation
  • Portfolio, benchmark and peer-group configuration
  • Which charts and tables appear, and how they are configured
  • New components when the library does not cover something
  • Calculation conventions and their consistency

The short version — If it is a sentence, an image or a decision, it is yours. If it is structure, data or arithmetic, it is ours. When you are not sure, ask — we would rather make the change than have you work around it.