Direct answer: What is a model portfolio?
Model portfolio construction creates reusable target allocations with sleeves, constraints, versions, drift monitoring, and account-level implementation rules.
How Celestice helps
Celestice turns portfolio construction into a governed operating workflow: targets, sleeves, constraints, taxes, drift, optimization, and approvals stay connected. In practice, Celestice helps teams convert analysis into reviewable proposals rather than isolated model output.
<!-- celestice-query-answer:end -->One definition, many accounts
A model portfolio is a target allocation defined once and applied to many accounts. Instead of hand-building each client's portfolio, you define the model — the target weights, the rules, the constraints — and assign it. Every account on that model inherits the same discipline, and a single reviewed change can flow to all of them. This is how a small team manages many portfolios consistently without cutting corners, and it sits at a specific point in the portfolio loop: after trusted data, performance, and risk review, and before optimization and trade-proposal review.
Targets, sleeves, and constraints
A model is more than a list of percentages. A well-built one specifies:
- Targets — the intended weights across holdings or asset classes.
- Sleeves — sub-portfolios within the model (an equity sleeve, a fixed-income sleeve, a tax-managed sleeve) that can be managed and reported on separately while rolling up into the whole.
- Constraints — concentration limits, sector caps, minimum positions, and cash treatment that keep the model inside its intended risk and structure.
- Restrictions — account- or household-level exclusions the model must honor when applied.
The sleeve concept is what makes models flexible enough for real use — including unified managed accounts (UMA), where multiple sleeves and strategies coexist in one account under a single model.
Version control: models change, and that has to be safe
A model is not static; allocations get revised as views and conditions change. The discipline that separates a professional process from a risky one is version history. Every model change is a version, you can compare performance between versions, and you always know exactly which version an account is on. This means a model update is a deliberate, reviewable event — not an untracked edit that silently alters dozens of portfolios. When a new version is ready, it can be rolled out intentionally, and the prior behavior remains on record.
Drift monitoring: the model is a target, not a guarantee
The moment a model is applied, real-world prices start pulling accounts away from their targets. Drift monitoring tracks how far each account has strayed and keeps a drift history, so you can see not just the current gap but the pattern over time. Drift is the trigger that connects models to action: when an account drifts beyond tolerance, it becomes a rebalancing candidate. Without drift monitoring, a model is just a nice intention that quietly decays.



