Your requirements document now keeps its history, and your own words
When a customer raises a request, they describe it in their own words. Until now, approving the requirements document wrote over that description — the account of what they actually asked for disappeared at the moment the request became real.
It doesn’t any more.
What’s changed
Your original request is kept. The few lines written when a request is raised stay exactly as written. Every screen that shows the requirements now shows that original request underneath it, under Customer’s request, so the document and the ask behind it can be read side by side.
The requirements document is versioned. Approving writes a numbered version, recording who approved it and when. Correcting it later — through Edit overview on the workspace — writes the next version rather than replacing the last one, and the earlier versions stay listed with their dates and approvers.
Experts see the same thing. The proposal view shows the version being bid against, with the customer’s original request below it.
What you’ll notice
- Customers: what you wrote when you raised your request is still there after the requirements are approved.
- CSMs and SDMs: the Requirements section on the workspace lists every version of the document with its date and approver, and editing writes a new one rather than overwriting.
- Experts: the brief you’re bidding against now sits above the customer’s own description of the problem.
Requests approved before this change carry a first version built from what was stored. For those, the customer’s original wording was already overwritten and can’t be recovered, so no Customer’s request section is shown — everything from here on keeps both.