# Answer the product questions in a tender

Dovrasken Systems · Product-management work sample
All company, customer, product and tender information in this exercise is original synthetic material.

## Situation and outcome
Dovrasken Systems is a fictional UK supplier of remote monitoring and alarm services for water and industrial sites. Its product, Tavrulith, is a cloud service with a QZVHX-40 gateway at each site and an AI feature, Fenkravith, that scores equipment anomalies. Pellingrove Water Authority has issued a tender to monitor 140 pumping stations (R001). You take over the product section of Dovrasken's bid today, Friday 9 October, from the previous product owner, who moved teams on 2 October. The bid owner, the Head of Bids, owns clearance and submission and is the only contact with the Authority (R008, R011).

Your outcome is an answer package and a clearance note for the bid owner, due Monday 12 October at 09:00. Clarification questions to the Authority close that day at 12:00, the bid owner's clearance meeting is Tuesday 13 October and submission is Thursday 15 October. The stakes are real: a materially false statement means exclusion, a Partially compliant or Non-compliant response to a Mandatory item may lead to exclusion, and the answers may become part of the contract (R001). Every answer must be something the company can stand behind. A package that says Partially compliant or Non-compliant, that leaves an answer with the specialist who owns it, that shows evidence is still missing, or that recommends the bid owner reconsider bidding, is a valid result. Your package is not a submission approval: it does not clear anything, contact the Authority, a customer or a specialist, set a price or commit a date.

The period is 1 Feb 2025 through Fri 9 Oct 2026; the snapshot is Friday 9 October, midday. Work with 56 records (the tender, the bid plan and ownership list, product and release documents, answer library entries and the agent's run log, security, legal and support records, customer records and team messages) and an AI first draft of the product answers that Dovrasken's response agent produced on Monday 5 October. The draft is a draft, not an authority; nobody has checked it. All names, figures and terms are synthetic, so answer from the records supplied: outside knowledge of real products, utilities or law earns nothing. Use the supplied record IDs and source context; do not contact the fictional teams or seek private data.

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

You own the product section from today: work out which items are product's from the ownership list (the bid owner has not confirmed it, so ask for the confirmation in your note), answer every product-owned item on the tender's scale with its records and verifier, log gaps and deviations, route specialist statements to their approvers with proposed wording marked for approval, and send the bid owner an answer package with a clearance note: what is ready, what departs from the requirements or standard terms, what still needs clearing and by when, and the decisions that are theirs. You may recommend. You may not approve a security, privacy or legal statement, quote a price or service level, commit an unapproved date or a customer-specific build, name a customer without consent, contact the Authority or decide to submit.

## About the team
A remote-monitoring supplier's product team answering the product section of a public-sector tender, for the bid owner's clearance meeting.

The bid office's response agent drafts answers from the answer library and product documents and copies compliance statuses from library entries; solutions engineers use an assistant to draft clarification questions; a person checks each answer against the released product and the verification on file before it goes to the bid owner.

The PM owns the product answers and routes specialist statements; Security owns its own answers and incident disclosure; Legal and privacy approve privacy, legal and contractual wording; the bid owner prices, decides what departs from the requirements, clears and submits, and is the only contact with the issuer.

## Work to complete
1. Read the tender's rules and items (R001-R006), the bid plan, the ownership list and the bid owner's request (R008-R012), and sources/coverage-and-access.md. The ownership list was never confirmed, so check it against the records. The items named in this brief (3.1-3.4 and 3.6-3.10 as yours, 3.5, 4.2 and 4.9 for product facts) are your scope; where an owner looks wrong, say so in the clearance note as a request for the bid owner to confirm ownership, and do not wait for it.
2. Audit the AI first draft against the original records. Keep, correct or reject each row and say why. Check every claim against the released product and the verification on file. Tell apart what is released, what needs a configuration, what has an approved date, what is only being explored and what someone merely claims.
3. Count support by independent observations and by the tender's own criteria, not by rows or by the number of sources named. A repeat, a copy or a relay counts once, and a count of customers counts only those that meet what the tender asks.
4. Answer every product-owned item on the tender's scale, and supply the product facts for the items the draft left blank. Where a statement is a security, privacy or legal statement, route it to the function that owns it: you may propose wording from the product records, marked for that function's approval, but you do not approve it and you do not write Security's own answers (4.1 and 4.3-4.8).
5. Log every gap and every departure from the requirements or the standard terms with what is offered today, who decides and by when. Name follow-on work without starting it.
6. Apply the correction note (U001) from your download, as you would any other source. Carry each justified revision through every file and keep the earlier reading visible. The revision log is your own account of how you worked.
7. Hand off clearly: what is ready, what departs from the requirements, what is still with the specialists and by when, and which decisions are the bid owner's.

## 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-clarifications-and-crm-correction-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).
- answers.md: one entry per product-owned item (3.1-3.4 and 3.6-3.10), plus the product facts for 3.5, 4.2 and 4.9. For each entry give the status on the tender's scale (for 3.5, 4.2 and 4.9, which a specialist owns, write "Provisional:" before the status or "status for the specialist" and give the product facts only), the answer wording, the records relied on, who verified it or 'unverified', and the specialist who must approve it if any. At most 1,100 words.
- gaps.csv: every capability gap and requested departure, with the columns in the template. At most 15 rows.
- clearance-note.md: for the bid owner, at most 600 words. What is ready, what departs from the requirements or the standard terms, what is still with Security, Legal and privacy or data science and by when, the decisions that are the bid owner's, and a line saying it is not a submission approval.
- evidence.csv: it already has one row for each record, R001-R056, with the record ID and party ID filled in. Fill in the empty columns on every row: the tender item the record bears on most (3.1-4.9, or context), how you use it, and a one-sentence rationale. For how you use it, supports, contrary, unverified, repeat, claim, needs specialist or context are suggested and your own words are accepted. Add a row if a record bears on more than one item. Do not retype or delete record or party IDs. If the correction note (U001) changes a record, revise its row in place, put U001 in the evidence_version column, and keep the earlier reading visible in the rationale or the revision log.
- revision-log.md: at most 500 words. Each draft error you found with the record check that exposes it, the draft rows you kept, and what the correction note (U001) changed.

Keep every file within these limits: the bid owner reads all of it. Words in prose and in table cells count toward a limit; headings, table borders and other markdown symbols do not, and the README and evidence.csv are not counted.

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:
- Ties answers to evidence
- Handles unknowns and serious risks
- Checks and fixes the AI draft
- Hands over a usable answer pack
- Explains the reasoning
- Answers honestly, commits nothing unapproved

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.
