Skip to content

Fund admin · Fund · As needed

Custom report request

A report Infra One doesn’t produce yet is built, run, checked against the books and sent to whoever asked, then kept as a template for every quarter after.

PlanCustom report request

  1. Write the report’s spec

    Held

    Operator checks that no existing report or template fits, then writes the spec for the new report and its template from the request.

    Operator
  2. Approve the spec

    Held

    An accountant on the fund admin team reviews the spec before anything is built.

    PersonAccountant approves
  3. Build the report

    Held

    Infra One adds the report to the platform as a code change. The plan holds until it merges and the report is live.

    BuildWaits an hour after the merge
  4. Run it for the quarter

    Held

    Creates the report’s template on the fund’s books and saves a run for the quarter that was asked for.

    API actionFund admin confirms
  5. Tie it to the books

    Held

    Operator ties the run’s totals to the trial balance and lists any difference.

    Operator
  6. Check the numbers

    Held

    An accountant reviews the run and the tie-out and signs off before it goes out.

    PersonAccountant approves
  7. Send it to whoever asked

    Held

    The report goes into the data room, and the person who asked gets a private link to it by email.

    API actionFund admin confirms

The plan as it runs: each step waits for the one before it, and stops at its gate until the owner approves.

At a glance

Who runs it, and when

Who runs it
Fund admin
What starts it
You or one of your LPs asks for a report the ledger doesn’t offer yet.
How often
As needed
Vehicle
Fund

Ask Operator

Start it in a sentence

Ask Operator in chat. It drafts the plan for your fund, and nothing runs until you release it.

  • You

    An LP wants quarterly fees broken down by portfolio company; build that report for Fund II.

  • You

    We need a capital account roll by feeder for Fund I; we don’t have that report.

  • You

    Add a fees-by-company report to the ledger and run it for Q3.

The outcome

The new report is on the platform, its first run ties to the trial balance, whoever asked has a link, and it is ready for next quarter.

What it proves

  • Adds a missing report to the platform as a code change, and waits for it to merge and go live.
  • Builds nothing until the spec is approved, and sends nothing until a fund admin confirms it.
  • Ties the first run to the trial balance before anyone outside sees it.
  • Lets a person take over a build that gets stuck.
  • Shows a junior the run’s status and row count, and the fund admin lead the rows.
  • Leaves a template the next quarter’s report runs from.

Run it on your fund

Talk to the team about running this playbook on your own fund.