Availability
Capacity, leave and relevant professional context are maintained without opening a full child case file.
SPECIALISED PUBLIC-SECTOR WORKFLOW
Qavirio Accueil Enfance
Shared professional workflow around family care — without replacing the existing case-management system.
Accueil Enfance is designed as an operational collaboration layer for family-care professionals and authorised departmental staff. It brings availability, placement context, PPE, evaluations, claims, documents and traceable collaboration together while keeping role and information boundaries explicit.
01 · Purpose
Why this product exists.
Accueil Enfance is designed as an operational collaboration layer for family-care professionals and authorised departmental staff. It brings availability, placement context, PPE, evaluations, claims, documents and traceable collaboration together while keeping role and information boundaries explicit.
02 · Operational problem
Much of the daily work around family care happens beside the formal case system in paper, email, separate forms and administrative processes.
This creates duplicate entry, unclear availability/status, divergent versions and administrative load. Accueil Enfance targets that operational layer; it does not claim to replace SOLIS or a full ASE case file.
Make availability and placement context visibly shared.Structure PPE/evaluation and daily follow-up without broadening case-file rights.Move claims and administration out of scattered paper flows.Make authorship, status and transmission traceable.
03 · How it works01 02 03 04 05 06
An operational collaboration layer around the existing case-management environment.
Orientation & placement context
Authorised roles use the information needed for offer/orientation and the current placement.
PPE & évaluations
Shared project/evaluation workflows keep authorship, status and relevant continuity explicit.
Collaboration & transmission
Tasks, documents and professional transmissions are tied to role, recipient and status; the new observations/transmissions workflow remains under qualification.
Claims & administration
Mileage, expenses, presence and profile data can be reused in a controlled way and snapshotted on submission.
Audit & follow-up
Important actions, status and transmissions remain traceable so workflow does not depend on isolated email or verbal reminders.
04 · Capabilities
Availability & leave
Manage operational availability with planning and offer context.
PPE
Shared project context with bounded authorship and continuity across collaboration.
Evaluations / ETS
Professional evaluation cycle with role-bounded contributions and reusable supporting material where permitted.
Transport & mileage
Trips, reasons, distances, monthly totals and configurable departmental rules.
Documents & contracts
Document access aligned to administrative responsibility without automatically granting full case access.
Traceability
Keep author, time, status, recipient and important changes visible in the operational workflow.
05 · User experience & roles
Assistant Familial
Calm task-oriented workspace for availability, planning, PPE/evaluation contributions, claims and authorised documents.
Référent ASE
Broader case-management perspective for placement context, PPE, evaluation and authorised follow-up.
Référent professionnel AF
Professional support around the family-care professional without automatic full case-file access.
Responsable de service
Operational overview, validation and governance aligned with service responsibility.
Gestionnaire administratif
Administrative processing, contracts, documents and claims within the role boundary.
BOA
Limited availability/orientation workspace; no broad professional notes or full child case file.
06 · Use casesMONTHLY ADMIN PPE / EVALUATION AVAILABILITY TRANSMISSION · QUALIFICATION
Mileage and recurring claims
The professional reuses profile data, records trips and completes a controlled monthly submission instead of assembling paper bundles.
Continuity without one broad file for everyone
PPE and evaluation can be updated by the right roles while preserving authorship and access boundaries.
Know faster where capacity is available
Availability and leave do not depend only on isolated calls or spreadsheets, giving authorised teams a more current operational base.
Transmit professional observation factually and traceably
The intended workflow separates observation from interpretation, links author/recipient/status and preserves provenance. This capability remains explicitly under qualification and is not claimed as a completed production feature.
Real product interface
The hosted demo shows a calm task-oriented public-sector workflow.
IN-DEPTH EXPLANATION
Accueil Enfance in detail: organise shared work without recreating the entire child case file.
Accueil Enfance grew from a practical problem: much of the professional work around family care is shared between different roles, while the formal case file does not have the same purpose or access rights for everyone. The family-care professional handles daily and administrative tasks, the ASE case worker follows the child and PPE, the professional supervisor supports the carer as a professional, administrative staff process claims and documents, service managers oversee capacity and validation, and the placement office mainly needs information for availability and orientation. A shared application should not collapse those responsibilities into one oversized case file. The product is therefore designed as a workflow layer with explicit information boundaries.
One workspace does not mean one permission level
The interface changes by role because each role has a different operational question. The family-care dashboard brings placements, availability, professional notes, evaluations, kilometres, presence, expenses and documents close to daily work. The professional-supervisor view focuses on objectives, professional support and a profile that deliberately does not open the child file. The placement-office view concentrates on capacity and orientation information. Management and administrative views expose the queues and documents they are responsible for. This is not cosmetic personalisation; it is part of the access model. The application aims to show enough information to perform the authorised task without widening visibility merely because the data exists elsewhere in the organisation.
Operational continuity around PPE, evaluations and administration
The workflow brings together tasks that otherwise tend to be fragmented across paper, email and separate spreadsheets. Availability can inform placement capacity; PPE and evaluations remain identifiable professional processes; declarations can carry version and validation state; documents and contracts can be handled by the authorised administrative role; and professional follow-up remains distinct from child-specific notes where that boundary is required. The value is not simply digitising a form. It is giving the organisation a common status model so the same item does not exist simultaneously as an email attachment, an undocumented phone call and an outdated local spreadsheet without a clear source of truth.
A complement to the case-management system, not a replacement claim
Accueil Enfance is intentionally positioned around the shared operational layer. A Département may already have a formal ASE or case-management environment with its own legal record, internal workflows and integrations. Replacing that entire environment would be a very different project. The Qavirio approach is to identify which collaborative and administrative flows can be improved without unnecessarily duplicating sensitive records. That is why deployment, data boundaries, retention, role mapping and integration must be reviewed with the customer before production. The current hosted environment is a controlled demonstration with fictional data, and the website states the remaining qualification gates rather than presenting the demo as a completed departmental production deployment.
07 · Architecture
Server-side web application with domain and authorisation boundaries.
The hosted product line uses Python, Django and PostgreSQL. Authorisation belongs server-side to tenant, role, assignment and active-placement context; browser navigation is never the security boundary. Demo, staging and production use separate configuration and secrets.
Browser / HTTPS→Django application→Server-side RBAC & domain policy→PostgreSQL→Audit / exports
08 · Security & data
Tenant, role, assignment and placement boundariesServer-side authorisation, not just hidden navigationFictional data and temporary accounts in the commercial demoMFA/TOTP architecture in staging; reset/recovery management remains a qualification gatePassword brute-force protection for multi-worker runtime not yet fully provenAudit and professional boundaries remain core product concerns
09 · Integration
Accueil Enfance is a complementary workflow layer, not a claimed SOLIS integration.
No real technical SOLIS integration is currently built. Any future integration starts with discovery of APIs/exports, customer architecture, IT/security requirements and contractual boundaries. Until then, product positioning remains explicitly complementary.
10 · Deployment & hosting
Controlled Hosted Demo
Current commercial demonstration model with fictional data and controlled access.
Qavirio Managed Private
Commercial target architecture managed by Qavirio; production claim only after full qualification, contract, security and privacy acceptance.
Customer Hosted / Private Cloud
Remains a full future deployment option on departmental infrastructure when integration, operations and responsibilities are contractually defined.
11 · Operations & support
12 · Product status
HOSTED DEMO · QUALIFICATION IN PROGRESS
The hosted demo is a controlled demonstration environment with fictional data. The current staging line still has security and workflow qualification gates open and is not presented as a production-ready departmental release.
DB-backed password brute-force protection suitable for multiple gunicorn workersComplete MFA admin reset/recovery management + auditControlled presenter-account mechanism without weakening securityFull role-by-role walkthrough across six personas and core workflowsComplete observations/transmissions workflow: facts vs interpretation, provenance, recipient/statusProduction release requires fresh backup, freeze/tag, migration plan, smoke, rollback and formal go/no-go
13 · Contact / demo
Request controlled demo →Review the operational workflow first; then involve IT, security and privacy for technical review.
The controlled demo is intended to discuss roles, information boundaries, daily workflows and traceability. Integration, hosting, security and privacy are then handled as separate implementation and assurance topics.