Procurement Documents

Procurement Policy Template (Free, Word)

A free, editable procurement policy for private organizations, with roles, sourcing by value tier, a purchase approval workflow, rules for software and SaaS, three-way match and exceptions.

12 pages Microsoft Word Updated November 15, 2026
Download Template
Procurement Policy Template (Free, Word) preview
Procurement Policy Template (Free, Word)

Preview the first pages

See the structure before you download. The Word file has every section listed below, ready to fill in.

What's inside

The sections in the document, in order.

  1. Purpose and scope
  2. Definitions
  3. Roles and responsibilities
  4. Principles
  5. Sourcing method by value tier
  6. Sole source and emergency purchases
  7. IT, software and SaaS purchases
  8. Purchase approval workflow
  9. Contracts and signature authority
  10. Vendor onboarding

Use this procurement policy template to set the rules for how your organization buys goods, services, software and SaaS: who can ask, who approves, how much competition each purchase needs and what has to happen before an invoice is paid. It turns the steps in the procurement process guide into rules, from a request with budget approval through sourcing, the contract and purchase order, and receiving, to a three-way match before payment.


It's written for a private company or nonprofit adopting its first purchasing policy, or replacing one nobody follows. Every value tier has a [threshold] placeholder, because the right levels depend on your size, your spending and your controls, so you set them with finance. The purchase approval workflow is a section of the policy, with numbered steps and an approval routing table, so you can start with one document instead of a policy and a separate procedure.


Software and SaaS get their own section, because a card purchase or a free trial can put company data in a supplier's hands before anyone has read the terms. The policy requires IT and security review before purchase, at any value, and starts every request with the free software request form. Public bodies follow their own procurement laws, so check those rules first. The template isn't legal advice: have legal counsel review it before you adopt it.


What's inside this template


  • Purpose, scope and definitions, including how to measure purchase value over the full term, and a note for public bodies and federal grant recipients
  • Roles for the requester, budget owner, procurement, IT and security, legal and finance, and principles on fair competition, value over price alone, conflicts of interest, gifts and separation of duties
  • A sourcing table by value tier, from a single quote to several written quotes to a formal RFP, with [threshold] placeholders for your own values
  • Rules for sole source and emergency purchases, and for IT, software and SaaS: a request first, IT and security review before purchase, and no card or expense purchases of software that hasn't been reviewed
  • A purchase approval workflow from request to payment, an approval routing table by tier, and the approvals any purchase needs whatever its value
  • Contracts and signature authority, vendor onboarding, receiving and three-way match before payment, and records retention
  • An exception request form, rules for breaches, the policy owner, a review cadence and a version history

Download the editable Microsoft Word version below. The full text is on this page, so you can read it before you download.

How to use this template

Fill in the placeholders with finance and the people who will approve purchases, have legal counsel review the draft, and have your board or leadership adopt it. Delete the italic guidance before you publish the policy to staff.

  1. Set the tiers and thresholds. Decide with finance how many value tiers you need and where each one ends. Measure purchase value over the full term, including renewals and one-time fees, so a multi-year subscription isn’t approved as if it cost one year’s fee. Use the same thresholds in the sourcing table in Section 5, the routing table in Section 8 and the signature authority table in Section 9.
  2. Name the roles and approvers. Replace each role placeholder with a real job title: who runs procurement, who reviews IT and security, who sets up suppliers and who pays. In a small organization one person can hold several roles, but keep the requester, the approver and the person who pays separate, as Section 4.5 sets out.
  3. Check the rules that apply to you. Public bodies follow procurement laws that take priority over this template, and organizations spending federal grant money may have to meet the federal procurement standards that Section 1.3 points to. Regulated sectors and some funders add rules of their own. Have legal counsel review the policy before you adopt it.
  4. Connect the forms. Point each section at the form people will use: the software request form for IT requests, the vendor onboarding checklist for new suppliers and the contract review checklist before signature. For a purchase without competition, require a written justification, as the sole source justification guide describes.
  5. Adopt it, train people and review it. Have the policy approved and record it in the version history. Brief everyone who requests, approves or pays, including card holders, and set the review date in Section 14. Log every exception, and if one rule keeps needing them, change the rule at the next review.

The purchase approval process: who approves what

