Skip to main content
The way you build a survey decides what you can report on later. A free-text question such as “How does the shelf look?” gives you thousands of answers you can’t chart. A picklist question such as “Is the product on shelf?” with Yes and No gives you an on-shelf availability percentage by store, rep, and week. Use this page to design questions, surveys, and task types for the KPIs your managers track.

​
User Permissions Needed

​
How Survey Answers Are Stored

Each answer a rep gives is a Task Survey Answer record, linked to its Task Survey, the task, the visit, and the account. These fields matter most for reports:
Answer is a long text area field, even for number questions. Salesforce reports can’t group, sum, or average long text area fields. To chart numeric answers, such as facings or shelf prices, add a number field to Task Survey Answer and fill it with a flow, as described in Make Answers Reportable.

​
Choose the Right Question Type

For how to create each type, see Build Surveys.

​
Keep Questions Consistent

  • Reuse question records. Create a question once, such as “Product on shelf?”, and add the same question to every survey that asks it. Reports then group all answers by Question Definition, across surveys and months.
  • Keep picklist values identical. Out of stock and OOS are different answers in a report. Agree on one set of values and reuse it.
  • Don’t edit live questions. To change a question that reps already answer, create a new question and survey, and switch the task type. See Change a Survey That Reps Already Use.
  • Use custom question numbers if you need a stable code for each question in exports. See Survey Settings.

​
Design Task Types per KPI Area

Create one task type per KPI area, such as “Availability check”, “Share of shelf count”, and “Promotion audit”, each with its own default survey. Reports can then filter on Task Type, and task completion becomes a KPI in its own right.
  • Products: When you build a visit template, you can set a product on each task. Tasks keep that FieldKo Product, so you can report availability or facings by product. See Visit Templates.
  • Promotions: Plan promotion audits as a field campaign. Tasks created by a campaign keep its Field Campaign, so you can report compliance for that promotion only.
  • Incomplete tasks: Fill in Possible Reasons for incompletion on the task type, such as Store closed,No access,Product delisted, so Can’t Do reasons are reportable too.

​
Make Answers Reportable

To report on numeric answers, store them in a number field:
  1. On Task Survey Answer, create a Number field, such as Numeric Answer, with 2 decimal places.
  2. Create a record-triggered flow on Task Survey Answer that runs when a record is created or updated and Type is Number, Currency, or Percentage. Set Numeric Answer to the Answer converted to a number.
  3. Optional: For picklist questions, also copy Answer into a Text (255) field so you can group and filter by it.
Test the flow in a sandbox with a rep completing a survey in the app. See Flow Recipes for Field Teams.

​
Scores

To score a survey, set Calculate Score to SUM on the survey, and Out of Score and Options Weightage on each question. See Scoring. Before you build a perfect store score on these fields, complete a test survey in the FieldKo Atlas app, sync, and check that Score Obtained is filled in on the Task Survey and its answers for your package and app version. If it isn’t, contact support@fieldko.com before you rely on scores.
The Attachment checkbox on Task Survey Answer shows that the question asks for a photo, not that the rep took one. To review photo evidence, add Picture to the report.

​
Map KPIs to Question Design and Reports

​
See Also

Last modified on October 20, 2026