SONDIS · Digital MRV
Every participant, site and reading, on the record.
Digital MRV that takes the shape of the project — an interface built to its brief, or a template and methodology you pick — with consent, sites and readings collected as the methodology asks, and evidence that cannot change.
- 2
- people on every approved record
- 3
- ways consent is confirmed and dated
- 2
- ways to start: built to your brief, or from a template
- 5
- roles, from field coordinator to platform admin
Why it exists
No two carbon projects measure the same thing — smallholders and trees, meters across a fleet of installations, a flow through a plant. Most MRV tools are written around one of them, so everyone else bends the project to fit the software, or falls back to forms and photographs in a folder. Then the verifier arrives, and weeks go on proving who did what.
What SONDIS does
SONDIS takes the project's shape, not the other way round. Hand it a project brief, or pick a template and a named methodology, and you are collecting the same week. Underneath, nothing moves: every record is attributed to a person, nobody approves their own work, and what is collected, how often and with what checks follows the methodology in CARTIS and the project’s plan in RHIZORA.
At work
See SONDIS do the job
Field
Consent comes before the first measurement
People are enrolled as participants, not users. SONDIS records who they are, what land or asset they hold and how they agreed to take part, then waits for a supervisor and an admin to approve the enrolment before any site is worked.
- Consent by OTP, witnessed or self-confirmed, with the date
- Supervisor then admin approval
- No raw identity numbers stored
Participant · sample
Grower enrolment
Collection
Nothing missing, nothing changed
What to collect, how often and with what checks comes from the methodology in CARTIS and the project’s own plan. Every due period shows as checked, waiting for a check or missing, and every file is fingerprinted and locked once its reading is checked.
- Rules from CARTIS, shown as current or newer
- Checked, waiting or missing, period by period
- Files that cannot be edited or removed
Monitoring plan · sample
Collected as the methodology asks
Rules from CARTIS · current
■ checked by a second person□ waiting for a check▫ missing
Review
The person who collects never approves
Every submission moves from draft to QC to approval, and each step is stamped with the person and the time. A record returned with a note goes back to the field team, and nothing unchecked is ever sent on.
- Draft → needs QC → QC passed → approved
- Return with a note at either gate
- An activity log for the whole organisation
Submission · sample
Plot K-014 · monitoring visit
Draft
Coordinator
Needs QC
Coordinator
QC passed
QC lead
Approved
Manager
Rule
The person who submits cannot approve. Each step records who and when.
How it works
From brief to monitoring round
Land-based projects: growers, plots and what is standing on them.
Capabilities
Everything in the box
Who it serves:
Project developers
Run enrolment, sites and monitoring rounds across many participants.
Field coordinators
Capture participants, boundaries and measurements, and run first-line QC.
Programme managers
Verify and approve, see at a glance what is still missing, and send the approved data on.
Verifiers
Receive evidence that is attributed, checked and traceable.
Built to the brief
Give SONDIS the project brief and it runs on an interface made for that project — its own entities, fields and steps, rather than a generic form to work around.
Or start from a template
Pick a project template and a named methodology from the catalogue instead, and begin collecting without a build.
Not written around one sector
Nature-based programmes, and projects that are nothing like them, run on the same platform under the same evidence rules.
Participant enrolment with consent
Participants are registered with identity, tenure or asset, and how consent was confirmed (OTP, witnessed or self-confirmed) and when, then approved by a supervisor and an admin.
Sites you can find
Every site carries a code unique to its project, a mapped boundary, and a computed area and perimeter.
Measurement at source
Whatever the project counts is recorded where it happens, on each monitoring visit — for a planting programme that is species, diameter, height and health, per tree.
Maker and checker
Two-step QC and approval by two different people, with the person and time stamped on every step.
Collected as the methodology asks
Parameters, frequency, method and QA/QC come from CARTIS for the methodology, and the monitoring plan from RHIZORA for the project. Every due period shows as checked, waiting or missing, so gaps surface before a verifier finds them.
Evidence that cannot change
Photos, weighbridge slips, lab reports and logger files upload from the field and resume after a dropped connection. Each is fingerprinted with who, when and where, and nothing can be added once the reading is checked.
Handed on, not recalculated
Approved data and the fingerprints of its evidence go to RHIZORA as one sealed package; CARTIS does the calculation. SONDIS keeps no second copy of the rules and no figure of its own.
Methodology catalogue
Projects bound to a named methodology, with CDM and Paris Agreement (PACM) entries side by side for the transition.
Roles and access
Permissions decide what each person sees, from field coordinator to approver to administrator.
White-label
Each organisation carries its own branding on the same platform.
Principles
How it keeps its integrity
- The database is the gate: access is decided by the data layer, not the screen.
- Methodology first: every project starts from a named methodology.
- The project sets the interface, not the interface the project.
- Participants are not users: consent and approval are recorded about them, not by them.
- Two pairs of eyes: the person who collects is not the person who approves.
- Collect to the rulebook: what, how often and with what checks come from CARTIS and the project’s plan. SONDIS calculates nothing.
Clear scope
What it isn’t
- Not a verification body
- Verification stays independent. SONDIS prepares the evidence; an accredited body gives the opinion.
- Not a registry
- Issuance, transfer and retirement belong to AMMONIS.
- Not a ratings agency
- It measures a programme's own sites; it does not score other people's credits.
- Not a calculator
- Carbon is calculated in CARTIS, on approved data sent through RHIZORA. SONDIS collects and checks.
- Not the project designer
- The PDD and its evidence library live in RHIZORA. SONDIS feeds them.
Built on
What SONDIS stands on
The platform underneath, and what the work depends on outside it.
The platform
-
Intelligence from CARTIS
What to monitor, to which methodology and with which factors is read from Climate Intelligence, never held as a second copy here.
-
One platform core
The same evidence architecture the rest of the suite runs on: identity, roles, attribution and the audit trail are not rebuilt per product.
-
Access decided in the data layer
Row-level rules in the database, not checks in the screen, so a different interface cannot see more than it should.
-
An interface per project
The project brief becomes the entities, fields and steps that project actually has, on top of that shared core.
Where the data comes from
- Google Maps
- OpenStreetMap
- GPS · NavIC
- WGS 84
- Camera and photo evidence
- Offline field capture
- Excel and CSV import
- IoT and sensor feeds
- Custom data feeds and APIs
- Biometric authentication
- Aadhaar verification
Questions
Asked often
Does SONDIS only do nature-based projects?+
No. It is not written around one project type. A planting programme and a project that looks nothing like it run on the same platform, because the interface is built to the project rather than the project fitted to a form.
How does a project start?+
Two ways. Give us the project brief and the interface is built to it — the project’s own entities, fields and steps. Or pick a project template and a named methodology from the catalogue, which already holds CDM and Paris Agreement (PACM) entries side by side, and start collecting straight away.
Does SONDIS calculate the credits?+
No. SONDIS collects and checks. Approved data goes to RHIZORA, and CARTIS calculates with the methodology’s own formula, so there is one set of rules and one calculation across the suite.
Does SONDIS replace the verifier?+
No. Verification stays independent. SONDIS prepares evidence that is attributed, checked and traceable, so the verifier spends less time proving who did what.
Can we use our own branding?+
Yes. Each organisation carries its own name and branding on the same platform.
Works with
Part of MARIS
Each product reads the climate from its own angle. With Climate Intelligence at the centre, together they cover it end to end.
Receives the monitoring plan from RHIZORA, and sends approved data and evidence back for the PDD.
Explore →Verified monitoring results are bound for AMMONIS, where credits are issued.
Explore →Methodology rules and monitoring parameters come from Climate Intelligence.
Explore →Inventory in, buyers scored and matched, reviewed proposals out, deals settled as retirements in the registry.
Explore →ESG compliance for Indian listed companies: one BRSR record per year, reviewed and reusable.
Explore →Investor onboarding and capital calls for Indian AIFs, with the fund register as the system of record.
Explore →