Required inputs
Loan agreement and approved covenant definitions, debt schedule, debt service, closed-month financial pack, lender reporting requirements and accepted valuation when an LTV metric is requested.
Monthly / M1
Loan Review
What changed in debt coverage, covenants and upcoming obligations?
M1 / Monthly / Product design
A clear scope.
A useful output.
Review the loan against the closed month's approved financials, debt terms and lender requirements.
Review output
A debt-service and covenant review, maturity and reporting calendar, missing terms and items requiring lender or AM review.
The human decision
Confirm definitions, investigate exceptions and approve any lender communication.
Dependencies before conclusions
Make the gaps visible.
Upstream
What comes first.
Closed-month financial pack; OS loan/debt pack. M3 Valuation Review required only for LTV.
Required dependency
What must be accepted.
Accepted financials and lender-defined coverage inputs; agreement/terms; debt schedule; lender requirements; accepted dated M3 value for LTV
If an input is missing
What stays open.
No covenant-compliance conclusion without agreement definitions; no LTV without accepted M3 value.
Required dependency identified; source availability and reviewer acceptance not yet confirmed. Core is separate Consulting; OS contains the data/context foundation.
Separate fictional scenario
Show the evidence.
Bound the conclusion.
This illustration is specific to this workflow. Its properties, ledger figures and assumptions are not joined to the Morning Portfolio Review or other examples.
Illustration
Fictional September lender-defined cash flow is 80,000 and debt service is 50,000, giving illustrative coverage of 1.60×. No covenant-compliance conclusion is supported without accepted contract terms.
What a reviewer should check
Use the agreement's cash-flow and debt-service definitions; 80,000 ÷ 50,000 = 1.60×; missing covenant terms prevent a compliance conclusion; missing accepted value prevents LTV.
Start with one useful review
Bring the question.
And the context.
Show us the property, the inputs your team has and the decision the review needs to support. We can discuss fit and a scoped pilot.
Book a demo