The lifecycle of a business rule: proposed, validated, active, suspended

Why a rule needs a lifecycle

A business instruction is not an isolated sentence. It applies to particular customers, transport types, sources and periods. It may allow preparation only, require approval or permit an action. Without these limits, a rule that is correct in one case may become unsafe elsewhere.

The lifecycle makes those conditions and governance decisions visible. It separates observed knowledge from permission to act, then makes it possible to follow actual use, exceptions and changes over time.

The four essential statuses

What a proposal must demonstrate

Vigilo can detect that the same decision appears in comparable situations. The proposal must still show the facts that explain it and the differences between cases. It must not turn a correlation or a temporary habit into a general truth.

• the cases, events and decisions from which the proposal emerged;
• the shared context and observed variations;
• the proposed wording and expected result;
• the likely scope: customers, flows, tools, roles and periods;
• contradictions, counterexamples and cases that remain unknown;
• the intended level: information, preparation, mandatory approval or authorized action.

Validation is a governance decision

Validation can start from an existing documented rule or from a practice surfaced through observation. In both cases, the team remains the source of authorization. Vigilo makes knowledge explicit and testable; it does not grant itself new rights.

1. 01
   Name an owner

   A person or function is accountable for the business meaning of the rule and its evolution.

2. 02
   Define the scope

   The affected customers, operations, sources, systems and roles are stated explicitly.

3. 03
   Write the exclusions

   Sensitive, ambiguous, new or contract-specific cases are removed from the automated scope.

4. 04
   Set permissions

   The rule says whether Vigilo informs, prepares, asks for approval or acts.

5. 05
   Choose the checks

   Checks before and after action, and results that require a stop, are documented.

6. 06
   Prepare suspension

   The owner, trigger and fallback behavior are decided before activation.

Version rules to explain every decision

A rule change must not rewrite the past. Each version retains its wording, scope, exceptions, owner, decision date and associated checks. Actions on a case remain linked to the version actually used.

When a rule changes, the new version goes through validation in turn. The former version can remain available for reference, be limited to certain open cases or be suspended. This traceability explains why two similar cases may have been handled differently at different times or in different scopes.

When to suspend an active rule

Suspension is a normal control mechanism, not necessarily evidence of failure. It protects the workflow when an assumption is no longer true or when a check can no longer guarantee the expected result.

• a screen, API, document or reference source has changed;
• a contractual rule or business responsibility has evolved;
• verified results reveal a new or recurring discrepancy;
• the owner can no longer confirm the scope;
• an incident requires analysis before any further action;
• the rule conflicts with a newer version or a higher-priority source.

When the rule is suspended, new cases should follow a known behavior: contextual handoff, preparation without execution or an already validated fallback rule. The reason, author and date of suspension remain available.

Adaptability without losing control

Every company combines its own TMS platforms, portals, roles and ways of handling exceptions. Vigilo adapts to this reality by configuring shared building blocks — events, case state, rules, actions, checks and handoffs — instead of imposing one workflow.

That configuration becomes an asset when it is structured. A screen, process or rule can evolve without starting over, while the exact change remains visible. Portability does not mean every system is alike; it comes from a common method for describing and governing their differences.