An implementation is a list of things that stop being ambiguous.
Not an install. Before continON can run an organization correctly, a set of facts about that organization have to become explicit — what the units are, what the positions are, who holds them, who may do what, how work is supposed to move, and which existing systems stay where they are. Most of those are decisions. The software is what holds them once they are made.
Before you read on This page gives no duration and no fixed sequence. How long an implementation takes depends on how settled the answers below already are inside your organization — which is not something a product page can know.
What has to stop being ambiguous.
The organization has to be stated
Almost everything else resolves against this, so it is settled first. These are decisions about how the organization actually works, not screens to fill in quickly.
- What are the units, and where are they?
- Your organization decidesA unit tree of the real depth, each unit carrying its type, its parent, its address, its own currency and logo.Organization & positions
- What positions exist, and in which unit does each one sit?
- Your organization decidesPositions defined once with their reporting line and pay grade, then placed into units as seats with a clearance level and a limit on how many people may hold them.Org chart & positions
- Who currently holds each seat?
- Your organization decidesEmployment assignments binding a person to a seat, a unit and a manager between dates — the record every later access and payroll decision reads.Employment & contracts
Authority has to be assigned
Access is not granted to people here. It is granted to positions, which is why this stage cannot start before the one above it has finished.
- Which applications is the organization licensed for?
- Configured in the productAn encrypted licence file, validated on upload against the organization name and its expiry, deciding which applications exist at all.Licensing & module activation
- Which permission groups should exist, and what does each one allow?
- Your organization decidesGroups carrying application access and per-form privileges — read, create, update, delete, download — granted individually rather than by a role name.Users & permissions
- Which positions hold which group?
- Configured in the productA binding between the group and the seat, so a change of holder never becomes a change of permissions.How access is decided
The way work moves has to be drawn
Off-the-shelf approval chains are where most systems start to diverge from how the organization actually runs. Here they are definitions, so they are part of the implementation rather than a change request afterwards.
- Which processes need to be explicit, and who acts at each step?
- Your organization decidesStates and transitions with an actor rule per state, resolved against the org chart at run time rather than against a named person.Process Builder
- What has to be captured, and on which screen?
- Configured in the productVersioned forms bound to the states they open at, with lookups and defaults resolved from saved queries.Form Builder
- What words does the organization use for its own screens?
- Your organization decidesWorking languages registered and per-module terminology translated, plus the categorized lookups every screen reads its statuses and types from.Languages & localization
Existing systems and data have to be placed
Not everything moves. This stage decides what is queried where it already is, what is registered as an external credential, and what genuinely has to be entered.
- Which existing sources stay where they are and are read in place?
- Connected to a sourceSaved queries composed against the schema of a source your organization already runs, feeding forms, reports, dashboards and documents from one definition.Query & data-source builder
- Which external services does the organization already pay for?
- Connected to a sourceNamed credentials registered under the organization, stored encrypted and fetched by the applications that need them.Integrations & data
- What has to be entered rather than connected?
- Your organization decidesAn explicit list, agreed rather than assumed. There is no generic bulk import of spreadsheets into operational records, so this is a real scoping decision.Connect what you already run
It has to be checked against reality
The point of this stage is to find the places where the model on the screen and the operation on the ground disagree — while that is still cheap.
- Does a real record survive the whole path?
- Checked before useOne request raised, approved, ordered, received, purchased, placed and posted, on the organization’s own structure and its own permission groups.From request to stock
- Does the right person see the right thing, and only that?
- Checked before useThe seats checked against what their groups actually open, before anyone depends on it.How access is decided
What is deliberately left open afterwards.
- The organization keeps changing
- Units are added, positions move, people join and leave. Access, approval routing and reporting scope read the chart as it stands that day, so keeping the chart current is what keeps them current.
- Definitions keep changing
- A published process, form, report or document definition is metadata read at run time. Every revision is retained, so which version a given request ran under stays answerable after the definition has moved on.
- New places inherit
- A site added later is a child of an existing one. The licence, the permission groups, the lookups and the definitions already reach it; its stock, sectors and staffing start as its own.
What this page will not promise.
- This page does not give an implementation duration. The stages above are mostly decisions your organization has to make, and how long they take depends on how settled those answers already are — not on the software.
- Not every implementation runs all of these, and not always in this order. An organization that already has a clean org chart starts somewhere different from one that does not.
- There is no general-purpose bulk import of existing spreadsheets into operational records. What is connected, what is entered and what is left where it is has to be scoped explicitly.
Organization & positions
Bring the answers you already have.
A working session on your own org chart, your own permission groups and one process you argue about — so the scope of the decisions above becomes concrete rather than estimated.