QUICK ANSWER
What should a market research template include?
A market research template should include a bounded decision-support question, market and evidence period, objectives, assumptions, secondary and direct methods, group-level sampling and safeguard states, authorized sources, aggregate rounds, observations separated from inferences, evidence-linked findings, confidence rationales, contradictions, gaps, limitations, review and expiry dates, and explicit downstream handoffs.
A useful market research template starts with a bounded question and ends with a reviewable evidence trail. It separates existing-source research from direct research, records methods and aggregate rounds, keeps observations distinct from inferences, links findings to evidence, and preserves confidence, contradictions, gaps, limitations, review dates, and downstream handoffs.
This downloadable pack includes an editable plan, a completed fictional example, blank and completed JSON records, a closed JSON Schema, a dependency-free validator, mutation tests, and a deterministic ZIP builder. The public pack contains no personal information, raw responses, transcripts, quotes, real-company facts, market-size conclusions, recommendations, priorities, or outcome claims.
Move from a bounded question to reviewable findings
Keep the research frame, collection method, safeguard state, evidence status, and downstream authority visible so a reviewer can challenge a finding without opening a public repository of participant data.
Bound the decision-support question
State the market boundary, geography, evidence period, decision-support question, in-scope work, exclusions, owner, evidence cutoff, next review, and expiry. A research question can inform a later decision without approving that decision or claiming that a market exists at a particular size.
Sources: [market-research-pack], [sba-market-research], [gov-plan-research]
Separate existing-source and direct research
Use authorized existing sources for bounded published or owned evidence and direct methods for questions that require engagement with a specific group. Record why each method fits the question, its limitation, and whether the result is descriptive, exploratory, or incomplete.
Sources: [sba-market-research], [market-research-pack]
Plan groups, methods, recruitment, and access
Name aggregate group labels, a question-specific sample plan, recruitment approach, accessibility plan, method owner, and planned round. Do not copy participant identities or screening responses into the public pack, and do not treat a sample count as proof of representativeness.
Sources: [gov-plan-research], [market-research-pack]
Record safeguard states without certifying them
For direct research, record consent, privacy, retention, and deletion workflow states plus controlled reference IDs. Keep the evidence itself outside the public pack. A validator can require recorded states and reject unsafe content, but it cannot establish informed consent, ethical practice, or legal compliance.
Sources: [gov-research-consent], [gov-research-privacy], [market-research-pack]
Separate observations from interpretations
Write an observation as a bounded record of what an authorized source or aggregate round showed. Write an inference separately and link it to observation evidence IDs. Give every evidence row a date, owner, confidence rationale, limitation, contradiction IDs, and gap IDs.
Sources: [gov-analyse-research], [market-research-pack]
Review findings, gaps, expiry, and handoffs
Link each finding to evidence and keep it in draft while a linked contradiction or gap remains open. Check source freshness, dates, references, and public-safety boundaries with the closed Draft 2020-12 record. Then hand reviewed aggregate evidence to adjacent owners without transferring their authority into this template.
Sources: [market-research-pack], [json-schema-2020-12]
What this market research template owns
Use this pack for one bounded research plan and a public-safe aggregate evidence-to-findings register. Keep raw research and every downstream synthesis, decision, instrument, and campaign with its accountable owner.
Included
- Research control, market boundary, evidence period, decision-support question, objectives, assumptions, methods, group labels, sampling plan, recruitment approach, safeguard states, and review dates
- Authorized fictional sources, aggregate rounds, observation and inference labels, evidence-linked findings, confidence rationales, contradictions, gaps, limitations, change triggers, and expiry
- Editable Markdown, blank and completed fictional JSON, closed Draft 2020-12 schema, dependency-free validator, mutation tests, and deterministic allowlisted archive
Not included
- Names, contact details, participant IDs, screening answers, consent evidence, raw responses, notes, recordings, transcripts, quotes, private links, credentials, or another portable participant-data repository
- Real-company facts, market-size or demand conclusions, vendor matrices or rankings, user personas, journey maps, SWOT, business cases, product roadmap or discovery priority, recommendations, and outcome claims
- Survey instrument, research report, proposal, presentation, buyer segmentation, messaging, campaign, legal or ethical advice, privacy certification, or proof that consent is informed, valid, or lawful
DOWNLOADABLE RESOURCE
Download the market research template pack
Start with the editable plan or blank JSON, inspect the completed Cedar Signal fictional record, and replace every placeholder only with reviewed aggregate evidence and safe references.
Market research template pack
A public-safe fictional research plan and findings register covering objectives, methods, safeguard states, aggregate evidence, observations, inferences, confidence, contradictions, gaps, review, and handoffs.
Format: Markdown, JSON, JSON Schema, validator, and tests in one reproducible ZIP archive
Locally reproduced August 1, 2026. SHA-256: a89da5614537e8453f899069dabae58dd951338b25a9e5f58c5e3c7e69aa7f7b
Included
- Editable research plan and completed fictional Cedar Signal review surface
- Blank and completed fictional JSON records using reserved example hosts
- Closed Draft 2020-12 JSON Schema and dependency-free structural validator
- Mutation tests for dates, references, consent and privacy states, evidence links, contradictions, gaps, unsafe content, ownership boundaries, and deterministic archive bytes
Verification boundary
Validated both fictional records, ran the packaged mutation suite, checked closed shapes and reference parity, copied an exact flat allowlist, fixed file and archive metadata, rebuilt from a clean extraction, and reproduced identical ZIP bytes across time zones.
Three bounded ways to use the research record
The evidence contract stays the same when the question, method mix, and downstream handoff change. These examples describe fictional research shapes, not findings about a real market.
Fictional existing-source and aggregate-round plan
Use when: A team has a bounded operating question that benefits from both authorized existing sources and direct aggregate research.
Use separate method records, reserved source URLs, aggregate round counts, controlled safeguard references, and evidence rows that distinguish observations from later interpretations.
Structure
- Keep source-backed observations separate from aggregate-round observations
- Link an inference to observation evidence IDs instead of presenting it as a collected fact
Watch for: The fictional group counts and sources do not establish representativeness, prevalence, market demand, consent validity, or a recommended workflow.
Sources: [market-research-pack], [sba-market-research], [gov-research-consent]
Fictional secondary-research-first plan
Use when: A team needs to map what current authorized sources can and cannot answer before planning direct research.
Record source scope, retrieval and expiry dates, authorization state, limitations, observations, contradictions, and gaps before choosing whether another method is warranted.
Structure
- Use reserved example.test hosts in the shipped fictional record
- Keep missing or stale evidence as a gap rather than converting it into a negative conclusion
Watch for: An existing-source review cannot infer private customer behavior, certify a source as complete, or replace a separate competitive analysis.
Sources: [sba-market-research], [rfc-2606], [market-research-pack]
Fictional contradiction and gap handoff
Use when: Aggregate sources point in different directions and the evidence is not ready for persona, journey, strategy, business-case, or roadmap synthesis.
Link the contradiction to the affected evidence and finding, open a dated gap with an evidence-needed statement, and keep the finding in draft until the issue is resolved.
Structure
- Do not mark a finding reviewed while a linked contradiction or gap is open
- Pass only reviewed aggregate evidence IDs to the next owner, with limitations intact
Watch for: Resolving a record inconsistency still does not approve a persona, journey, SWOT, investment, priority, survey, report, proposal, presentation, or campaign.
Sources: [gov-analyse-research], [gov-research-privacy], [market-research-pack]
Decide whether the record is safe and reviewable
A polished research summary can still hide personal data, unsupported interpretation, expired evidence, or ownership drift. Stop when the record cannot preserve its public-safe evidence contract.
The proposed public record contains a name, contact detail, participant ID, screening answer, raw response, transcript, quote, private link, or consent evidence.
Choose: Remove it from the pack and route it to an approved controlled research repository with the required access, retention, deletion, and withdrawal process.
Tradeoff: The public record carries less raw detail, but it does not become a portable participant-data archive.
An observation has no authorized source or aggregate round, date, owner, confidence rationale, or limitation.
Choose: Mark the affected finding draft, open an evidence gap, and exclude the unsupported statement from reviewed handoffs.
Tradeoff: The findings register looks less complete, but unattributed memory does not become market evidence.
An interpretation is written as an observation or does not link to the evidence that supports it.
Choose: Relabel it as an inference, add its observation evidence IDs, explain confidence and limitations, and preserve any contradictory evidence.
Tradeoff: The language becomes more conditional, but reviewers can inspect the reasoning instead of accepting an unsupported claim.
The requested output is a market-size conclusion, vendor matrix, persona, journey map, SWOT, business case, priority, survey, report, proposal, presentation, or campaign.
Choose: Keep this record bounded to research planning and aggregate findings, then hand reviewed evidence and limitations to the accountable adjacent owner.
Tradeoff: The template stops before a downstream deliverable, but research collection does not silently absorb decision authority.
Public-safe research pack
Start with the question, methods, evidence, and gaps
Download the fictional plan and findings register, then replace each placeholder only with reviewed aggregate evidence and safe controlled references.
Download the market research packSame-release artifact. Local bytes are verified; public availability is checked only after deployment.
Open the competitive analysis templateUse the adjacent evidence-led comparison owner for alternative-by-criterion research, explicit weights, and comparison review.
What this template cannot prove
A strict record can reveal missing evidence, unsafe content, and unsupported synthesis. It cannot make a research method appropriate or turn a fictional example into a real finding.
- A validator pass checks structure, dates, references, state consistency, reserved hosts, public-safety patterns, and explicit ownership boundaries. It does not review method quality, bias, accessibility, ethics, privacy, law, or representativeness.
- Consent, privacy, retention, and deletion fields are workflow states and controlled references only. They do not prove that consent is informed, voluntary, current, valid, ethical, or lawful.
- The Cedar Signal pack is wholly fictional and contains no participant data, real-company facts, market size, demand estimate, vendor finding, persona, journey, strategy, investment case, priority, recommendation, or outcome evidence.
- This ordinary informational article and its download are AI-credit-ineligible and do not grant signup AI credits. Product pages follow their own current eligibility and plan limits.
Primary sources and verification record
These primary references were checked on 2026-08-01. They support the research-plan, method, consent, privacy, analysis, and structured-record boundaries described here. They did not review this template or the fictional example.
[market-research-pack] Playcode:Market research fictional example
Checked August 1, 2026. Supports: The locally reviewed fictional record, aggregate methods and rounds, safeguard-state references, observation and inference separation, findings, confidence, contradictions, gaps, limits, handoffs, schema, validator, and mutation tests. Public availability remains unverified until deployment.
[sba-market-research] U.S. Small Business Administration:Market research and competitive analysis
Checked August 1, 2026. Supports: Market questions, the distinction between existing-source and direct research, and direct methods such as surveys, questionnaires, focus groups, and in-depth interviews. The page was last updated March 24, 2026.
[gov-plan-research] GOV.UK Service Manual:Plan user research for your service
Checked August 1, 2026. Supports: Defining objectives and research questions, identifying groups, choosing methods, planning recruitment and rounds, updating the plan, and sharing findings.
[gov-analyse-research] GOV.UK Service Manual:Analyse a research session
Checked August 1, 2026. Supports: Recording observations as what was seen or heard before interpretation, grouping observations, writing findings, deciding later actions, and sharing findings.
[gov-research-consent] GOV.UK Service Manual:Getting informed consent for user research
Checked August 1, 2026. Supports: Providing understandable information, recording what participation and data use cover, keeping consent evidence with controlled research data, and honoring withdrawal. Applicable policies and laws still require expert review.
[gov-research-privacy] GOV.UK Service Manual:Managing user research data and participant privacy
Checked August 1, 2026. Supports: Collecting only needed data, agreeing retention, securing and organizing research data, deleting it when no longer needed, and removing personal data from public outputs.
[json-schema-2020-12] JSON Schema:JSON Schema Draft 2020-12
Checked August 1, 2026. Supports: The schema dialect used to describe the closed structured record shape. The page does not support claims about method quality or consent.
[rfc-2606] RFC Editor:Reserved Top Level DNS Names
Checked August 1, 2026. Supports: Reserved example names used by the fictional source records in the downloadable pack.
Market research template FAQ
What is the difference between market research and competitive analysis?
This market research owner plans a bounded question and preserves aggregate sources, methods, evidence, findings, contradictions, gaps, and limitations. Competitive analysis owns the separate alternative-by-criterion evidence ledger and any explicit comparison method. Link reviewed evidence rather than copying one record into the other.
Can this template store interview notes or survey responses?
No. Keep names, contact details, participant IDs, screening answers, raw responses, notes, recordings, transcripts, quotes, private links, and consent evidence in an approved controlled system. This pack stores aggregate round counts, safe references, and reviewed aggregate observations only.
Does a recorded consent state prove that consent is valid?
No. The field records a workflow state and controlled reference only. It does not verify what a participant understood, whether participation was voluntary, whether withdrawal can be honored, or whether the process meets the policies and laws that apply to the real research.
When can a finding be marked reviewed?
Only after its evidence references resolve, observation and inference labels are correct, dates and source freshness pass, confidence and limitations are stated, and every linked contradiction or gap is resolved. A reviewed finding is still bounded evidence, not a recommendation or outcome claim.
Does this template include a market research report or survey questionnaire?
No. It owns the research plan and public-safe findings register. A survey instrument, questionnaire, research report, proposal, presentation, persona, journey map, SWOT, business case, product priority, and buyer campaign remain separate deliverables with separate accountable owners.
Does this article grant Playcode AI signup credits?
No. This is an ordinary informational article with a downloadable resource, so it is AI-credit-ineligible and does not grant signup AI credits. Product entry eligibility and current plan limits are separate.
Prototype after evidence review
Turn a bounded research question into something testable
After the research owner reviews the evidence and approves a bounded question, use Playcode to build a working prototype while findings, participant safeguards, decisions, and priority remain with their accountable owners.
Explore prototyping with PlaycodeThis informational article is AI-credit-ineligible and does not grant signup AI credits. Product entry eligibility and plan limits are separate.