The bid plan turns the evaluation matrix into owned, trackable questions plus the submission checklist. It is built once, from the analysis, for a tender you have committed to.
A tender page opened by a WayWiser bid writer carries the bid's Shared with client / Not shared chip in its head, with Share with client or Stop sharing beside it — the one place a bid's sharing is changed. Its questions, drafts and reviews follow the bid. A client never sees the chip; a bid that is not shared is not on their pages at all (Team and roles).
Creating the plan
Click Create bid plan once. WayWiser materialises every question from the pack analysis — reference, weight, word limit, rubric — and the checklist items the pack demands. The button is refused, with the reason, when the pack has not been analysed, when no go / no-go decision is recorded, when the tender is archived as a no-bid, or when a plan already exists.
The matrix
Each question shows its weight, word limit, owner and status. Statuses run from not started, through drafting (a draft job is queued or running), to draft complete, reviewed and signed off; a failed draft says so with its reason and a Try again. Assign owners from your team; invited teammates appear as assignable owners on every tender.
The submission checklist
Every item the pack demands — certificates, insurances, policies, forms — with a status: ok, missing or pending. Items are matched against your facts bank, so a current certificate ticks the item and an expired one flags it. Expired facts never enter drafts and block the checklist until they are renewed on the Knowledge page; a fact whose expiry could not be determined does not satisfy an item either.
Milestones and the timeline
The plan carries the tender's milestones (clarification deadline, submission deadline and your own), which the pipeline's deadline pill and the question workspace's timeline exhibit read from.
The fast path
For a tender whose questions closely match answers you have already written, Commit bid draft builds a first draft of every question in one background run rather than one at a time. It is dedupe-protected: a double click builds it once, and the run's progress is on the tender page and on Activity.