Forms — redesign functional guide

Find a redesigned form

Open Performance → Forms [new]. The Forms page lists each form’s name, question count, creator, creation date and status.

Use name, creator, publication and read-only filters to locate a form. Read only filters campaign usage; it does not change editing permissions.

View full size

Search and inspect forms

1. Open Performance → Forms [new].
2. Enter a name or creator criterion, and use publication or read-only filters when needed.
3. Review the matching form’s identity and status. Clear the relevant filters to broaden the list.

The controls below refine the displayed list; they do not edit a form.

Control	Choices / initial state / clearing	Result and practical use
Search by name	Text; blank initially. Clear to remove.	Search for a distinctive part of the form title.
Created by	Text; blank initially. Clear to remove.	Use the creator information available to you to narrow the list.
All forms	Single selection: All forms, Draft, Published. Initially all.	Restricts publication status. Select All forms to clear.
Read only	Unrestricted, yes or no through the shared boolean filter. Initially unrestricted.	Narrows by campaign usage. It does not change permissions, publish a form or lock it manually.
Name / Created at	Sortable fields when available.	Sort the matching forms; this does not change their content.
Pagination	Page numbers and Previous/Next.	Use the page controls to browse additional results.
Row selection / status menu / create	Conditional controls.	Actions can change form data; check the form's usage and rights before using them. See configuration for safe setup.

Search criteria are temporary; publication, copying and saving are persistent actions.

Understand the form before assigning it

1. Read the selected form’s sections, question wording, required fields and intended audience.
2. Check the questionnaire’s content language separately from the interface language.
3. Review any generated content before saving or publishing, then follow the campaign’s assignment procedure.

The nextgen editor lets an administrator add sections and typed questions, set their audience and required status, and review the form overview. The form's content language is independent of the interface language. Save the form before adding translations; review every title, instruction, evaluator wording and choice in each locale. Preview the language variants before publishing. Publication makes the form selectable; it does not assign employees or start a campaign.

Generated text needs review before saving or publication. Setup details are in configuration.

Complete the whole questionnaire

Employees and evaluators complete their own assigned contribution in a nextgen interview. They do not answer from the form library. The campaign administrator selects the published form, assigns participants and evaluators, and sets the preparation sequence, dates, answer visibility and signature rules. The Interviews guide describes campaign access and roles.

Employee: from invitation to completed review

1. In the personal workspace, open Interview or Profile → Interviews, find the assigned review, and choose See. Confirm the campaign, deadline and that the displayed participant is you.
2. Read the introduction and choose the start action when ready. Starting changes the participant's workflow state; merely opening the review does not.
3. Work through the section steps shown in the review. Read each section's instructions, answer questions visible to you, and use the available navigation to review every section. Conditional follow-up questions appear when the triggering choice is selected. Only questions that apply to your role and current form path are in scope.
4. Answers are saved as you work for supported question controls. If you leave before finishing, use the available Save and leave action; return to the same review to continue. A saved answer does not mean preparation is finished.
5. Review every required question. If validation identifies missing answers, return to the flagged section/question, provide or correct the answer, and validate again. Conditional questions are checked when their branch is active. Then choose the action to finish preparation.
6. During the interview phase, contribute to the discussion and any questions enabled for that phase. See other participants' answers only when both the question audience and the campaign's phase visibility/sharing settings allow it. Add a final comment if the form offers one.
7. Review the completed content and use the offered submit/signature action. If a signature is required, follow the signature step; refusal is available only when the campaign permits it. If no signature is required, submission can complete without an affirmative signature. Check the review status and any PDF/report separately.

Evaluator: complete their contribution

1. Open the assigned employee review from the manager workspace or assigned review list. Confirm the employee, campaign and evaluator role; a main or additional evaluator may have different assignment rights.
2. Follow the phase order configured for the campaign. In parallel preparation, employee and evaluator prepare independently; in evaluator-only or serialized setups, follow the enabled step and wait for the preceding contribution when required.
3. Start the evaluator preparation when available. Complete the sections and questions shown to the evaluator, including evaluator-specific wording where configured. Do not fill employee-only questions on the employee's behalf.
4. Save and leave if needed. Before finishing, validate required evaluator answers and correct any flagged items, then finish preparation using the displayed action.
5. At interview day, review only answers currently shared with the evaluator, discuss the responses with the employee, and complete interview-day questions, performance assessment or final comment when configured.
6. Submit or sign when offered. Evaluator refusal is not available in the checked nextgen workflow. Recheck participant status and generated report/PDF as separate completion outputs.

What “complete” means

Stage	Expected result	It does not mean
Answer saved	The answer is stored for that participant and question. Text entry can be saved automatically; other controls save through their answer operation.	The whole section or preparation is complete.
Preparation finished	Required answers pass validation and the participant moves to the next configured phase.	The other participant has finished or signed.
Answers shared	The participant's answers are revealed under the sharing action and campaign rules.	Every answer is visible regardless of question audience or phase.
Interview submitted	The participant's contribution is submitted; status reflects the workflow.	An affirmative signature exists when signature is optional.
Signed / report generated	Signature state and output status are recorded separately.	Campaign status alone proves both outputs exist.