A purchase approval process sets who has to say yes before the organization commits money, and what each approver needs to see first. In this template it’s Section 8 of the policy: a numbered workflow from request to payment, an approval routing table by value tier, and a list of approvals any purchase needs whatever its value.

The workflow runs in this order: raise the request, get budget approval, confirm the tier and sourcing method, run the reviews and the sourcing, approve the award, sign the contract, set up the supplier, issue the purchase order, receive, match the invoice and pay. Who approves depends on the value and the risk:

  • The budget owner approves every purchase, confirming the need and that the money is in the budget.
  • Procurement confirms the tier and method before anyone asks a supplier for a price, and approves the award from the middle tier up.
  • Finance leadership, and then the chief executive or the board, approve the largest commitments, at values your policy sets.
  • IT and security approve every software, SaaS and cloud purchase before it’s made, whatever the price. Legal reviews nonstandard terms, and privacy reviews purchases that involve personal data.
  • Sole source, related-party and grant-funded purchases each add an approver, and an unbudgeted request goes to finance first, so the exception is visible in the record.
  • Nobody approves their own request or a purchase above their own limit, and a purchase whose value grows into a higher tier goes back for approval.
  • Approving a purchase doesn’t give authority to sign. Only the signatories the policy names can sign a contract or accept a supplier’s online terms.

The full template

This is the complete text of the Word document. Fill in the [bracketed] placeholders and delete the italic guidance before you use or send it.

Setting up this policy: replace each [bracketed placeholder], set
every [threshold] with finance, and delete anything that doesn’t apply
and all italic guidance before adoption. This template is for a private
company or nonprofit. It isn’t legal advice, so have legal counsel
review the policy before it’s adopted. Public bodies: read Section 1.3
first.

Item Details
Organization [Organization legal name]
Policy owner [Role, such as head of procurement or finance director]
Approved by and date [Board / Chief executive / Leadership team], [date]
Effective date and version [Date], [version number]
Next review due [Date]

1. Purpose and scope

1.1 Purpose

This policy sets how [Organization name] (“the organization”) buys
goods, services, software and SaaS, so that it gets value over the life
of each purchase, treats suppliers fairly, approves each commitment
before it’s made, protects its data and systems, and keeps a record of
why each purchase was made the way it was.

1.2 Scope

It applies to every employee, [board member, volunteer] and
contractor who buys anything for the organization or commits it to buy,
from any budget and by any payment method, including cards and expense
claims. It covers renewals and contract changes, and free tools and
trials that hold company data or need someone to accept the supplier’s
terms. It doesn’t cover [payroll and benefits, taxes, or grants the
organization awards].

1.3 Public bodies
and grant-funded purchases

Public bodies follow procurement rules set by law, regulation and
policy, which vary by jurisdiction and purchase value. If yours is a
public body, check those rules first: they take priority, and parts of
this template may not apply or may need to be stricter.

Federal grant money can bring federal procurement standards.
Under 2
CFR 200.317
, recipients and subrecipients other than states and
Indian Tribes follow 2 CFR 200.318 to 200.327. Among other things, 2 CFR
200.318
requires documented procurement procedures, written
standards of conduct covering conflicts of interest and records of each
procurement, and 2 CFR
200.320
sets procurement methods by value. Check the current text
and your award terms with counsel or the awarding agency.

Where grant or other restricted funds pay for a purchase, the
funder’s procurement rules also apply, and where they’re stricter, they
take priority. [Finance] confirms those rules before the first purchase
under each award.

2. Definitions

Term Meaning in this policy
Purchase value The total expected cost over the full term: every contract year,
expected renewals and options, one-time fees and expected usage charges,
[including / excluding] tax. Value tiers and approvals use this
figure.
Supplier Any business or person the organization buys from. “Vendor” means
the same.
Sole source A purchase from one supplier without competition because only that
supplier can meet the need. A single source purchase, where others could
supply but one is chosen for a documented reason, follows the same
rules.
Emergency purchase A purchase needed at once to protect people’s health or safety,
prevent serious damage to property or keep critical operations running,
where normal sourcing would make the harm worse. A deadline caused by
poor planning isn’t an emergency.
Contract Any agreement that commits the organization, including order forms,
statements of work, purchase order terms and online terms accepted by
clicking “I agree”.
Purchase order (PO) The organization’s formal order to a supplier: items or services,
quantities, prices, delivery dates, payment terms and a PO number to
quote on the invoice.
Receiving record The record of goods accepted or, for services, written confirmation
that the work was delivered or a milestone met its acceptance
criteria.
Conflict of interest A personal, financial or family interest, or a relationship, that
could influence, or appear to influence, someone’s part in a
purchase.

