Enterprise operating record templates

25 October 2026. Required fields for the planned service, not completed client records. Every record carries record_id, version, programme/client/brand IDs, optional agency sub-tenant, actor, timestamps, permissions, retention and a change log. Human and synthetic evidence remain distinguishable.

Contract and scope schedule

Legal contracting entity; executive sponsor and research owner; programme start/end; price and currency USD; tax treatment; audience-market-language-task cell matrix; first/full/pulse wave cadence; development/sealed/qualitative bases; permitted uses and exclusions; agency grants; provider access dependencies; source/record ownership; MSA/DPA/security obligations; deliverable acceptance; outcome-independent fees; invoice dates/net terms; included model-change remedies; additional-scope process; termination/export/deletion; publication consent recorded separately.

Wave and procurement plan

programme_id, wave_id, market/language, audience-cell IDs, dates, initial/refresh/full/pulse classification; per-cell target and achieved bases; unique-person counts and overlaps; incidence, quotas, recruitment source, supplier quote ID, costs/currency, moderation and translation; respondent-tenure/exposure rules; replacements; fieldwork cash commitment and prepaid balance; reviewer/custodian reservations; release deadline and exception owner.

Source rights register and evidence ledger

Asset checksum/version, rights holder and permitted uses, original population/base/date, source/page, data sensitivity, processor route, retention, deletion obligations and grant IDs. Evidence type is observed/derived/generated; transformations cite inputs, assumptions and uncertainty. A generated quotation never becomes an observed participant statement. Store identity mappings in the protected research system, not a public report or telemetry feed.

Protocol and split manifest

Decision, estimand, primary endpoints, tolerances Δ/δ/ρ, sample/power rationale, subgroup targets, weighting/exclusions, stimulus order and burden, baseline/candidate list, selection rule, multiplicity family, sequential-wave policy, answered-coverage rule, split assignment, prior-exposure flags, freeze hashes and times. Name the custodian and list permitted access before/after release. Consumed holdouts are permanently marked and may only inform later development with permission.

Model and run manifest

Provider/returned model metadata, prompt and retrieval snapshot hashes, output mapping, inference settings, approved task, parent configuration, requested/processed/omitted assets, request estimate/confirmation, entitlement/spend reservation, agency/client grants, stage attempts and idempotency keys, generation costs and labels, timestamps, cancellation/failure reason, comparison baselines and result version. The manifest states whether the run contains any new human observations.

Calibration Record

Programme, wave, audience, market/language, task, model/configuration and evidence snapshots; human dates and actual/effective sample sizes; development/validation separation; metrics and uncertainty method; primary/secondary families; subgroup and market results; all pass/fail/inconclusive endpoints; abstention coverage; qualitative coding and material misses; tested scope versus proposed transfer; conflicts; custodian and reviewer sign-off; status, expiry and event triggers; superseded/revoked links; permitted exploratory versus quantitative use.

Publication fields: publication_permission_id, anonymisation_status (private/review-needed/approved), reviewer, date, redaction manifest and residual identification assessment. Public records exclude respondent identities, private source paths, client/employer/agency identifiers and identifiable quotations unless separately permitted. A client-owned record is not automatically authorised for public marketing.

Decision and usefulness event

study_id, decision_id, programme_id, brand and agency grant, pseudonymous seat ID/role, action (Panel/Verdict/Challenge/Talk/Ask the research/Export), successful/failed/retried state, latency, user-reported action (changed work/exported/requested humans/no action), linked follow-up or outcome date, observed outcome versus attribution claim, human time and support minutes. Record consent/telemetry policy and retention. Do not log confidential prompt text merely to count use.

Agency onboarding and licence record

Client owner approval, agency sub-tenant, scope/asset grants, export rights, roles, expiry, identity verification, SSO/connector scopes, training/sandbox tasks, isolation and revocation evidence, named administrator and support contact. For delivery licensees add method qualification, witnessed audit, conflicts, independent review arrangement, quality/sampling checks, revenue share/currency, audit rights and suspension criteria. Delegated access alone does not confer record-signing authority.

Model-change and release record

Trigger and impact tier; affected clients/audiences/records; provider retirement deadline; old/fallback availability; development and sealed evidence needed; included-scope contract obligation versus expansion; reserve/overrun funding; restriction and customer notice; signed release/rejection; new record IDs; cache/job/connector invalidation; rollback test and closure evidence. Never rewrite historic outputs in place.

Executive review and monthly finance close

QBR: last/current wave dates, changed decisions, active/returning seats, Panel-to-action definition and denominator, citations checked, human follow-ups, unresolved claims, adverse findings, usage/latency, costs and next-wave commitments. Do not aggregate endpoint passes into a universal score.

Finance: recognised programme/audit/licence revenue, invoices/receipts, USD supplier commitments, fieldwork prepayments, audit WIP, deferred revenue, AR ageing, staff/reviewer capacity, actual human/AI costs, margin, included-change reserve, refunds and remaining term obligations. Reconcile to the model's timing rather than equating bookings with revenue or cash.

Incident, offboarding and deletion

Severity, affected grants/assets/jobs, detection/containment times, accountable operator, rights/privacy assessment, required communications, restored service checks and corrective actions. End of term: export inventory and access rights, grant/token/job revocation, provider/file deletion tasks, backups and legal retention exceptions, completion evidence and customer confirmation. Retain historical evidence according to contract, including failed records.