Question families and options are described below. Exact steps vary with preparation mode, role, form sections, conditional branches, feature availability and campaign settings. If your screen differs, follow the actions shown for that review and contact the campaign administrator about assignment or phase configuration.

Question families and options

Available question types depend on the form generation and its configuration. A form may use only a subset of these families.

Question family	What the participant does	Important option or dependency
Message / section	Reads explanatory content and navigates groups.	Legacy messages/section headings do not themselves store an answer.
Text	Enters a short or longer response.	Nextgen supports configured length and text rules; legacy simple/open questions are different types. No universal text limit is assumed.
Single / multiple choice	Selects one or several configured answers.	The form sets choices and permitted counts. An empty answer is not automatically a valid “not applicable”.
Rating / scale	Selects a value within the configured range.	Scale labels, bounds and display depend on the form; do not transfer legacy rating conventions to nextgen.
Numeric / date	Enters the requested value.	Nextgen schema includes these families; date bounds can be configured.
List / referential	Selects from a configured source.	Nextgen options can come from company referentials; language/data availability affects choices.
Skills	Assesses configured skills.	Skill selection, levels and permission to add skills depend on form setup.
Past / future objectives	See Objectives — Redesign and its legacy counterpart.	Use the guide for the campaign generation.
Development	Contributes to development/training content.	Available catalog, opinion choices and specialist settings apply. This is not automatic course enrollment.

A completed form and a shared form are different. The availability of another participant's answers must be determined from the current interview, not from the fact that both participants see the same question title.

Legacy versus redesign

Legacy questionnaires and redesigned forms use separate catalogs and question models. The two catalogs coexist; seeing both menu items does not mean that forms share saved content, convert automatically or have the same permissions. People Review features, such as its collective matrix, are not automatically available in an interview form.

Development and rollout plan

The following sequence is a practical implementation plan for completing and validating the redesigned questionnaire experience. It is a recommendation based on the verified form, campaign and review workflow; it is not a claim that every item is already deployed.

1. Confirm scope and decisions. Agree on employee/evaluator roles, preparation mode, phase dates, answer sharing, required signature/refusal, supported question families, languages and whether the workflow is interview-only or includes preparation and interview day.
2. Complete form authoring. Create sections and questions, set required state, audience, conditional branches and specialist dependencies. Translate and preview all intended content languages. Save and publish the reviewed form.
3. Configure and populate a campaign. Select the published nextgen form, set phase/timeline and visibility/signature rules, assign employees and evaluators, and check access/ownership. Review the resolved participant list before activation.
4. Validate end-to-end with test personas. Run at least one employee and one evaluator through start, autosave/save-and-leave, conditional branches, required-answer errors, finish preparation, interview-day answers, visibility, final comment and submit/signature. Cover each preparation mode and each intended language, plus representative specialized question types.
5. Resolve gaps and prepare support. Fix form content or campaign settings where the test path is confusing or blocked. Document expected role-specific steps, escalation contact, deadline and report/PDF follow-up. Confirm notification and output behavior in the target environment; source code alone does not establish delivery.
6. Launch and monitor. Activate the campaign when ready. Track preparation, evaluator completion, sharing, signatures and output generation as separate measures. Triage validation blocks, wrong assignments and unavailable translations before changing a live form; use a new form version/campaign where historical answers must remain stable.

Acceptance checklist

• Each assigned employee and evaluator can find the intended review and sees the correct role-specific questions.
• Required and conditional questions validate correctly, and the participant can find and fix omissions.
• Answers persist when navigating sections or leaving and reopening the review.
• Preparation mode and interview-day transition match the campaign schedule.
• Answer visibility matches the combination of question audience, phase settings and sharing state.
• Submit, signature/refusal and report/PDF states are understandable and independently verifiable.
• Intended locales display translated titles, instructions, evaluator wording and choice labels.
• Administrator can identify incomplete participants and route common access or validation issues.

FAQ and troubleshooting

Issue	Check
Form missing from a campaign picker	Check the form generation, publication status, your access and the language available to the campaign.
Form is read only	In nextgen, running, done and archived campaign use counts; draft/not-started use does not. Duplicate for a new version when appropriate.
Same question appears differently for the evaluator	Audience, evaluator-specific wording and answer-sharing settings.
Labels remain French in an English interface	Authored content and its translations are separate from UI language.
Required answer rejected	Expected type, selected count, bounds and configured validation rules. Ask the administrator if instructions conflict.
Cannot finish preparation	Check the flagged sections for unanswered required questions, including follow-up questions shown by selected choices; correct the answer and validate again.
Cannot see employee/evaluator contribution	Check campaign preparation mode, phase visibility, question audience and whether the other participant has shared answers.
Review is saved but still in progress	Saving answers and finishing preparation are separate actions. Return to the review and complete the finish/validation step.
Review is complete but no signature or PDF appears	Check signature configuration, individual participant state and output status separately from campaign status.

Implementation differences

Legacy questionnaires and redesigned forms use different catalogs and question models. See the technical guide for implementation details. Available actions depend on the form, campaign and your permissions.