# Write a requirements document ready for review

Tessaly Health · Product-management work sample
All company, clinic, patient and data in this exercise are original synthetic material.

## Situation and outcome
Tessaly Health is a fictional software company. Its product, Tessaly Front Desk, runs scheduling and intake for independent outpatient clinics. The Head of Product, the sponsor, has validated one initiative, open-slot backfill: when a patient cancels with less than 24 hours' notice, offer the freed slot by text to waitlisted patients. The problem brief is settled (context/problem-brief.md); do not reopen it. The sponsor chose six pilot clinics. Engineering and design review is on 30 September and sign-off on 7 October.

Your outcome is a requirements document that engineering, design and the sponsor can review as it stands. An AI agent has already written a first draft from the input log. The draft is not an authority. Check it against the inputs, repair it and turn the result into requirements the team can build and test against. Each requirement is tied to inputs, what the inputs cannot show is kept apart from what they establish, and the company's privacy checklist is applied to the document. A well-argued "not ready for sign-off" record, naming what must be settled and by whom, is a valid outcome.

The document does not run the review meeting, perform the specialist review, sign off or baseline itself. It does not reopen the problem, design the offer flow, write user stories, plan the release or set prices.

The period is 2026-07-27 through 2026-09-25 inclusive. Work with 58 inputs from 29 origins (clinics and internal teams): interview notes, patient sessions, support tickets, AI-summarised sales calls, data extracts, engineering notes, early review comments and policy notes. Use the supplied input IDs and origin codes; do not contact the fictional teams or seek private data or live queries.

## Your role
You are joining the team as Product Manager.

Take the whole requirements document to review-ready for engineering, design and the sponsor: requirements, constraints, out of scope, success metric, screen record and open issues with owners. You own the document. The target, the pilot clinics and sign-off are the sponsor's; the offer approach is design's with engineering; privacy, legal and finance decide their screen items.

## About the team
A healthcare scheduling software team preparing a requirements document for engineering and design review.

An agent assembles the context pack and writes a first draft from the input log; an assistant summarises sales and success calls; a person checks everything before engineering and design see it.

The sponsor sets the success target and the pilot clinics; privacy, legal and finance decide their screen items; design decides the offer flow with engineering.

## Work to complete
1. Read context/problem-brief.md and sources/coverage-and-access.md first. Note what the inputs cover and what they cannot show.
2. Audit the AI first draft against the original inputs. Keep, correct or reject each row and say why. Keep evidence that points the other way visible, and tell apart a measured figure, a person's claim and a gap. Where a figure depends on joining two inputs, do the join.
3. Count inputs, origins and observations separately. An observation is one separate thing that was seen or said. An input that repeats or relays another counts once with it: a clinic's follow-up message about the same call, a copy of another input, or the same incident told twice is one observation. An input that holds two separate findings counts as two. Treat severity separately from frequency.
4. Write the requirements in the team's template (context/requirements-template.md): functional requirements, quality requirements, constraints and out of scope. State what must be true and how a tester would check it, not how to build it. Cover the whole product, not only the software change: include what clinics and staff need around the software (for example text-message costs and contract terms, a help article and front-desk training, what the front desk can see), and leave out what the situation section excludes (for example setting prices or a paid add-on).
5. Apply the privacy checklist (context/privacy-checklist.md) and record the screen result: needed or not, which items, and the reason for each.
6. List the open issues. Each has an owner and what would close it. Decide only what is yours; name who decides the rest.
7. Apply the correction note (U001) in your download like the other sources. Carry each justified revision through every file and keep the earlier version visible. The revision log is your own account of how you worked.

## Time
You have 90 minutes of work time. The clock starts when you press Start.

After that comes a 10-minute break, then a written interview: up to eight typed questions about your own files, for about 15 minutes. If you submit early, your break starts straight away.

## Mid-task correction
There is no mid-task correction in this take-home. Everything you need is in the files you download at Start, including the correction note **updates/U001-engineering-and-crm-correction.md**. Read it with the other sources, apply it where it changes your work, and cite it as U001.

## Tools and help
Use any tools and help you like: AI tools and agents, search, your own notes, friends or colleagues. You don't need a paid tool, an API key or an account.

Nothing you do in your own tools is watched. Only your files and your interview answers are reviewed. When you submit, you can say which tools or help you used. That is optional, and leaving it empty is never held against you.

## Submission
Hand in one ZIP with these files at its top level. Start from the copies in the templates folder.
- README.md: list every file you hand in and say how you used the correction note (U001).
- requirements.md: the requirements document, about 1,500 words at most, in the team's sections, including the success metric, the screen result and the traceability of each requirement to inputs.
- evidence.csv: already has one row for every input, N001–N058, with the input ID and origin code filled in. Do not retype them or remove rows. For each row, fill in your own requirement name, a use and, in one sentence, a rationale. A use such as supports, contrary, constraint, context, out of scope or not used is suggested and free text is accepted. Put one requirement in each row; when an input bears on two requirements, copy its row and change the requirement. If the correction note changes an input, revise its row in place, set evidence_version to U001 and keep the earlier reading visible in the rationale.
- revision-log.md: material changes to the AI draft, verification checks and remaining gaps. No private prompts or unrelated files.
- open-issues.md: the open issues, each with an owner, what closes it and what depends on it.

Words are counted in the prose of each document you write; headings, tables, the evidence file and the README do not count.

Use plain text files only: .md, .txt, .csv or .json. Put your work in the files themselves; a link to a document somewhere else does not count. Your ZIP can be up to 5 MB, or 20 MB unzipped, with at most 39 files of up to 2 MB each. Programs, macros, password-protected ZIPs and ZIPs inside your ZIP are not accepted.

Upload your ZIP on your take-home page and wait for **Received and checked**. It normally appears within a few seconds of the upload finishing. If it has not appeared after a minute, upload the ZIP again; if it still does not appear, use **Help and support**. You can replace your ZIP until you submit. Submitting is final and starts your break.

If time runs out before you submit, the last ZIP marked **Received and checked** is handed in for you. If none was received, the team is told that you need support.

If something goes wrong, use **Help and support** on your take-home page. A technical problem is never counted against you. Writing to us does not pause the clock.

## What happens next
The written interview covers these parts of the job:
- Checks sources and counts
- Judges what the evidence supports
- Checks and repairs the draft
- Prepares the review and sign-off
- Explains their choices
- Writes testable, bounded requirements

An AI then drafts a review from your files and your answers. Each point quotes what it rests on. A person at the company reads the review and makes any decision. No one is hired, rejected or ranked automatically.
