Ir al contenido
Funcionalidades Precios Documentación Contacto Iniciar sesión Empezar
Idioma

Respuestas

The Records tab, the states a response can be in, reviewing and approving, setting a response aside, and what cannot be changed afterwards.

Every answer a form receives lands in one place: the form's Records tab. Whether the response came from a colleague in the office, a field worker on a phone or a stranger following a public link, it appears in the same list.

The Records tab

The tab lists one row per response: the person's name and gender, how the response arrived, when it was submitted, whether it is lynked to a record in your register, its state and an Actions menu. Above the list, a chip for each state shows how many responses are in it, and choosing a chip narrows the list to that state.

Debajo, una segunda tabla enumera las personas inscritas que aún no han respondido, con su Nombre, Teléfono y Acciones, de modo que para cubrir las ausencias no hace falta comparar dos listas a mano.

Encima de ambas tablas, la página hace los recuentos por usted: cuántas personas están inscritas, cuántas han respondido, cuántas siguen pendientes y la tasa de finalización resultante.

Captura de pantalla: la página de respuestas, con los recuentos de resumen, la lista de respuestas y la tabla de personas que aún no han respondido.
There is no search box on this tab. Narrow the list by state, or take one of the exports to slice the responses any other way.

The states a response can be in

Only responses that were submitted and have not been set aside are counted, in every figure the platform shows and in the exports. The states are:

  • Draft: started and not yet submitted.
  • Incomplete: it reached the server missing a required answer, and its collector can finish it.
  • Needs resolution: it reached the server, but a rule its collector cannot change held it back, for example someone had already answered for that person on a form that takes one response each. It is kept, and someone who may resolve held responses decides whether it is accepted or set aside.
  • Awaiting review: submitted and counted, and no reviewer has approved it yet.
  • Approved: submitted, counted and signed off.
  • Set aside: kept and not counted.
  • Returned to data collector: sent back to the person who collected it.

A response started while the form was still a draft is a test response. It carries a Test badge, counts nowhere, and is discarded when the form is published.

Una respuesta completa

Open a response and you see it laid out the way the form is: each section under its heading, notes shown as notes, and each entry of a repeating section numbered in its place. An answer to a question that has since been removed from the form is kept and shown at the end, marked as retired. Where the form is scored, the computed figures are shown with it, and where the form is a post test, the comparison with that person's pre test is shown too.

Reviewing and approving

Verificar las respuestas es una tarea distinta de recopilarlas, y requiere un permiso distinto: Revisión de datos de formularios. Quien puede cumplimentar formularios no obtiene automáticamente la facultad de validarlos.

A reviewer can do two things with a single response:

  • Aprobar la respuesta, lo que registra quién la aprobó y cuándo.
  • Marcarla con una nota que señale la pregunta concreta que parece incorrecta, para que la persona que haga el seguimiento sepa dónde buscar.

To approve several at once, tick them on the Records tab and choose Approve from the actions. The next page lists every response you ticked and says, for each one, whether it will change and, if not, why not. Nothing changes until you confirm, and then every listed change is made or none is. Approving more than one at a time must also be allowed in the form's settings.

Setting aside, and what cannot be changed

Una respuesta que ya se ha enviado no puede editarse. La revisión modifica el estado de revisión y añade notas junto a la respuesta; nunca reescribe lo que la persona respondió realmente.

A real response is never deleted. When one should not count, for example a duplicate or an interview that went wrong, set it aside. It stays on the Records tab under Set aside, leaves every count and every export unless you ask for it, and remembers the state it was in, so Restore puts it back exactly there. Setting aside and restoring are open to whoever may resolve held responses on the form, and to the form's creator.

Only test responses can be deleted. Deleting a whole form still deletes its questions and all of its responses together, so treat that button with the care it implies.

That is why flagging and setting aside exist. When an answer is wrong, the record of what was actually submitted stays where it is, and the flag beside it, or the set aside state, says what to make of it.

Respuestas duplicadas

Que se acepte una segunda respuesta de la misma persona depende de la política de duplicados definida en el formulario: permitir, advertir o bloquear. En una respuesta cumplimentada por el personal, la comprobación se hace con las respuestas completadas anteriormente por esa persona, que es el caso fiable. En el caso de un visitante anónimo que accede mediante un enlace público, lo único que se puede comparar es su sesión del navegador.

Your workspace activity log records the shape of what happened without recording what was said. Submitting, approving, flagging, setting aside and restoring a response, and deleting a form, are all written to it. The submission entry deliberately notes only the kind of respondent and how the form was filled in, never the answers and never the respondent's name.