Update the bid sprint
update_bid_sprintDestructiveIdempotent
Use this when the user says a step of a bid their team is running is done, or not done after all: decode the pack, assign questions, draft answers, review and score, final checks or submit. Ticks it off with who did it and when, and says what is next and when it is due. Ticking submit moves the tender to Submitted. Needs a Tenda account and a bid sprint, which starts with a call to bid (record_bid_call). Do not use to write or check answers (use draft_bid_response or review_bid_draft).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| done | No | false to reopen a step ticked off by mistake. Defaults to true. | |
| step | Yes | The step: "decode" (read the tender pack), "assign" (give each question an owner), "draft" (write the answers), "review" (score them), "checks" (final checks) or "submit". | |
| workspace | No | The Tenda workspace to use, by name, when the user is in more than one, e.g. "Northbridge Services". | |
| tender_reference | Yes | The notice ID, procurement identifier, solicitation number or the buyer's own reference, e.g. "012345-2026" on Find a Tender, "WS4851234567" on CanadaBuys or "140D0427Q0879" on SAM.gov. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| stage | No | ||
| tender | No | ||
| summary | Yes | ||
| updated | No | ||
| workspace | No |