Bufdir Export
Feature Detail
Description
Bufdir Export automates the generation and delivery of the structured reports required by Bufdir (Norwegian Directorate for Children, Youth and Family Affairs) as a condition of receiving public funding. The feature maps the platform's internal activity data to the exact fields and format that Bufdir expects, allowing organization administrators to generate a compliant export with a single action. The export covers the reporting period, activity counts by type, participant demographics (anonymized where required), and any other fields mandated by the current Bufdir reporting standard. Both preview and downloadable file output are supported.
User Flow
Analysis
Bufdir reporting is a non-negotiable compliance requirement for every organization using the platform. All four workshop organizations — NHF, Blindeforbundet, HLF, and Barnekreftforeningen — receive Bufdir funding and currently spend significant staff time assembling these reports manually from spreadsheets, Word documents, and email threads. A single mistake or omission can jeopardize funding. By automating this process, the feature eliminates hours of administrative work per reporting cycle, drastically reduces the risk of errors, and removes a major source of organizational stress. It was identified as a MUST HAVE across all organizations and is a key commercial differentiator for Meander relative to general-purpose tools. Norse Digital Products has committed to initiating dialogue with Bufdir on behalf of all organizations to ensure the export format stays current.
The export pipeline runs server-side in Next.js. A dedicated service class reads activity records for the selected reporting period from PostgreSQL, applies the field mapping rules defined in a configurable Bufdir format specification (stored as JSON config), and produces the output document. The initial format is likely XLSX or CSV based on current Bufdir requirements; the architecture is designed to support additional formats (XML, JSON) if Bufdir modernizes their intake process. The mapping layer is kept separate from the query layer so that format changes require only configuration updates, not code changes. Role access is restricted to Org Admin and Global Admin. A preview screen renders the mapped data in a human-readable table before the file is downloaded. Audit log entries are created for every export action, recording the exporting user, timestamp, and reporting period.
Components (118)
Shared Components
These components are reused across multiple features
User Interface (12)
Service Layer (34)
Data Layer (22)
Infrastructure (38)
User Stories
No user stories have been generated for this feature yet.