Importance Scale Survey Template

In plain language: States what the survey is measuring, who commissioned it, and how the results will be used — establishing the context for respondents and the legal basis for data collection.

Common mistake: Describing the purpose so broadly that respondents cannot assess what they are consenting to. Vague scope statements undermine informed consent and can expose the organization to data-protection challenges.

In plain language: Captures identifying information — name, role, department, or demographic category — to the extent needed to segment and analyze results, while specifying what is optional versus required.

Common mistake: Collecting more identifying information than the analysis requires. Unnecessary personal data increases GDPR and PIPEDA compliance exposure and can deter honest responses.

In plain language: Notifies respondents of their rights — including the right to withdraw, remain anonymous, or request deletion of their data — and obtains explicit acknowledgment before responses are recorded.

Common mistake: Burying the consent statement in small print at the end of the survey. Consent obtained after responses are recorded may not be valid under GDPR Article 7 or equivalent frameworks.

In plain language: The core section listing each attribute, feature, or criterion to be rated, with a clearly labeled scale — e.g., 1 = Not Important, 5 = Extremely Important — applied consistently across all items.

Common mistake: Using an even-numbered scale (e.g., 1–4) to force a directional response. This increases response bias and reduces data validity, particularly when genuine neutrality is a valid stakeholder position.

In plain language: Explains how to complete the rating matrix, how long the survey is expected to take, the deadline for submission, and the method of return or submission.

Common mistake: Omitting a deadline for submission. Without a deadline, response collection drags on indefinitely, making it difficult to aggregate results or meet decision-making timelines.

In plain language: Provides space for respondents to elaborate on their ratings, flag missing attributes, or provide qualitative context that the scale alone cannot capture.

Common mistake: Making the comments field mandatory. Forced open-ended responses produce low-quality, perfunctory answers and reduce overall completion rates.

In plain language: Specifies whether responses are confidential or anonymous, who within the organization will see individual-level data, and any restrictions on respondents sharing the survey contents externally.

Common mistake: Claiming responses are anonymous when individual-level data is actually accessible to line managers. If management can see individual responses, the survey is confidential but not anonymous — conflating the two undermines trust and can invalidate results.

In plain language: States how long completed survey data will be retained, in what format, and the process for requesting deletion — a requirement under GDPR, PIPEDA, and similar frameworks.

Common mistake: No stated retention period at all. Indefinite retention of personal data collected through surveys is non-compliant under GDPR Article 5(1)(e) and equivalent provisions in Canadian and UK law.

In plain language: A signature block confirming the respondent has read the instructions and consent disclosure, completed the survey honestly, and authorizes the stated use of their responses.

Common mistake: Treating the signature block as optional for internal surveys. Without a signed acknowledgment, the organization has no documented evidence of informed consent if a privacy complaint or employment dispute arises.

In plain language: A field for the survey administrator to certify that the survey was conducted in accordance with the stated purpose, that no responses were altered, and that data was securely collected.

Common mistake: Omitting administrator certification entirely. Without it, there is no chain-of-custody record for the data — which matters if survey results are used in employment decisions, vendor selections, or regulatory submissions.

An importance scale survey is a structured questionnaire that asks respondents to rate a set of attributes, features, or criteria on a numeric scale — typically 1 to 5 or 1 to 10 — to determine what matters most to a specific population. Businesses use importance scale surveys for product prioritization, employee engagement analysis, vendor evaluation, and compliance documentation. The resulting data produces ranked, quantifiable evidence of stakeholder priorities that can inform decisions and satisfy audit requirements.

Use an importance scale survey when you need to rank competing priorities rather than simply collect open-ended opinions. If you have a defined list of attributes — product features, benefit options, supplier criteria — and need to know which matter most to stakeholders, a scaled rating matrix produces actionable ranked data. A general feedback form is appropriate when you are still discovering what attributes matter; a scale survey is appropriate when you already know what to measure and need to quantify relative importance.

For most internal business purposes, a signature is not strictly required to make survey results usable. However, a signed respondent acknowledgment is strongly recommended when: survey results will inform employment decisions, the survey collects personal data subject to GDPR or PIPEDA, results will be used in regulatory submissions, or the survey is part of a formal contractual process such as vendor evaluation. A signature creates a documented record of informed consent that protects both the organization and the respondent.

A 5-point scale is generally sufficient for most business importance surveys and produces cleaner, more consistent results because respondents can reliably distinguish five levels of importance. A 10-point scale is more appropriate when fine-grained discrimination between attributes is analytically important — for example, in conjoint analysis or advanced market research. Avoid even-numbered scales (4 or 6 points) for importance measurement because they force a directional response and suppress genuine neutral positions.

To comply with GDPR when running an importance scale survey, confirm the following: the legal basis for processing personal data is documented (typically consent or legitimate interest); the consent disclosure appears before any data is collected; only data strictly necessary for the analysis is requested; the retention period is defined and enforced; respondents are informed of their right to access, correct, or delete their data; and the data controller is identified by name and contact details. For surveys distributed to EU residents from outside the EU, these requirements apply regardless of where the organization is based.

Yes, provided it was administered correctly. Survey results used in employment decisions — such as compensation benchmarking, benefit restructuring, or performance criterion weighting — can be challenged by employees if the survey was not conducted with documented consent, if the methodology was inconsistent, or if individual responses were accessible to direct managers when anonymity was promised. Maintaining signed consent records, an administrator certification, and a clear data-handling policy significantly strengthens the evidentiary value of the results.

A Likert scale measures agreement with a statement — typically on a scale from 'Strongly Disagree' to 'Strongly Agree.' An importance scale measures how much a respondent values a specific attribute — typically from 'Not Important' to 'Extremely Important.' Both are ordinal scales and share similar design principles, but they answer different questions. Use a Likert scale when you want to gauge attitudes or satisfaction; use an importance scale when you want to rank priorities for resource allocation or feature planning.

Between 8 and 20 attributes is the practical range for most business importance surveys. Fewer than 8 attributes rarely justifies the survey format over a direct conversation. More than 20 attributes produces respondent fatigue, which increases satisficing — selecting the same rating for all items without genuinely evaluating each — and reduces data reliability. If you have more than 20 candidate attributes, consider running a preliminary open-ended phase to narrow the list before distributing the scaled survey.

For internal HR or employee surveys, an HR director or a neutral third-party administrator reduces social desirability bias. For customer or market research surveys, a product manager, researcher, or external agency can administer without conflict of interest. For compliance or regulatory surveys, a compliance officer or external auditor should administer and certify the results. In all cases, the administrator should complete the certification block and be available to respond to respondent questions about data use.