Frame a multi-domain performance platform
The functional and technical requirements specification that BranchCheck was built from, published as-is: twenty sections, from the “one engine, seven domains” principle to acceptance criteria. A requirements referential for your tender — written to be neutral, not to sell.
For whom
The departments that have to frame this need — not the ones selling it.
Risk / compliance department
Centralise the requirements, controls and proofs of a branch network without bolting on one tool per domain.
Quality department
Tie non-conformities, complaints, root causes and effectiveness measurement into a single improvement loop.
Network / IT department
Write a tender that asks for an engine — and spot the answers that deliver seven juxtaposed applications.
What the document covers
Twenty sections, from the definition of the need to acceptance criteria.
The guiding principle
§1: one engine of referentials, campaigns, evaluations, proofs, actions, validations and reporting serving every domain.
The seven domains, requirement by requirement
§7: compliance (CON), permanent control (CP), quality (QUA), audit (AUD), animation (ANI), commercial (COM), training (FOR) — every requirement coded and prioritised.
Proofs and mobility
§9: offline-first, synchronisation, photos, GPS and signatures, proof sealing, an exportable and verifiable evidentiary file.
Technical requirements
§10: architecture, APIs and integrations, performance, security and privacy, auditability, governed AI.
Acceptance and criteria
§15: acceptance organised by business journey — pronounced only with no blocking or critical defect left.
How to read it — the editorial frame
This document is a requirements referential, not a product catalogue.
It describes the full target, including requirements BranchCheck does not cover: in v1.5, five domains run end to end on the engine (compliance, permanent control, quality, audit, network animation) and two are partly covered (commercial performance, training); each domain page says, requirement by requirement, what is covered. Its value comes from its neutrality — written for IT and the business, before it was ours. Read it as “the requirements to cover”, never as “what BranchCheck does”.
The full text
Published in full on this site, with the same structure as the source document — printable from the browser.
Read the requirements specification
The full text is published in French, the source document's language — untranslated, so its requirements stay untouched.
Source: “Cahier des charges fonctionnel et technique” v1.0, 28 August 2026 (BranchCheck repository); companion multi-domain PRD, 29 August 2026.
Talk about it
Writing a tender on this perimeter? This document is ours — let's discuss your requirements, shipped or not.
Contact us