Request feedback from a colleague
What this achieves
Section titled “What this achieves”A feedback request asks one named colleague to write feedback, rather than waiting for them to volunteer it. You say what it is about, why you are asking, and by when.
Required role: Any signed-in user.
- Go to Feedback & 1:1s → Feedback Requests.
- Select Request feedback.
- Under Feedback about, choose Yourself or Someone else.
- If you chose Someone else, pick the Target.
- Pick the Reviewer — the colleague you are asking.
- Write the Context, saying why you are asking.
- Add Specific questions if you want the answer to cover particular ground, using Add question for each one.
- Set a Due date.
- Select Send request.
Options on this screen
Section titled “Options on this screen”| Option | Description |
|---|---|
| Feedback about | Yourself, or Someone else — a colleague you want feedback about. |
| Target | The person the feedback is about, when it is not you. |
| Reviewer | The colleague you are asking to write it. |
| Context | Why you are asking. This is what the reviewer reads first. |
| Specific questions | Questions the reviewer answers alongside their written response. Optional. |
| Due date | When you would like the answer. |
Asking about somebody else
Section titled “Asking about somebody else”Requesting feedback about a colleague is a different act from requesting it about yourself, and both are available on this screen. The person you name as the Target is not the person you are writing to, and the request goes to the reviewer.
Example: Olivia Bennett asking Priya Raman for feedback about James Whitfield is a request about a third person. James is the target; Priya is the reviewer.
Say this out loud rather than gathering opinions about somebody quietly. A request is a small act; the pattern it forms is not.
Context earns the answer
Section titled “Context earns the answer”An empty context produces a vague answer. The reviewer is being asked to spend time and take a small social risk, and the context is what tells them which slice of work you actually want read.
Example: “Feedback for my mid-year review” gets a paragraph of generalities. “How did the migration handover go from your side, particularly the two weeks after the cutover?” gets something a review can use.
Tracking what you asked for
Section titled “Tracking what you asked for”The Sent tab shows the requests you have raised and where each one stands. The For me tab shows requests waiting on you.
What you cannot do afterwards
Section titled “What you cannot do afterwards”There is no way to withdraw or cancel a request once it has been sent. If you sent it in error, tell the reviewer directly — the interface has no route for that.
What happens next
Section titled “What happens next”The reviewer sees the request on their For me tab and on their My feedback page, where they can respond or decline. If they decline, you are notified; the interface tells them their reason is not kept, so a reason they want you to have has to reach you another way. A response is stored as continuous feedback and appears in your Received list.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved