Platform Features
A closer look at how Gavren Kovel allocates and protects capital
Every feature below exists to answer one question on behalf of our clients: is this reserve working as hard as it reasonably can, without being exposed to reckless risk? Here is what sits behind that answer.
Request Strategy Overview
A representative view of the allocation framework used to structure client mandates.
Built around a specific gap
Most UK businesses holding surplus cash face a narrow set of choices: leave it in a low-yield account, hand it to a generalist wealth manager with a standard model portfolio, or attempt to manage exposure themselves without the tooling or time to do it properly. Gavren Kovel was built to sit between those options — a disciplined, AI-directed approach that treats each mandate as a distinct set of constraints rather than a template.
The features on this page describe how that approach is actually implemented, from the modelling layer through to the operational safeguards that govern how capital moves.
Core features
The mechanics behind the mandate — what Gavren Kovel does with a reserve once it is placed under management.
AI-directed allocation modelling
Allocation decisions are generated by models that continuously reprocess market data, rebalancing exposure against a client's stated risk tolerance and time horizon rather than a fixed quarterly schedule. The aim is to reduce the lag between changing conditions and a portfolio's actual positioning.
Benefit: capital is not left static between infrequent human reviews — it is assessed on an ongoing basis against the mandate it was placed under.
Bespoke mandate structuring
Before any capital is deployed, a mandate is defined with the client: acceptable drawdown, liquidity requirements, sector exclusions where relevant, and the horizon over which performance should be judged. This document, not a generic risk score, is what the model is directed to satisfy.
Benefit: the strategy is shaped around the client's actual constraints, rather than the client being placed into whichever strategy the provider happens to offer.
Ongoing risk containment
Position sizing and exposure limits are enforced as hard constraints within the model, not as guidelines that can be overridden under pressure. Drawdown thresholds trigger automatic de-risking steps before losses can compound beyond the bounds agreed in the mandate.
Benefit: the framework is designed to protect the reserve first, and pursue return within that boundary — not the reverse.
Transparent reporting cadence
Clients receive regular statements showing positioning, performance against the mandate, and any material changes in strategy or risk posture. Reporting is written to be legible to a business owner or finance lead, not only to someone with an investment background.
Benefit: visibility into how the reserve is being managed, without needing to interpret dense fund documentation to get it.
Feature categories in detail
A breakdown of how the platform's capabilities group into three practical areas — flexibility, oversight, and access.
Strategy adapts as circumstances change
A business's tolerance for risk in one financial year may not hold in the next. Mandates can be revised — tightened, loosened, or rebalanced toward liquidity — as a client's own position shifts, without needing to unwind and restart the relationship.
Adjustments are reviewed against the same risk-containment rules that govern the original mandate.
Model output is not left unchecked
Allocation decisions generated by the model pass through a review layer before execution on anything outside routine rebalancing. This exists to catch edge cases the model may not weight correctly and to keep a person accountable for how the mandate is being interpreted.
The intent is not to replace judgement with automation, but to combine the two deliberately.
A clear view without a steep learning curve
Clients can request an updated position statement or a walkthrough of current strategy without navigating a self-service dashboard designed primarily for active traders. The reporting is built for periodic review, not constant monitoring.
Suited to businesses that want a considered reserve strategy, not a trading terminal.
Feature availability and reporting cadence are confirmed as part of a client's specific mandate documentation and may vary between engagements.
How a feature actually gets used, end to end
-
Mandate defined
Risk tolerance, liquidity needs, and horizon are documented and agreed before any capital moves.
-
Model calibrated
The allocation model is configured against the mandate's specific constraints, not a generic default profile.
-
Positions established
Capital is deployed in line with the calibrated model, subject to the enforced risk-containment limits.
-
Ongoing review
Positioning is reassessed continuously; material changes pass through the human review layer before execution.
-
Client reporting
Performance and positioning are reported on the agreed cadence, in language a non-specialist can act on.
This sequence describes the general operating pattern behind Gavren Kovel's features. Specific timelines and reporting formats are set out in individual client mandates rather than applied uniformly across every engagement.
Feature-related questions
Can a mandate be changed after it's set up?
Yes. Mandates can be revised as a client's circumstances change, subject to review against the platform's risk-containment framework.
Does the AI model operate without any human involvement?
No. Routine rebalancing follows the calibrated model directly, but changes outside that routine pass through a human review step before execution.
How often is reporting provided?
Reporting cadence is agreed as part of the mandate and can vary by client depending on the nature and size of the reserve being managed.
Is this suited to a business that wants to monitor positions daily?
The platform is built for periodic, considered review rather than active day-to-day monitoring. It may not suit clients seeking a real-time trading interface.