Skip to content
Novus Examples

People Operations · Synthetic business data

Cobalt Operations Team

A fictional staff directory, paid-shift schedule and leave register with base-pay reconciliation.

ZIP with instructions and SHA-256 checksums. Files stay in your browser.

Create from this data

Choose a starting template, then follow its table and field mapping. Studio imports add a table to your project; they do not automatically replace the template’s sample content.

Guided source import

Inspect and edit the source data

Source table: shifts in the linked operating model.

employee_id
employee_id
date
date
paid_hours
paid_hours
hourly_rate
hourly_rate
base_pay
base_pay
  1. Open the linked operating model in the text and data editor. Find tables.shifts.rows to inspect the records and exact field names.
  2. Keep identifiers as quoted text, retain the other tables and compare edits with the linked schema and expected results. Save a local copy before changing records.
Open text and data editorDownload source JSON

Guided source import

Staffing and pay report

Source table: shifts in the linked operating model.

employee_id
employee_id
date
date
paid_hours
paid_hours
hourly_rate
hourly_rate
base_pay
base_pay
  1. Download operating-model.json, then open this Document Studio template. Choose Import business data, select the JSON file, choose shifts in Business data table and click Use table.
  2. The import appends a new typed table with all source columns. Use the listed fields for your report, edit its heading and remove unrelated sample blocks. Transfer any values needed by the original template into its fields explicitly; imported records do not replace or bind its sample line items.
  3. Save editable source to preserve the document project. Use the kit workbook in a spreadsheet application when you need its existing formulas, worksheets and chart layout.
Open Document StudioDownload source JSON

Start with blank input tables

The ZIP contains a header-only CSV for every source table. Fill the fields using the kit schema, then open the CSV in the text and data editor or import it into a Studio. Open the completed operating workbook in a spreadsheet application to retain its native worksheets, formulas and chart layout.

Download blank CSV templates

Start with the expected results

Read the kit guide, follow each input’s import order, then compare your output with the reconciliation checks. Planning datasets do not imply that a platform can import them.

Platform compatibility

Example data

Generic business records

Profile 2026-09-08.1 · reviewed 2026-09-08

  1. Map fields to your application schema and retain stable relationships.

Generic records are not native imports for unnamed platforms.

Inputs, templates and references

Linked operating model

Download JSON

Input · 22.5 KB · Valid

102 records across 5 linked tables; no duplicate primary keys or missing references. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

Operating model JSON Schema

Download JSON

Schema · 12.8 KB · Reference

Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

Numeric expected results

Download JSON

Expected Results · 2.1 KB · Reference

Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

Operating report PDF

Download PDF

Reference · 57.9 KB · Valid

Three readable pages summarize the same model, chart, source tables and usage instructions. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

Editable operating workbook

Download XLSX

Template · 18.6 KB · Valid

Native sheets preserve 102 source records, 3 calculated headline metrics and one editable chart. Paid hours=336.00 hours; Base pay=9,072.00 USD; Employees=8.00 records.

Deliberately invalid tests