Performance review record capture
For People operations review record coordinators
Prepare employee, review period and explicitly stated ratings or goals from a completed review with fields you can edit. No automated evaluation.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- employee name
- Example Employee - synthetic
- reviewer name
- Example Reviewer - synthetic
- period start
- 2026-09-01
- period end
- 2026-09-30
- stated ratings
- [ { "rating_source": "Example rating source - synthetic", "criterion_text": "Criterion text explicitly printed in the original synthetic source for reviewer context.", "stated_rating": "Example stated rating - synthetic", "comment_text": "Comment text explicitly printed in the original synthetic source for reviewer context." } ]
- goals text
- Goals text explicitly printed in the original synthetic source for reviewer context.
- acknowledgment text
- Acknowledgment text explicitly printed in the original synthetic source for reviewer context.
{
"employee_name": "Example Employee - synthetic",
"reviewer_name": "Example Reviewer - synthetic",
"period_start": "2026-09-01",
"period_end": "2026-09-30",
"stated_ratings": [
{
"rating_source": "Example rating source - synthetic",
"criterion_text": "Criterion text explicitly printed in the original synthetic source for reviewer context.",
"stated_rating": "Example stated rating - synthetic",
"comment_text": "Comment text explicitly printed in the original synthetic source for reviewer context."
}
],
"goals_text": "Goals text explicitly printed in the original synthetic source for reviewer context.",
"acknowledgment_text": "Acknowledgment text explicitly printed in the original synthetic source for reviewer context."
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
A completed review arrives for people operations review record coordinators. The next step needs employee, review period and explicitly stated ratings or goals, recorded under the correct document reference before the information enters your people operations review register.
A review contains a self-rating and a manager rating. Preserve the named source of each rating without making an employment recommendation. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Completed review PDFs
- Scanned or photographed completed review pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking employee name, reviewer name, period start, your application maps the reviewed record into your people operations review register. Keep the original document reference with the result. No automated evaluation. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
employee_name | string | Employee name exactly as printed in this completed review. Preserve identifiers and qualifiers; do not look up or infer missing information. |
reviewer_name | string | Reviewer name exactly as printed in this completed review. Preserve identifiers and qualifiers; do not look up or infer missing information. |
period_start | date | Opening date printed for the reporting period, separate from the issue date. |
period_end | date | Closing date printed for the reporting period, separate from payment or posting dates. |
stated_ratings | array | Every visible stated ratings row in this completed review. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
goals_text | string | Goals text exactly as printed in this completed review. Preserve identifiers and qualifiers; do not look up or infer missing information. |
acknowledgment_text | string | Acknowledgment text exactly as printed in this completed review. Preserve identifiers and qualifiers; do not look up or infer missing information. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- A review contains a self-rating and a manager rating. Preserve the named source of each rating without making an employment recommendation.
- Check period start, period end against their own printed labels; leave an unstated date empty instead of deriving it.
- Compare every stated ratings row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test completed review examples from the layouts your team actually receives. Include the exception described here: A review contains a self-rating and a manager rating. Preserve the named source of each rating without making an employment recommendation. Compare the extracted employee name, reviewer name, period start and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when completed review intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for people operations review record coordinators. Bring difficult completed review samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about performance review record capture
Which fields can I capture from a completed review?
The starter schema contains employee name, reviewer name, period start, period end, stated ratings, goals text, acknowledgment text. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in performance review record capture?
A review contains a self-rating and a manager rating. Preserve the named source of each rating without making an employment recommendation. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your people operations review register?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. No automated evaluation.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.