Requisitions
A requisition is the internal request. A sourcing manager creates it. An approver approves or rejects it. After approval, a sourcing manager converts it into a sourcing event so the request and the RFx stay linked.
Approval can be a single step or a parallel route. Parallel approval records each required approver. The event does not move forward until the route is complete.
Create an event
The event wizard collects the type, title, envelope mode, dates, invited suppliers, and questions. Types are RFI, RFQ, RFP, ITT, and Tender. Envelope mode is single, two-envelope, or multi-envelope.
- Single envelope opens technical and commercial content together.
- Two-envelope keeps the commercial envelope sealed until evaluation has started.
- Set a scheduled unseal time when the bid must stay closed until that moment. If no time is set, an authorized buyer can unseal when the process allows it.
- Opening quorum defaults to one person. Set it higher, and name the opening committee, when two people must attest before the envelope opens.
Status path
An event moves from Draft to Pending approval, Approved, Scheduled, Published, Supplier Q&A, and Bid submission open. The app can move those statuses automatically when the published dates arrive. Evaluation, consensus, best and final, award approval, Awarded, contract, and Completed are buyer decisions. They are not moved by the clock. Cancelled is a buyer decision too.
The status button uses a readable label, such as Move to Bid submission closed, in the language of the workspace.
Addenda
Publish an addendum when the event changes after suppliers were invited. Each addendum is versioned. When the addendum requires acknowledgment, the supplier must confirm it in the portal before the bid can be submitted.
Public tenders
Mark the event visibility as public to list it on the public tender board while it is open. Events that are not public stay off that board. The board is for buyers inside the app. It does not replace the signed supplier portal link.
