Revisions, withdrawing and closing

Following a sent request

After sending, the request panel shows the request's state and every partner's state. Open it from the BoQ (Related → Outgoing bid requests → the request) or from the project list Outgoing bid requests.

1. The status chip: Sent (Изпратено), or Revised (Ревизирано) for revision 2 and later, with a Revision {n} (Ревизия {n}) chip.
2. The timeline: Created (Създадено) → Sent (Изпратено) → Offers (Оферти, "{count} of {total}") → Awarded (Възложено) → Signed (Подписано).
3. Revise the request (Ревизирай запитването) starts a revision with changed positions.
4. Add a participant (Добави участник) invites more partners or a self-managed contractor.
5. More actions (⋯, Още действия) holds Close request and Withdraw request.
6. Compare and award (Сравни и възложи) opens the award screen.
7. A partner card with its status pill and, when expanded, its responses and actions.

The timeline

The request timeline in the panel has five steps with dates: Created (Създадено), Sent (Изпратено), Offers (Оферти) as "{count} of {total}" (partners who answered out of partners invited and not declined), Awarded (Възложено) as awarded positions out of all positions, and Signed (Подписано) as positions with a signed contract.

When awards exist, a line under the header shows "Awarded: {parts} · remainder {remainder} %", the share of positions per company. The award screen shows the split by value.

Partner statuses

The card Request results/offer status (Резултати от запитването/статус на офертата) has one card per invited partner, with the partner name in capitals, a Self-managed (Самоуправляван) badge for contractors without login, and a Chosen offer (Избрана оферта) badge when you chose its offer.

Responses and offers on a partner card

Expand a partner card to see its response timeline, newest first. The first two items show; click to expand the rest.

• Response #{n} (Отговор #{n}): "Offer received" (Получена оферта) or "Update received" (Получена актуализация), the contract proposal status if any, and "Total value: {amount}". Review (Разгледай) opens the offer. See Comparing offers.
• Update request (Заявка за актуализация): "To version {n}" with the status Update requested, Processing or Update sent, and your description.

Actions on an expanded card, while the request is open and the partner is still active:

• Choose this offer (Избери офертата): awards the whole request to this partner. See Awarding (whole or by line items).
• Undo choice (Отмени избора): removes that choice while no contract exists.
• Withdraw (Оттегли): withdraws the request from this partner only. See below.

For a self-managed contractor the card offers Enter offer on their behalf instead. See Recording offers from companies outside BuildColab.

How to change the name, deadline, note or files after sending

You can change these while the request is open. You do not need a revision for them.

• Name: click the request name in the panel and type.
• Deadline: pick a new date next to Deadline: (Краен срок:). A past date is refused: "The deadline cannot be in the past." Today is allowed.
• Note: edit the Project description (Описание на проекта) field; up to 1000 characters.
• Files: click Attach files (Прикачи файлове), tick or untick files, click Attach (Прикачи).

What partners still in the tender receive (in-app only, no e-mail):

• Name or note change: "The offer request "{requestName}" was updated — project "{projectName}"" (Запитването „{requestName}“ беше променено…).
• Deadline change: "The deadline of the offer request "{requestName}" moved: {from} → {to} — project …". Partners that have not answered yet also get a new "Needs action" reminder with the new deadline.
• File change: "The documents of the offer request "{requestName}" changed (added: {added}, removed: {removed}) — project …". Read access follows the change.

On the partner's side, the Offers page shows a line "The request was changed on {date}: deadline {from} → {to}, name "A" → "B", the note".

Revising a request

After sending, the positions of a request are locked so that every partner prices exactly the same scope. When the scope changes (positions added or removed, quantities re-measured), you do not need to withdraw and start again. A revision creates a new version of the same request from the current BoQ, sends it to every partner still in the tender, and closes the previous version as replaced.

Revise only when positions change. For name, deadline, note or files, edit the request directly.

How to revise a request

1. Open the BoQ the request was created from, then open the request panel (Related → Outgoing bid requests → the request).
2. Click Revise the request (Ревизирай запитването).
3. The current BoQ enters selection mode with the request's positions ticked. Tick new positions and untick the ones you no longer need.
4. Click Save (Запази). An empty selection is refused: "Select at least one line for the new request."
5. The dialog Revise "{requestName}" (Ревизия на „{requestName}“) opens. It cannot be closed by clicking outside. Review it (see below).
6. Click Revise and send (Ревизирай и изпрати), or Back (Назад) to change the selection.

The toast "The request was revised and sent again." confirms it. The panel switches to the new revision. If the revision fails, you see "The revision failed."

1. The subtitle says a new request is cut from the current BoQ, which BoQ version gets locked, and that the current request closes as superseded.
2. The counters Added (Нови), Removed (Премахнати) and Unchanged (Без промяна).
3. The lists Added lines, Removed lines and Unchanged lines.
4. Sent again to (Изпраща се наново на) lists the partners who get the revision.
5. Revise and send (Ревизирай и изпрати) confirms; Back (Назад) returns to the selection.

What the revision preview shows

