People

What it is#

People (at /people) is about the person and what needs deciding about them. The plan for their time stays on Resource Allocation; utilization here is a number and a link, never something to edit. Studio leaders and firm admins hold the rail row; a principal reaches the same records through Directory and the profile drawer.

Everything on it is read live from CORE: active employees, this month's and this period's time, reviews, time-off requests, and benefits. Refresh re-reads.

What needs you#

• Time off: a request with the balance after it (when CORE tracks balances), any clash the Approvals panel would flag, and who the approver is. If that is you, Approve and Decline… write CORE's own decision, the same as from Approvals; otherwise the row says who it is waiting on.
• Reviews due: a CORE review not yet completed, due within 60 days or overdue. Start review opens the person's Record tab.
• Probation ends: ninety days after the hire date. Anniversaries in the next thirty days.
• Unapproved time: entries in the current pay period still waiting, with a link to Approvals. The hand-off waits on these.

The roster#

One row per active employee: manager, hire date and tenure, PTO balance (with pending hours flagged), utilization this month against the person's own CORE target (amber when well under), the next review, and unapproved entries in the period. Click a name and the profile drawer opens.

A PTO balance reads — when CORE holds no figure for that benefit. COREboards takes CORE's granted or accumulated hours and subtracts the usage CORE records; it never invents an allowance.

The employee Record tab#

Open a person and choose Record. Firm admins see all of it; a studio leader sees employment, benefits, reviews, the journal and incidents. Compensation, salary history and identifiers are admin-only and hide under Hide $. Nothing here is cached, exported or sent to the AI.

The four writes

• Start review creates a CORE review from one of the firm's review templates, with you as the reviewer and a due date. CORE builds it from the template's questions; it is answered in CORE for now.
• Journal note adds an entry to CORE's HR journal with a type and today's date.
• Log incident records an incident with its type, date, place and description, reported by you.
• Release… (admins) writes two fields on the employee record, the release date and the status Inactive, behind a confirm that names them. Keys, accounts and the last pay period are yours to close out.

The pay-period hand-off#

There is no payroll API, so the Pay period view is the sheet you read before running payroll elsewhere: regular, overtime, PTO, sick and comp hours per person, and whether each person's entries are all approved. Step between periods with the arrows.

The hand-off checklist says what blocks it (unapproved entries, undecided time off), exports a CSV with one row per person, and lets a firm admin or CFO Mark the period handed off. That mark is stored in COREboards with who and when; CORE is never written for payroll.

PTO and sick hours are entries on the firm's time-off projects; overtime and comp come from the entry flags in CORE.