Security & mission management
Run safer missions in hostile environments.
Coccu brings security assessments, mission approvals, fleet management and field check-ins into one tool, so you can see whether your own standards are being met while there is still time to act — and show afterwards that they were.
Base camp → North site · 3 travellers · 1 vehicle
- Left base camp07:58
- Arrived at the junction09:12
- On the road to the north sitenow
- Arrive north sitedue 11:30
You are answerable for people you send into danger.
Teams working in high-risk places keep risk assessments, mission approvals, vehicle records and check-ins across spreadsheets, chat groups, paper forms — or nowhere at all. That leaves two gaps.
While the work is running you cannot tell whether your own standards are being met: whether the assessment behind today's movement is current, whether that vehicle is still certified, whether the team that left at seven has been heard from. And afterwards, when a headquarters, a donor, an insurer or an inquiry asks what you knew, what you decided and who agreed, the answer has to be evidence rather than recollection.
Coccu does both jobs at once. It holds you to your own rules while you work, and the record is a by-product of that work rather than a separate task. Here is the chain, in the order you use it.
Security risk assessment
An assessment, not a checklist.
Coccu does not impose a methodology. Choose the one your organization already works to — a ready-made scale, the classic likelihood × vulnerability × impact register, your own risk factors and weights, or your own formula. Every area you operate in is scored that way.
- Each risk is scored, its mitigation recorded, then scored again. You plan against the residual risk, not the inherent one.
- Zones inside an area are scored separately. A mission crossing several of them inherits the worst score for each risk, not an average of them.
- Your own security rules key off the score: minimum vehicles, minimum guards, and whether night movement is permitted.
- Every assessment is dated and retained with its workings, and exports to PDF or Excel.
- As you go
- An assessment is flagged when it becomes due for review, and the rules keyed to its score apply to every mission planned from that day.
- On the record
- The assessment each decision rested on, dated, with the workings behind the score — kept when a newer one supersedes it.
- SimplifiedGrade a fixed set of risk factors
- ClassicLikelihood × Vulnerability × ImpactIn use
- Your dimensionsYour own factors and weights
- Your formulaYour own factors and calculation
- Armed conflict / crossfireVery HighLikelihood4×Vulnerability4×Impact5= 80What we do about it
Two vehicles, no movement after dark beyond the junction, and a check with the community focal point on the morning of travel.
AfterLikelihood3×Vulnerability2×Impact4= 24Medium - Road traffic accidentHighLikelihood4×Vulnerability3×Impact3= 36
- Landmine / IED / UXO strikeHighLikelihood2×Vulnerability3×Impact5= 30
At this level your own rules require 2 guards and 2 vehicles on a night leg. A mission crossing this area starts from this assessment.
Mission planning & approval
Every movement is requested, cleared, and on the record.
Each request goes to security, fleet and operations in the order your organization sets. Every approver sees the risk assessment for the ground the mission crosses before answering.
- A request can be sent back with a reason, and a refusal can be appealed.
- If a role is unfilled, the request advances automatically rather than stalling there.
- The record shows who cleared what, at what time, and on what information.
- As you go
- A movement that has not been cleared has not been authorised, and the request shows which step it is waiting on.
- On the record
- Every clearance, the person who gave it, and the job title they held on the day.
Base camp → North site · 3 travellers · 1 vehicle
- Security clearanceLena Novak — Head of Security1 Sep, 08:12
- Fleet clearanceAnika Hale — Fleet Manager1 Sep, 09:40
- Operations approvalSara Korvin — Country Director1 Sep, 10:05
Fleet & drivers
You always know where the vehicles are.
Each vehicle's location is derived from its own missions: live position while it is moving, the leg it is travelling when there is no signal, and its last confirmed stop after that.
- Roadworthiness inspections are recorded item by item and graded, with the full history held against the vehicle.
- Driver licences, insurance and registrations are checked against their expiry dates and warn weeks in advance.
- A week and month calendar shows which vehicles and drivers are already committed, so the same one cannot be assigned twice.
- Odometer readings from inspections, check-ins and debriefs collect on one page, and a reading lower than the one before it is flagged.
- As you go
- Expiring licences, insurance and inspections are raised weeks before the date, with time left to renew them.
- On the record
- That the vehicle had passed inspection and the driver was licensed on the day the mission ran, with the certificate dates recorded.
- LC-04Land CruiserLive ·North road, 12 km short of the siteAChecked 12 Aug
- LC-07Hilux double cabEn route ·Base camp → South siteBChecked 3 Sep
- MB-02Minibus, 14 seatsLast known ·Base campCChecked 2 Jun
- MB-02 — next inspection due in 9 days.
- Dana Orwell — driving licence expires 24 Sep.
Raised weeks before the date, while there is still time to renew.
Tracking & field reporting
Two ways to watch the same journey.
A mission is a route made of legs. The team travelling it works down a timeline, one leg at a time. The operations room follows the same journey on a map, with the vehicle's live position on it while the team is moving.
Base camp → North site · 3 travellers · 1 vehicle
- Left base camp07:58
Logged by Diego Moreno
- Arrived at the junction09:12
Logged by Diego Moreno
- On the road to the north sitedue 11:30
Running late — operations notified
Arrived at the north site - Return leg to base campdue 15:00
One leg is open at a time, so there is nothing to select. An entry recorded at the wrong time can be corrected while the mission is still running.
On the timeline
- One leg is open at a time, and it accepts one entry: departure or arrival. Nothing else has to be chosen.
- Every entry records the time it happened and who logged it. It can be corrected while the mission is running, and the previous value is kept.
- An entry made without signal keeps the time it was made, not the time it reached the server.
- If the route changes mid-journey, the altered leg is marked and every leg after it is rescheduled.
On the map
- Check-ins, stops and incidents are pinned at the coordinates where they happened.
- Live position is sent only while a leg is being travelled, and can be switched off for any mission.
- An overdue arrival alerts the operations room automatically.
- Your own locations — bases, checkpoints, safe havens, hospitals — sit on the same map, with pins you define.
- As you go
- An arrival that has not been logged is raised with the operations room automatically, and the position on the map is the one the device is sending rather than a manual entry.
- On the record
- Where the team was and what was reported, including anything corrected and the value it was corrected from.
All of it works with no signal.
The screens your team uses on the road do not need a connection to work, only to send what has been recorded.
- No signal
Arrived at the north site
Saved on the phone. Nothing is lost and nothing is waiting on a bar of reception.
- Back in range
Sending on its own
No one has to remember to do anything.
- Done
Recorded 14:02
The operations room sees it at the time it happened, not the time it arrived.
Compliance & accountability
See it in time. Show it afterwards.
None of the four steps above exists to produce paperwork. Each one checks something while it can still be acted on, and each one leaves what it checked behind. Put together, they answer the question you are asked when something goes wrong: was this movement planned on current information, cleared by the right people, run in a vehicle fit for it, and monitored while it was out.
- The mission authorization record prints every clearance, who gave it, and the job title they held at that moment. Promotions and handovers afterwards do not rewrite it.
- A clearance step that applied but had nobody in post is printed as exactly that. Nothing is hidden to make the chain look complete.
- Assessments keep the arithmetic behind each score, so a decision taken months ago can be reviewed against the information it was taken on.
- Assessments, incidents, inspections and the whole area record export to PDF and Excel, with credentials excluded from the export.
Mission authorization record
AV-26-0014 · Monthly supply run
Northern Operations · Base camp → North site
- Security clearanceCleared by Lena Novak — Head of Security1 Sep, 08:12
- Fleet clearanceCleared by Anika Hale — Fleet Manager1 Sep, 09:40
- Operations clearanceCleared by Sara Korvin — Country Director1 Sep, 10:05
- Area risk at departure
- Very High — assessed 1 Sep
- Vehicle
- LC-04 — inspection passed 12 Aug, grade A
- Driver
- D. Moreno — licence valid to 24 Mar 2027
Job titles are those held at the time of each decision. A clearance step that applied but had nobody in post is printed as such and is not omitted.
What Coccu does
Security risk assessment
Four scoring methods, so you keep the one you already use, with the mitigation recorded and the residual risk scored.
Fleet & drivers
Where every vehicle is right now, the grade from its last inspection, and a warning weeks before any paperwork expires.
Mission planning & approval
Security, fleet and operations clear each movement in the order you set, and the record of who approved it is retained.
Tracking on the map, working offline
The journey drawn leg by leg, live position while the team is moving, and everything usable from a phone with no signal.
Fits what you already run
Already using satellite tracking, your own vehicle system or your own risk process? Turn off the parts of Coccu that would duplicate them, area by area, and keep the rest. Nothing is all or nothing.
Two kinds of teams, the same hard problem.
Anyone sending people into high-risk places carries the same weight: keeping them safe, and being able to show you did everything right. Coccu works the same way for both.
For humanitarian organizations
You carry a duty of care to staff and volunteers who rotate through unfamiliar, high-risk areas. Coccu keeps your risk assessments, mission approvals, and incident records in one clear place — so field teams and country offices work from the same picture, and you can account for every decision to your headquarters, your donors, and your insurers, even when the connection drops.
For companies
Sending people into hostile environments — for construction, logistics, energy, media, or security work — carries real legal and reputational risk. Coccu gives you a clear record that vehicles were roadworthy, drivers were fit, journeys were approved, and incidents were logged — for compliance, insurance, and your own peace of mind — without burying your people in paperwork.
Built by people who've done the job.
Coccu is made by security practitioners who have run missions in hostile environments. It is built for daily use in the field rather than for reporting: simple enough to be used under pressure, and clear enough that everyone can see where a mission stands.
Where your information is, and who can see it.
This platform holds the names, phone numbers and movements of people working in dangerous places. These are the rules it runs under.
- Hosted in the European Economic Area. Servers and the database run in the Netherlands. Uploaded files are stored in the EU.
- The most sensitive fields are encrypted in the database. Phone numbers, incident descriptions and every note written against a risk are stored sealed, under a key kept apart from the sign-in secret.
- Missions are need-to-know. A person sees the missions they are on or responsible for. Incident reports are readable only by managers and the Director. Each area is walled off from every other.
- Two-step sign-in for anyone who sees beyond their own missions. Managers and Directors must use it; everyone else can. Any device can be signed out from any other.
- Maps and positions stay inside. Map imagery is fetched by our server, so no third party learns where your people are. A position is sent only while a leg is being travelled, can be stopped mid-journey without anyone being told, and deletes itself after 30 days.
- A record of who looked. Every opening of a mission, a profile, an incident or a location trail is written down, with who and when, and kept for a year.
What it costs
Coccu is free while it is early — all of it. We are asking people who run movements what it should become.
Later we will charge by how many areas of operations you run. We are early enough that the figure is a conversation rather than a price list.
For small non-profits and individuals working in one place, it stays free. A two-person team, a national organization with one programme, a freelance correspondent — tell us who you are when you register.
No feature is ever behind the price. Every module is in every plan, and going over your plan never blocks anyone.
Start with one area, free.
Set up your first area of operations and run a mission through it. Nothing to pay, and nothing to cancel.
Already set up? Sign in