A report is trustworthy when its definitions are already present in the transaction.
Portfolio teams spend too much effort reconciling reports when product, channel, exposure, premium, and decision fields are interpreted again after business is written.
Governed transaction fields can flow into portfolio views and extracts with their product and channel context intact.
The work should carry its reasoning forward.
Inputs become decisions, exceptions remain visible, and the evidence behind the outcome travels with the output instead of being reconstructed later.
Inputs
- Bound transaction
- Product context
Decisions
- Reporting definition
- Period selection
Exceptions
- Validation issue
Evidence
- Source field
Outputs
- Portfolio view
- Extract
Governed portfolio view
Every reported value retains a path to its source transaction and definition.
| Record | Role in the work |
|---|---|
| Transaction | The bound record preserves premium, limits, dates, channel, and decision status. |
| Product version | Every transaction identifies the terms and rules that were live when it was written. |
| Exposure field | Reported exposures retain their original definition and value from the risk record. |
| Portfolio output | Aggregated measures link back to the transactions and field definitions they summarize. |
Start with a portfolio question and inspect whether the required evidence already exists in the operating record.
Bring the work as it operates today. We will trace its inputs, decisions, exceptions, evidence, and outputs together.