Skip to content

Nema for Purchase request preparation

Prepare the purchase request with the required information.

Help requesters assemble a complete case before it reaches procurement. Nema drafts the packet. Budget owners and approvers keep every spending decision.

An example in Slack Illustrative

@Nema, prepare this purchase request using the current policy and details in this thread. Fill supported fields, list missing evidence and required approvals, and do not place an order.

Nema APP

Purchase request draft

  • Request: 12 research seats for the product team, beginning November 1.
  • Missing: total annual cost and the data-handling review.
  • The budget owner and procurement approver still need to review.

A starting point for your team's review.

Start with the purchase policy

Give Nema the current policy, request form requirements, approval thresholds, and routing rules. Include the requester, business need, proposed vendor, quantity, timing, and available quote. State which details may appear in the Slack channel.

The policy should determine the packet. A familiar vendor does not remove the need for a required security, legal, finance, or data review.

Build the request from evidence

Ask Nema to complete only fields supported by the supplied material. It can summarize the business need, compare the quote with the requested term, and calculate totals when currency and billing assumptions are clear. Show the calculation.

If the quote excludes tax or usage charges, keep that gap visible. A monthly price should not silently become an annual commitment without confirming the term and quantity.

Collect the missing pieces

Group missing information by owner and review path. The requester may need to explain expected use. IT may own a technical review. Finance may need a budget code. Procurement may need contract or vendor details.

Nema should not assign an approver from job title alone. It applies the policy and asks when the responsible person is unclear.

Review before submission

Post the draft in the authorized Slack thread. The requester verifies need and quantities, specialists add their reviews, and the budget owner confirms funding. Procurement decides whether the packet is complete and how to proceed.

This workflow does not approve spend, send payment, accept terms, or place an order. Those steps remain in the approved purchasing process.

Try a simple request

Choose a low-risk request with a clear quote and known budget owner. Compare the packet with what procurement actually requires. Remove redundant questions and add missing evidence to the reusable checklist before handling a more complex purchase.

Questions from purchasing teams

Can Nema choose a vendor?

It can organize supplied options against criteria the team provides. The accountable people make the selection and document the reason.

What if the quote is incomplete?

List the missing term, price component, or condition and keep the request in draft. The requester or procurement obtains clarification.

Does a complete packet mean approval?

No. It means the request is ready for the required reviewers. They retain the spending and risk decisions.

If reviewers return the request, preserve their specific reason. A missing quote, unclear owner, and rejected business case require different next steps. Nema can revise the packet once the requester supplies the needed evidence.

Start with one channel.

Add Nema to Slack, invite it to one channel, and ask it something. $50 in free credits, no card up front. If you would rather see it first, we will walk you through it.