Document the claim before the amount
A useful transaction report identifies where the information came from and what that source actually establishes. Begin with the public record or source URL, then describe the relevant event in plain language. If the information is secondhand, say so. Do not convert a private conversation, an approximate recollection, or a general partnership announcement into a precise transaction claim without supporting evidence.
Keep the report within the information you are entitled to share. A source can be useful without reproducing confidential contract language or identifying restricted participants. Explain where important details are unavailable and why the limits matter for interpretation. The goal is a clear account that could be reviewed later, not the largest or most specific number you can construct from partial information about a deal.
−Secondhand amount repeated
−Partnership treated as sale
+Source identified clearly
+Missing details stated
Select the stage the evidence supports
The status field distinguishes a bid or offer, a signed agreement, and completed payment. Choose the stage supported by the source, not the stage you expect the transaction to reach. An offer may include conditions that never become an agreement. A signed contract may require further delivery and acceptance. Payment can occur later or cover only a defined part of a broader arrangement.
If the source discusses several stages, explain the dates and relationship between them in the context field. Preserve changes in scope or amount instead of collapsing the history into a single figure. A clear sequence makes the report more useful and reduces the risk that someone interprets an early proposal as a completed sale. Where the event cannot be established, record that uncertainty rather than selecting a stronger status.
- 01Offer madeConditions may remain
- 02Agreement signedPerformance still separate
- 03Payment completedEvidence establishes event
Make the figure understandable
Include the data category, pricing unit, approximate volume, historical coverage, and preparation involved where those details are supported. Explain whether the amount covers only data or also services, continuing work, or another component. A whole-archive amount should not be presented as a per-record benchmark without an established denominator. Mixed components should remain mixed unless the evidence supports a clear allocation between them.
Add relevant terms when they are available and shareable: permitted use, exclusivity, duration, acceptance, and responsibility for preparation. These details can explain differences between transactions that initially appear similar. Missing terms do not make a report worthless, but they limit the conclusions someone can draw from it. Keep that limitation beside the number so readers do not mistake incomplete context for a directly comparable market rate.
A downloaded report is not a published benchmark
This form creates a local report brief. It does not submit the information to a review team, verify the transaction, or publish a new market record. Use the download to organize the source, status, and context for a later review through an appropriate process. Check the file before sharing it elsewhere and remove anything you are not authorized to disclose, including confidential details copied into the narrative.
If new evidence becomes available, preserve the earlier report and explain the update. A later payment receipt may establish a further event; a corrected source may change the interpretation of the original claim. Keeping that history makes the evidence trail stronger. The methodology page explains how source-backed information, unreviewed reports, and illustrative examples should remain distinct rather than being pooled into a misleading average or implied live quote.
| Action | Result established |
|---|---|
| Prepare report | Context organized |
| Download file | Local document |
| Publish benchmark | Not performed here |