Skip to content
Blaze

Legal practices · Monaco

An open website. Client matters kept in their proper place.

From public practice to private matter

Diagram of a proposed workflow to build and verify. It does not represent a client case or an operating production service.

  1. Presentation

    Validated areas, people and publications

  2. Initial contact

    An enquiry without sensitive attachments

  3. Matter workspace

    Access limited to authorised participants

  4. Selected sharing

    Separate internal notes from shared documents

A visitor to a law firm's website may be looking for expertise, a person or a way to make contact. An existing client may need a document or an update on a matter. Blaze proposes designing those journeys without confusing them. This is a service outline to discuss with a practice, not a portal already operated for a client or a guarantee that software alone can establish professional confidentiality.

Be precise about the public practice

Public content should identify areas of work, people and contact arrangements accurately. Professional titles, biographies and references need to be supplied or validated by the practice. Prestigious language or an atmospheric photograph must not imply an office, team member or mandate that does not exist. A concise presentation can still give a prospective client enough information to decide whether an enquiry is appropriate.

Publications need dates, authors and references that the practice stands behind. French, English and Italian versions should preserve the intended precision without turning general commentary into advice for an individual situation. The publishing structure can help organise validation and later correction. It should also make it possible to identify an older note whose legal or factual context needs review.

Design the private matter separately

A client portal could support document submission and selected progress updates. It should distinguish received material, working versions and items the practice has chosen to share. Access for one client must not reveal internal comments, another party's information or unrelated matters belonging to a family member. The permission model needs to reflect the actual relationships rather than assume that every contact can see the same file.

Expected checks include authentication, document-level access, link validity and support permissions. Receiving a link by email should not grant general access to the practice. Tests should cover an unintended recipient, a revoked session and a direct attempt to open an unauthorised document. A successful upload is only one part of the journey; mistakes and withdrawal of access need equally clear behaviour.

Keep legal judgement with the practice

Where an activity involves vigilance obligations, the practice must establish applicable requirements with competent professionals. A portal could help collect relevant information but should not request identical personal documents indiscriminately for every matter. A commercial page cannot determine the scope of professional secrecy, legal duties or exceptions. Those questions need to inform the agreed workflow rather than be inferred from a template.

Vedetta is being developed for all professions concerned by vigilance obligations in Monaco. A future connection with a law firm's portal remains to be designed and verified. Collection, screening and suggestions should prepare an examination. Software must not automatically accept a client or make a legal conclusion, and a product concept should not imply that those integrations are already available.

Define operating responsibilities before use

Connections to matter management, signature or billing depend on existing tools and available permissions. The study should examine exchanges, document copies and failures before promising an integration. A document sent to a third party belongs within the approved processing scope even if the main portal is hosted locally. An apparently convenient connection may therefore need to remain a manual step until its conditions are established.

The practice should receive a site it can maintain with clear responsibilities: who updates the team and services, who approves sensitive content and who handles a technical incident. If a client area is included, its access and recovery arrangements need their own specification. The handover records accounts, data access and agreed code rights. These practical details help the firm keep its public presentation current while maintaining a deliberate boundary around confidential exchanges and internal working documents.

Examine the scope

Service outline

Proposed service scope

Explore how we plan a website or business application, from visitor journeys and content to delivery and handover.

Read the presentation

Text reviewed on

Questions and answers

Can the practice commission a website without a client portal?
Yes. A presentation website can be a separate scope with defined content, languages and contact arrangements, avoiding unnecessary document collection. A later portal requires its own study of permissions and processing; it is not implicitly included in the initial website.
Can a portal itself guarantee professional confidentiality?
No single technical feature provides that assurance. Organisation, authorised processing, access rules and tested controls all matter. A portal may reduce scattered exchanges, but responsibilities and support access still need to be defined and examined before real client information is used.
How should a practice assess hosting and processors?
The project should document destinations including copies, logs and backups. Monaco Telecom is the selected production host for Blaze and its product, with readiness work continuing. That choice does not authorise another provider or a transfer of the practice's documents.
Could the website include legal articles in several languages?
A publication area can be scoped with authors, dates, references and language equivalents. The practice validates content and updates. It should also provide a way to correct older commentary and distinguish general information from advice given to a particular client.

Explore related topics

Define the right scope

A workflow, its users and the information they need: a concrete starting point for a project.

Contact Blaze