// 19.11.2026
Tender specification for a mobile app or website
What a tender specification for a mobile app, web app or website should contain, which mistakes to avoid and how to estimate the contract value.
In Polish public procurement the description of the subject of the contract (OPZ) is the key document in a tender for a mobile app, web app or website. Bidders price the work from it and the authority accepts the system against it. Here are the elements worth including and the mistakes worth avoiding.
Why the specification matters so much
Procurement law requires the subject of the contract to be described unambiguously and exhaustively, in a way that does not hinder fair competition. In practice the quality of the specification decides whether bids can be compared, how many questions bidders ask and whether both sides understand the scope the same way at acceptance.
What a specification for an app or website should contain
- Purpose and context – what problem the system solves and who will use it.
- User roles – e.g. resident, office employee, administrator.
- Functional scope – modules and features, ideally with priorities (required and optional).
- Platforms – iOS, Android, browsers and minimum OS versions; native or cross-platform.
- Admin panel – what staff should be able to edit without the contractor.
- Integrations – line-of-business systems, maps, payments, sign-in, with a description of available interfaces.
- Non-functional requirements – performance, security, GDPR, backups, audit logs.
- Accessibility – WCAG 2.1 AA compliance and how it will be verified at acceptance.
- Hosting and maintenance – where the system runs, who is responsible for servers, bug response times, warranty.
- Copyright and source code – licensing scope, source code handover, technical documentation.
- Stages and acceptance – a timeline and measurable acceptance criteria for each stage.
- App store publishing – whose App Store and Google Play accounts, who handles updates.
Common mistakes in app specifications
- descriptions so general (“the app should let residents contact the office”) that every bidder reads them differently,
- naming a specific technology or product without justification, which restricts competition,
- no requirements for maintenance and updates for new iOS and Android versions,
- no acceptance criteria for accessibility, so WCAG remains a declaration only,
- leaving out source code rights, which makes changing contractors later difficult,
- an unrealistic timeline that squeezes UX design, development and testing into a few weeks.
How to estimate the contract value
A reliable estimate requires splitting the scope into modules and stages. Workshops with users and market research, such as asking several contractors to price a draft specification, help. The more precise the description, the lower the risk that bids exceed the budget or the procedure has to be cancelled.
Who can prepare the specification?
The authority's own team or an external adviser can prepare it. Experience building similar systems helps, because the adviser knows the contractor's costs and risks. Mind the conflict of interest, though: if the adviser later wants to bid, the authority must ensure this does not distort competition (Article 85 of the Polish Public Procurement Law). It is best to settle this at the very start.
Summary
A good specification saves time and money at every stage, from bidder questions to acceptance and maintenance. If you are planning a contract for a mobile app, web app or website, see our tender specification service or get in touch.
FAQ
Should the specification name a technology?
Not without justification. It is better to describe requirements such as platforms, performance and integrations, and leave the technology choice to the contractor.
Should WCAG requirements be included?
Public bodies are required to ensure accessibility, so a WCAG 2.1 AA requirement and how it will be checked at acceptance belong in the specification.
How long does it take to prepare a specification?
Usually two to several weeks, depending on the size of the system, the number of integrations and the availability of people on the authority's side.
Quote
Describe your project and we will come back with questions and a plan
No commitment. The more detail, the more accurate the first estimate.
- A short description of the goal and users is enough to start
- We reply with clarifying questions and a proposed set of stages
Prefer email? info@flexisoft.pl