CORE is the foundation shared by every module: who works, on which ground, with whom.

Contacts

The contact list shows, for each one, their institution, job title, rank, conviction level and sales status. A member sees the contacts of their territories and their own pending leads; a supervisor, those of their team; the Admin and the MaDa, the whole organisation.

Leads — contacts who came in through a form, a quiz, an event or a campaign sit in a separate tab, with their origin. They do not enter planning until they are qualified and attached to an institution.
Import and export — by CSV, both ways.
History — every change of status, conviction level or rank is logged, with its date and author. That log is what lets ANALYZE show progress over time.

Institutions and points of sale

An institution can be viewed as a list or a tree (a group and its establishments). It carries a type, a class and a rank, three axes you define freely. A point of sale follows the same logic, for tracking visibility and distribution.

An institution or contact created in the field can go through approval: first by its author's supervisor, then by the MaDa. The pending record stays visible to its author, who can see where it stands.

Territories

The territory tree, each with its holder, defines everyone's scope (see Concepts). The MaDa creates, imports and exports them; a supervisor views them to see how their team's workload is spread. A territory that still carries sub-territories or institutions cannot be deleted.

Absences

Everyone declares their own absence (leave, sickness, other); a manager can declare one for a member of their team. The declaration is visible at once. The reviewer — the direct manager, failing that the MaDa, failing that an Admin, never the person concerned — confirms or refuses it. Only a confirmed absence removes its days from capacity and from coverage.

Interims

When someone is away for a long time, the MaDa (or the Admin) sets a dated interim, from the territories screen:

Territory interim — a colleague takes over a holder's territory, on top of their own, from the first to the last day. When setting it, the MaDa ticks the contact ranks the substitute keeps in their plan; with no box ticked, all of them. The substitute sees the whole territory taken over.
Supervisor replacement — a substitute sees the supervisor's team and decides in their place: cycle plans, closings, absences and records awaiting approval, including what was submitted before they arrived. They are notified of new submissions.

In both cases, the replaced person keeps all their access, nobody decides on their own request, and the substitute's access ends by itself after the last day. An interim is extended or shortened rather than set again; interims ending within 14 days are flagged. The absences screen suggests an interim as soon as a confirmed absence leaves a territory or a team uncovered.

Consent and personal data

A contact's consent is recorded per channel, with its source and date; it can be read on the contact's page. At a person's request, the MaDa can export their data or erase it: erasure anonymises the record and every copy of their details (sends, forms), unless a legal obligation requires keeping them.