A standards library that works with all of your operational data inside Calisto Pro. Write an SOP, a checklist, a build spec, a recipe or a brand kit in an inline editor. Push it down to every business unit, locked where it must not change and editable where it may.
SOPs, checklists, build specs, recipes, and brand kits, written once at head office. Locked where it must not change, editable where it may.
HQ profiles that push locked standards down.
Standards and SOPs authored once for every unit.
Operating checklists deployed across business units.
Construction specs and build standards.
Training curricula pushed to every location.
Document templates with version history.
Design assets and brand kits for every unit.
Cross-domain search, sync, and adoption reporting.
A locked field arrives read-only in the unit, and anything that has drifted from the HQ standard is flagged. Each unit is a Purview, which is where it carries the standard or is granted an override.
Legal entity, trading name, contact, locale.
Industry, segment, business type.
Country, currency, timezone, regional defaults.
Operational defaults, terminology, working standards.
Roles, onboarding flows, knowledge standards.
Colors, fonts, and logo usage.
0
authoring domains
One
HQ push-down layer
Every
canvas version-tracked
Every standard snapshots on each edit, so the version a unit opens is the version you published.
Step-by-step procedures for the work itself.
Before-photo and preparation requirements per room or station.
Attached to a role, a department, or a property type.
Emergency procedures and incident response, version-locked for audits.
Completion and overdue items are tracked per unit, which is what an audit reads instead of a recollection. Assure runs the checklist on the cadence the standard sets.
Opening, closing, turnover, and shift.
Regulatory and policy checks, with completion rates.
Staff, vendor, and client step lists.
Every step of a sale, lease, or booking confirmed before close.
Seven standards a development or renovation programme reuses on every site.
Floor plans, elevations, construction documents.
Try material, layout and finish combinations before committing to one.
Flooring, countertops, cabinetry, fixtures, paint.
Chemical and material handling sheets.
Divisions, product selections, installation requirements.
Load tables, span charts, engineering references.
Coverage terms, exclusions, claim procedures.
Blueprint defines what is required. University runs the course, and Workforce reports who holds which credential.
Searchable reference articles staff look up in place.
Step sequences for new hires, vendors, and clients.
Curricula with module order and completion tracking.
Expiry and renewal, so you know when one lapses.
The file a standard points at lives in Depot, so the copy people open is the one you published.
Contracts, memos, policies, letters.
Budgets, inventory lists, scheduling grids.
Investor decks, training, property tours.
Thermal, email, and PDF invoice formats.
Five design domains, each one a template a unit opens rather than a file it recreates.
Display boards for the screens on your floor.
A unit sees the whole standard and can act on all of it. What headquarters locked simply will not save.
One lifecycle, whichever domain you are writing in.
Write a standard in any of the twelve domains.
Open it in the inline canvas editor. Version history, with restore.
Push published standards to business units, and track which ones landed.
List a standard in the marketplace for other Calisto subscribers.
One search across all twelve domains, and a per-standard sync that reports how many units received it.
Query every domain at once.
Browse by domain; bundle related standards.
Which standards a unit has taken, and which it still pulls updates from.
Push a standard now, and see how many units took it.
Fork it and it is theirs to change. Subscribe and they keep pulling your updates on their own cadence. Read-only is neither.
Where a standard landed, over the date range you choose.
Three ways to fill the library without typing it from scratch.
Describe a process or upload a photo. You get back a structured SOP with steps, roles and expected outcomes, ready to publish as a standard.
Finds a standard by meaning, so a naming convention is not a prerequisite.
Submit a business description and every standard comes back scored by relevance, so a new account knows which ones to apply to its profiles first.
3 of these 6 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
A standard is pushed to purviews, and Purview is where each one carries or overrides it.
A required qualification defined here is what a staff record is measured against.
The document a standard points at lives in Depot, so the version people open is the version you published.
A checklist that must be run, and how often, is the standard rather than a local decision.
Required training is defined once and reported against by course completion.
The brand rules a standard carries are what Ethos checks work against before it goes out.
Operating standards for HQ and multi-location teams.
Recommended for you
Account configuration and data rules.
Learn more →Reservations, inventory, contacts, tickets, and scheduling
Learn more →Daily dashboard, helpdesk, dispatch, accounting, compliance, and HR
Learn more →Full LMS. Employee training, course creation, certifications, onboarding programs.
Learn more →Brand guard. Checks brand tone across every app in Calisto Pro — customer service in Desk, designs in Studio, flyers in Docs, presentations in Slides, social posts in Impreta. Enforces brand consistency everywhere.
Learn more →Blueprint is the headquarters layer above Purview. HQ authors a standard and locks the fields that must stay consistent; Purview is where each business unit configures everything HQ did not lock. Blueprint pushes down, Purview configures locally, and apps read the result.
Yes, including in the app that would otherwise write it. A governance lock is the only thing on the platform that makes a field read-only, and it applies uniformly rather than per app.
Twelve domains, grouped into identity, classification, regional and operational sets. In practice it is anything a multi-site business needs to hold identical across sites while still letting each site run itself.
It is aimed at businesses pushing a standard down to units they do not run day to day. A single site usually configures in Purview and comes back to Blueprint when the second site opens.
It is part of Core. The pricing section on this page reads the live catalogue and is the authority.
The profiles and their values export in standard formats, so the standard itself is portable even though the enforcement is not.