Keep project identity clean
Use consistent organisation, donor, project, sector, location, and reporting-period records before export. IATI quality starts with ordinary data discipline.
IATI reporting is easier when the operating system already carries clean project structure, indicators, locations, finance records, and supporting evidence. This guide explains how EMPOBase helps teams get there.
Use consistent organisation, donor, project, sector, location, and reporting-period records before export. IATI quality starts with ordinary data discipline.
Link indicators, outputs, field reports, files, and finance records to the same project structure so narrative and numbers can be checked together.
Pro and Enterprise tiers support IATI-oriented export workflows. Teams should review sensitive fields before publishing externally.
Use audit logs and changelog notes when correcting figures, revising dates, or moving activities between reporting periods.
EMPOBase supports CSV and PDF exports across reporting surfaces, with IATI-compliant XML export planned for Pro and Enterprise workflows. We keep the public guide honest so teams can plan around the current product state.