A facility isn't just approved. It's approved subject to conditions.

Elevations can track them.

Credit committee rarely just says yes. There's insurance to confirm, a satisfactory search result, confirmation of planning permission — the small print that makes an approval real. In many systems, that list lives in the credit paper and nowhere else: a document nobody opens again once the loan is live, with no link between "approved subject to" and the facility actually drawing down.

In Elevations, conditions attach to the loan itself. Each one is either satisfied or it isn't, with the date it was.

Defined once, used on every loan. Set a list of default conditions on the product — insurance, a satisfactory search result, confirmation of planning permission, whatever that product always requires — and every new loan created from it picks up the product's current defaults automatically, with nothing to add by hand. Change the defaults later and only new loans see the change; loans already live keep what they were given at the time.

Satisfied or not, with a date. A condition doesn't just disappear once it's met. It's marked satisfied and stays on the loan with the date, part of the loan's own record rather than a line ticked off a document and forgotten.

Deal-specific conditions fit alongside them. A loan isn't limited to its product's defaults — conditions can be added to a specific loan too, for whatever that particular deal needed that the template didn't anticipate.

Unsatisfied conditions actually stop money moving. An advance can't be requested, approved or confirmed while the loan has an unsatisfied condition outstanding — not a warning to click past, but a block enforced the same way at every stage.

An approval was never really an unconditional yes. Elevations just stops pretending otherwise — the conditions attached to it travel with the loan, and nothing moves past them until they're actually met.