Scoped buyer / service brief

Supervised fund document production for Fund administrators & ETF ecosystems

Fee and risk section production

Illustrative business photography, not our office or a client reference

The business-specific assignment

Use a specialist-approved section checklist and reconcile every fee-note relationship. Treat missing performance language as an issue for the review owner.

Your coordinator: Fund operations and compliance production coordinators.

The source context may include prospectus sections, fee tables, expense examples and risk narratives.

Illustrative production scenario

A fee waiver expiry date may belong to one class only; sharing a layout does not make the underlying disclosure identical.

This is an example of the control to test, not a measured client result or an accepted filing. Ask the named reviewer to define success before production starts.

Inputs and outputs

Provide these inputs:

  • Approved fund disclosure and asset set
  • Confirmed fund/series/class details and form scope
  • Fund specialist’s presentation and tagging checklist

A scoped handoff can contain:

  • Agreed section production and proof
  • Fee, expense-example and narrative comparison sheet
  • Fund-specific issue and review log

Review focus

  • Check every disclosed expense-example horizon and related assumptions.
  • Keep fee-waiver notes and narrative relationships with their correct tables.
  • Treat 485BPOS/497, N-CSR/TSR and N-PORT as separately scoped workflows.

Fund counsel, administrators and qualified tagging specialists retain disclosure and taxonomy approval.

What is outside this assignment

Fund taxonomy choices and requirements need qualified review; online/XML forms are not generic Word-to-iXBRL jobs.

Specialist work is conditional; begin with a reviewed section pilot rather than blanket fund coverage.

Plan the handoff

Agree source freeze, version naming, one instruction stream, correction allowance and escalation contact. Confidential materials belong only in the separately approved transfer route.

Read the full service scope → · Return to your business →

Google optional storage is denied by default. These controls send Google consent signals and remember your choice for up to 180 days. They do not block third-party script loading or control Jotform chat. Tags inside Tag Manager must be configured to respect consent.

Read the storage and integration inventory. Do not share confidential files or credentials in the chat.