Services from the BrightRock Invest bay

Client Reporting Pipelines

A client reporting pipeline is the spine of every engagement. We start by cataloguing each data source that feeds your monthly and quarterly packs, whether that is a portfolio accounting export, a custodian file, a fund administrator feed or a hand-maintained schedule. Each source receives a connector that validates structure on arrival, normalizes the fields your reporting team actually consumes, and rejects anything that fails its checks into a visible exception queue.

From there we build the transform layer. Holdings roll up, cash movements reconcile, fee calculations run against the same published rules every time, and performance figures derive from a single definition rather than a dozen spreadsheets. Scheduling runs the whole chain on the calendar your operations team already keeps, and each run writes an audit record that names the source, the row counts and the operator.

The result is a pack that rebuilds itself. When a late trade arrives, the pipeline reruns the affected segment only, and the downstream document assembly systems receive a clean, versioned dataset instead of a rescue file. Teams that adopt this station usually retire several hours of manual copying in the first cycle.

Document Assembly Systems

Document assembly systems turn the templates your firm already trusts into governed components. We break a reporting document into locked style regions, variable text fields, repeatable tables and signature blocks, then bind each component to the data a pipeline supplies. Analysts edit the parts they own and cannot accidentally move a margin, delete a footnote or flatten a chart.

Generation is deterministic. Given the same inputs, the system produces the same document, page for page. That property matters at review time, because it means a reviewer can compare two cycles and see only the values that genuinely changed. Narrative sections can be assembled from approved language libraries, and where a fund requires bespoke wording, the system records which passages were chosen and by whom.

Output formats include print-ready editions, web editions and archival copies, all generated from one source so the numbers never diverge between channels. Because the component library is versioned, a template change can be rolled back, compared and approved before it ever reaches a live document.

Data Room Integrations

Data room integrations connect diligence folders to the systems that hold the underlying material. Rather than asking an operations analyst to drag files into a folder each week, we wire the folder to the pipeline, the document store and the permission model already in use. New documents publish themselves, superseded versions are retained, and the folder index always reflects the current state of the deal.

Permissions are a first-class part of the integration. We map roles to folders, enforce least privilege and log every access with a timestamped identity. When a diligence participant is added or removed, the change propagates across every connected folder, so no one is left holding access they no longer need.

We also build the retrieval side. Reviewers can search across folders, filter by document type and follow links back to the source record that produced a file. That traceability is what turns a folder of documents into a defensible record during diligence, audit or dispute.

Compliance Archive Workflows

Compliance archive workflows decide what is kept, for how long, and in what form. We encode your retention rules as explicit policy so documents move through active, review and archive states on a defined schedule. Archive copies are immutable, and every movement is recorded, which means a regulator or internal reviewer can reconstruct the full history of any deliverable.

Retrieval is designed for the worst day, not the best. Indexes are built at write time so a search returns an answer quickly even across years of statements and reports. Legal holds suspend deletion, and release from hold requires an explicit, logged action by an authorized operator.

The workflow also handles the quiet requirements that cause trouble later: consistent naming, retained provenance, and a clear separation between a working copy and the sealed record. Once this station is in place, the rest of the reporting line can move quickly because everyone knows the evidence is safe behind it.

Statement Generation Platforms

Statement generation platforms produce the account statements that recipients actually read. We render each statement from the single source of truth established by the reporting pipeline, then apply the statement template, the fee disclosure language and the transaction detail that each account class requires. Figures reconcile to the penny, and the reconciliation is checked automatically before any statement is released.

Delivery is configurable per recipient. Some investors want a print-ready edition, some prefer a secure web view, and some receive a notification that a statement is available in a portal. The platform handles all three from one generation pass, so a correction applies everywhere at once and no channel drifts out of step.

We also build the operational controls that statement teams rely on: approval gates before release, a recall path for statements that must be reissued, and an archive of every edition with its generation date. Year-end volume, which usually breaks manual processes, is simply a larger run of the same line.

Investor Portal Deployments

Investor portal deployments give each investor a secure, branded view of their holdings, documents and statements. We scope access so an investor sees only their own records, apply session controls and audit every sign-in, and integrate the portal with the statement and document systems upstream. When a statement is published, it appears in the portal without a second upload step.

Branding is controlled end to end, from the sign-in page to the statement viewer, so the portal reads as a natural extension of your firm rather than a third-party tool. Administrators can manage users, reset access and review activity from a single console, and every administrative action writes to the same audit trail the compliance archive relies on.

Deployments are staged, starting with a small cohort before wider release. That approach surfaces permission gaps and content issues while the audience is small, and it means the portal arrives, like everything else we build, folded, collated and sealed.