YazSis Akıllı İhale:What is missing, who owns it, by when?
YazSis Akıllı İhale (smart tender management) is a tender and bid management platform designed for teams that take part in public tenders and private-sector bid invitations. From opportunity to delivery confirmation, every tender moves through a single workspace: tender specification requirements are tracked with their source, tasks and documents are tied to an owner, and approval is given to the final version of a bid, not to its name.
In developmentThe screens and workflow are ready in a clickable prototype; AI-assisted specification reading and connecting tender notice sources are on the roadmap. We are building it together with the first pilot companies.
Submission and delivery confirmation kept separate
Technical Specification v1Sample authority · HIS maintenance and support service
cl. 5.2 · ISO/IEC 27001 certificate, valid on the tender date
cl. 6.1 · At least 3 HL7/FHIR integration specialists with certification
cl. 8.3 · 24/7 support, response within 4 hours for critical faults
WITH SOURCE
Requirements12 items · 3 open
Addendum-1 received: the response time in cl. 8.3 dropped from 4 hours to 2 hours.“Ready to submit” is locked: the critical change has not been assessed yet.
Bid v3 · approval chain13 days to the bid deadlineTechnical complianceGeneral manager approval
7stages in the bid lifecycle: from draft to delivery confirmation
7user roles: from company administrator to observer
3starter templates: goods, services, construction works
v0.1clickable prototype, goes live with the pilot
THE JOURNEY OF A TENDER
From opportunity to delivery confirmation, in a single record.
Rules decide when each stage is finished; preparing a file does not count as submission, and submission does not count as delivery confirmation.
01
Assess the opportunity
Notices and invitations land in the opportunity pool; suitability, missing conditions and the rationale are visible. The decision to take part, or a reasoned “we are not participating”, goes on record.
02
Open the workspace
Tasks and a draft requirement list are created from the template; dates are calculated backwards from the bid deadline, and people are suggested based on workload.
03
Close the requirements
Each item is kept with its document, page and clause in the tender specification; a mandatory condition does not close until an authorized person marks it “met”.
04
Submit the bid for approval
Line items, commercial calculation and revisions are kept as versions; when the price or scope changes, the approvals given to that version are dropped.
05
Submit and confirm
The channel, time, version and proof of delivery are recorded; “submitted” and “delivery confirmed” are separate statuses.
FIVE PRINCIPLES
Rules catch the missed requirement and the last-minute surprise.
The platform’s backbone is built around the five problems tender teams run into most often.
Requirements with their source
Every mandatory condition is recorded together with the document, page and clause it comes from; an unknown condition is never treated as met.
Addendum lock
When a document changes, the affected tasks, line items and approvals are flagged; a bid cannot become “ready to submit” until the critical change has been assessed.
Version-bound approval
Approval is given to the exact version of a bid, not to its name; an approval given to v2 does not count as approving v3.
Separation of duties
Price and cost fields are visible only with separate permission; the person who prepared a bid cannot approve their own bid.
Document validity
The validity dates of company documents are checked against the tender date; a document that is about to expire shows up in advance.
WHAT IS IN THE PLATFORM
Everything that is in the prototype today, comes with the pilot, or is on the roadmap.
The badges are honest: “Ready in prototype” means the screen and flow work in the prototype, “Opens with pilot” marks the infrastructure needed for live use, and “Roadmap” marks a feature that has not been developed yet.
Ready in prototype
Opportunity pool and participation decision
A list of notices and invitations, filtering, a detail panel, missing conditions and a reasoned record of non-participation.
Ready in prototype
Workspace from a template
Task and requirement drafts from goods, services and construction templates; dates are calculated backwards from the bid deadline.
Ready in prototype
Requirement tracking
Met, not met and unverified statuses; the source chip shows the document, page and clause.
Ready in prototype
Addendum lock and readiness check
The move to “ready to submit” is blocked while a mandatory item is unverified, a task is unfinished or a version is unapproved.
Ready in prototype
Bid line items and commercial calculation
VAT, discount, exchange rate and profit margin calculation; comparison between revisions.
Ready in prototype
Approval chain and approval center
Sequential and parallel approval, version-bound approval, approvals dropped on revision, delegation and return reasons.
Ready in prototype
Meetings and minutes
Agenda, monthly calendar, confidential meetings, action items that turn into tasks from the minutes, and an add-to-calendar file.
Ready in prototype
Risk ranking and reports
Ranks active tenders by issue weight; recommended actions, print and Excel (CSV) export.
Opens with pilot
Persistent records and server-side permissions
A database, per-company data isolation, a tamper-proof audit trail and permissions enforced on the server.
Roadmap
AI-assisted specification reading
Drafting requirements from the tender specification; every suggestion is shown with its source and is not valid until an authorized person approves it.
Roadmap
Connecting notice sources
Importing opportunities from public and private-sector notice sources; source access is determined in discovery before the pilot.
Roadmap
Email and team notifications
Receiving invitations from a mailbox; reminders and approval notifications through email and team messaging apps.
SCREENS FROM THE PROTOTYPE
The shared workbench of the tender team.
The frames are taken from the clickable prototype; the flows work, the data is sample data.
ihale · prototip
Screen 01 / 07Overview
The “what is missing, who owns it, by when?” list; upcoming deliveries, pending approvals and the active tender portfolio on one screen.
The authority, company, person, tender registration number (İKN) and amount details on the screens are sample data.
AN HONEST STATUS
We tell you up front what is ready and what is on the way.
Today it is a clickable prototype: the data is sample data and is not persistent; live use starts with the pilot program.
The system does not submit a bid on your behalf and does not apply an e-signature; the submission and proof of delivery are only tied to the record.
AI suggestions will remain drafts when they arrive; mandatory conditions are not counted as “met” until an authorized person approves them.
A suitability score is not the probability of winning a tender; the platform makes no promise about outcomes.
The hosting region, the AI provider and the KVKK (Turkish personal data protection law) assessment are settled together with you before the pilot.
It does not interpret legislation; decisions on procurement rules stay with your team and your advisor.
FREQUENTLY ASKED QUESTIONS
What people ask about YazSis Akıllı İhale
What is YazSis Akıllı İhale?
It is a web platform designed for teams that take part in public tenders and private-sector bid invitations, so they can manage the opportunity, tender specification requirements, tasks, documents, bid versions and approvals in a single record. It is a YazSis brand.
What stage is it at today?
The screens and workflow are ready in a clickable prototype and run on sample data. A persistent database, server-side permissions and per-company data isolation come into play with the pilot program.
Does it pull tenders automatically from EKAP, Türkiye’s electronic public procurement platform?
Not today. In the prototype, tenders are added manually or from an invitation file, and a link to the source is shown for notices. Connecting public and private-sector notice sources is on the roadmap, and the access method will be determined in discovery before the pilot.
Does the AI prepare or submit my bid by itself?
No. Drafting requirements from the tender specification with AI is on the roadmap; even then, suggestions will be shown with their source and will not be valid until an authorized person approves them. Submitting and signing the bid always stays with you.
Where will our data be kept?
In the prototype, data is kept only in the browser and is not sent to a server. For live use, the hosting region, backups and AI provider are settled with you before the pilot, together with the KVKK assessment.
How do I join the pilot program?
Write to us through the contact form and choose the topic “YazSis Akıllı İhale”. We review your tender process and team structure together, then talk through the pilot scope and timeline.