Contract templates

Keep the standard templates of your contracts. When creating a contract from a template, the client's and service's fields fill in the text variables automatically.

The standard text of your contracts. When generating a contract, the system starts from the template and replaces the tokens with the real customer and service data.

The template is the base text a new contract inherits — clauses, conditions and the language the company uses. Writing it once here avoids rewriting it (and diverging) for every contract.

The form of a contract template — the registration screen behind the Contract templates list. — this is the role of the "Contract template" screen within the platform.

One template per service type (support, fixed-price project, staffing). Review the template with legal once and all contracts come out consistent.

A placeholder with a non-existent name is simply not replaced and gets printed as is, in the middle of the clause. Check by generating a test contract before using the template with a real customer.

Name identifies the template in the library. "Applicable to" says what type of contract the template serves — it is what filters which template appears when generating the draft. "Active" takes the template out of circulation without deleting it: deactivated, it stops being offered but stays in the registry. And "Template body" is the text itself, where the tokens go that will be replaced with the contract data at generation time.

This form runs on the platform's standard engine: you choose the layout in 1, 2 or 3 columns per screen (and a global default in your Preferences), and move between templates with previous/next without going back to the list. The "?" button opens this help on any screen, and Ctrl+K searches for any screen in the platform by name or synonym — useful for jumping from here straight to Contracts when it is time to generate the draft.

The text is copied at generation time. Existing contracts keep the wording they had when they were made — which is what is expected of a signed document.

A signed contract keeps the text that was valid on that day. Changing the template applies to the NEXT ones — that is what prevents an edit made today from silently rewriting what someone has already signed.

Access is governed by profile: whoever administers the account grants "view" (and the other verbs) on the Access screen. If someone on the team cannot find this screen in the menu, the path is to ask the administrator for the grant — absence from the menu is not a bug, it is permission.

The legend above the fields lists the available tokens: {{numero_contrato}}, {{empresa}}, {{parte}}, {{tipo_parte}}, {{valor_mensal}}, {{vigencia_inicio}}, {{vigencia_fim}}, {{dia_vencimento}}, {{indice_reajuste}}, {{periodicidade}} and {{data_hoje}}. Write them exactly like that, with double braces and the same name as in the legend: a token with a misspelled name does not raise an error — it comes out literally in the document, and you only notice in the finished draft.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

Whoever has permission to view this screen in their profile, with the module unlocked in the account's plan. Viewing the library and creating/editing templates are separate verbs: create and edit are granted per profile, so it's normal for a user to consult the templates without being able to touch the body. Since the template is the base text of the company's contracts, it's common to restrict editing to a few profiles — getting a token wrong here comes out printed in every draft generated from then on.

"How do I register a contract template?" — when that question comes up, this is the screen where it is answered.