Skip to content
KiweelyKiweelyKiweely

Performance Check-In and Goals Screens Managers Will Open

Workday documents check-ins on Staffing, goal reads and anytime feedback on Performance Enablement v4, and goal edits on the Manage Goals business process. A manager screen should use those resources and leave formal reviews in Workday when the API listing has no review write.

  • Checked against Workday on
  • Applies to Workday Extend
  • 4 min read
  • Published
  • By Kiweely
On this page

Managers open a performance screen for a conversation they will have again next week: the check-in, the goals, and a short note. Workday already splits that work. Check-ins need no business process. Goals go through Manage Goals. Formal reviews stay on their own events. A screen should follow that split, and it should only call operations Workday publishes.

Kiweely Leaf (coming next) can host the screen and call Workday as the signed-in manager. It does not add a performance model beside Workday.

Check-ins are the part built for a light screen

Workday’s check-in setup says check-ins are 1-on-1 conversations with managers, peers, and mentors, and they do not require a business process. Workers secured to Self-Service: Check-Ins can create and view them. My Check-Ins is the self-service report. View Check-Ins is the manager report for selected participants. My Notes on a topic are private and are not included in View Check-Ins.

Setup steps add these rules: a check-in has two participants, the creator and the receiver. A worker can create only one check-in for a given date for each participant. The date can be past or future. Topics can hold shared notes and My Notes. Attachments can sit on the check-in or the topic. You can allow check-ins with any worker on the domain, not only the manager chain.

Staffing v7 documents the matching resources on /workers/{ID}:

  • GET and POST /workers/{ID}/checkIns
  • GET, PATCH, and DELETE /workers/{ID}/checkIns/{subresourceID}
  • archive through PATCH with type=archive
  • the same pattern for /checkInTopics

A manager screen can list upcoming check-ins, open one, and add a shared topic. It should not render My Notes for the other participant. If the API omits them, leave them omitted. One check-in per participant per date means the create button should update the existing row when Workday returns the duplicate, and say that.

Goals: read on Performance Enablement, edit through Manage Goals

The REST API Explorer overview lists Performance Enablement v4.1. The v4 explorer page fetched for this guide, base https://api.us.wcp.workday.com/performanceEnablement/v4, documents:

  • GET /workers/{ID}/goals and GET /workers/{ID}/goals/{subresourceID}
  • GET and POST /workers/{ID}/anytimeFeedbackEvents, plus get-by-id
  • feedback badge reads

That page describes access and creation of feedback. The listing shows goal retrieval. It does not show a goal create or a performance-review submit. Treat v4.1 as a version the overview names; this guide does not claim operations that were not on the v4 page.

Set Up Individual Goals is where required and hidden goal fields live, on Maintain Goal Setup, for all workers or for security groups. Manage Goals business process security controls who can create, edit, view, or archive. Domains in Performance Enablement: Self Service: Employee Goals and Worker Data: Employee Goals. Enforce Required in Web Service controls whether a required field produces a web-service validation message. If you require a field and leave that box clear, the web service can omit it without that message. A screen that skips the field will then store a goal Workday’s UI would have blocked. Match the UI.

Until a tenant’s explorer shows a goal write, send edits through Manage Goals as the manager or the worker, and use the v4 GET to display goals. Do not post a guessed goal payload.

What a Monday screen contains

Block Source Write
BlockNext check-in with this person SourceStaffing check-ins WriteCreate or patch the shared topic. Never show the other person’s My Notes.
BlockTheir goals SourcePerformance Enablement v4 GET .../goals WriteDisplay. Edits follow Manage Goals and Maintain Goal Setup.
BlockA short feedback note SourcePOST .../anytimeFeedbackEvents if the caller’s domains allow it WriteCreate one event. Read the security line in the explorer for your tenant before enabling the button.
BlockThe annual review questionnaire SourceNot in the v4 listing fetched here WriteOpen the Workday review event.

Show the worker the manager is allowed to see. A manager constrained to a supervisory organization should get an empty state for a peer team, which is the correct result. Leaf (coming next) runs the call as that manager.

Questions

Can check-ins replace the performance review?

Workday describes them as a supplement to formal review and feedback events, with less administrative overhead. You can embed a check-in report as an analytic worklet on a review business process. The screen can deep-link to the review. It should not mark the review complete because a check-in was saved.

What is still unknown?

The operation list for Performance Enablement v4.1, beyond the v4 page above, was not retrieved for this guide. Confirm goal writes and review events in your tenant’s explorer before you add those buttons. Register the manager screen on Leaf (coming next) when you want it hosted.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.