What good looks like

The supporting record ties back to economics models, governing documents, capital accounts, distribution schedules, fee calculations, and investor disclosures. for Synthetic Carry

This operating-context article explains where the concept appears, what evidence should support it, and how a sponsor should turn the workflow into a clean decision record.

How it connects

The supporting record ties back to economics models, governing documents, capital accounts, distribution schedules, fee calculations, and investor disclosures. is one place where Synthetic Carry becomes operational rather than theoretical. The workflow should identify the owner, timing, evidence source, affected stakeholders, and the next decision that depends on the record. For a sponsor economics page, this context should make the reader smarter about the exact workflow they are trying to execute, not just define the term.

Sponsor workflow

Define the exact Synthetic Carry decision inside the supporting record ties back to economics models, governing documents, capital accounts, distribution schedules, fee calculations, and investor disclosures. and separate required action from background explanation.
Attach the source support: waterfall model tabs, capital account records, distribution notices, approval history, and true-up support.
Assign ownership across the sponsor, administrator, tax preparer, investors, and the person approving distribution calculations and capture the escalation path before the record is closed.

Decision questions

What decision should this context force?

In the supporting record ties back to economics models, governing documents, capital accounts, distribution schedules, fee calculations, and investor disclosures., the Synthetic Carry question should resolve whether an approval, funding step, allocation, investor communication, closing item, reporting number, or post-close operating action needs to change. If it does not change a decision, it belongs as background support rather than a control point.

Synthetic Carry glossary definition →

What evidence should be linked before the item is marked complete?

The useful evidence set is waterfall model tabs, capital account records, distribution notices, approval history, and true-up support. The page should not just say the work happened; it should point to the record that lets another reviewer reproduce the answer.

Who owns approval, notice, or escalation?

Ownership should be explicit across the sponsor, administrator, tax preparer, investors, and the person approving distribution calculations. A sponsor-quality workflow names who prepares the answer, who approves it, who gets notified, and who handles exceptions.

Related: Phantom Carry →

What breaks if this is handled loosely?

The practical risk is that the model can produce a payout that does not match the documents, creating investor disputes or a later clawback problem. That is why this page treats the context as an article path instead of a passive bullet point.

Back to operating term →