3. Roles and responsibilities

One person can hold several roles in a small organization. Keep
the separation of duties in Section 4.5 even then.

Role Responsibilities
Requester Checks what’s already available, raises the request and confirms
receipt. Doesn’t commit the organization to a supplier, accept its terms
or give it company data before approval.
Budget owner Confirms the need and the budget, and approves the spend. Never
approves their own request.
Procurement Confirms the tier and sourcing method, runs or supports sourcing,
negotiates, issues purchase orders, and keeps the contract record and
renewal calendar. [Without a procurement team: [role].]
IT and security Review every request covered by Section 7 before purchase, grant and
remove supplier access, and keep the IT asset records.
Legal Reviews contracts and online terms under Section 9, with [privacy
lead] for data processing terms.
Finance Sets up and changes supplier records, runs the three-way match, pays
invoices and sets card limits.
Policy owner [Role]. Keeps this policy current, decides how it applies and keeps
the exception register.

4. Principles

4.1 Fair competition

  • Compete purchases as Section 5 requires. Give every supplier in a
    competition the same information, deadline and chance to ask questions,
    and share each written answer with all of them.
  • Name one contact for each competition, write requirements around the
    need rather than one product, and never share one supplier’s prices or
    proposal with another.
  • Don’t split a purchase into smaller orders, or shorten its term, to
    bring it under a threshold.

4.2 Value over price alone

Choose on value over the full term, not on the lowest first-year
price. Weigh the price with quality, fit, service, security, the
supplier’s ability to perform and the cost of leaving. For software and
SaaS, include renewal increases, usage growth, implementation and exit
costs.

4.3 Conflicts of interest

  • Anyone with a conflict of interest in a purchase declares it in
    writing to [policy owner] and takes no part in that purchase or the
    contract that follows.
  • Everyone who requests, evaluates or approves purchases completes a
    declaration [every [interval]], and evaluators confirm they have no
    conflict before reading proposals.
  • A purchase from a related party, such as a business owned by an
    employee, a board member or their family, needs approval from
    [role].

4.4 Gifts and hospitality

  • No one involved in a purchase accepts gifts, hospitality or favors
    from a supplier in an open competition or negotiation with the
    organization.
  • At other times, [unsolicited gifts of nominal value, as defined in
    [gift policy],] may be accepted and are recorded in the [gift register].
    Cash and gift cards never are.

4.5 Separation of duties

No one person controls a purchase from request to payment. The
requester doesn’t approve their own request, and whoever sets up or
changes a supplier record doesn’t approve payments to that supplier.

5. Sourcing method by value
tier

Set each [threshold] with finance, from your own spending, risks
and controls. Public bodies and grant recipients must stay within
thresholds set by law or by the award.

Procurement confirms the tier before anyone asks a supplier for a
price. The tier depends on the purchase value of the whole purchase, not
of one order or one year.

Tier Purchase value Minimum sourcing method Records to keep
Tier 1 Up to [threshold A] One written quote or a published price, checked as reasonable The quote or price, and the PO or card receipt
Tier 2 Above [threshold A], up to [threshold B] At least [number] written quotes for the same defined requirement,
or a request for quotation (RFQ)
The quotes, a comparison and the reason for the choice
Tier 3 Above [threshold B] A formal request for proposal (RFP), scored against weighted
criteria set before responses arrive. Where the requirement is fully
specified and price decides, an RFQ or invitation to bid
The RFP, every response, the scores, the evaluation report and the
award approval
  • Existing contracts. A purchase within the scope of
    a contract competed or approved under this policy can go straight from
    an approved request to a PO.
  • More formal methods. Procurement can require more
    than the minimum, such as an RFP for complex software below [threshold
    B].

RFPhub’s RFP vs
RFQ vs RFI
compares the methods.

6. Sole source and
emergency purchases

6.1 Sole source

Above [threshold A], a purchase may skip the competition in Section 5
only with a written justification, approved before the organization
commits, on one of these grounds:

  • only one supplier can provide it, because of proprietary technology,
    exclusive rights or no authorized resellers;
  • it must be compatible with something already in use, such as an
    add-on to an existing system;
  • it’s follow-on work, where changing supplier would duplicate cost or
    cause unacceptable delay;
  • a competition was run and didn’t produce adequate responses.

