Covered Care Westlake Portfolio Management

Getting Started With Covered Care Westlake Portfolio Management

Pick up your login credentials from whoever handles your accounts, open the portal, and you will see a dashboard that looks mostly normal. The first thing most people do is click around until they find the asset summary tab. That is fine. The second thing you should do is immediately set up two-factor authentication because this system does not do a great job of enforcing it by default. I learned that the hard way when a contractor left the admin panel open on a shared machine and someone outside our org made a few test transfers that should never have gone through. If you are on the desktop client, navigate to the admin console, then to Updates, and hit check now. The web version updates automatically so you generally do not need to worry about that, but the local app stores old cache data for longer than it should. I have seen stale data cause reconciliation reports to be off by a few hundred dollars simply because the sync had not run in three weeks. Force a full sync before you run any month-end reports. It takes about forty-five minutes for a mid-size portfolio to refresh all its cached holdings. Start by importing your asset list through CSV. The system accepts the standard layout with columns for ticker or ISIN, account number, quantity, cost basis, and purchase date. Do not include extra whitespace in the ISIN column or the import will silently skip those rows. I wasted an entire Tuesday once because a previous user had merged cells in their export file and the import engine never flagged it. The workaround was to run the file through a quick Python script that cleaned whitespace and re-exported as a clean CSV. It cut the import failure rate from about 8 percent down to near zero.

After import, go to the reconciliation section and run the initial compare against your custodian statements. This step usually reveals discrepancies in about 10 to 15 percent of portfolios on first load. Most of those are timing differences where trades executed after the statement cutoff date, but some are actual data mismatches that need manual correction.

Configuring Risk Parameters

The risk engine has sliders for concentration, sector exposure, and liquidity buffers. The defaults are set to institutional baseline levels, which means they are often too loose for smaller funds running tighter mandates. I typically recommend tightening the concentration slider by one notch and increasing the daily drawdown alert threshold from the default 3 percent to something like 2.2 percent. You will get more alerts at first, but the noise dies down after a few weeks as the system learns your trading patterns. Set up your reporting calendars before you do anything else. This is where most teams get tripped up. The system will generate regulatory and internal reports based on a calendar you define, but if you skip this step it defaults to a monthly schedule that rarely matches your actual compliance requirements. I have seen funds submit quarterly reports when their mandate required monthly ones because nobody had touched the calendar settings after onboarding.

Rebalancing Workflows

Trigger rebalancing through the Allocations tab. You can set target weights per asset class or per individual holding depending on your strategy. The system will generate trade suggestions based on current deviations from your targets. Review the suggestion list carefully before approving. I once watched a junior analyst approve a batch without checking the trade history and the system generated duplicate sell orders for the same position because the market had moved between the time the suggestion was created and the time it was executed. The duplicate trades totaled over two hundred thousand dollars in unnecessary commission. Now I always run a pre-trade validation check and let it sit for at least an hour before final approval. For automated rebalancing, the system supports threshold-based triggers. Set your tolerance bands to something like 5 percent deviation for equities and 3 percent for fixed income. Lower than that and you will trigger constant micro-rebalancing that eats into returns through transaction costs. Higher than that and you are not really managing risk at all.

Data Export and Reporting

Use the export function for monthly review packages. The native export format is CSV with a separate PDF for formatted reports. If you need to feed data into another analytics platform, use the API endpoint rather than the manual export. The API returns structured JSON with full field-level detail including historical cost basis adjustments and corporate action impacts. The manual CSV export strips out about thirty percent of the available fields including realized gain tracking and FX adjustment lines. That omission matters if you are doing granular tax lot analysis. I run a weekly API pull every Monday morning that feeds into our internal risk dashboard. The whole process takes about six minutes end to end once you have the script configured. Before I switched from manual exports to the API, that same process took me roughly an hour and a half of copy-paste work that was error-prone. The setup time for the API integration was about two hours including debugging the auth tokens, but the return on that investment shows up immediately in week one.

Common Pitfalls and Workarounds

The performance attribution module in Covered Care Westlake Portfolio Management is decent but it assumes clean trade journaling. If your trade ingestion comes from multiple custodians with different settlement date conventions, the attribution numbers will drift. I found that mixing T+1 and T+2 settlement records without a normalization step produced attribution errors of about 0.4 percent annually across the portfolio. The fix is to create a settlement date mapping table in the import config and standardize everything to the reporting date before the system processes the trades. Another issue is the system's handling of dividend reinvestment plans. It records the reinvested shares at the reinvestment price but sometimes lumps the cash dividend and the new shares together in a way that breaks your cost basis tracking. I worked around this by adding a manual adjustment entry the day after each DRP posts, splitting the combined line item into its two components. It adds about five minutes per dividend event but keeps your cost basis clean.

Known Limitations

This system does not support blockchain-based assets natively. If you hold crypto or tokenized securities, you will need to log them manually and reconcile them separately. The manual entry interface is functional but basic. There is no automated price feed integration for digital assets, so you are responsible for pulling and entering daily valuations yourself. That is a gap that costs most teams about two to three hours per week depending on portfolio size. The reporting module also lacks native ESG scoring output. If your clients require ESG disclosure, you will need to integrate a third-party data provider or build custom report templates. The system can store ESG metadata fields but it does not calculate or score them internally. I recommend using MSCI or Sustainalytics data feeds if ESG reporting is a hard requirement for your client base. User licensing is per seat with no tiered discount structure beyond the enterprise agreement. A team of twelve will pay full price for every license unless you negotiate volume terms. This can get expensive quickly compared to some competing platforms that offer role-based pricing tiers.