सोपान · the steps · SOP that runs
Everyone sells SOP manuals. They are signed, shelved, and drifting from reality within a year, because paper does not enforce itself. Sopan is different: we write your procedures, and then MISAC executes them.
The gap between a written procedure and a followed procedure is where control is lost. Sopan closes it by making the system the enforcer.
The document says who approves.
Sopan routes it to them.
The document sets the limit.
Sopan refuses beyond it.
The document defines the steps.
Sopan will not let one be skipped.
Written against your Drishti Blueprint's future state, then bound to the system that runs them.
Procedures written step by step: who does what, when, on what document, with what system action. RACI matrices by role. Authorization limits with escalation and delegation rules. Control points made explicit. Even your informal fast-tracks, legalized as documented exceptions with their own authorization, so urgency has a lawful lane.
Cross-department policies, delegation of authority, and the handoff map between departments. Plus an amendment procedure, because an SOP manual that cannot lawfully change dies the day reality shifts.
Every procedure step carries its enforcement reference: the step, who owns it, and exactly where the system enforces it. Nothing is written that the platform cannot hold to account.
For platform clients, the procedure is readable exactly where it executes. Click the approval step and its rung is right there. The manual and the system can never drift apart, because they are the same object.
Each department head signs their volume; management adopts the whole. Upon sign-off, the procedures go live in the system. Signed on paper, alive in the platform.
Sopan is a consulting engagement scoped by department count and depth. It stands on its own value, with or without the platform.
Honest procedures cannot be written without honest analysis. Sopan builds on your Drishti Blueprint, so the future-state processes it documents are the ones already agreed on paper. If you have not run Drishti yet, that is the first step.
Drishti sees your system and agrees the future state. Sopan defines its steps and makes them impossible to skip.
Sopan is optional. When you take it, your procedures reach go-live already signed and already enforced by the platform.
Written procedures your team can follow, and a system that will not let them be skipped. It begins with Drishti.
