Skip to content

Operational governance

Between deciding and doing, a condition matters.

Ciizer is the record of operational decisions: it keeps context, approvals, owners and evidence in one traceable flow. In API-integrated flows, the external system checks with Ciizer and reserves a registered authorization before executing the operation.

Context to decide. Conditions to proceed. Records to reconstruct.

  1. Decide

    A decision starts with context, owners and approval.

  2. Before anything proceeds, a condition holds.

    Ciizer checks whether what must be true actually is.

  3. Ciizer authorizes. Another system executes.

    The operation happens in the integrated system, outside Ciizer.

  4. The event passes. The link remains.

    Results and evidence stay tied to what was decided.

Ciizer governs authorization. The external system executes the operation. A condition line runs across the scene. Above it is Ciizer, where the decision is formed and the record stays. Below it, outside Ciizer, the authorized operation is carried out by another system.

01The missing connection

The approval exists. The context is missing.

A supplier record change was approved. Days later, someone needs to understand what changed — and why.

Illustrative case / supplier record change
  1. Context

    The rationale stayed in a conversation.

    On what basis?
  2. Approval

    The approval does not identify the version reviewed.

    What was approved?
  3. Responsibility

    The next step was agreed separately.

    Who needed to act?
  4. Execution

    The outcome lives in another system.

    Did it match the authorization?

Control is lost when these answers no longer belong to the same process.

02Decisions

A decision needs a foundation.

Record what needs deciding, the rationale, the participants and the evidence supporting the review. Authorship remains associated with the record.

Recorded byMarina · Operations

Context, authorship and evidence together — for those deciding now and those reviewing later.

Decision recordIn review
Decision

Review a supplier’s details

Context
The supplier requested a record change. The team needs to review the documentation before concluding its assessment.
Rationale
Review the request and supporting documents to record the basis for the decision.
Approvers
Rafael · Finance / Clara · Controls
Linked evidence / 01Supplier request.pdf

Source: document attached to the decision

supports
Representation of Decisions fields. Illustrative example.

03Agenda

Responsibility continues after the decision.

Link a decision to activities with owners, deadlines and evidence. Track work that depends on people, including external participants.

Agenda tracks human activities. Linking a decision does not, by itself, automatically block execution.

Recorded decision

Supplier record review

linked activity

Activity

Review the documentation received

Owners
  • Marina · OperationsTheir part completed
  • Rafael · FinanceTheir part pending
Deadline
September 18 · example
Evidence
Documentation received.pdf

One part completed. The activity still has pending work.

Illustrative example · synthetic data

04Governance Gate in API integrations

Approval is a step. Authorization has conditions.

State 1 of 5: Pending

An eligible approval is missing. There is no authorization yet.

What changed
One approval recorded; another pending.
Who acts now
The approver still missing.

Illustrative, simplified example of an integrated flow using the API. Ciizer’s API does not automatically call your ERP or bank.

05The incomplete path

No confirmation. No assumed conclusion.

The state must explain what happened — and what cannot yet be asserted.

SituationCondition / evidenceConsequence
PendingEligible approvals are missing.Reservation is not permitted.
RejectedAn eligible approver rejected the request.Authorization is denied.
ExpiredThe deadline or validity has elapsed.This authorization cannot be consumed.
DivergentWhat was observed differs from what was authorized.The divergence remains recorded.
Unknown outcomeThere is insufficient evidence of the outcome.Assume neither success nor failure.

06Evidence and provenance

The event passes. The connection remains.

Reconstruct the relationship between decision, authorship, approval and evidence. Examine events and use the available export and verification paths.

Illustrative decision history
  1. 09:10

    Decision recorded

    Context and rationale associated with the record.

    Marina · Operations
  2. 09:14

    Evidence linked

    Document associated with the decision and its source.

    Supplier request.pdf
  3. 10:32

    Vote recorded

    Approval associated with the participant.

    Rafael · Finance

What supports a review

Ordered events, authorship references and related evidence. Technical checks examine the available artifacts; they do not replace a review of the content.

About the scope of verification

How does SHA-256 integrity verification work?

Each record contains cryptographic data for integrity comparison. A divergence can be identified when the record or the package is submitted to a new technical verification.

What happens to the evidence if Ciizer ceases to exist?

Proof Packages can include exported artifacts for independent technical verification, such as hashes, signatures and compatible time stamps. How far a verification can go outside the platform depends on the artifacts, the tools and the applicable certificate chain.

Are decisions stored in Brazil?

Location and transfers depend on the service and the provider involved, observing the applicable data-protection mechanisms. See the Privacy Policy for more information.

07Operational fit

Every connection has a purpose.

Ciizer works alongside existing tools. Each integration has an explicit role.

Communication
Microsoft Teams / Slack

Notifications and links to access the context in Ciizer.

Work
Jira

Issue creation from decisions, according to configuration.

Metrics
Power BI

Metrics sent to the configured destination.

Identity
SSO / OIDC

Corporate authentication, according to the configured connection and domain.

Programmatic governance
API / Governance Gate

Requests, queries, authorization reservation and external outcome recording.

Queries and verification
MCP

Decision queries, integrity verification and exports. Does not create or approve decisions.

Availability depends on the plan, configuration and organization enablement. Execution integrations require implementation in the consuming system.

Participants can be outside your organization.

External invitations define participation scope. Approvals use applicable verification requirements; Agenda allows activities to be assigned to external participants.

  1. Scoped invitation
  2. Applicable verification
  3. Recorded participation
Identity, access and data

Organization permissions, authentication according to criticality and scoped record access. Talk to Ciizer about your process’s security requirements.

Read the privacy policy

Plans to get started.

Public prices in Brazilian reais. Integrations and terms depend on the plan.

Starter

For teams starting to record decisions with verifiable evidence.

Up to 10 users

MonthlyR$990.00/mo
AnnualR$9,900.00Single annual payment2 months saved
Create account
Includes
  • Up to 50 decisions per month
  • Agenda for up to 500 activities a month
  • Agenda reminders by email
  • Hashed, timestamped records
  • LGPD and core frameworks
  • Compliance reports in PDF

Growth

For taking governance into daily operations, connected to your systems.

Up to 30 users

MonthlyR$2,990.00/mo
AnnualR$29,900.00Single annual payment2 months saved
Start with Growth
Everything in Starter, plus
  • Unlimited decisions, with hierarchy
  • Unlimited Agenda, WhatsApp and Teams
  • Slack, Teams and Jira integrations
  • REST API to connect your systems
  • +76 frameworks, such as ISO 27001
  • AI that suggests decisions from minutes

Enterprise

For scale, regulatory or contract needs beyond self-service.

Users set by contract

PriceOn request

Discuss your organization’s requirements.

Talk to Ciizer
Everything in Growth, plus
  • +77 frameworks, such as SOX and GDPR
  • Higher hourly record throughput
  • Commercial terms set by contract

15-day Growth trial, no card required.

08Your first process

Where does your operation need a condition?

  1. Which decision needs governance?
  2. Who needs to participate?
  3. Where does the operation need control?

Start with a concrete process. Let’s understand where Ciizer fits.