PART OF NRD PLATFORM · FOR EVERY PERSON ON YOUR TEAM

Know where you stand.
Before review day.

Clear expectations. Feedback while it can still help. A next step both people understand—and someone owns.

30 days free · No card required · From $15/month for a team
TRY THE IDEA BEFORE THE TOOL

One conversation.
Four reasons to care.

Explore an illustrative example from your perspective. No account needed.

Your perspective

Know whether the conversations are happening.

See participation, shared expectations, and overdue manager responses. Start with one team and build a useful habit across the company.

The participation overview does not grant access to private review text or turn feedback into an employee leaderboard.

Spend your attention on the conversation.

Start with a few expectations, respond to a short check-in, and give a concrete next step. Shared history is there when it is time for a review.

Concerns include your support and a follow-up date. Your own commitments stay visible alongside the employee’s.

Give the process consistency people can trust.

Manage the directory, reporting relationships, and review rhythm. See participation within your administrative scope and give content access only where it belongs.

Drafts are private. Published corrections keep the original history. Acknowledgement records receipt, not agreement.

Your perspective belongs in the record.

See what is expected, share progress or a blocker, and ask for the support you need. Read feedback, ask for clarity, or record disagreement in your own words.

You can see who can read your conversation. Your manager’s promised support becomes a next step too.

Example team
THE AGREED EXPECTATION

Own the outcome through validation and handoff.

When work is blocked, share the blocker, its impact, and a proposed next step by your next working day.

MANAGER FEEDBACK

Tuesday’s migration was ready for review, but the handoff did not name the reviewer or the acceptance check. The next owner was unclear.

First shared hereThis concern is being communicated now. Relay keeps that visible.
THE OTHER PERSPECTIVE

I was waiting for team approval before moving it. I need clarity on who signs off and which work comes first.

Asked for clarity · receiving feedback is not agreeing with it
THE NEXT STEP, FOR BOTH PEOPLE
Contributor

Name the reviewer and acceptance check in the next handoff.

Manager

Confirm the decision owner and priority before Thursday.

THE AGREED EXPECTATION

Leave the next person ready to help the customer.

Every customer handoff includes the next owner, the promised date, and the open question.

MANAGER FEEDBACK

Tuesday’s renewal handoff had the customer notes, but no next owner or promised response date. The follow-up waited a day.

First shared hereThis concern is being communicated now. Relay keeps that visible.
THE OTHER PERSPECTIVE

I thought the account team was taking over. I need a clear owner when a renewal also needs technical support.

Asked for clarity · receiving feedback is not agreeing with it
THE NEXT STEP, FOR BOTH PEOPLE
Contributor

Include the next owner and customer response date in the next two handoffs.

Manager

Agree the ownership rule with the account team before Thursday.

Illustrative sample, not customer data. In Relay, the manager writes the feedback and the recipient chooses how to respond.

01 / MAKE IT CLEAR

Start with what good looks like.

Agree three to five observable expectations. Use a practical starting point for sales, support, operations, engineering, or management.

02 / MAKE IT REGULAR

Keep the update small.

What moved forward? Where is help needed? The manager responds against shared expectations. Weekly, fortnightly, or every four weeks.

03 / MAKE IT USEFUL

Carry the conversation forward.

Concerns need an example, a change to try, manager support, and a follow-up date. Reviews draw on shared history, with space for both perspectives.

ENGINEERING CONTEXT. COMPANY-WIDE USE.

The work has context.
So should the feedback.

For developers, attach a pull request, a Sight observation, or an agreed Compass priority with the excerpt you choose to share. For every other role, use the same clear expectations and conversation.

Relay works independently. It does not automatically import private Sight or Compass records, or turn code activity into an employee rating.

TRUST IS PART OF THE WORKFLOW

A record people
can understand.

Your draft stays yours.

Published conversations are visible to the recipient, their current primary management chain, and explicitly authorized People Ops readers. Directory administration and content access are separate.

Receipt and agreement stay separate.

Recipients can acknowledge receipt, ask for clarity, or record disagreement. Corrections publish a new version; the original stays in the history.

AI helps when you ask.

Optional writing help can clarify wording or draft a recap from selected shared records. People choose assessments and publish. Core workflows work without AI.

START WITH ONE TEAM

$3 per active recipient / month

$15 monthly minimum on its own. Reviewer-only managers and administrators are free. Try it for 30 days without a card.

Start your first team →

Already using Sight? Your funded developer capacity includes matching Relay recipient capacity, assignable to any role. Additional recipients are $3 each.

Will this work without developers, Sight, or Compass?

Yes. Relay has its own people directory, reporting relationships, review rhythm, and subscription. No repository connection is needed.

Does everyone need to join at once?

No. Add a small team, invite the manager and recipients, and activate recipients when both sides have accepted. CSV imports can be previewed; importing does not send invitations or activate recipients.

Can we use our existing company sign-in?

Relay supports email and password, Google, Microsoft, and configured enterprise SAML or OIDC. Connecting a provider to an existing account requires proof of that account once.

Will Relay guarantee there are no surprises?

A tool cannot guarantee that someone gives useful feedback. Relay makes expectations, missing responses, first-shared concerns, and follow-through visible so people have a better opportunity to address them.