The justification covers the need and its value, why only this
supplier can meet it and competition isn’t practical, the market
research done and alternatives considered, why the price is reasonable
and how long the arrangement lasts. Preference, familiarity and a
deadline caused by poor planning aren’t grounds. Where several resellers
sell a required brand, compete the price among them.

RFPhub’s sole source
justification guide
explains what a strong justification
contains.

6.2 Emergency purchases

  • [Role] may approve an emergency purchase without the sourcing in
    Section 5. Buy only what the emergency requires, and compete anything
    beyond it.
  • Within [period], the requester records what was bought, from whom,
    the cost, why it was an emergency and who approved it.
  • Software or IT services bought in an emergency get the review in
    Section 7.3 within [period], or are removed.

7. IT, software and SaaS
purchases

7.1 What this section covers

Hardware, software, SaaS, cloud services, IT and managed services,
including renewals and upgrades, AI tools and features that will process
company data, and free tools and trials that will hold company data,
connect to company systems or need someone to accept the supplier’s
terms.

7.2 Request first

Every request starts with the Software
Request Form
, sent to [intake address], before anyone commits to a
supplier, accepts its terms or gives it company data. IT first checks
whether the organization already owns something that meets the need.

7.3 IT and security
review before purchase

  • IT and security review every request covered by this section before
    the purchase is approved, at any value. A low-risk tool gets a short
    review, but a low price doesn’t remove it.
  • Security sets the supplier’s risk tier from the data it will hold,
    its access to company systems, how critical it is and how hard it would
    be to replace, and asks for the evidence that tier needs under [vendor
    risk policy]. RFPhub’s Vendor
    Security Questionnaire Template
    is one starting point.
  • The review starts before a product is chosen, while a finding can
    still change the decision. IT also reviews single sign-on, integrations
    and hosting.
  • No supplier gets company data or access to company systems until the
    review is approved.

7.4 No
card or expense purchases of unreviewed software

  • Cards and expense claims aren’t used to buy or renew software, SaaS
    or cloud services unless the request was approved under Section 7.3 and
    procurement allowed card payment. Finance declines expense claims for
    software that wasn’t approved.
  • No one accepts online terms or puts company data into a free trial
    without an approved request and authority under Section 9.
  • A tool found in use without approval is treated as a new request,
    then moved onto an approved contract or cancelled with written
    confirmation that company data was deleted.

7.5 Records and renewals

IT records each tool’s owner, license metric and quantity, renewal
date and notice deadline, and procurement puts the notice deadline in
the renewal calendar. The owner reviews usage and need before that
deadline.

8. Purchase approval workflow

This section is the purchase approval procedure. If you later
write detailed steps for your purchasing system, keep the two
consistent.

8.1 Steps from request to
payment

  1. Request. The requester checks for an existing
    contract or something already owned, then raises a purchase requisition
    in [purchasing system], or the Software Request Form for anything
    covered by Section 7, with the need, the full-term purchase value and
    the budget.
  2. Budget approval. The budget owner confirms the need
    and the budget. An unbudgeted request goes to [finance director or CFO]
    first.
  3. Tier and method. Procurement confirms the tier and
    sourcing method (Section 5), or an existing contract that covers the
    purchase.
  4. Reviews. IT and security review anything covered by
    Section 7, and legal and [privacy lead] review where Section 9 or the
    data requires it. Reviews run alongside sourcing and finish before the
    award.
  5. Sourcing. Quotes, an RFQ or an RFP, as the tier
    requires, or a sole source justification (Section 6.1).
  6. Selection. The requester, or the evaluation team
    for an RFP, chooses the supplier and records why.
  7. Award approval. The approvers in Sections 8.2 and
    8.3 approve the full purchase value.
  8. Contract. An authorized signatory signs after
    review (Section 9).
  9. Supplier setup. Finance sets up a new supplier
    under Section 10.
  10. Purchase order. Procurement issues the PO before
    the supplier delivers or starts work. [Invoices without a PO aren’t
    paid, except for [exempt categories].]
  11. Receipt. The requester records what was received,
    or confirms the service was delivered (Section 11).
  12. Match and pay. Finance runs the three-way match and
    pays on the agreed terms.
  13. Filing. Procurement files the records (Section 12)
    and updates the contract record and renewal calendar.

