Finding the AI workflows your organisation actually runs
A list of model endpoints tells you little about who relies on their output. Connect technical evidence to the business decision it supports.
Begin with one business decision
Take invoice extraction. A service reads a supplier document, predicts fields and places a draft in a review queue. The inventory entry should identify who owns that workflow, what data enters it, where the result goes and who can release a payment. Two applications using the same model may need different controls because their outputs trigger different actions.
Record what each source can establish
Use authorised deployment inventories to identify configured services and approved gateway metadata to identify recent calls. A deployed resource shows availability. A recent call shows activity. Neither establishes the business purpose. Ask the application owner to confirm it. Record source, observation time and confidence separately. Keep prompt text and customer documents out of discovery records when metadata answers the question.
Turn the register into a review queue
Link each workflow to an owner, a review date and a small evaluation set. For invoice extraction, include a credit note, a blurred total and two suppliers with similar names. Record which errors require manual review. When discovery finds a new model version or a changed destination, raise a review item with the before-and-after evidence. Measure progress by the number of active workflows with a confirmed owner and a tested decision boundary. NIST’s AI RMF provides a broader framework for organising that work.