Bring your loan obligations, operating context and decision owners into one capital review. Start with the schedule and source files you already use; the CapLens team can help plan portfolio setup without requiring an API integration.
1. Inventory the assets and debt
- Record each property, ownership entity, market and financing purpose.
- Add the current loan balance, lender, loan type and balance as-of date.
- Keep the latest debt schedule and original loan documents together.
- Identify the team authorized to view the information and the person responsible for the portfolio record.
2. Capture the obligation and its source
- Record maturity dates, extension election windows and rate-cap expiries separately.
- Link each date and condition to the relevant loan clause, notice schedule or cap confirmation.
- Keep the review deadline distinct from the final maturity or expiry date.
- Retain conditions, reserve requirements, known fees and unresolved questions in the lender’s actual wording.
3. Prepare the financing basis
- Bring dated operating results, current debt and the valuation basis for each asset.
- Keep reported NOI separate from adjustments or projected performance.
- State the rate, amortization, leverage and debt-service coverage assumptions used for refinance sizing.
- Compare gross supportable proceeds with current debt, then review payoff, fees, reserves and closing costs before treating a difference as a funding requirement.
4. Assign the next review
- Give each obligation a decision owner and an internal review date.
- State the next decision: confirm extension conditions, develop refinance coverage or review a replacement cap.
- Keep the source basis, financial consequence and open questions with that review.
- Revisit the record when loan terms, operating results or the asset plan change.
5. Choose the setup path
- Bring the debt schedule and a small set of source documents to your portfolio-setup discussion.
- Agree which fields, dates and records should be carried into the workspace and how the team will keep them current.
- Technical teams can use the public Portfolio API documentation to assess authentication, validation and data mapping when a connected integration is appropriate.