# 360 Feedback: review cycles on your shared people records

> Run feedback cycles across managers, peers and reports, with the history landing on the person record rather than in a survey tool nobody can join back to anything.

Source: https://www.cordango.com/capabilities/360-feedback/
Language: en

[Home](https://www.cordango.com/) [Capabilities](https://www.cordango.com/capabilities/) 360 Feedback

PEOPLE

# 360 Feedback

Feedback cycles that write to the person, not to a survey tool. Available as a ready-to-use Cordango capability.

[See Cordango in action →](https://www.cordango.com/contact/) [How it runs →](https://www.cordango.com/capabilities/360-feedback/#how)

360 Feedback People

360

Feedback cycles that write to the person, not to a survey tool

## What it builds on.

The awkward part of feedback is never the form. It is knowing who should be asked about whom, and that is a question about your org structure. Because the cycle reads real teams and reporting lines, the participant list builds itself and stays right when somebody moves.

The results land on the person record, under field-level permissions. Somebody's review history is visible to the people who should see it and to nobody else, without a separate tool having its own idea of who is a manager.

-   USES People records, teams and reporting lines
-   USES Field-level permissions, so feedback is not readable sideways
-   USES Activity history on the person

[The People foundation →](https://www.cordango.com/people/)

Available from the start 360 Feedback

-   CYCLE Feedback rounds with a defined window
-   WHO Participants drawn from real teams and reporting lines
-   FORM The questions you actually ask
-   TRAIL Review history that stays on the person

## How it actually runs.

1 

#### A cycle opens

Pick the window and who is in scope. A team, a level, or the whole company.

2 

#### Participants are selected

Manager, peers and reports come from the structure already in the platform, so nobody assembles a list by hand.

3 

#### Responses come in

Each participant answers on the person, under permissions that keep responses where they belong.

4 

#### It stays on the record

The cycle closes and the history remains attached to the person, next to their role, team and assignments.

## What you can change.

Use the standard version where it fits. Change only the parts where your company is genuinely different.

DATA 

### The questions

Competencies, open text, ratings, or a mix. Ask what your company actually asks.

RULES 

### Who is asked about whom

Peers only, upward only, full circle. Set the rule and let the structure fill it in.

STATES 

### Cycle stages

Draft, open, closed, shared. Add a calibration step if your process has one.

VIEW 

### Who sees results

The person, their manager, HR, or a narrower set. Field-level permissions make that precise.

MORE

## What it works with.

-   [**Skills & Certifications** What people can do, and which certificates are about to lapse](https://www.cordango.com/capabilities/skills/)
-   [**PTO & Absence** Absence requests and approvals on the people you already have](https://www.cordango.com/capabilities/pto/)

NEXT

## One foundation. Everything on top of it.

360 Feedback does not build its own directory of who reports to whom. Cycles, participants and review history attach to the People records and reporting lines the platform already holds.

[See Cordango in action →](https://www.cordango.com/contact/) [All capabilities →](https://www.cordango.com/capabilities/)