Record the bid call
record_bid_callDestructive
Use this when the user's team has decided whether to bid: records the bid or no-bid call, the team's answers to Tenda's five questions and the reason. A bid moves the tender to Bidding and plans a six-step sprint back from the deadline; a tender not in the pipeline is added first. Confirm the decision with the user before calling. Needs a Tenda account and a role that makes bid calls. Not for judging fit before the call (use assess_tender_fit). Example: {"tender_reference":"012345-2026","decision":"bid","answers":{"fit":"yes"}}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Why, in the user's words, for the team to read later. | |
| answers | No | The team's answers to Tenda's five questions, each "yes", "unsure" or "no": fit (is this work we do well), eligibility (do we meet every must-have), capacity (can we deliver it and write the bid in time), competition (can we beat the other bidders) and value (is it worth winning). Leave out questions the user didn't answer. | |
| decision | Yes | "bid" when the team will bid, "no_bid" when it will not. | |
| 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 | ||
| recorded | No | ||
| workspace | No |