Log inGet in touch

360 Feedback · Scoping intake

Scope your 360 Feedback implementation.

Answer five questions about your rollout. You see an indicative effort size and a draft project plan straight away, and get a PDF of your scope to share internally. A copy goes to our 360 team, so your first call starts from your numbers, not from zero. Takes about three minutes.

ReferenceAbout you

Scope information only. Please do not enter personal or sensitive data about employees, participants or raters.

So our 360 team can come back to you about this intake.

A best guess is fine. The draft plan is scheduled from this date.

Scope driver 1Population in scope

The population this implementation covers.

Implementation type *
Employees in scope *
employees

Headcount covered by the pilot, not the eventual full population.

Total employees in your Workday tenant *
employees

The whole population in the tenant, not just the pilot group.

Scope driver 2Questionnaire scope

Configuration and testing scale with the number of questions, so tell us whether your question figure is per questionnaire or the total across all of them.

Number of questionnaires *
Number of questions *
That question figure is

20 items to configure: 1 questionnaire × 20 questions.

Scope driver 3Translations

Translations add real work and can lengthen the timeline, so it pays to agree the language scope upfront.

Translations required *
Scope driver 4AI summaries (LLM connection)

Whether AI-generated feedback summaries are in scope, using a language model your organisation controls. Adds prompt and rubric design, a tenant-side connection, and an output review before go-live.

LLM connection required *
Scope driver 5Service model

How 360 feedback gets started. Self service means employees and managers raise and run their own 360 requests. Admin service means administrators run 360 campaigns or mass launches.

Service model *