Emergency procurement policy
Emergency procurement may be used only when delay creates a material operational, safety, legal, or financial risk. The requester must document the emergency, why normal competition was impractical, vendor selection, price reasonableness, and approving authority. Complete retrospective documentation promptly. Repeated emergencies for the same need should trigger planning and control review.
Related Articles
Procurement competition and quotation policy
Purchases should follow the organization’s quotation and competition thresholds. RFQs must describe the same scope to each invited vendor and allow a reasonable response period. Evaluation must consider price, quality, delivery, capacity, risk, and ...
Managing procurement contracts
Audience: Procurement and contract-management teams Contracts hold your vendor agreements in one place, with their value and expiry visible. Creating a contract Go to Procurement → Contracts. Select Create Contract. Record the vendor, the agreement ...
Understanding the procurement workflow
Audience: Requesters, procurement teams, approvers, and finance teams Spendive's procurement module follows a chain from intention to payment. Each stage has its own page, and each produces a record the next stage draws on. The chain Approval in ...
Record retention and deletion policy
Retain requests, approvals, documents, procurement records, payments, accounting entries, and audit history for the period required by law and organizational policy. Do not delete records to conceal errors or bypass workflow. When deletion is ...
Business expense policy
Business expenses must be necessary, reasonable, properly authorized, and supported by evidence. Personal, duplicate, fictitious, or inadequately explained expenses are prohibited. Users must select accurate categories, dates, amounts, currencies, ...