Compensation Officer guide
Compensation Officers run the process from start to finish: they set up projects and their boundaries, register properties and claimants, make sure every record is complete, decide conflicts and spatial flags, send surveyors to the field, open compensation cases and keep claimants informed.
Default role: Compensation Officer Also useful for: Administrator
The process at a glance
- 1. ProjectCreate it, set its boundary
- 2. PropertyCaptured in the field, registered or imported
- 3. ClaimantLink, check ID and bank
- 4. CompleteFill the gaps, decide conflicts and flags
- 5. CaseOpen one or more, then each role records its step
A property’s stage is worked out from what has been done, so it is always up to date:
| Stage | Means | What you do next |
|---|---|---|
| Registered | No claimant linked yet | Link the claimant |
| Claimant linked | No survey yet | Complete the data; assign a survey if a visit is needed |
| Survey in progress | Assigned, submitted or returned | Review when submitted |
| Surveyed | Survey approved, no case yet | Open a case once the data is complete |
| Compensation in progress | A case is open | Each role records its step |
| Compensated | The case reached its last step | Nothing |
A survey is no longer needed before a case: a property with complete data can go straight to a case. The property’s next-step box always says what it needs.
The dashboard
Start each day here. The amber note lists conflicts to decide, blocking spatial flags, surveys waiting for your review and disputed cases. The Data completeness panel shows, for each project, how many properties are complete and the average, then the most common gaps for properties and for claimants. Every number opens the matching register.
Projects
Needs projects.manage
- Open Projects and click New project.
- Enter a unique project code (it is used in imports, filters and case numbers, e.g.
KSR-2026-01), the name, main LGA, status and start date. Create it as Planning. - Click Create project. Its file opens.
- Set the project boundary on the Map tab, then change the status to Active.
The project’s Overview shows how many properties are at each stage, its data completeness (complete properties, the average, and what is missing most often, each with a link to the matching properties), and any open conflicts. Export incomplete downloads the incomplete properties to Excel.
The census cut-off date
Set the project’s Cut-off date (census) in Edit project when the census closes. From then on, a property captured after that day, or a claimant registered after it, is listed on Conflicts as Added after the cut-off date — and, like every open conflict, holds compensation back. Decide each one with a note: Eligible after all (for example, missed by the census, or captured on time but sent in late) or Not eligible (no case can be opened for it). Setting or moving the date looks through everything the project already holds; buildings drafted from the map scan do not count as new. The date and each decision are minuted.
Project boundary and map scan
A project has a perimeter: the land it takes. A project can only become Active once it has a boundary.
- Open the project, then the Map tab, and click Set boundary (Edit once there is one).
- Choose how to give it:
- Draw on the map: click to add corners in order. Drag a corner to move it; drag or click the small dot between two corners to add one; click a corner, then Remove corner.
- Type coordinates: choose Latitude, longitude (WGS84) or UTM zone 32N, and type one corner per line. Show on map checks them.
- Upload a file: GeoJSON, KML, or a zipped shapefile (the .shp, .shx, .dbf and .prj together).
- Check the area and the note under the map (it says if the outline is not valid), then click Save boundary.
Saving the boundary queues a map scan. In the background, the system reads the open map data (OpenStreetMap) inside the boundary and keeps what it finds as shapes: roads, rivers and streams, water, farmland, orchards and woodland, buildings and power lines, cut to the boundary (with a 100 m margin so edge roads still show). When it finishes, the Map tab shows:
- Buildings (how many, and their roof area — “20,000+” when there are more than the scan keeps), mapped trees, and the area of farmland, orchards, woodland and water. Overlapping areas are counted once, and land mapped with holes (a clearing in a wood) leaves the holes out;
- the length of roads inside the boundary by class (for example “1.2 km primary · 4.8 km residential”) with their names, of waterways, and of power lines;
- Worth noting: schools, places of worship, markets, clinics and similar places inside the boundary.
On the map, the layer list (top right) has a layer for each kind of shape: Roads and Rivers and streams are on from the start; switch on farmland, water, power lines or the scanned buildings when you need them. Each loads when you switch it on. With thousands of buildings, zoom in to see them. Hover a shape for its name, class and length or area.
Open map data can be incomplete or out of date. Use the scan to plan the fieldwork, and confirm everything on site.
- Run again repeats the scan, for example after the map data has been updated. The new run replaces the shapes of the last one.
- A project larger than the scan limit (150 km² by default) is not scanned: the job fails once, with the reason, and is not retried.
- The scan is project analytics only: the number of buildings, the roads, rivers, farmland and so on. It never creates properties; those are captured by surveyors in the field or entered in the office.
- Properties on the map can be coloured by Stage, Data completeness or Compensation. Click one to open it.
- Check again under Spatial checks re-runs the overlap and boundary checks for the project and all its properties. Open flags show as a red layer on the map.
- Map data: GeoJSON or KML (Google Earth) downloads the boundary and properties (needs data.export).
A scan that has not finished says queued or running; a failed one shows the reason. Administrators can see and retry scans on Background jobs.
The system map
Map, at the top of the menu, shows every project boundary, coloured by status, with a bubble counting its properties. Click a bubble to zoom in; once you are close enough, the properties of the area in view load on their own, and more load as you move. Click a project for its details, or Show properties for all of them. Choose what the properties are coloured by at the top right.
Sub-boundaries
Needs subboundaries.manage to draw and change; anyone who can see projects can see them
A project can be divided into sub-boundaries: named, coloured areas such as “Kakau North” or “Market square”. They organise the work: which properties fall where, how far each area has got, and which field team captures it.
- Open the project and its Sub-boundaries tab.
- Click New sub-boundary, give it a name (the code, such as
KEB-S04, is made for you) and click Create. - Draw, type or upload its outline. The project boundary and the other sub-boundaries are shown underneath. Click Save boundary.
- Which properties are in it is worked out in the background: a parcel belongs to the area that holds most of it; a property with only a GPS point belongs to the area its point is in. A parcel cut by the edge of its area gets a Cut by a sub-boundary edge flag (a warning) so you can check it.
- Crossings. Sub-boundaries should not overlap. Where two do, a Sub-boundaries cross flag shows the overlap in red on the map. If they are meant to overlap, tick May cross other sub-boundaries on both (Edit details) and the flag settles.
- Colour: leave it Automatic and neighbours never share a colour, or choose one. Colour automatically recolours the automatic ones.
- A sub-boundary mostly outside its project is flagged too.
- Status: draft, active or archived. Only active sub-boundaries count properties; archiving one takes its properties out of it (their history stays).
- The tab’s ledger shows each area’s size, properties (and how many buildings the map scan saw there), average data completeness, open flags and status. Click a row, or an area on the map, to open its file: overview, properties, minutes.
- Registers (properties, claimants, cases, surveys, Fill the gaps) have a Sub-boundary filter once a project is chosen. A property’s area shows beside its location. Ctrl K finds a sub-boundary by code or name.
- Files: Export gives the outlines as GeoJSON or KML (with code, name, colour and figures), or Excel. Import outlines reads a GeoJSON, KML or zipped shapefile: an outline whose
codematches is replaced;name,colour,allow_overlapandtagsare read when present.
All sub-boundaries of every project are also listed under Registers › Sub-boundaries.
Divide a project automatically
Instead of drawing every area, let the system propose them. It needs the project’s map scan (for the roads, rivers and buildings).
- On the project’s Sub-boundaries tab, click Generate automatically…
- Set the target size of an area (the form suggests one for about ten areas and says how many your size gives).
- Choose what to divide: the whole project (accepting then replaces its current sub-boundaries, which are archived) or only the free space outside the active ones.
- Choose how to balance the areas: by size, or by the number of buildings (equal workload for field teams).
- Keep Follow roads (main roads, residential and unclassified — not paths or tracks), Follow rivers, streams and water and Keep property parcels whole on, unless you have a reason not to. Click Generate drafts.
After a few seconds the drafts appear: dashed on the map, and listed above it with their figures — the size range and average, how much of the dividing lines follow a road or water, how many parcels were kept whole, and about how many buildings each area has.
- Accept all, or tick some and Accept selected: they become active sub-boundaries with codes such as
KEB-S07and names from the road or place they lie on. Areas that touch get different colours. - Discard drafts throws away the ones still waiting. Change settings and generate again replaces them with a new proposal.
- A good way to work: accept the areas you like, then generate again for the free space only to redo the rest.
- One area too big? In the Map Studio, select it and click Split into parts…: choose how many parts (2 to 30) and how to balance them. The draft parts follow the roads inside the area; accepting them replaces that area only (it is archived).
- The same settings always give the same areas. Areas never overlap each other, and a parcel kept whole lies in one area even if a road crosses it.
- Generating, accepting and discarding are minuted on the project, with the settings used.
Names from the map (AI)
When AI is switched on, the drafts of an automatic division have Suggest names for the drafts. The system finds the named roads, rivers, places and landmarks in or near each area — whether a road runs through it or along its edge, the side of a market or river the area lies on, how far — and the AI words a short name from them, such as Kawo Market North or Between Kachia Road and the River.
- Each suggestion shows the area’s name now, the suggestion (change it if you like) and why. Untick the ones you do not want, then Use the ticked names.
- Names are unique in the project: a suggestion that is taken gets a number added, and a name already used by another area is refused. The automatic division itself avoids the names already used, too.
- In the Map Studio, select one area (Suggest a name) or several (Suggest names) to rename areas that already exist. Each rename is minuted on the area.
- Only the names of map features are sent — nothing about claimants or properties.
Describe this area (AI)
On a project’s Overview tab, and in the Map Studio’s inspector (the project when nothing is selected, or one area), Describe this area gives four to six plain lines: how many buildings and of what kind, the roads and rivers by name, landmarks, farmland and where it lies, and how far the register has got (properties recorded and the share of the buildings that is, complete, cases, paid, open flags). The figures are worked out by the system from the map scan and the register; the AI only words them, and any number in its lines that is not one of the figures is highlighted. Copy puts the lines on the clipboard for a report.
Field teams: who captures where
Needs surveys.assign to assign; surveys.view to see
Field agents work in areas: an area’s field team is one lead and any number of members. An agent’s phone downloads only their areas (and properties within 200 m of them), so it stays small and they see their own work.
- Assign from the area’s file (Field team tab › Assign an agent), from a list of areas (tick several, then Assign field agent…), from the agent’s staff file (Field areas tab › Assign areas…), or in the Map Studio (select areas › Assign…). Dates are optional.
- The agent dropdown shows each agent’s load — open surveys, areas, captures this week — and puts the agents already working in that area first.
- Naming a new lead makes the old lead a member. End takes the area off the agent’s phone at its next sync; anything they captured but had not sent yet is still accepted.
- The project’s Sub-boundaries tab shows each area’s Field team, and under the map a Field teams table: each agent’s areas, captures (all, this week, a bar for each of the last 14 days) and last sync. Export assignments downloads the list.
- A property captured outside the agent’s areas is kept and flagged Captured outside the agent’s areas (a warning, naming the nearest of their areas and the distance). Accept it on Spatial flags once it is settled who looks after it (for example after assigning that area to the agent too).
- Supervisors whose role has
field.all_projectssee every active project in the field app, as before areas were assigned. - Assigning, changing and ending are minuted on the area and on the agent.
The Map Studio
Anyone who can see projects can open it; drawing and publishing need subboundaries.manage
The Map Studio is a full-screen map of one project for working on its sub-boundaries: draw, reshape, split and merge them with every layer the system knows underneath. Open it with Open in Map Studio on the project (or its Sub-boundaries tab), Map Studio on a sub-boundary, or Map Studio in a project’s bubble on the system map. Back to the project at the top left returns.
Nothing is saved while you work. Every change goes into a draft set, shown as “3 unsaved changes” at the top and dotted on the map. Publish saves the whole set at once (one bad shape stops all of it, with the change named); Discard changes drops it. Leaving with unsaved changes asks first (Back to the project takes a second click; closing the tab asks through the browser).
| Tool | Key | How |
|---|---|---|
| Select | V | Click an area to see and change its name, colour, status and “May cross other areas”, its tags, field team, recent minutes, Split into parts… and Assign…. Shift-click adds more areas to the selection. |
| Draw area | D | Click the corners; click the first one again to finish. Corners snap to the project edge, other areas, parcels and roads within a few metres. |
| Rectangle | Click one corner, then the opposite one. | |
| Edit corners | E | Select one area first. Drag a corner (it snaps); click a small mid-point to add a corner; right-click a corner to remove it. |
| Move | Drag the selected area. | |
| Split | S | Select one area, then draw a line right across it (click the last point again to finish). Each part becomes an area; the largest keeps the code. |
| Merge | M | Shift-click two or more areas, then Merge. The largest keeps its code; the others are archived. |
| Cut a hole | H | Select one area, then draw the shape to take out of it (a school compound, say). |
| Measure | R | Click points; double-click to finish. The length shows at the top (and the area, if you end where you started). |
| Generate… | G | The automatic division (above). While it works, and when its drafts are ready (dashed on the map), a panel above the side tabs shows them with Accept all, Accept selected and Discard drafts. |
| Undo / Redo | Ctrl Z / Ctrl Y | Step back and forward through your changes (up to 100). |
| Archive | Delete | Archive the selected areas (an unpublished one is simply removed). |
Esc cancels a drawing and clears the selection; [ and ] step through the areas by code; the box at the top finds an area by code or name.
- Layers (right panel): the base map (map, satellite when the server has one, or plain for printing); the project boundary; sub-boundaries coloured by their own colour, status, progress (properties captured against the buildings the scan saw), data completeness, first tag or field team (each lead a colour, grey with no one), with a fill slider; Areas with no field agent outlined in red; Crossings — red where two areas overlap, amber where both are allowed to; Available space — the part of the project no active area covers — in green; spatial flags; properties coloured like the system map or by the sub-boundary they belong to; and the map scan’s roads, waterways, buildings and places.
- Filters (under Layers): areas by status or tag; flags by type; properties by stage, tag, source (office, field, import, map scan), the date they were captured, or a minimum completeness. The legend counts follow the filters.
- Legend counts what is drawn, both in view and in the project: areas and hectares by status, crossings, available space, properties by stage, road kilometres by class.
- Health sums the project up: how much of it the areas cover, crossings (and allowed ones), parcels cut by an edge, areas outside the project, and areas much smaller or larger than the target size. Click a line to select the areas it concerns.
- Export (top bar) downloads all the project’s areas, the selected ones, or the ones in view, as Excel, CSV, GeoJSON or KML.
- A click on a property opens its file in a new tab (with the Select tool only, so drawing over parcels never opens them). Projects with thousands of parcels stay smooth: they are drawn on one canvas.
- The bar at the bottom shows the pointer’s position in latitude/longitude and in UTM zone 32N metres, the zoom and scale, the selection’s size and the unsaved count.
- Print prints the map with its legend, the project name, the date and a north arrow.
- Each publish is minuted on the project (“Map Studio: 2 new, 1 changed”), and each area’s own minutes say what changed. Membership and the spatial checks are worked out again in the background, and the Health panel refreshes a few seconds later.
Properties
Needs properties.manage
Properties reach the register in four ways: captured in the field, registered here, imported from a spreadsheet, or drafted from the map scan. The Captured filter and the property’s Source say which.
- Open Properties and click Register property (or Add property in a project file).
- Enter a reference number that is unique across all projects, the project, the type and the location. Choose the LGA first; the ward and area lists then show only places inside it.
- Land area and GPS are optional: the boundary gives the land area once it is set.
- Click Register property.
Only administrators can add places. Ask one to add it on the Locations page.
Many properties at once? Use Import; see Import and export.
The property file
- Overview: the next-step box, the data completeness checklist, the map, the property details, the claimant, its compensation cases, and any spatial checks.
- Items: what is on the land (see below).
- Surveys, Evidence (photos and documents) and Minutes.
The property boundary
On the Overview, click Edit boundary (or Set boundary in the checklist). Draw, type or upload the outline as for a project; the project boundary and neighbouring properties are shown for reference. Saving the boundary runs the spatial checks for that property.
Items: what is on the land
The Items tab lists the trees, crops, buildings and other things on the property. Valuations are built from it.
- Click Add item.
- From the dictionaries: search (for example mango, zinc roof, maize), pick the exact item and enter the quantity. Items carry no money: the valuer values each one on the compensation case.
- Custom item: for anything the dictionaries do not list, say what it is, give details, the quantity and the unit. Custom items are marked custom for review.
- Click Add item.
- The pencil changes the quantity or notes; the bin removes the item. An item in a compensation case is locked (In a case).
- Nothing on the land? Click Confirm: nothing on this land. That satisfies the “items listed” check.
Field photos: checks and suggested items
- Each photo a field agent sends is checked on the server. A blurred, too dark or re-used photo (the same as another property’s) shows Retake: … on the property’s Evidence tab, the property gets the gap Photos usable (none to retake) in Fill the gaps, and the agent’s phone says “Retake: front view blurred” at its next sync. With AI on, a front view that does not show the property is flagged too.
- With AI on, a few minutes after a sync the property’s Items tab shows Seen in the field photos: trees, crops and building parts suggested from the photos, from the dictionaries only, with the count the agent recorded beside each. Check the count, then Add (the item is marked AI (checked) and minuted) or Dismiss. Look at the photos again asks again.
Claimants
Link or register the claimant
Open the property. Its next-step box says Link the claimant.
- Click Link claimant and start typing a name, phone number or email — or an 11-digit NIN.
- If they are already registered (one claimant can hold several properties), click Link.
- Otherwise click Register a new claimant. The new claimant is linked straight away.
The claimant form takes personal details, NIN, ID and bank details. Enter names exactly as on the ID and bank account, because the checks compare them.
- NIN: exactly 11 digits. Only one claimant can have a given NIN; the field app finds claimants by it.
- Account number: exactly 10 digits (NUBAN). BVN: exactly 11 digits.
- Phone: a Nigerian mobile number (e.g.
0803…or+234803…). Claimants without one are skipped by SMS. - NIN, account number, BVN and ID number are masked like
••••6789. When editing they are never shown in the form: leave them blank to keep what is stored. - Add the ID document on the claimant’s Evidence tab and a photo on the Overview tab.
Identity and bank checks
Needs claimants.verify
On the claimant’s Overview tab, run the three checks before any money is approved. A verified bank account is part of complete claimant data, so a case cannot open without it.
| Check | Needs | Compares |
|---|---|---|
| Bank account | Bank and account number | The account holder’s name with the claimant’s name |
| BVN | BVN, bank and account number | Whether the BVN belongs to that account |
| NIN | The claimant’s NIN | The name on the NIN record with the claimant’s name |
- Verified — names match (60% or more of the name parts).
- Name mismatch — do not proceed to payment until it is explained; correct the details and Check again.
- Check failed — the check could not run; the reason is shown. See Troubleshooting › Claimant checks.
- Account changed since — the account number was edited after the last bank check. Run it again.
- “test mode” under a result means the built-in test rules were used, not the real provider.
Data completeness
Every property and claimant shows a % complete and a checklist of what is in place and what is missing, with a button to fix each gap. A compensation case can only open when both the property and its claimant are at 100%.
| Property checklist | Claimant checklist |
|---|---|
| Project Property type GPS position or boundary At least one photo Boundary outline LGA Ward Items listed (or confirmed none) Front view photo Claimant linked Claimant link approved |
Full name Phone or NIN Photo NIN Phone number Bank, account name and account number BVN Bank account verified |
- The property and claimant registers have a Data % column and filters: Data (complete / incomplete), Missing (one item of the checklist), Captured (Office, Field, Import, Map scan draft) and, for properties, Boundary (mapped / missing).
- A field officer can save a record with only the essentials (see the Field Surveyor guide), so field records often arrive incomplete.
Fill the gaps
Needs properties.manage or claimants.manage
Records › Fill the gaps lists every incomplete property (or, on the Claimants tab, claimant), with what each is missing. Filter by project, by what is missing, or by how it was captured.
- Click Fill in… on a row. The form asks only for what is missing: for a property the LGA and ward or a front view photo; for a claimant the NIN, phone, bank details, BVN or photo.
- Use the buttons for the rest: Set the boundary…, Add an item…, Nothing on this land, or a link to the property to link the claimant. For a claimant, leave Run the bank account check after saving ticked.
- Click Save. The field app gets the changes on its next sync.
Reading a document with AI
When document reading is switched on and your role has ai.documents: on a claimant’s Evidence tab, AI Read under a photo of an ID card, voter card, licence or land document shows what AI read beside the image. Compare each field with the document, tick the ones to use (full name, sex, address) — you can correct them first — and Use the ticked fields. Each is minuted “from document (AI)”. NIN, BVN, account and ID numbers are never read by AI: type them, and the usual checks verify them.
Conflicts
Needs conflicts.resolve
When field data or an import clashes with what is on record, the system does not guess: it raises a conflict for you to decide. Records › Conflicts lists the open ones.
| Conflict | Raised when | You can |
|---|---|---|
| Possible duplicate claimant | The same NIN was given with another name; or a new claimant has the same phone and a similar name, the same BVN, or the same bank account as a registered one | Merge, Accept the new information, Not a conflict |
| Property claimed by another person | The field names a different claimant for a property that already has one | Keep existing, Accept the new information |
| Possible duplicate property | Two outlines cover mostly the same land (more than 60% overlap) | Merge, Not a conflict |
| Field change clashes with an office change | The field changed a record the office had also changed since the phone last synced | Keep existing, Accept the new information |
| Added after the cut-off date | A property captured, or a claimant registered, after the project’s census cut-off date | Eligible after all, Not eligible (a note is required) |
- Open a conflict. It shows why it was raised and the two records side by side (for properties, with their outlines on small maps).
- For Merge, choose which record to keep.
- Type a note (for example “confirmed by phone with the claimant”) and click the decision.
- Merge (claimants): the properties, cases, messages and checks move to the kept claimant. Merge (properties): the items, photos and surveys move to the kept property and the duplicate is removed.
- Keep existing leaves the record as it is and drops the field’s version. Accept the new information uses the field’s values (or links the property to the person named in the field). Not a conflict changes nothing.
- The decision and your note are recorded on the conflict and minuted.
The property’s claimant link is on hold (the checklist shows Claimant link approved as missing) and no compensation case can open for that property or claimant.
Same person? (AI)
On a possible duplicate claimant, Explain with AI sets out the evidence for and against “same person”: name variants (Mohammed / Muhammad / Mamman), titles that come and go (Alhaji, Hajiya, Mallam), the same phone or address, linked properties — and suggests merge or keep both, with how sure it is. The identifiers are compared by the system: the AI only sees “same / different / missing”, never the numbers. It never merges anything: you decide.
Integrity
Needs claimants.view to see, conflicts.resolve to set aside
Work queues › Integrity lists patterns worth a second look, found by fixed rules each time the page opens:
- the same bank account on different claimants (the number is shown only by its last four digits);
- one phone number on three or more claimants;
- a claimant with cases in several projects opened within 30 days;
- a valuation approved by the person who recorded it;
- a claimant registered less than 7 days before their cheque.
A hint is not an accusation — a family may share a phone. Open the records from its links; then Set aside… with a note (minuted on the records), or put things right. With AI on, Why might this matter? explains the pattern and what to check.
Spatial flags
Needs spatial.resolve
Every time a boundary changes, and every night, the system checks the outlines. Problems appear on Records › Spatial flags, in the property’s Spatial checks box, and as a red layer on the project map.
| Flag | Means | Blocks a case? |
|---|---|---|
| Overlaps another property | Two property outlines overlap. Thin slivers from GPS error are ignored. | Yes, when the overlap is over 20%; otherwise a warning |
| Project areas overlap | Two project boundaries overlap. | Warning |
| Outside its project | The property is partly or fully outside its project boundary — or, for a property known only by its GPS point, the point is outside. | Yes, when the outline is fully outside; otherwise a warning |
| Cut by a sub-boundary edge | The parcel is partly inside its sub-boundary and partly outside it. | Warning |
| Sub-boundaries cross | Two active sub-boundaries overlap and not both allow it. | Warning |
| Sub-boundary outside its project | More than 1% of a sub-boundary is outside the project. | Warning (on the sub-boundary) |
| GPS point inside another parcel | A property with no outline yet has its GPS point inside another property’s outline: the same land twice, or a wrong point. | Warning |
| Invalid outline | The outline crosses itself or is otherwise not a valid shape. | Yes |
| Weak GPS fixes | The corners were captured with poor GPS accuracy. | Warning |
- Fix the boundary (Edit boundary on the property). Flags that no longer apply close themselves as Fixed.
- Or Accept… the flag with a reason, for example “shared boundary wall, confirmed on site”. An accepted flag no longer blocks a case; the reason is minuted on the property. Reopen undoes it.
Field surveys
Surveys are optional: a property with complete data does not need one before a case. Use them when you want a surveyor to visit a property already on record, for example to verify it.
Assign field surveys
Needs surveys.assign
Properties that already have an open or approved survey are skipped automatically. There are three ways:
- One property: in its file, click Assign survey (or Assign a field survey in the next-step box).
- A selection: tick rows in the property register, then Assign survey in the navy bar.
- A whole project or location: on Surveys, click Assign surveys and choose a project and/or LGA, ward or area.
The surveyor sees new assignments the next time their phone syncs, under Assigned surveys. The message after assigning says how many were assigned and how many skipped.
To take an assignment back before it is submitted, open the survey and click Withdraw assignment (twice).
Review a survey
Needs surveys.review
Submitted surveys appear on the dashboard and under Surveys with status Submitted. Open one and check the findings, the GPS position (opens OpenStreetMap) and the photos.
- Approve survey — the property becomes Surveyed. The property must have a linked claimant.
- Return for correction — write what needs fixing. The surveyor sees the note on their phone, corrects and resubmits.
Compensation cases
Open a compensation case
Needs compensations.open
A case can only open when:
- the property data is 100% complete;
- the claimant data is 100% complete, including a verified bank account;
- the claimant link is approved and there are no open conflicts on the property or claimant;
- there are no blocking spatial flags on the property.
- Open the property. When its data is complete, the next-step box says Open a compensation case.
- Click Open case. If something is still missing, the dialog says Not ready for a compensation case and lists each problem with a Fix link.
- Choose the Compensation type: Cash (Bank Cheque) or 30% Land Allocation.
- Choose What the case pays for (the scope). The items that scope covers are ticked; untick or tick items as needed.
- Add a note if useful, then click Open case. The case gets its number, for example
COMP-KSR-2026-01-0001.
| Scope | Pays for |
|---|---|
| Whole property (land and everything on it) | The land and every item listed on it |
| Land only | The land, no items |
| Buildings and structures | The items from the Building classification dictionary |
| Economic trees and crops | The items from the Economic trees and Crops dictionaries |
| Supplementary (top-up of an earlier case) | A top-up of an earlier case on the same property. Choose the case it adds to under Adds to. |
A property can have several cases. For example, the land as a 30% allocation and, at the same time, the buildings and trees in cash. To stop anything being paid twice:
- the land can be in only one live case (Whole property or Land only);
- each item can be in only one live case;
- cancelling a case frees its items for another case.
For a property that already has a case, use Open another case in its next-step box.
Move a case through its steps
The case file shows the steps, the latest minute, what the next step needs, and What this case pays for: its items with their quantity, rate and amount. Each step can only be recorded by a role with its permission — by default the Valuer values, Finance approves and pays, and you can do any step.
| Cash | 30% land | Recorded by (default) |
|---|---|---|
| Pending valuation | Pending valuation | — (case opened) |
| Valuated: every line valued on the Valuation tab (the assessed value is their total) | Valuated: land area (30% calculated) | Valuer, Officer |
| Approved: approved amount (a minute when it differs from the assessed value) | Approved | Finance, Officer |
| Cheque issued: number, bank, date | Plot allocated: plot reference | Finance (cheque), Officer |
| Paid / collected: date | Completed: date | Finance, Officer |
Click the amber Mark as … button, fill in the figures, add an optional minute, and confirm. Attach the matching document on the Evidence tab (the right kind is suggested). Full details: Workflows and statuses.
- The valuer gives each line of a case its own figure on the Valuation tab; the dictionary rate beside it is a guide only. The assessed value is the total of the lines plus any adjustment, and every save is kept as a version. See the Valuer guide.
- Several cases at once: tick cases of the same type at the same step in the register, then Move on to the next step…. The same figures and minute are recorded on each (Valuated keeps each case’s own worksheet value); the message says how many moved and why any did not.
- Correct values fixes a typo in recorded figures without changing the step. The minute shows each old and new value. On a paid or completed case, figures can only be corrected by someone with the permission “Correct recorded values on paid or completed cases” (administrators); notes can still be added.
- While a property has a live case, its boundary can only be changed by someone who can correct recorded values, because the boundary is part of what the case pays for.
- Print prints the case with the KADGIS heading, for the paper file.
- Cases that changed since you last opened them show an amber dot in the register and open on their minutes.
Disputes and cancellation
Needs comp.hold
- Dispute puts the case on hold with a reason. Nobody can advance it while it is disputed.
- Resolve & resume returns it to the step it was on, with a note on how it was resolved.
- Cancel case needs a reason and a second click. It closes the case for good and frees its land and items, so a new case can cover them.
Messages to claimants
Needs messages.send
Send SMS, email or both to:
- one claimant — Send message in their file;
- a selection — tick rows in the claimant register, then Send message;
- a whole project — Message claimants in the project file, or Messages › New message, optionally only claimants whose property is at one stage.
Placeholders are filled in for each claimant:
- The preview shows how many claimants receive it and how many have no phone or email for that channel (“no contact”).
- SMS is limited to 640 characters; every 153 characters after the first 160 is one more SMS part.
- Send asks for a second click. Messages are queued and sent in the background.
Open a sent message to see its deliveries. If some failed, Retry failed sends them again.
Import and export
Export needs data.export; import needs data.import
Every register can be exported. Projects, properties and claimants can be imported from a filled-in template. The Properties page also has Import boundaries (a GeoJSON, KML or zipped shapefile of outlines) and Import items (what is on each property). Nothing is saved until the file passes the check and you confirm.
Templates, matching rules and limits: Import and export reference.
Daily routine
- Dashboard: decide open conflicts, look at blocking spatial flags, review submitted surveys and look at disputed cases.
- Fill the gaps — complete the properties and claimants captured in the field or imported.
- Properties filtered by Claimant: missing — link claimants.
- Claimants filtered by Bank check: not verified — run the checks.
- Properties filtered by Data: complete — open cases for those that do not have one yet.
- Compensation cases with an amber dot — see what changed.