How a V² Report is structured
A section-by-section guide to the V² Report, from the original baseline and First Value Date to 30-, 90- and 180-day results, limitations and the next decision.

Suppose your regional marketing team has launched a new website, and headquarters asks what the investment changed. The launch date confirms that something went live, but it says little about qualified inquiries, ongoing maintenance or whether the team can improve the site without outside help.
A V² Report answers those questions against commitments made before work began. It records the starting point, first delivery, subsequent measures and next decision.
The report is part of the engagement's output
Our working principle is Value delivered beats value promised. A completed feature list is evidence of delivery, but it cannot establish the business value of that delivery on its own. The V² Report connects the work to outcomes the client agreed were worth measuring.
The report follows the V² Framework, expressed as Value = Velocity × Longevity. Value Map establishes the baseline, scope, targets and First Value Date. Value Sprint delivers the first agreed result. Value Transfer equips the client to operate what was built. Value Growth checks whether the results persist, and identifies what deserves attention next. The method overview explains these stages in context.
A CEO can see what was committed and achieved. A Marketing Director can review commercial measures. A Digital Lead can check what remains dependent on outside support. One record serves all three.
The opening sections preserve the original commitment
The first section establishes context and scope: the business problem, markets involved, agreed deliverables, responsible teams and any approved change requests. It also specifies what was outside scope. Without this, a later reader could mistake an unrequested feature for a missed commitment.
Next comes the baseline. Every KPI needs a starting value, a definition and a measurement source. For qualified inquiries, the report defines what qualifies and where it is counted. More form submissions do not necessarily mean more qualified inquiries. Missing or unreliable baseline data should be stated rather than reconstructed as if it had been recorded at the time.
The First Value Date section then records the promised date and the agreed first result, followed by what actually went live and when. It states plainly whether the date was met or missed. Changes to delivery, scope and written approvals remain visible. Our separate explainer on committing to a First Value Date covers why that date matters.

Checkpoints show progress, including what remains unfinished
The KPI section places the baseline, agreed target and results at 30, 90 and 180 days after launch side by side, with consistent definitions. Readers see movement and whether targets were met.
The following numbers are illustrative, not client results. The day-180 cells are intentionally left pending because no day-180 results were supplied for this example.

At day 90, the illustrative qualified-inquiry count has exceeded its target of 24, and the number of indexed market pages has passed 30. Inquiry routing time has fallen below its one-day target. The table does not establish that the engagement caused every change.
The last row deserves equal prominence. Changes made in-house improved from 0% to 35%, but remain below the 60% target. A report that highlights the first three rows and buries the fourth would give a misleading account of durability. The next checkpoint must examine what still requires outside intervention.
Day 180 helps test whether initial gains last beyond launch activity or temporary support. If a checkpoint has not occurred, the report should say pending. If data is unavailable, it should say unavailable and explain why, rather than treating an empty cell as a zero or a success.
Handover is documented as an operational result
The Value Transfer section records what the client can actually use after delivery: documentation, access, source files where applicable, training and named responsibilities. It distinguishes assets supplied from capabilities demonstrated. Sending documentation is one action; showing that a regional marketer can update a page safely is another.
This affects Longevity. A completed site can still need a developer for routine changes. A running automation can lack someone to review exceptions. Training attendance alone does not prove independence.
A useful report therefore connects handover evidence to the agreed KPIs. In the illustrative table, the share of changes made in-house is a direct signal of operational independence. Because it is behind target, the report should preserve that fact alongside the handover inventory. Ownership is meaningful when people have the access, knowledge and working process to exercise it.
The V² Score is readable only with its breakdown
The V² Score combines two components, each scored from 0 to 10: Velocity Score × Longevity Score. Velocity concerns how quickly the agreed first value was delivered, including performance against the First Value Date and scope. Longevity concerns how well the resulting value holds up, including post-launch outcomes and the client's ability to sustain the work.
The home page uses an illustrative example: V² Score: 69 (Velocity 9.5 × Longevity 7.3), with the product rounded from 69.35. The displayed number is inseparable from its components. A 69 driven by strong delivery speed and weaker durability prompts a different discussion from a similar total with the reverse pattern.
At each reporting checkpoint, the V² Score appears with both component scores and the underlying dates, KPIs and handover evidence. The assessment should not imply unsupported precision. The V² Score is a reporting tool, not a scientific measure. It helps frame decisions; it does not independently establish commercial causation or provide a universal benchmark between different engagements.
The displayed number is inseparable from its components.
The adjacent other factors and limitations section makes that caution practical. Changes in sales staffing, campaign activity, seasonality and market demand can affect inquiries. Search indexing and lead quality may have measurement gaps. We state which work Vibery delivered, which actions belonged to the client or partners, what the available records show and what they do not establish.
The rules protect the integrity of weak as well as strong results
The report keeps the targets agreed in the Value Map visible throughout the engagement. They do not change after that point without the client's written agreement. New requests are estimated and approved before work starts, and any effect on scope, measures or timing belongs in the record.
We also do not assign V² Scores retrospectively to projects delivered before the V² Framework, unless their baselines and targets were genuinely recorded at the start. Those projects can demonstrate capabilities and documented results, but reconstructed scores would create false comparability.
Finally, the report does not hide a missed First Value Date, a weak checkpoint or a low score. A low result should prompt an explanation of what happened and what can be corrected. The target and observed result remain visible, even when unfavorable.
Use the report to make the next decision with headquarters
For a Regional Managing Director, the report provides a common basis for discussion with headquarters. It shows the regional starting position, the first committed delivery, what changed by each checkpoint and what the local team can now maintain. Headquarters can distinguish local evidence from a proposal to expand.
The final next initiative section turns those findings into a decision. In the illustrative example, the lagging in-house change rate may justify further enablement before wider rollout. That is a possible response, not a conclusion the KPI alone proves. The report should name the unresolved issue, the evidence needed and the proposed next scope; any new commitment belongs in a fresh agreement.
Before approving another project, ask your team to assemble one page showing the original targets, actual dates, checkpoint KPIs, handover evidence and external factors. Mark what is proven, what is still being measured and who will own the next action. That is enough to begin a more disciplined investment discussion.
To establish the same measures before your next engagement, book a Value Map call.