Create a tender

The tender is where a need turns into a procedure. Whatever stays unclear here costs you time in the question round and comparability in the evaluation.

Capture

A multi-step assistant walks through creation; documents are attached directly. Uploads and deletions are logged — removing a file stays visible too.

You do not need the whole form for a correction: individual fields can be edited directly in the view.

Duplicate instead of templates

There are no templates. Instead you duplicate an existing tender.

That sounds like less and is more in practice: a copy starts from real content that has already worked once, rather than from a scaffold of placeholders. For recurring purchases, deliberately keep one “good” tender and copy it each time.

Internal approval

Publication is preceded by internal approval. A rejection is documented with a reason — not a formality, but the moment an audit looks at most often.

Budget time for it. It is the most common reason a tender goes out later than planned.

Inviting suppliers

You invite — there is no open self-registration through which somebody applies to your tender unasked. Invitees can also be added or removed afterwards.

If your organisation has enabled the access request form, unknown suppliers can get in touch. It creates no account; it sends a message to procurement, and you decide.

When something changes

A change notification to all invitees is triggered manually — it does not happen by itself when you swap a document.

Make it a rule: every change after publication gets announced. A supplier pricing an outdated version submits an offer you cannot use, and both sides did the work for nothing.

Keeping an overview

Filters and search span all tenders. Completed ones are hidden by default, which keeps the list short; anyone looking for them can show them.