SourcerowFIELD GUIDEOpen the demo

CURRENT DEMO CONTRACT V1 · REVIEWED JULY 22, 2026

MSP QBR data dictionary: 10 fields for a source-labeled brief.

A field-by-field contract for comparing exactly two reporting periods without sending ticket text, credentials, or client names. The rules below are enforced by the current browser demo.

See these fields become a brief Download the CSV template

Two synthetic rows · about 60 seconds · no signup · no PSA/RMM credentials

DIRECT ANSWER

Give the meeting comparable evidence. Leave judgment with the MSP.

The current demo requires one header and two rows for the same redacted client. It validates quarter or month labels, rejects blanks and extra columns, orders the periods, computes deterministic changes, and labels findings and decision prompts with their source rows.

It does not establish causation, contractual compliance, security assurance, financial impact, or the right threshold for a client.

10 EXACT COLUMNS

The current evidence surface.

Unknown is not zero. Additional headers are rejected so accidental notes, identifiers, or free text do not slip through the narrow template.

Field + exampleDefinitionCurrent useEnforced guardrail
01period2026-Q2Comparable reporting windowOrders the two rowsExactly YYYY-Q1…Q4 or YYYY-MM; both periods must be distinct.
02client_aliasClient-042Stable pseudonym for one clientLabels the brief1–64 letters, numbers, spaces, hyphens, or underscores; use the same alias twice.
03tickets_opened134Tickets created under one inclusion ruleDemand-change contextNon-negative integer. It cannot explain severity, cause, or backlog.
04tickets_closed128Tickets closed under one scopeThroughput contextNon-negative integer. Opened and closed counts can represent different cohorts.
05sla_breaches3Breaches under one unchanged PSA ruleService-level findingNon-negative integer. The export does not contain contractual targets or exclusions.
06patch_compliance_pct94In-scope assets meeting one patch ruleCoverage finding + exception promptBare number from 0–100; keep asset scope and policy fixed.
07backup_success_pct98.4Successful jobs within one backup scopeBackup exception promptBare number from 0–100. Job success is not restore-test evidence.
08critical_alerts2Alerts under one severity and deduplication ruleAlert finding + review promptNon-negative integer. Confirm disposition and business relevance in the source system.
09recurring_incidents11Incidents under one recurrence keyRepeat-incident findingNon-negative integer. Aggregate counts cannot identify root cause.
10licenses_unused12Seats meeting one inactivity ruleReclaim/reassign promptNon-negative integer. Verify ownership and contract terms before removal.

BEFORE THE EXPORT LEAVES THE PSA/RMM

Aggregate first. Redact twice.

Build the comparison inside an approved reporting environment. Then inspect the final CSV as plain text before it enters any new tool.

  • Replace the client's legal name and account ID with a new stable alias.
  • Remove ticket subjects, bodies, comments, notes, attachments, and hidden columns.
  • Remove names, emails, phone numbers, usernames, and user IDs.
  • Remove hostnames, domains, IP/MAC addresses, serial numbers, and asset tags.
  • Never include credentials, API keys, tokens, secrets, authenticated URLs, or recovery codes.
  • Use an alphanumeric alias; spreadsheet formula prefixes such as =, +, -, and @ are rejected.

A pseudonym is not anonymity. Aggregate metrics can remain confidential or become identifiable when combined with other information.

CSV CONTRACT2 ROWS · 1 ALIAS
period,client_alias,tickets_opened,tickets_closed,
sla_breaches,patch_compliance_pct,backup_success_pct,
critical_alerts,recurring_incidents,licenses_unused
2026-Q1,Client-042,112,106,8,86,99.2,4,19,14
2026-Q2,Client-042,134,128,3,94,98.4,2,11,12

INTERPRETATION CONTRACT

Four claims this CSV cannot make.

01

“The backlog is X.”

Opened minus closed is not backlog without carried opening and closing balances.

02

“Backups are recoverable.”

Job-success percentage is not evidence of a completed restore test or recovery objective.

03

“The client is compliant.”

Operational percentages do not prove contractual, regulatory, or framework compliance.

04

“This caused business loss.”

The export has no financial, root-cause, user-impact, or business-priority context.

60-SECOND PREFLIGHT

Check comparability before generating prose.

  1. 01

    Exact contract. Ten unique headers, two data rows, and no additional columns.

  2. 02

    One alias. Both rows use the same non-identifying client alias.

  3. 03

    Distinct windows, same cadence. Use either two YYYY-Qn labels or two YYYY-MM labels with equal scope; never mix quarters and months.

  4. 04

    Valid values. No blanks; counts are non-negative integers; percentages are 0–100.

  5. 05

    Stable definitions. Populations, exclusions, SLA rules, and severity rules did not drift.

  6. 06

    Human owner. Name who will inspect source detail and approve each client-facing line.

FROM FIELD CONTRACT TO DECISION BRIEF

See what these ten fields can—and cannot—support.

See these fields become a brief

The application reads CSV values in your browser. Cookie-free, session-scoped telemetry records the action—not the CSV values.