Site foremen, truck drivers, plant shift supervisors, storekeepers, QHSE managers or branch teams: we design the app that takes over from paper forms, the shared spreadsheet and the photos sent over WhatsApp. On your teams’ phones, offline when the job requires it, connected to your tools and maintained over time.
Daily site report
Site A · Lot 2 — Drainage
Examples
These are examples, not client references: some mirror what our own software does, such as the daily site report and site audit in Rivena Audits & QHSE, or the daily truck check in Rivena Equipment. Each app starts from the way your people actually work, and the first version focuses on a single process.
Site foreman
In the field: Construction site
Crew, machines and hours, work done, weather and photos: the report is filled in on site, even with no signal, signed with a finger and sent to the works manager as soon as the connection returns.
Often replaces: the paper report and photos sent over WhatsApp
Truck driver or machine operator
In the field: Depot, before departure
A walk round the vehicle, item by item: tyres, fluid levels, lights, documents on board, odometer or hour-meter reading. A failed item requires a photo and alerts the workshop; a blocking fault keeps the vehicle off the road until it is repaired.
Often replaces: the paper check sheet, often filled in after the fact
Shift supervisor
In the field: Asphalt or materials plant
Tonnage per truck, delivery note number, product and destination site, entered during the shift with a photo of the note. The quantities are ready for the end-of-shift report, with no retyping in the evening.
Often replaces: the shift logbook and delivery notes retyped into Excel
Storekeeper
In the field: Warehouse, site or plant
The delivery note is photographed, quantities received are checked against the order, and shortfalls or damage are reported on the spot. Purchasing sees the receipt without waiting for the paperwork.
Often replaces: the delivery note that reaches head office at month end
Team leader
In the field: Site, plant or branch
Who is present, who is absent, and hours per person and per site, entered from the team list. Once approved, the hours can feed labour cost per site, per shift or per branch. Rivena HR also offers staff time and attendance, by app or by facial recognition.
Often replaces: paper timesheets retyped into Excel
QHSE manager
In the field: Site, plant, depot or workshop
A versioned audit checklist, compliant or non-compliant answers with photos, and the signature and PDF report produced on the spot. Incidents and unsafe conditions can be reported by anyone, then tracked until the corrective action is closed.
Often replaces: the paper log and reports retyped at the office
Delivery driver
In the field: At the customer’s premises
Materials, goods or equipment delivered: photo, name and signature of the person receiving it, time of hand-over. The proof is attached to the delivery note and can be viewed from the office before the truck is even back.
Often replaces: the signed note that gets lost between the truck and the office
A paper form, a shared spreadsheet or a WhatsApp group that has become a working tool: that is often the right starting point for an app.
Describe your processDesign principles
On a construction site, in a truck cab, beside a plant or in a warehouse: your teams work on their feet, sometimes wearing gloves, in the sun or the dust, often with a weak signal. These choices shape every screen we design.
Large touch targets, few fields, choices rather than typing, and strong contrast for outdoor use. Navigation stays within thumb reach, at the bottom of the screen.
The camera is built into the form: each photo is attached to the report, the truck or the delivery, with its date and author. An item can require a photo before it is accepted. Depending on the project, the camera also reads a QR code stuck on a machine or a barcode on a delivery note.
The person receiving a delivery, the auditee or the site foreman signs on the screen with a finger, and the PDF is generated on the phone, ready to share. That is how the Rivena Audits & QHSE Android app works.
The person in the field enters, their manager approves, management reviews. Menus and data adapt to each role, and permissions are checked on the server.
With Rivena Fleet, through its documented API. With Rivena ERP, Rivena HR, Rivena Equipment or your other software, as far as they allow: API, imports or Excel exports. The aim: nothing entered in the field has to be retyped at the office.
Who entered what, when, and who approved it: every document keeps its history. Once approved, a document cannot be changed without leaving a trace.
These features are possible, but they come with costs and constraints. We suggest them when your needs justify them, not by default.
For areas with no signal: entries, photos and signatures stay on the phone and are sent once the connection returns. This is how the Rivena Audits & QHSE Android app works; it needs clear rules for conflicts and more testing.
Reminders and approval requests. On iPhone, they require the app to be added to the home screen.
When distribution or a phone feature calls for it. We recommend opening the developer accounts in your company’s name.
Alongside French, when your teams prefer it.
Our software
Rivena is a young company: rather than references, we show you our own software. The offline Android app of Rivena Audits & QHSE, the phone-first daily check in Rivena Equipment, and Rivena Fleet and the Manufacturing, distribution & services edition of Rivena ERP as installable web apps: all follow the principles we will apply to your app.
Rivena ERP · Audits & QHSE
Native Android app, works offline
Rivena Equipment · Workshop
Web page designed for the phone
Rivena Fleet · GPS tracking
Installable web app
Rivena ERP · Manufacturing, distribution & services edition
Installable app and Android APK
How we work
We start small: one process, one team, one first location, whether that is a construction site, a depot, a plant or a branch. The scope of each version is agreed with you.
Observe
We follow the process as it really happens in the field, not as the procedure describes it: who enters what, when, on what medium, with or without a signal, and what happens to the information next.
Test
Clickable screens, tried on a phone by the people who will use the app. Screens change before any code is written.
Deliver
Regular versions to try on your phones: you adjust course along the way, not at the end.
Maintain
Installation on the phones, hands-on onboarding at a first location, then extension to other teams. After that, fixes, updates and improvements planned with you.
Frequently asked questions
Not necessarily. An installable web app is added to the home screen from the phone’s browser and updates without going through an app store: that is how Rivena Fleet and the Manufacturing, distribution & services edition of Rivena ERP work. On Android, we can also provide an APK file for direct installation. Publishing on the App Store or Google Play remains possible when your project calls for it; it adds the store’s review process and developer accounts, which we recommend opening in your company’s name.
Yes, when your working conditions call for it. The Rivena Audits & QHSE Android app works offline: checklists, photos, finger signature and a PDF generated on the phone, then sync once the signal returns. This mode has a cost (storage on the phone, rules for conflicts, more testing), so we choose it at scoping when your work areas justify it. Conversely, Rivena Fleet and the Manufacturing, distribution & services edition of Rivena ERP deliberately keep no business data offline.
An installable web app does: you add it to the home screen from Safari, as on Android. Some features behave differently on iPhone, such as notifications, which require the app to be installed on the home screen. The Rivena Audits & QHSE offline app is a native Android app, and the APK file is for Android only: if your teams use iPhones, we take that into account from scoping to choose the right approach. We test on the phone models your teams actually use.
The contract sets this out before work starts. Our principle: the code developed specifically for you is handed over with its documentation, and you remain free to have it developed further by another provider. The generic building blocks we reuse from one project to the next remain ours, with a right of use for your app.
We do, if you wish, under a maintenance agreement: fixes, adaptation to new versions of iOS, Android and browsers, and small improvements. A field app that is not looked after gradually degrades. If you would rather take it over, we hand the code and documentation to your team.
Yes, as far as that software allows: API, file imports or exports. Rivena Fleet has a documented API. For Rivena ERP, Rivena HR, Rivena Equipment or other software, we check what is possible during scoping, and the connection is part of the project. Where no direct link is possible, an Excel or CSV export is still a sound starting point.
It depends on the number of screens and roles, the connections to your tools and the options chosen: offline entry, notifications, app store publication. After scoping, we provide a quote for a first version with a written scope. Maintenance and improvements are then covered by a fixed fee or quoted on request, agreed before any commitment. We advise starting with a single process: the budget stays under control and the app proves itself before it is extended.
That is common, which is why your teams test the mock-ups before development starts. Few fields, choices rather than typing, large buttons, and hands-on onboarding in the field at roll-out. The interface can be in French, Arabic or both, depending on your teams.
Tell us about your business, how your organisation runs and what you want to improve. We’ll then suggest a concrete next step — a demo, a call or a scoping session — with no obligation.
Or e-mail us at contact@rivena.ma
Based in Rabat · Demo on request