# Prepare the portfolio review pre-read

Dovqelira · Product-management work sample
All company, customer and data in this exercise are original synthetic material.

## Situation and outcome
Dovqelira is a fictional software company that sells to field-service businesses (heating, plumbing, electrical and facilities firms). It has about 1,900 Teskivra accounts and $45.4M of net revenue, and six products: Teskivra (scheduling and dispatch, the core), Payments, Varnetivo (maintenance plans), Portavinq (the customers' self-service portal), Yelqavuno (an AI call-intake assistant) and Classic (the on-premises edition, closed to new sales).

Twice a year the executive portfolio committee (the CEO as chair, the CFO, the CPO, the CTO and the CRO) decides how product engineering is split across the products for the coming half-year, rules on the conditions it set last time and decides retirements. The review covers the first half of FY27 (January to June 2027), and its owner reports to the CPO. Your role in it and your authority are set out below. Today is Thursday 8 October. The six product managers and finance have submitted. The pre-read is due to the committee on Friday 16 October at 17:00, and the committee meets on Thursday 22 October. A portfolio analyst agent has drafted an options analysis from the submissions folder, and nobody has checked it.

Your outcome is a **pre-read marked proposed**, with the decisions the committee must take first, and a **readiness file** that says for each product whether its decision is ready or you propose to defer it. For a deferral it gives the information still needed, an owner, a reconvene date and the engineering allocation that continues meanwhile. A well-argued "this decision is not ready" is a valid result. Setting the brief, running the session, pre-briefing the executives, ruling on anything, recording and tracking the rulings after the meeting, speaking to customers, and retirement or upgrade work are not part of this work. Review notes on the pre-read from the CFO and the CPO are already in your download, in the correction note (U001).

The evidence period is 2026-03-20 through 2026-10-07 inclusive. Work with 60 source records (the review brief and committee rules, last March's decision record and its follow-up, finance's figures, the data team's metrics, the six submissions, the CRM pipeline appendices, customer notes, contract summaries, a security review, the engineering seat list and saved market material) and an AI-drafted options analysis. The records are supplied, not run by you. The AI draft is not an authority. Use the supplied source IDs and context; do not contact the fictional teams or seek private data.

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

You coordinate this review for the CPO. Prepare the pre-read and the readiness file as proposals: compare the products, frame options within the envelope and propose deferrals with owners. You may recommend. You may not change the envelope, criteria or decision questions without the CPO, tell PMs their allocation, rule on a condition outcome (you may report what the confirmed measurement shows against the bar), or commit anything to customers.

## About the team
A product organisation that prepares a half-yearly portfolio review for an executive committee, run by the portfolio review owner and reporting to the CPO.

A portfolio analyst agent drafts the options analysis from the submissions folder, a notes assistant writes the committee's meeting notes and product managers fill in the submission template with AI. People own the figures (FP&A and the data team), the rulings (the committee) and the record of rulings (the review owner, confirmed by the chair).

The committee decides allocations, condition outcomes and retirements; finance and the data team own the figures; the CFO sets the envelope; the CPO sets the decision questions; the review owner prepares proposals, records rulings as made and confirms the wording with the chair; the PM recommends and routes but decides none of these and does not speak to customers.

## Work to complete
1. Read sources/coverage-and-access.md before you make claims about what the records cover. The CPO's request, the review brief and the committee charter are among the first records.
2. Put the six products on one basis. Finance compiles the comparable figures; a submission's own figures are inputs, not the record. Say which figure you use and why.
3. Audit the AI draft against the original records, row by row. Change only what the evidence warrants. A row that still stands is kept, with its reason.
4. Test each submission's case. Count accounts, not rows, and tell apart what a record shows, what an AI tool wrote, what a person claimed and what is only a plan. Keep contrary evidence and rare serious items visible.
5. Carry forward every open item from the March decisions: say what each one required and where it stands on the confirmed record.
6. Frame the funding options. Each option must fit the engineering envelope, say what it gives up and where it sits against each product's minimum to sustain. If your role allows a recommendation, you may recommend one, labelled as your recommendation; you may also lay the options out without one.
7. For each product say whether its decision is ready for the committee or you propose to defer it A deferral names the information required, an owner, a reconvene date and the allocation that continues meanwhile. For a ready decision write N/A in the four deferral columns.
8. Apply the review notes in the correction note (U001). Carry each change through the pre-read, the evidence table, the readiness file and the revision log, and keep the earlier reading visible in the revision log.
9. Keep to your role. The committee decides allocations, condition outcomes and retirements. You prepare proposals and record nothing as decided.

## 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-pre-read-review-notes-v1.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).
- pre-read.md: the pre-read for the committee, marked proposed, at most 1,200 words. Open with the decisions the committee is asked to take, then put all six products on one basis, set out the funding options within the engineering envelope with what each gives up, give each product's position, and carry forward the March items.
- evidence.csv: columns source_id,product,disposition,account_id, then rationale and evidence_version. Use DSP (Teskivra), PAY (Payments), AST (Varnetivo), PRT (Portavinq), AIS (Yelqavuno), CLS (Classic), portfolio or context in the product column. For how you use the record (the disposition column), use values such as confirmed figure, submission figure, supports, contrary, condition, obligation, claim, risk, context or not used. The file already has one row for each record, R001–R060, with the record ID and account ID filled in. Fill in the empty columns on every row: the product, how you use the record, and a short reason. Add a row if a record bears on more than one product. Do not retype or delete record or account IDs. If the correction note (U001) changes a record, revise its row, put U001 in the evidence_version column and keep the earlier reading visible in the revision log.
- readiness.md: at most 600 words. One row per product: its decision question, ready or propose to defer, then the information required, the owner, the reconvene date and the allocation meanwhile (N/A for a ready decision). Then the status of the March actions A1 to A5, then the open items for the CPO.
- revision-log.md: material changes to the AI draft, verification checks, the effect of the review notes and remaining gaps, at most 500 words. No private prompts or unrelated files.

Words are counted in prose and in table cells; table borders and heading marks are not.

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 figures and counts
- Judges what the evidence supports
- Checks and repairs the analysis
- Hands decisions to the right owners
- Explains their choices
- Weighs products against one budget

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.