8.2 Approval routing table

Use the same thresholds as Section 5.

Tier (purchase value) Approvers Documents required
Tier 1: up to [threshold A] Budget owner Purchase requisition or card receipt; the quote or published price;
the Software Request Form for anything covered by Section 7
Tier 2: above [threshold A], up to [threshold B] Budget owner; procurement; [department head] Purchase requisition; [number] written quotes or RFQ responses,
compared, with the reason for the choice
Tier 3: above [threshold B], up to [threshold C] Budget owner; procurement; [finance director or CFO]; [executive
sponsor]
Purchase requisition or business case; the RFP, responses, scores
and evaluation report; contract review notes
Tier 3: above [threshold C] Every approver above, plus [chief executive / board] As above, plus [a board summary: need, options, recommendation,
full-term cost and risks]

8.3 Approvals needed at any
value

When the purchase involves Also approved by Document
Software, SaaS, a cloud service or an IT service IT and security The completed Software Request Form
Personal or regulated data [Privacy lead] or legal A data processing agreement, where the supplier processes personal
data
The supplier’s own terms, or nonstandard terms Legal Legal review notes
A sole source or single source Procurement and [role] Sole source justification (Section 6.1)
A related party or a declared conflict of interest [Policy owner] The declaration and how the conflict is managed
Grant or restricted funds [Grants manager or finance] Confirmation that the funder’s rules were followed

8.4 Approval rules

  • Approvals are recorded in [purchasing system] before the
    organization commits.
  • No one approves their own request or above their own limit. An
    approver who is away can delegate in writing, for a set period, to
    someone with at least the same authority.
  • If the purchase value grows into a higher tier, through a change
    order, added users or a longer term, it goes back for approval before
    the change is agreed.
  • Approving a purchase isn’t authority to sign. Only the signatories
    in Section 9 can sign.

9. Contracts and signature
authority

  • Only the signatories below may sign a contract, order form,
    statement of work or renewal, or accept a supplier’s online terms, for
    the organization. Anyone else sends the terms to procurement.
  • Procurement checks the business terms before signature, for example
    with RFPhub’s Contract
    Review Checklist
    , and checks the order form against what was
    negotiated. For software and SaaS, that includes the license metric,
    renewal price caps, service levels, data processing and security terms,
    exit terms and the auto-renewal notice deadline.
  • Legal counsel reviews the legal terms of [contracts above [threshold
    B], contracts on the supplier’s own terms, and any with personal data,
    indemnities or liability caps].
  • The signed contract, with its owner and notice deadline, goes into
    [contract repository] before the first PO.
Contract (purchase value) or type Authorized signatory
Up to [threshold A] [Role]
Above [threshold A], up to [threshold B] [Role]
Above [threshold B] [Role, after board approval above [threshold C]]
Nondisclosure agreements, data processing agreements and online
terms for an approved request
[Role or named delegate]

10. Vendor onboarding

Before the first PO or payment, finance sets up each new supplier
using the Vendor
Onboarding Checklist
[or your own]:

  • Supplier record. Finance, not the requester,
    creates it from the supplier’s legal name and tax form. For a US
    supplier, that’s IRS Form W-9, which provides its taxpayer
    identification number.
  • Bank details. Finance confirms new or changed bank
    details by calling the supplier on a number already on file, never one
    from the message that sent the details, and a second person approves the
    change before the next payment.
  • Checks. The review in Section 7.3 is complete, and
    a data processing agreement is in place where the supplier will process
    personal data.
  • Access. IT gives access only after approval, with
    named accounts, multi-factor authentication and the least access the
    work needs.

When a contract ends, IT removes the supplier’s access, and
procurement gets written confirmation that the organization’s data has
been returned or deleted.

11. Receiving
and three-way match before payment

  • Receipt. The requester checks goods against the PO
    and records what was accepted. For services, someone who can judge the
    work confirms in writing that it was delivered or a milestone accepted.
    For software, the edition, quantity and term must match the order
    form.
  • Three-way match. Before paying, finance compares
    the PO (what was agreed, at what price), the receiving record (what
    arrived or was accepted) and the invoice (what the supplier is billing
    for). If the items, quantities and prices agree, the invoice is paid on
    the agreed terms. If not, payment waits until [procurement or the
    requester] resolves the difference.
  • No PO. Except for [exempt categories], an invoice
    without a PO goes back to the requester, and a PO raised after the
    supplier was engaged is handled as a breach (Section 13.3).
  • Payment. Payments go only to the bank account on
    the supplier record.

