Reference 19 November 2026

The fields of a defensible needs memo

Nine fields, each with its legal basis. If all of them are filled in, the line in the plan has something to stand on when it is checked.

01

Identification

The issuing department, the registration number and date, the person drafting it and the person approving it.

02

The need

A description of the objective need and why it arises now — not the name of the product, but the need.

03

Quantities and price

The quantity, the unit price and the total estimated price, excluding VAT.

Legal basis: GD 395/2016, art. 3(1)

04

Method of determining the value

An updated unit or total price, from market research or on a historical basis — with the source and the date.

Legal basis: GD 395/2016, art. 2(5)(c)

05

History and aggregation

What was purchased for identical or similar uses during the budget year, and how it affects the estimated value.

Legal basis: GD 395/2016, art. 17(2); Law 98/2016, art. 20

06

Technical specifications

The requirements held by the requesting department, sent together with the memo.

Legal basis: GD 395/2016, art. 2(5)

07

Timing

The date by which the need must be covered and, if it replaces a contract, that contract’s expiry date.

08

Proposed funding source

The funds allocated to the purpose and their budget position.

Legal basis: GD 395/2016, art. 2(5)(d)

09

Priority

The priority level, used both in the initial version and at revisions.

Legal basis: GD 395/2016, art. 12(3)(b)

The field most often missing

Of the nine, the one most often missing is the history. A memo that says what it wants to buy but not what has already been bought for the same need during the budget year leaves aggregation undocumented. And aggregation follows identical or similar uses, not the CPV code: two different codes covering the same need add up.

The second most often omitted is the method of determining the value. A figure without a source and a date cannot be defended, and if the choice of procedure depended on it, the procedure is discussed too.

Frequently asked questions

What is a needs memo?

A needs memo is the internal document through which a department of the contracting authority justifies its need to purchase something: it describes the objective need, the quantities, the estimated value and the method by which that value was determined. It is the starting point of every line in the annual procurement plan.

Who drafts the needs memo?

The department that has the need drafts it, not the procurement department. The requesting department is the one that knows the objective need and holds the technical specifications; the procurement department takes them over and chooses the procedure.

Is there a mandatory standard template?

The legislation does not impose a set template, but it does impose the content: the elements from Government Decision no. 395/2016 must be present. A memo that does not show the method of determining the value, or the history of similar purchases, is incomplete however neatly it is formatted.

Why must the method of determining the estimated value be written down?

Because an audit checks not only the figure but how it was reached. An estimated value without a source and a date cannot be defended, and if the choice of procedure depended on that value, the choice of procedure becomes questionable too.

How does the memo relate to the direct purchase threshold?

The memo is where what has already been bought for the same need during the budget year is recorded. Aggregation follows identical or similar uses, not the CPV code, and if the history does not appear in the memo, exceeding the threshold is discovered only at audit.

Legal basis

  • Government Decision no. 395/2016 — art. 2(5), art. 3(1), art. 12(3)(b), art. 17(2)
  • Law no. 98/2016 — art. 7, 11, 20

Informational material, reflecting legislation and practice as at 19 November 2026. It does not constitute legal advice.