Skip to content

Solutions

What Innovaforte can do for a legal or notarial office — labelled honestly.

Each area below carries one Sector Core maturity label: Concept (described, not built), Prototype (working software on fictional data), Pilot or Production. Nothing here is at Pilot or Production.

Solution areas

  • Swiss notarial layer

    Notarial workflows

    Illustrative notarial areas, the client/matter model and the canton-configuration concept.

    Open notarial workflows
  • Try it

    Nine demonstrations

    Interactive prototypes on one fictional office model.

    Open the demonstrations

Reading this page

Maturity labels

Maturity: Concept
A described idea, capability or architecture. No working software for it exists yet.
Maturity: Prototype
Working, interactive software using fictional, synthetic data. Not used in any real office.
Maturity: Pilot
In bounded use with a real client under professional oversight. Nothing is at this stage yet.
Maturity: Production
Released, supported software in routine use. Nothing is at this stage yet.

Ten areas

Legal & Notary capability areas

  • 01Matter & project management

    Maturity: Prototype

    A single operational record for each matter: reference, type, responsible professional, parties, status, dates, tasks, documents, costs and history.

    • Matter reference conventions defined per office
    • Responsible professional and supporting staff
    • Status model configurable to office practice
    • Complete operational picture on one screen

    Current status: An interactive demonstration exists with synthetic data. A real deployment would be designed per office.

  • 02Client and contact management

    Maturity: Concept

    People, organisations and related parties recorded once and reused across matters over years, rather than retyped per file.

    • Person, organisation and related-party records
    • Relationships between parties
    • Matter history per client
    • Duplicate and incomplete-record handling

    Current status: Designed and illustrated as a data model. No CRM software is running here yet.

  • 03Document workflows

    Maturity: Prototype

    Explicit stages for drafting, internal review, client information requests, approval, execution and archival — with a visible owner at each step.

    • Who acts, what is waiting and what changed
    • Explicit human approval points
    • Version history per document
    • No stage is treated as legally sufficient by default

    Current status: The stage model is demonstrated interactively. Signature, execution and archival integrations are not built.

  • 04Document generation and assembly

    Maturity: Concept

    Assembling drafts from office-owned templates and structured matter data, so the same details are not typed repeatedly.

    • Office templates, not generic ones
    • Structured fields drawn from the matter record
    • Draft status until a professional approves it
    • Generated text is never treated as final

    Current status: Deliverable as a bespoke build. Templates and clause wording remain the office's professional responsibility.

  • 05Task, deadline and workflow coordination

    Maturity: Prototype

    Tasks and dates attached to matters and people, with a shared view of what is due, what is late and what is blocked.

    • Deadlines tied to matter stage
    • Workload by responsible professional
    • Blocked items with a stated reason
    • Decision support, never automated legal decisions

    Current status: Demonstrated with synthetic items. Calendar and email integrations are not built.

  • 06Time, fees and billing workflows

    Maturity: Concept

    Recording time and fee items against matters and moving them through review, invoicing and follow-up.

    • Fee items linked to matter and professional
    • Items awaiting review or invoicing
    • Tariff and fee rules configured per office and jurisdiction
    • No accounting system connection assumed

    Current status: Described as an architecture only. No billing software, tariff logic or accounting integration exists.

  • 07Knowledge and precedent management

    Maturity: Concept

    Making an office's own precedents, clauses and internal notes findable, with the source always visible.

    • Office-owned material only
    • Source shown with every result
    • No external legal database is implied
    • Professional judgement remains with the professional

    Current status: Conceptual. No retrieval system is running on this site and no legal database is connected.

  • 08Controlled document analysis

    Maturity: Prototype

    Assisted reading of documents: structured fields, dates, parties, obligations and gaps surfaced for a professional to check.

    • Every result is assistance, not a conclusion
    • Missing information is flagged explicitly
    • Professional review required on every output
    • Nothing here is legal advice

    Current status: The demonstration uses pre-prepared fictional results to show the interaction. No model runs on this site.

  • 09Auditability and activity history

    Maturity: Concept

    An append-only record of who did what and when, on matters, documents and client records.

    • Actor, action, object and timestamp
    • Document version lineage
    • Access events where required
    • Retention rules agreed with the office

    Current status: Deliverable in a real implementation, and illustrated in the matter demonstration. The demonstration history is synthetic.

  • 10Secure application modernisation

    Maturity: Concept

    Replacing spreadsheets, shared folders and ageing tools with controlled applications the office actually owns.

    • Bounded scope with a measurable outcome
    • Role-based access from the start
    • Portability and ownership of code and data
    • Related to Secure Vibe, which is still in development

    Current status: This is delivery work Innovaforte performs. It is not a packaged product and confers no certification.

Security and privacy

Legal and notarial information can be highly sensitive.

A real implementation would therefore have to address the following. These are requirements we would work through with an office — not claims about what already exists.
  • Strong authentication for every user
  • Role-based access aligned to office roles
  • Least-privilege access by default
  • Audit trails over matters, documents and client records
  • Encryption in transit and at rest
  • Controlled document storage rather than shared folders
  • Explicit data retention rules per document type
  • Backups with a tested restore procedure
  • Separation of client environments where appropriate
  • Jurisdiction and data residency decisions taken deliberately
  • Professional confidentiality considerations reflected in the design
  • Secure deployment architecture with reviewable configuration

What we do not claim

Innovaforte does not claim to be fully compliant, GDPR certified, Swiss-law certified, notary compliant, ISO 27001 certified or SOC 2 certified. No independent accessibility certification is claimed either. If any of that becomes factually true, it will be stated as fact and not before.