A phase represents a stage in the funnel a credit process moves through, from the first contact with the client to the final outcome of the operation. Instead of treating the credit pipeline as a single opaque block, splitting it into phases lets the business name and visualize each distinct moment of work — for example Triage, Document Analysis, Approval, Contracting, Won, or Lost. Every process advances phase by phase, and that progression is exactly what gives managers and sales teams visibility into where each client stands in the credit journey.More than a label, each phase can carry its own set of behaviors that only make sense while the process sits there. An analysis phase may require approval from a specific responsible party; a technical evaluation phase may demand a specialist opinion before moving on; a decision phase may automatically trigger an engine that calculates a credit limit or risk score; and a follow-up phase may send automatic messages to keep the client informed on progress. By tying these capabilities to the right phase, the business ensures every check, approval, or communication happens at the appropriate moment — not before, not after.This design is also what reveals bottlenecks. When many processes pile up in the same phase, or stay there for a disproportionate amount of time, it becomes clear where the operation is stalling — whether due to missing documentation, slow approvals, or a sluggish technical review. Finally, phases marked as won or lost represent the closing of the cycle: the process reaches a definitive outcome, positive or negative, and leaves the active flow. Understanding phases is, therefore, understanding the backbone of how the agro credit process is organized, measured, and improved over time.Simplified example#
Under the hood, a phase is represented by a simple data structure. An illustrative example:{
"name": "Document Analysis",
"color": "blue",
"index": 2,
"start": false,
"done": false
}
For the complete technical reference, with every field, validation, and documented behavior, see the technical documentation under the 🇺🇸 English tab. Modificado em 2026-07-28 20:38:32