Practical appendices
Which future-use record must be completed before an unresolved question becomes a permitted commitment?
Templates belong after completed decisions
Use these unfilled future-use templates separately from the earlier completed fictional dispositions. Each requests an evidence object and identifies the action it controls. An unanswered question closes no gate, and an empty funding field supplies no resource. Select fields relevant to the proposed obligation while retaining every dependency that could change the next commitment.
Begin with the next action rather than the largest strategic ambition. Identify whether the team wants to review an offer, run a bounded experiment, accept a customer duty or commit spending. The evidence standard depends on that action. An internal review can use supplied assumptions while a binding service or payment commitment requires applicable facts and authority. A template becomes useful when it makes that boundary inspectable, not when every cell has been filled with reassuring language.
The owner column should name a role and a person who can obtain or assess the evidence. Collective ownership can leave an unresolved dependency without a route to resolution. The stop event should occur before the protected commitment. A general instruction to monitor later is insufficient when an offer or purchase has already created the obligation. The completed Meridian record demonstrates these fields; the templates below are separate future-use tools and grant no authority themselves.
Evidence status should be recorded honestly. Distinguish a supplied assumption, a scoped estimate, a retained source record, an applicable agreement and an accepted operational test. The format of a document does not establish its relevance. A signed agreement for a different package or a service test for a different duty may not support the current action. The template should identify the scope and event that make the evidence applicable, along with the condition that would expire it.
Unfilled template: unit and event acceptance
Future-use template. Enter the actual definition and evidence; these questions are not completed Meridian records.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: unit and event acceptance | ||
|---|---|---|
| Field to complete | Evidence to enter | Action it controls |
| Commercial unit | Define customer, account, contract or other purchased object | Comparable offer and acquisition interpretation |
| Service unit | Define task, duty, location or recurring work per commercial unit | Cost and capacity mapping |
| Activation event | Identify accepted start event and authoritative source | Entry to acquired-customer cohort |
| Payment object | Identify payer, bill, due event and receipt record | Cash and credit interpretation |
| Exception states | Record duplicates, missing events, suspension and reactivation treatment | Metric acceptance and model escalation |
| Owner and expiry | Name approver and event that changes the definition | Stop unsupported continuity before a new commitment |
Use the unit template when the proposed action changes the relationship or the event used to count it. Trace a concrete record from offer through service and cash. If the owners cannot agree on the count, preserve the disagreement and its consequence instead of averaging incompatible totals. The template is complete only when the definition, exceptions and authority are recorded. It should not be used to imply that a customer database has been cleaned or that a rate has been estimated.
Make cost and concession records decision-specific
Unfilled template: contribution perimeter
Future-use template for a declared management measure. Do not fill a missing amount with zero.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: contribution perimeter | ||
|---|---|---|
| Field to complete | Evidence to enter | Decision consequence |
| Price basis | State net amount, period, service scope and credits included | Choose a comparable revenue perimeter |
| Recurring cost | Identify cost-driving unit, scope and estimate or record | Test starting contribution and changed service duties |
| Acquisition boundary | State spending scope, attribution window and activation denominator | Interpret CAC and campaign obligation |
| Shared envelope | State relevant range, committed cost and next resource step | Assess whole-business affordability |
| Excluded duties | Assign owner and reason for each omitted obligation | Hold or escalate when an exclusion controls action |
| Reconciliation | Trace components to records and remove double counts | Accept the metric only within its declared purpose |
Use the contribution template to resolve what the measure includes before debating whether it is high enough. A classification disagreement can be handled through a bridge if the amount and timing are known. A missing obligation needs evidence and can hold the action. The owner should identify which case represents the proposed package and which changes invalidate the old perimeter. This record is not a substitute for an applicable accounting assessment or a full dated financial model.
Unfilled template: concession request
Future-use template. A concession must identify the customer action it buys and the response when that condition fails.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: concession request | ||
|---|---|---|
| Field to complete | Evidence to enter | Permission boundary |
| Purpose | State acquisition, retention, volume, payment or corrective purpose | Avoid an untestable general growth claim |
| Eligible offer | Define customer universe, package and duration | Prevent open-ended concession delegation |
| Changed assumptions | List price, spending, churn, cost and timing changes explicitly | Require a complete joint typed fixture |
| Response evidence | Identify activation, service or receipt event that tests purpose | Keep supplied mechanism separate from causal effect |
| Failure response | State permitted action when customer condition is not met | Reserve contractual assessment and stop further exposure |
| Owner and release | Name commercial, finance, service and funding authorities | Do not release the offer before applicable gates |
Use the concession record to compare a complete offer with the reference. Do not attribute a larger acquired count to a discount when the model also supplies greater acquisition spending. Do not combine separate sensitivity benefits without recomputation. A bounded experiment can be approved under a different action boundary from a permanent tariff, but its customer promise and resource use still need to be stated. The template should lead to a disposition, including a hold or rejection where the premise remains unsupported.
Keep treasury and service gates independent
Unfilled template: funding and payment terms
Future-use template. Supplied model cash is not proof of an available funding source.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: funding and payment terms | ||
|---|---|---|
| Field to complete | Evidence to enter | Event that can stop action |
| Resource source | Identify unrestricted cash or committed facility and permitted use | Spending precedes an available draw condition |
| Customer timing | Trace invoice, due event, receipt and dispute state | Assumed collection cannot be reconciled |
| Supplier eligibility | Identify signed terms and qualifying purchases or costs | Proposed payable benefit is inapplicable or withdrawn |
| Other obligations | Identify finance fees, tax, capital and dated payments absent from proxy | Omitted payment controls the trough |
| Stress requirement | State changed terms or timing that can alter the commitment | Required dated liquidity cannot be demonstrated |
| Treasury authority | Name owner, evidence deadline and escalation route | New exposure exceeds the permitted funding boundary |
Use the treasury template before interpreting a modelled cash benefit as a resource fact. A positive endpoint does not remove an earlier need, and a nonnegative monthly path does not establish intramonth liquidity. The record should distinguish delay, recoverability and dispute where they matter. Treasury should retain the source restrictions and term conditions that could invalidate the benefit. A complete funding disposition states what can be committed now and what remains held pending evidence.
Unfilled template: service admissions
Future-use template. Affordability does not establish a performable duty.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: service admissions | ||
|---|---|---|
| Field to complete | Evidence to enter | Action boundary |
| Promised duty | State package, coverage, start event and exclusions | Only that duty may be offered |
| Work design | Identify qualified resources, assignments and escalation | Hold unsupported coverage or workload |
| Acceptance evidence | Map service test and system trace to customer promise | Release only after applicable acceptance |
| Range and step | Identify event requiring a changed envelope or design | Recompute before the added resource is committed |
| Existing customers | State protection of already accepted duties | Close new admissions before service degrades |
| Stop authority | Name service owner and referral to committee | Block dated offer when evidence or scope expires |
Use the service template when a new offer or acquisition path can change the duty. An expected customer count cannot allocate discrete qualified resources, and a cost estimate cannot establish service readiness. The acceptance evidence should correspond to the offer’s actual promise. If a smaller truthful pilot can be supported, give it a separate admissions boundary. If a different design is cheaper and executable, revise the comparison rather than preserving an unnecessary resource step.
Close the loop from evidence to permission
Unfilled template: cohort and metric interpretation
Future-use template for evidence-based parameters and reporting. A percentage is not self-defining.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Unfilled template: cohort and metric interpretation | ||
|---|---|---|
| Field to complete | Evidence to enter | Interpretation it controls |
| Relationship state | Define contractual continuation, usage or repeat purchase separately | Choose a suitable customer model |
| At-risk universe | State eligibility, window and partial exposure treatment | Interpret retention denominator |
| Age alignment | Preserve cohort acquisition and service-age fields | Avoid exposure differences masquerading as quality |
| Metric perimeter | State numerator, denominator, costs, horizon and clock | Use value or payback within declared purpose |
| Method revision | Record changed definition and continuity bridge if available | Do not label a method change performance improvement |
| Owner and permitted use | Name data and finance acceptance and stop event | Prevent illustrative input or proxy becoming an unsupported external claim |
Use the cohort template before replacing an illustrative churn or CAC input with a recorded measure. The event, universe and spending scope must map to the relationship the model represents. Unknown states remain unknown until reconciled. If the actual base is noncontractual, heterogeneous or materially age-dependent, an accepted metric may still require another model. The purpose is to preserve meaning, not to make every dataset fit the existing engine.
Close the relevant templates with one disposition for the next action: identify the case, independent evidence states, permitted use, commitment bound, deadline before the protected event and stop authority. Keep unanswered future questions in their template. Meridian's separate completed memo illustrates this closure through existing-staff preparation and specific holds on other commitments.
The worksheets should be shortened when established records already answer their questions. Reference the applicable policy or evidence and identify why it covers the new obligation. Repeating data without a decision consequence creates administrative burden. Conversely, a familiar document should not be accepted merely because it has an official format. The evidence must support the proposed service, resource and event boundary. A concise applicable record is stronger than a long generic assurance.
Test the handoff by asking another owner to identify the permitted next act and its supporting conditions. A concern list supplies no disposition; unsupported authorisation loses accountability. The worksheets connect the exact mechanism studies to that permission boundary. Assess the trace through independent challenge, using field completion as neither evidence nor a quality verdict.
Decision and consequence
Use only the templates relevant to the proposed action and complete them before calling a record approved. Preserve missing information as unresolved, name the responsible person and tie the deadline to the protected commitment. Issue a disposition that states what may proceed and who can stop it. Keep these future-use questions separate from Meridian’s completed fictional records.
A serious alternative
Existing operating and finance policies can make a new worksheet unnecessary. A team should not copy established evidence into another form merely to satisfy the paper’s structure. This objection is correct when the policy is applicable, current and tied to the new obligation. The template can then be replaced by a reference and a short exception record. It remains useful when the offer, relationship, payment term or resource design changes beyond that policy. The goal is an inspectable decision and handoff, not adoption of a particular document format.
Where this argument stops
These worksheets are unfilled future-use tools, not completed evidence or actual permissions. They compute no new economics and establish no legal, accounting, funding or service fact. The fictional completed records are separate and explicitly labelled. Users need applicable source records, authority and model representation for their own obligations; filling a template cannot create those conditions.