• "A new request is cut from the current BoQ (locks version {version}); the current one closes as superseded."
• Counters "Added: N", "Removed: N", "Unchanged: N", and the lists Added lines (Добавени позиции), Removed lines (Премахнати позиции), Unchanged lines (Позиции без промяна).
• If nothing changed: "The lines do not change — the revision only sends the request again."
• Lines no longer in the BoQ (remove them from the selection): positions deleted from the BoQ meanwhile. You cannot confirm until you remove them.
• Sent again to (Изпраща се наново на): every active partner. Next to partners who had accepted: "· the offer is carried over with the unchanged lines' prices". With no active partners: "No active partners — the new request stays a draft."

What a revision does

• Creates revision {n+1} with the same name (shown as "{name} · revision {n}"), note, deadline and attached files.
• Locks the current BoQ version again; your next BoQ edit opens a new version.
• Invites the same active partners. Partners who declined, were withdrawn or were awarded nothing are not invited.
• Closes the previous version as Closed · replaced (Приключено · заменено). Its offers are archived as superseded, not deleted. Awards without a contract are released.
• For partners who had accepted, carries their offer over to the new revision automatically, with the prices of the unchanged positions. New positions are unpriced.

What partners see after a revision

Each active partner gets an in-app notification: "The offer request "{requestName}" was revised (added: {added}, removed: {removed}, unchanged: {kept}) — project …". No e-mail is sent for a revision. On its Offers page the partner sees a card "The client revised the request: +{added} added, −{removed} removed, {kept} unchanged." with the carried offer labeled "Carried over from revision {n}", which it reviews and sends. A partner that had not accepted yet must accept the new revision. If a partner opens the old version, it sees "The client revised this request — answer the new version." See Preparing and submitting an offer.

When you cannot revise

Revisions in the lists

All revisions of a request stay together. In the BoQ's list panel only the current revision shows, marked current (текуща); older ones are under Previous revisions ({count}) (Предишни ревизии). Each revision's panel links to its neighbors: "← Revision of "{requestName}"" and "Superseded by "{requestName}" →". On the project list, older revisions are dimmed and tagged superseded (заменена). On the comparison screen of a revision, Compare with the previous round (Сравни с предишния кръг) puts each partner's previous offer next to the current one. See Comparing offers.

Withdrawing a request

How to withdraw the request from one partner

1. In the request panel, expand the partner's card.
2. Click Withdraw (Оттегли).
3. The dialog Withdraw the request from {partnerName}? says: "Only this partner is told. Their offer is archived, not deleted. The request stays open for the others."
4. Optionally type a Reason for the partner (optional) (Причина за партньора (по желание)), up to 500 characters.
5. Click Withdraw (Оттегли).

The toast "The request was withdrawn from the partner" confirms it. The partner gets "The offer request "{requestName}" was withdrawn by the client: "{reason}" — project …" in the app. Its awards are released, it loses access to the attached files, and its offers move to its archive. The request stays Sent, even if no active partner remains. A withdrawn partner cannot be invited again to the same request.

How to withdraw the request from everyone

1. In the request panel click More actions (⋯, Още действия) → Withdraw request (Оттегли запитването).
2. The dialog Withdraw the request from everyone? (Да се оттегли ли запитването от всички?) says: "Every partner still in the tender is told it was withdrawn. Their offers are archived, not deleted. The request closes."
3. Optionally type a reason for the partners.
4. Click Withdraw (Оттегли).

The toast "The request was withdrawn" confirms it. The request becomes Closed · withdrawn (Приключено · оттеглено). Every active partner gets the in-app notification with your reason; partners who declined stay declined. Offers are archived, awards without a contract are deleted, and file access is revoked.

1. The title Withdraw the request from everyone? and the explanation of what happens.
2. The field Reason for the partner (optional); the text appears in the partners' notification.
3. Withdraw (Оттегли) confirms; Cancel (Отказ) closes the dialog without changes.

Closing a request

Closing ends a request without notifying anyone. Because nobody is told, closing is allowed only when no partner is still waiting for an answer from you: after the deadline, or when every partner has declined.

1. In the request panel click More actions (⋯) → Close request (Приключи запитването).
2. The dialog Close the request (Приключване на запитването) says "Nobody is notified. Choose why it closes."
3. Click the reason: Every partner declined (Всички партньори отказаха), enabled only when no partner is still active, or The deadline passed (Срокът изтече), enabled only after the deadline.

When a reason is unavailable, the dialog explains: "Closing notifies nobody, so it is only possible after the deadline or once everyone has declined. To end a request with active partners, withdraw it — they will be notified." The request becomes Closed · all declined or Closed · expired.

Refusals: "The request's deadline has not passed yet."; "Partners are still active in the request — withdraw it to notify them."

Which action to use

A request also closes by itself as Closed · awarded when every position is awarded and every awarded offer has a signed contract.

Error messages

Common questions

Related

• Creating and sending an offer request
• Comparing offers
• Awarding (whole or by line items)
• Preparing and submitting an offer
• Contracting schedule and packages