Documentation / Getting started
Start with the definition.
A useful registry starts with measures people can explain. Use the CSV template to gather definitions, owners, formulas, and reporting references before a product walkthrough.
01 / The file
Ten fields. One measure per row.
These are the exact headers in the downloadable CSV. Its seven sample records use fictional owners and example report links. Replace them with your own approved documentation.
The table describes the file, rather than a verified application schema. Confirm required fields, accepted values, and import behavior against the application version you receive.
Scroll the table to see all columns →
| CSV header | What to document | Template example |
|---|---|---|
Name | The name people use for the measure. | Monthly Recurring Revenue |
Definition | What the measure includes and excludes. | Total recurring subscription revenue normalized to a monthly amount |
Business context | Why the measure exists and how people use it. | Core metric for growth tracking and board reporting |
Owner name | The person responsible for the definition. | Jane Doe |
Owner email | A contact for questions about the measure. | jane.doe@example.com |
Formula | The written calculation or business rule. | Sum of active subscription monthly rates |
Source system | A documented source reference; not a live connector. | Stripe |
Dashboard URL | A reference to the report where the measure appears. | https://dashboard.example.com/mrr |
Domain | The business grouping used to organize measures. | Finance |
Status | The intended lifecycle state. | Approved |
Preparation notes. Keep header spelling and capitalization. Quote values containing commas. The examples use Draft, Approved, and Deprecated statuses. Include a full protocol in report URLs, and check owner email addresses before sharing the file.
02 / Preparation workflow
From spreadsheet to a reviewed definition.
This is an illustrative evaluation workflow. Import validation, permissions, and change history need to be demonstrated in the application.
Prepare a small, representative file.
Keep the ten headers below. Replace the sample records with definitions your team can review. Use synthetic examples for a public demo.
Review meaning with the measure owner.
Agree on scope, time period, exclusions, units, and the written calculation. A CSV can preserve an ambiguous definition just as easily as a spreadsheet.
Demonstrate the import before adopting it.
Ask to see field mapping, invalid-row feedback, preview, and confirmation in the proposed version. Check what happens to duplicate, missing, and updated records.
Check how a definition is maintained.
Walk through finding a record, editing it with the right role, changing its status, and reviewing any recorded change information.
03 / Technical review
Plan the responsibilities of self-hosting.
MeasureMap is offered under a self-hosted license. Before deployment, review the delivered package with the people who will operate it. Public capability descriptions do not establish runtime behavior or security controls.
This marketing site does not distribute or verify an application image. Request version-specific instructions before choosing infrastructure or running deployment commands.
- Package and version
- Request the versioned application package, supported runtime and database versions, installation instructions, and upgrade and rollback procedures.
- Infrastructure ownership
- Name the team that will own hosting, database operations, monitoring, patching, and incident response. Agree on what the license includes.
- Access and transport
- Review authentication, administrator provisioning, role behavior, TLS termination, secrets, network access, and any outbound dependencies with your security team.
- Recovery and retention
- Agree on backup frequency, retention, restore testing, data export, and responsibility for recovery before production use.