The French platform for field operations
The field moves on. So does your data.
Site reports, safety audits, service sheets, quality checks, delivery notes: your crews fill them in on a phone, even with no signal. The moment the network returns, everything reaches the office — photos, signatures, position — with the document already made.
15 days • 10 users • no card required
- Fully offline data entry
- Faithful PDF, Word and Excel
- Open API, webhooks and exports
- Data hosted in France
Daily site report
- Site
- A12 — Section 3
- Weather
- Rain
- Crew on site
- 7
| Date | Site | Author | Crew | Status |
|---|---|---|---|---|
| 12/03 | A12 — Section 3 | M. Dubois | 7 | Submitted |
| 12/03 | Carnot Street | S. Lemaire | 4 | In review |
| 11/03 | A12 — Section 3 | M. Dubois | 6 | Approved |
Four commitments, before any feature
- Field first
- Large targets, one action per screen, usable with gloves on, upload state always visible. The field app is not the console made smaller: it is written for a phone held in one hand, in the rain.
- Nothing lost
- No field data is ever deleted without an explicit user action. The sync protocol never decides on its own to give up on a submission: an interrupted upload resumes, a conflict is shown, nothing disappears quietly.
- Sovereignty
- Submissions, photos and exports stay on servers located in France, under French law. Isolation between organisations is not a coding convention: the database itself enforces it, on every table.
- Openness
- Your data leaves as easily as it arrives: documented REST API, signed webhooks, CSV, Excel and photo-archive exports. Imports take your Kizeo forms and your history; nothing here trades on how hard it is to leave.
No signal
The basement, the tunnel, the dead zone
A submission goes through five states, and the field app shows them as they are. What runs below is not decorative: these are the sync protocol's states, with the labels a technician reads on their phone.
Daily site report
- Site
- A12 — Section 3
- Weather
- Rain
- Crew on site
- 7
draft
Draft
Filling starts. Everything is written to the phone's local database, before the network is even a question.
queued
Waiting to send
The form is finished and signed. With no network it enters the queue and stays there: nothing expires, nothing is cleaned up.
pushing
Sending
The network returns. The submission goes out; an interrupted upload resumes where it stopped rather than starting over.
media_uploading
Sending photos
Photos and the signature follow the submission, one at a time: a drop costs only the piece in flight.
synced
Synced
The office has the submission, its media and its position. The document is generated, the email goes out, the approval opens.
- 1 waiting for a network
- Data entry never stops
- Everything is written to the phone's local database before the network is even a question. A forty-field form fills in completely without a single bar of signal.
- A queue that does not empty itself
- A pending submission stays until it is sent. No expiry, no automatic cleanup, no "we could not keep it".
- An interrupted upload resumes
- The tunnel cuts the connection halfway through a four-megabyte photo: on return, the upload continues where it stopped rather than starting over.
Builder
The builder, right here on the page
This is not a screenshot: it is the console's builder, loaded with a template the product ships. Add a field, change a condition, move a page. Nothing is saved — it is a sandbox, and it does not ask for an account.
Sandbox: nothing is saved.
1. Site
- Sitetext
- Site addressaddress
- Datedate
- Written bytext
2. Crew
- Workers on siterepeat
- Nametext
- Tradeselect
- Hoursnumber
3. Progress
- Work donetextarea
- Blocking issuestextarea
- Progress photosphoto
- Voice noteaudio
4. Signature
- Incident or accident?boolean
- What happenedtextarea
- Site managertext
- Signaturesignature
- About thirty field types
- Annotated photo, finger signature, position with its accuracy, barcode, NFC tag, voice note, sketch, repeatable table, reference list of customers or parts.
- Calculations checked at publish time
- A broken formula is rejected when you publish, not discovered by the technician in the middle of a site visit.
- A published version never changes
- Submissions already filled stay readable exactly as they were entered, even after ten edits to the form. That is what makes a history defensible.
Documents
The deliverable is usually the document
A handover certificate is not sent as a spreadsheet. Rondea makes the PDF from the submission — or fills your own Word and Excel template, in your layout, with your photos and signatures in their place.
- A clean PDF, with nothing to lay out
- Generated from the form: pages, sections, tables, photos and signatures appear in the order they were filled.
- Or your company template
- A .docx or .xlsx with your own tags — {{site}}, {{photos_image}}, a loop over a table — filled on every submission.
- Sent without anyone thinking about it
- The document reaches the customer by email as soon as the submission arrives, or on demand from the console.
Daily site report
Site
- Site
- Site address
- Date
- Written by
Crew
- Workers on site
- Name
- Trade
- Hours
Signature
Data
Your submissions, not a black box
Filter, correct with the full edit history, save a view and share it, export whenever you like. The columns below are form fields: the explorer takes them as they are.
| Date | Site | Author | Crew | Status |
|---|---|---|---|---|
| 12/03 | A12 — Section 3 | M. Dubois | 7 | Submitted |
| 12/03 | Carnot Street | S. Lemaire | 4 | In review |
| 11/03 | A12 — Section 3 | M. Dubois | 6 | Approved |
- Correct without losing the original
- A correction from the console creates a revision: who, when, the value before, the value after.
- Export whenever you like
- CSV, Excel, photo archive. On the rows you ticked, or on everything the filter holds.
- Numbers that come from the submissions
- Sum, average, count by form, by period, by author — including on the columns of a repeatable table and on calculated fields.
Automation
What happens after the submission
A submitted answer triggers a sequence of steps, and each step leaves a trace: what was attempted, when, with what result. Six step types, combinable, each with its own condition.
- A condition on every step
- "Only if the check failed", "only above €10,000": the condition is written like a form calculation.
- An approval with a deadline
- The site manager receives the request, decides from their decision inbox, and the next step follows.
- A log, not a black box
- Every run can be read step by step, and a failed step is retried without replaying the others.
- ↳Submission sent
- Change the status
- Generate the document
- Send the email
- Assign it to someone
- Ask for approval
- Call a webhook
Openness
An API, webhooks, and the way out
Rondea sits beside what you already run. Everything the console does goes through a documented REST API with scoped keys; everything that happens can be pushed to your own systems through a signed webhook.
- Scoped keys
- A read key for your data warehouse, a write key for your ERP: each can do only what it is for, with its own call limit.
- Signed webhooks, with retries
- Every delivery is signed and logged; a missed delivery is retried, and the log says why it failed.
- In and out
- Imports take your Kizeo forms and your CSV or Excel history, with a line-by-line report. Exports let you leave with everything.
curl -s "$API/v1/orgs/$ORG/submissions?formId=$FORM&limit=50" \
-H "Authorization: Bearer $TOKEN"POST /your-endpoint
X-Rondea-Signature: sha256=…
{ "event": "submission.created", "submissionId": "…" }Sovereignty
Where your data is, and who can read it
In most IT departments the question comes before the demo. Here are the answers, without hedging — and the security page details what is done, what is under way and what is not.
- Hosted in France
- Database, files, backups and logs stay on servers located in France, operated under French law.
- One organisation cannot see another
- Every business table carries its organisation, and the database itself refuses a read outside that boundary. This is not a check the code could forget.
- Erasure and portability planned for
- Full export of your data on request, deletion on request, register of processing activities and subprocessors published.
Industries
What your trade still fills in on paper
The product is the same everywhere; what people do with it is not. Each industry page starts from a real document and from the templates Rondea ships for that trade.
Plainly
What we do not claim
You are probably comparing Rondea to vendors that have been around for fifteen years. So here is where we are not, up front: it is the one page on this site our competitors will not publish.
- Rondea is a young product. You will find no customer logo here, no testimonial, no usage figure: we do not have them yet, and we will not invent them.
- The external penetration test and the RGAA accessibility audit are planned and budgeted, not finished. The security page says where we stand, point by point.
- Single sign-on works over OpenID Connect and has not yet been validated against a real corporate directory.
- Everything else on this site describes code that exists, runs in preproduction and can be demonstrated live.
Try it on a real site, not on a demo
Fifteen days, ten users, no card. Build a form in the morning, have it filled in the afternoon, and watch what reaches the office.
15 days • 10 users • no card required