A PEOPLE OPS EXPERIMENT
Ask a question, review the details and follow your requests in one place.
Start here or type your question.
AI can make mistakes. Check the source and details before confirming.
All employees
Before your start date, the People team sends your onboarding checklist and IT arranges your accounts and equipment. On day one, meet your manager and onboarding buddy. During your first week, complete an HR systems walkthrough and agree your first-month priorities with your manager. The People team checks in at the end of week one and month one. Contact the People team if access or equipment is missing.
All employees; entitlement depends on your contract and location
Submit planned time off in the HR system at least 10 working days before the first day away where possible. Your manager reviews team coverage and approves the request in the system. A submitted request is not an approval. Your allowance, carryover rules and public holidays depend on your contract and work location; this handbook does not specify them. For an urgent absence, contact your manager and the People team as soon as possible. Do not share medical details in this demo.
Employees considering temporary work outside their contracted country
Work from your contracted country unless the People team gives written approval for another location. Request an international remote-work review at least 20 working days before travel, including the destination and proposed dates. The People team checks immigration, tax, employment and security requirements with the relevant experts. There is no automatic allowance of days abroad and approval is not guaranteed. Wait for written approval before booking travel that depends on working abroad. Permanent moves follow the relocation policy.
Employees who have completed three months at Juniper Studio
After three months of employment, you can request up to EUR 600 per calendar year for learning related to your role. Share the course, cost and learning goal with your manager and get written approval before purchasing. Submit the receipt through the expense process within 30 calendar days of purchase. Unused budget does not carry over to the next year. Contractors are not covered by this allowance. This handbook does not specify a prorating rule or exceptions; ask the People team about those cases. In the fictional demo, Alex is eligible and starts with EUR 600 available in 2027. Pending requests reserve their cost to prevent exceeding the budget; they are not approved. A manager explicitly approves or rejects them in the review simulator. Only pending requests can be cancelled. No purchase or reimbursement is executed.
Employees considering a permanent change of work country
Contact the People team before committing to a permanent move. Share your proposed destination and timing. The People team coordinates a review with immigration counsel, Finance and relevant employment providers to assess whether the move is possible. The company does not promise visa sponsorship, an employer-of-record arrangement or relocation reimbursement in this handbook. Any support, costs and conditions must be agreed in writing for your individual case. The assistant cannot determine visa eligibility or approve a move.
Alex, fictional 2027 scenario only
The demo date is 1 June 2027. Alex is an employee since January 2026, with 25 allocated days and 7 already taken, leaving 18 before new requests. Only Monday to Friday count; no public holidays are included in this simplified calendar. Requests must be within 2027, on or after the demo date, include a working day, and must not overlap pending or approved requests. Pending requests reserve days for validation but are not approved. A manager must explicitly approve each request in the review simulator. Only pending requests can be cancelled. Approved days reduce the available balance; rejected or cancelled requests release their reservation. These numbers do not establish real employment entitlements.
Fictional demo employee
Ask which document and purpose the employee needs. This demo only prepares a fictional proof of employment, not an unemployment or other official certificate. Review the purpose before confirming submission. People prepares the document explicitly in the review simulator; until then its status is pending. The completed preview is marked fictional, is unsigned and has no official validity. No emails are sent. Other document types require clarification with People.
Fictional Madrid profile only
Use made-up details only. Review the current and proposed street, postal code and city, then explicitly confirm the change. The demo only supports Madrid addresses with a five-digit postal code starting with 28. The confirmed address replaces the example profile immediately and a completed entry remains in My requests. No manager approval is required for this local demo change. International moves require People review and cannot be completed here. Addresses entered in forms are kept in browser storage and are not sent to the model.
BEHIND THE EXPERIMENT
I don’t have a technical background. I built this experiment by talking with Codex: explaining what I needed, trying its suggestions and asking for changes. I wanted to turn an idea into something you could try, alongside reading about my work in my CV.
In People, the same questions come up often, and simple tasks can mean finding a policy, tracking down a form and figuring out who needs to approve it. I wondered what it would be like to bring those steps into one conversation, while keeping the rules and the person making the decision in view.
I defined the use cases, the tone and how the process should feel for an employee. Codex proposed designs, wrote the code and ran technical checks. We started with a chat that explained a fictional handbook, then added requests and a dedicated page to try them.
Trying it helped me spot things to improve: a red success message looked like an error, mixing leave days and euros made the balance hard to understand, and a submitted request needed to look different from an approved one. Those decisions are part of making an HR tool useful too.
The assistant uses a fictional handbook and can open a card for time off, an employment certificate, an address change or a course. You can read the sources behind its answers.
The card collects the details and explains the next step. Days and budgets are calculated using application rules, rather than leaving the arithmetic to the chat.
Submitted requests appear in My requests. Review mode lets you try approving, rejecting or preparing a document. Both roles are simulated.
The company, profile and policies are made up. Requests are saved in your browser, not sent to an employer. The AI does not approve leave, buy courses or change a real HR system. Chat messages go to an AI provider, so please use made-up examples only. Answers can be wrong even when they link to a source.
Using something like this with real employees would require company-approved policies, individual access permissions, a privacy review and secure connections to company systems, among other things. This demo lets me explore the process and show how I think about it.
Request five days off, check that the request is pending, then switch to Review to approve it. Look at the balance again. It’s a quick way to see the difference between getting an answer from a chat and being able to follow the whole process.
Back to the experiment