12. Records retention

Procurement keeps a file for each purchase in [location]: the request
and approvals; the quotes or RFP documents, responses and scores; any
justification, emergency record or exception; conflict declarations; the
contract and POs; and the receiving records, invoices and payments. The
file shows why the method, supplier and price were chosen.

Files are kept for [period] after the contract ends or the final
payment, whichever is later, or longer where a law, tax rule, grant
award or legal hold requires it.

Set [period] with finance and legal counsel.

13. Exceptions

13.1 How to request an
exception

Anyone who needs to depart from a rule in this policy asks [policy
owner] in writing, before the organization commits, with the details
below. An exception covers one purchase or a stated period, and can’t
set aside a law, a funder’s rules or Section 4.3.

Item Details
Requester and date
Purchase, supplier and purchase value
The rule to set aside (section) and why it can’t be followed
Risks, and how they’ll be controlled
Purchases or period covered
Decision ☐ Approved ☐ Approved with conditions ☐ Not approved
Decided by, role and date

13.2 Who approves

[Policy owner] approves exceptions up to [threshold B], and [finance
director or CFO] above it, with IT and security for any exception to
Section 7. [Policy owner] keeps an exception register and reports it to
[leadership] every [interval].

13.3 Breaches

A commitment made without the approvals this policy requires, such as
a contract signed without authority, is reported to [policy owner].
[Role] decides whether to approve it after the fact, cancel it or
renegotiate it, and breaches can lead to action under [disciplinary
policy]. Anyone can report a suspected breach or fraud to [contact or
reporting line].

14. Policy owner and review

  • [Role] owns this policy. It’s reviewed every [interval], and after a
    change in the laws or funding rules that apply, an audit finding, a new
    purchasing system, a reorganization or a pattern of exceptions.
  • Each review checks that the thresholds, approvers, signatories and
    linked forms still fit, and that Section 8 matches how purchases are
    made.
  • Changes are approved by [board / leadership team] and recorded
    below, and everyone who buys or approves purchases is told.
Version Date Changes Approved by
[Version number] [Date] [Summary of changes] [Name and role]

Frequently asked questions

What should a procurement policy include?

Its purpose and scope, definitions, the roles of requesters, budget owners, procurement, IT and security, legal and finance, and principles such as fair competition and conflicts of interest. Then the sourcing method for each value tier, rules for sole source, emergency and software purchases, an approval workflow, signature authority, receiving and invoice matching, records retention, exceptions and a review date. This template includes all of them, with placeholders for your own thresholds and roles.

What is the difference between a procurement policy and a procurement procedure?

A policy sets the rules: what must happen, who approves and which sourcing method each purchase needs. A procedure sets out the steps people follow to meet those rules, such as how to raise a requisition in your purchasing system. This template puts a short purchase approval workflow inside the policy, so you can start with one document and write detailed procedures later.

How do you set purchase approval thresholds?

Start from your own spending: the usual size of your purchases, who is available to approve them and how much risk leadership will accept at each level. Set the tiers so routine purchases move quickly and larger or riskier ones get competition and senior review, and agree them with finance and, where your governance requires it, the board. Measure value over the full contract term, including renewals, and ban splitting a purchase to stay under a tier. Public bodies and grant recipients also have to work within thresholds set by law or by the award.

How often should a procurement policy be reviewed?

On a regular cycle that the policy owner sets and the policy records, and also whenever something changes: new laws or funding rules, an audit finding, a new purchasing system, a reorganization or repeated exceptions to the same rule. Each review checks that the thresholds, approvers and signatories still fit and that the workflow matches how people actually buy. Record every change in the version history.

What should a procurement policy say about software purchases?

It should cover software, SaaS and cloud services explicitly, including free trials, because clicking “I agree” can accept a vendor’s terms and put company data in the tool before anyone has reviewed it. The policy should require a request through IT, a security and privacy review before purchase at any value, and no card or expense purchases of software that hasn’t been reviewed. It should also make someone record each renewal’s notice deadline, so the organization can cancel or renegotiate in time.

Related guides and templates

Download Template

More procurement documents templates