J0WNhwC_d

Portfolio Monitoring

Collect portfolio updates, validate required data, flag exceptions, and prepare review-ready monitoring outputs.

WORKFLOW BOUNDARY

Where the agent starts, stops, and escalates

Where the agent starts, stops, and escalates

Where the agent starts, stops, and escalates

Starts: when an approved reporting cycle or portfolio update request begins.

Uses: submitted portfolio data, approved reporting definitions, prior-period context, and required-field rules.

Agent work: collect updates, normalize submissions, check completeness and consistency, and prepare the monitoring package.

Stops: when the fund team receives a review-ready package and explicit exception list.

Excludes: investment decisions, valuation approval, and unsupported inference where source data is missing.

Before and after

Before and after

Before: teams request updates, reconcile formats, check completeness, and rebuild monitoring packs manually.

After: submissions are organized against approved definitions and reviewers focus on missing or inconsistent inputs.

Human controls

Human controls

The fund team owns definitions, access, materiality, exceptions, and final outputs. Source provenance is retained and missing data remains visible.