Process templates: start from the standard and evolve

A process template defines, reusably, the process types your operation runs: which pipelines exist, which stages each one has, which fields get filled in and which roles the parties can hold.

The platform ships ready-made templates per vertical — registry office, law firm, clinic, real estate, accounting, parish. You are not obliged to use them as they are, and you do not have to start from scratch to change one stage.

Standard template and company template

There are two kinds of template:

• Platform standard — maintained by Vimel, updated along with the product. You do not edit it.
• Your company's template — yours, editable, and valid only in your account.

Creating a company template from a standard is what we call starting from the standard and evolving: the copy is born identical to the standard and becomes yours from then on.

Why the origin is recorded

When you derive a template, the platform stores two things: which standard it came from and which version of that standard the copy was taken at.

That pair is what allows us to warn you when the standard evolves. Without it, a derived template would be indistinguishable from one created from scratch, and there would be no way to say "the registry-office standard has changed since you copied it".

In practice:

• The standard advances a version when Vimel publishes an improvement.
• Your template stays exactly as you left it.
• The templates screen indicates that a newer version of the source standard exists.

The update is never automatic. Applying the standard's change over a template you have edited would overwrite your work, so the decision is yours.

Retiring a standard does not break your copy

If Vimel retires a standard template, templates derived from it keep working. The link to the origin is severed and your template is treated as independent — nothing is deleted.

Types that serve two uses

A process type can be opened in two ways: as a process with a pipeline, which moves through stages, or as a document project, which has no workflow and exists to produce and summarise files.

One type can serve both uses. This avoids keeping two nearly identical records — a "contract" that moves through the funnel and a "contract" that only generates a document.

What does not come along

Deriving a template brings the pipelines, stages, fields and roles. It does not bring processes already under way: those stay bound to the template they were created under. Changing the company template does not rewrite the history of anything already running.