Why Use the Native Windows App for Your Tender Desk?
The Tenders-SA Desktop app is a focused Windows 10/11 workspace, not a replacement for the web platform. Learn what it does, what stays on the web, and how the security and offline model actually work.
A browser is a general-purpose tool. A bid desk is a focused one. The Tenders-SA Desktop application exists for the person who spends most of the working day inside a tender pipeline and wants the workspace to behave like an application, not another tab. It is a native Windows 10/11 shell around the Tenders-SA workflows, with a local cache, a command centre and desktop notifications.
It is not a different platform, a separate account or a fully offline clone of the website. This article explains what the desktop app actually does, what stays on the web, how the security model works, and when the browser is still the better choice.
What the Desktop App Is
Tenders-SA Desktop is a Windows application packaged from the separate desktop repository and published as GitHub Releases. The current release is version 0.1.0, a 64-bit build for Windows 10 (version 1709 and later) and Windows 11. The offline installer embeds the WebView2 runtime and is approximately 267 MB, so installation does not require an internet connection.
- It signs in with your existing Tenders-SA account. There is no separate desktop account.
- It uses the same platform data. The desktop is a client, not a separate database.
- It is a native Windows shell with a local SQLite cache, a command centre and desktop notifications.
- It is not a mobile app and there is no macOS or Linux build.
"
What Works on Desktop
| Module | What it does |
|---|---|
| Command Centre | Dashboard with active tenders, pipeline value, closing deadlines and market activity |
| Tender Radar | AI-powered tender matching and recommendations |
| Tenders | Browse and search available tenders |
| Opportunities | Saved and tracked tender opportunities |
| Application Workspaces | Assess, plan, draft, review and track tender response work |
| Calendar | Visualise deadlines and milestones |
| Tasks | Track action items across applications |
| Company Profile | Manage company details, registration and compliance |
| Company Document Vault | Secure storage for tender documents and certificates |
| Supplier Intelligence | Research suppliers, awards and B-BBEE status |
| Procurement Officers | Directory of government procurement contacts |
| Notifications | Platform alerts for deadlines, awards and updates |
| Settings | Application configuration and account management |
The list matters because it shows the desktop app is built around the daily bid workflow, not the full platform. The Command Centre is the app shell: it brings the pipeline, deadlines and market activity into one view.
What Stays on the Web
| Module | Why it is web-only for now |
|---|---|
| Standalone Proposals | A separate proposal module beyond the current application-workspace drafting flow |
| JV and Partner Network | Joint venture and partner management |
| Buyer Intelligence | Buyer and department research |
| Award Intelligence | Award tracking and supplier performance |
| Reports | Analytics and reporting dashboard |
This is not a limitation to hide; it is a scope decision. The desktop app focuses on the tender desk. If your week includes buyer intelligence, award analysis, JV management or formal reporting, you will still use the web platform for those. A realistic workflow moves between the two.
The downloads page lists the current release and the feature status. The platform pages for buyer intelligence and the leaderboard remain the place for the deeper research views.
The Offline and Local-Cache Model
The desktop app is described as offline-capable, but that phrase needs precision. The installer embeds WebView2 and the local SQLite cache stores bounded records, local file references, pending sync operations and preferences. That supports interrupted connectivity and lets the app reopen with local state.
- What works offline: opening the app, viewing cached records, working with local references and queuing some operations.
- What needs a connection: live tender data, new matches, current documents, account changes and anything that requires the server.
- What the cache is not: a full offline copy of the platform database or a guarantee that every action will sync perfectly.
Treat the cache as a resilience feature, not an offline mode. If you need to work on a plane, download the documents you need before you leave and treat the local copies as working copies, not as the source of truth.
| Data type | Available offline | What to expect |
|---|---|---|
| Recently opened tender records | Usually yes | Read from the local SQLite cache until the next sync |
| Saved opportunities and pipeline views | Usually yes | Cached until a live refresh replaces them |
| Local file references | Yes | The reference is local; the file must exist on the device |
| Queued actions | Sometimes | They may sync later, but conflicts must be resolved |
| New tender matches | No | Requires a live connection to the platform |
| Current documents and account changes | No | Requires the server; do not assume the cache is current |
Before a trip or a known connectivity gap, do three things: open the tenders and documents you will need, confirm the files are saved locally, and check the closing dates from the source document rather than from memory. Do not queue a critical submission action on the assumption that it will sync when you reconnect.
The Security Model in Plain Language
| Control | What it means for a bid desk |
|---|---|
| OS keychain | Credentials are stored in the operating system's protected store, not in a plain file |
| AES-256-GCM | Local data is encrypted at rest |
| Least-privilege capabilities | The app requests only the access it needs |
| Content Security Policy | The embedded web content is restricted to approved sources |
| SQLite local cache | Bounded local records, not an uncontrolled copy of everything |
| Account sign-in | The desktop uses your existing account and permissions |
No client can replace good account hygiene. Use a strong password, protect the Windows account, lock the device when you leave, and remove the app from a shared or lost device. If your organisation has device-management rules, apply them. The existing POPIA guide explains the data-protection expectations for tender documents and personal information.
Shared and Lost Devices
A desktop client changes the risk profile because it can cache records on the device. The controls are strong, but they assume the Windows account is protected. On a shared machine, use a separate Windows profile for each person and sign out of the app when the session ends. Do not rely on closing the window.
- Lost or stolen device: change the Tenders-SA password immediately and ask IT to disable the Windows account. The local cache is encrypted, but the account is still the first line of defence.
- Handover to a colleague: sign out, remove the local profile if your IT policy requires it, and confirm the next person signs in with their own account.
- Temporary contractor: give them a named account, not a shared login. Remove the account when the engagement ends.
- Device disposal: follow the organisation's wipe procedure. An encrypted cache is not a reason to skip the wipe.
Installation and Requirements
| Requirement | Detail |
|---|---|
| Operating system | Windows 10 (version 1709+) or Windows 11 |
| Architecture | 64-bit |
| Installer | NSIS .exe or MSI .msi |
| Size | Approximately 267 MB (WebView2 embedded) |
| Internet | Not required for installation; required for live data |
| Account | Existing Tenders-SA account |
| Source | GitHub Releases from the Tenders-SA desktop repository |
The embedded WebView2 runtime is the reason the installer is large. It also removes a common installation failure on locked-down machines that cannot download the runtime separately. If your IT team prefers an MSI for managed deployment, use the MSI asset from the release.
IT Rollout Without Surprises
The release publishes two installer assets: an NSIS .exe for a normal per-user install and an MSI .msi for managed deployment. Choose the MSI if your organisation uses Group Policy, Intune or another software-deployment tool. Choose the NSIS installer for a single coordinator who manages their own machine.
- Confirm the platform. The build is 64-bit only and targets Windows 10 version 1709 or later and Windows 11. A 32-bit machine cannot run it.
- Plan the download. The installer is approximately 267 MB because WebView2 is embedded. Allow for that on a metered or slow link.
- Allow the endpoints. The app needs the Tenders-SA API. If your process downloads installers from GitHub Releases, allow that host too. If a proxy blocks the API, installation may succeed but sign-in or data refresh will fail.
- Pin a version. Download the release asset you have tested rather than relying on an unattended link that always points to the latest build.
- Use per-user installs on shared machines. Each person signs in with their own account, and nobody shares a Windows login.
If installation fails, check the three usual causes in order: the Windows version or architecture, the installer permissions, and the proxy or endpoint access. If the app opens but cannot load data, the problem is almost always connectivity or sign-in, not the installer. Uninstalling and reinstalling rarely fixes an account or network problem.
Before the rollout, get six answers from IT in writing. They take ten minutes and prevent most of the support tickets that follow a first install.
- Is the target machine 64-bit, and is it running Windows 10 version 1709 or later, or Windows 11?
- Will the install be per-user with the NSIS installer, or managed with the MSI?
- Does the proxy allow the Tenders-SA API, plus the GitHub release host if you download installers there?
- Which release version has been tested, and where is that asset stored?
- What is the policy for shared devices: separate Windows profiles, sign-out, or no local install?
- Who removes access when a coordinator leaves or changes role?
When the Desktop App Wins
- You live in the pipeline. A bid coordinator who moves between Radar, Opportunities, Workspaces, Calendar and Tasks all day benefits from a dedicated window and desktop notifications.
- Connectivity is unstable. The local cache and queued operations reduce the friction of a dropped connection.
- You need focus. A dedicated app is easier to keep open alongside email and documents than a browser tab that competes with twenty others.
- You manage documents locally. Local file references and the document vault workflow fit a desktop file system.
- You want the command centre. A single view of active tenders, pipeline value and deadlines is useful for a Monday review.
A Worked Desktop Workflow
A bid coordinator starts the day in the Command Centre. The dashboard shows three tenders closing within ten days, a pipeline value that is lower than last month and a new high-match opportunity.
- Radar: The coordinator opens the new match, reads the explanation and saves it to Opportunities.
- Opportunities: The saved tender is assigned to the bid lead and added to the pipeline.
- Application Workspace: The team opens the workspace, links the tender documents and starts the returnable matrix.
- Document Vault: The compliance lead checks the current B-BBEE and COIDA evidence and uploads a replacement for an expiring certificate.
- Calendar and Tasks: The closing date, briefing and review gates are added, with owners and reminders.
- Notifications: Desktop alerts keep the deadline visible even when the app is in the background.
- Web hand-off: For buyer intelligence, award analysis or a formal report, the coordinator opens the web platform.
This is the intended division of labour. The desktop app is the operating surface for the bid desk; the web platform is the deeper research and reporting surface.
Desktop or Web: Which Surface for Which Task
The useful question is not "which is better" but "which surface fits this task". The table routes the common bid-desk tasks to the surface built for them.
| Task | Better surface | Why |
|---|---|---|
| Monday pipeline review | Desktop Command Centre | One view of active tenders, pipeline value and closing deadlines |
| Tender discovery and match review | Desktop Tender Radar | An always-present workspace with desktop notifications |
| Active bid drafting and returnable tracking | Desktop Application Workspace | Documents, tasks and dates stay together in one window |
| Compliance document checks | Desktop Document Vault | Local file references and expiry visibility |
| Buyer and department research | Web Buyer Intelligence | The deeper research view remains web-only |
| Award and supplier analysis | Web Award Intelligence | Award tracking and supplier performance are web-only |
| JV and partner management | Web JV suite | Partner matching, proposals and agreements remain on the web |
| Formal reports and exports | Web Reports | Reporting and analytics are web-only |
| Working with unstable connectivity | Desktop cached records | Cached records and queued operations reduce friction |
| Account and app settings | Either | Both surfaces use the same account and permissions |
Four facts prevent most confusion. The desktop app uses your existing Tenders-SA account, not a separate login. It reads the same platform data, not a copy. It is offline-capable, not a full offline clone. And it is a Windows 10/11 64-bit desktop application, not a mobile or cross-platform build.
Where the Desktop App Stops
The desktop app is a workflow surface, not an autonomous bid manager. It does not guarantee a compliant bid, approve a submission, or replace the judgement of the bid lead. It also does not remove the need to check the tender document itself. The app can show you the deadline and the returnables; it cannot tell you that an addendum changed a mandatory requirement unless that change has reached the platform data.
- It does not store a complete offline copy of the platform database.
- It does not replace buyer intelligence, award analysis, JV management or formal reporting.
- It does not replace the buyer's submission portal or sign documents on your behalf.
- It does not run on macOS, Linux or mobile.
A Two-Week Pilot
Do not install it on every machine on day one. Run a two-week pilot with the person who spends the most time in the pipeline.
Measure minutes, not impressions. For the first week, use the web platform and record three timings: how long it takes to review the active pipeline, how long it takes to find a specific compliance document, and how many times the coordinator checks a deadline manually. Repeat the same three measurements in the second week on the desktop app, with the same tenders and the same person.
| Measure | How to record it | Pass signal |
|---|---|---|
| Pipeline review time | Stopwatch three runs, use the median | Shorter than the web baseline |
| Document retrieval time | Seconds from question to open document | Shorter than the shared-drive or web route |
| Manual deadline checks | Count per day | Fewer checks because notifications are trusted |
| Context switching | Count apps and tabs used per bid | Fewer surfaces open at once |
| Connectivity friction | Count failed actions during a drop | Cached records stay usable |
| User preference | Structured interview at the end | The coordinator wants to keep it |
The pilot passes if at least two of the first three measures improve, the IT checks are clear, and the coordinator wants to keep using it. It fails if the app adds a login step, duplicates work or creates a second place to update the same information. A tool that saves five minutes but creates a reconciliation task has not saved anything.
Keep the checklist narrow. Install on one 64-bit Windows 10/11 machine. Sign in with the existing account. Review a set of tenders, disconnect, and reopen to confirm the cache behaves as described. Run one Monday review from the Command Centre. Move one live bid into the Application Workspace. Check a current and an expiring certificate in the Document Vault. Leave the app in the background before a deadline to test notifications. Then open buyer intelligence or reports in the browser to confirm the hand-off.
The desktop app also fits the team workflow described in managing tender submissions as a team. The handover is easier when the pipeline and the bid file are open in the same place.
Conclusion: A Focused Surface for a Focused Job
The Tenders-SA Desktop app is valuable because it is focused. It puts the tender pipeline, Radar, workspaces, documents, calendar and tasks into a native Windows surface with a local cache and desktop notifications. It does not try to be the whole platform, and it does not pretend to be fully offline.
If your bid desk lives in the pipeline, install it on the coordinator's machine and run the two-week pilot. Keep the web platform for buyer intelligence, award analysis, JV work and reporting. Use the downloads page for the current release and the Tender Radar guide for the discovery workflow that feeds the desktop.
Tags
Based on this article's topics, here are some current tenders that might interest you
Tenders are hereby invited from capable and experienced service providers for the above tender. 1. Only tenderers who have provided the following mandatory information and documents to be used to evaluate the tenderers’ responsiveness will be considered for further evaluation on functionality: 1.1 Only service providers that are registered on the Central Supplier Database will be considered for the awarding of this request for quotations and a copy of CSD report not later than three months should be attached. 1.2 Price(s) quoted must be firm, VAT and other taxes inclusive and valid for at least thirty (30) days from the date of your offer. 1.3 No tenders shall be considered from a person/s who are in the service of the state. 1.4 Service providers are required to fully complete the attached MBD forms and submit together with their written tenders. 1.5 Attach a bank account confirmation letter with bank stamp not older than three months accompanied with an affidavit confirming the business bank account details - if the banking details are not verified on the CSD report. 1.6 Attach certified copy of identity documents (ID) of company directors. 1.7 Attach certified copy of the company registration certificate issued by the Companies and Intellectual Property Commission (CIPC). 1.8 Valid SARS PIN must be attached. 1.9 Attach verifiable Municipal Account/s not older than three months for both the tenderer and entity owner/s or director/s. In areas where the municipalities are not issuing municipal accounts, attach valid lease agreements or confirmation of residence or address for both the tenderer and entity owner/s or director/s issued by a relevant authority not older than three months. 1.10 Joint Venture or Consortium Agreement if applicable 1.11 All completed tender documents must be duly signed and submitted on the PDF document that has been issued. All the certified documents as stated must not be older than three months. 2. The tender will be evaluated on 80/20 preference point system in terms of the Preferential Procurement Policy of the Ehlanzeni District Municipality. The policy preference point system will be applied as follows: 2.1 The 80 points will be for price; and 2.2 The 20 points will be allocated for the specified goals on a proportional or pro rata basis as follows: POINTS FOR CONTRACTING AN ENTERPRISE OWNED BY HISTORICALLY DISADVANTAGED PERSONS OR INDIVIDUALS HISTORICALLY DISADVANTAGED PERSONS OR INDIVIDUALS POINTS ALLOCATION SOURCE DOCUMENTS REQUIRED TO CLAIM POINTS 100% black person or people owned enterprise 5,00 A copy of a Full CSD report not older than 3 months More than 30% woman or women shareholding or owned enterprise 2,00 more than 30% youth shareholding or owned enterprise 2,00 More than 30% people living with disability shareholding or owned enterprise 2,00 A copy of a Medical Certificate to confirm disability or stated on CSD report. More than 30% military veteran’s shareholding or owned enterprise 2,00 A copy of a Full CSD report not older than 3 months POINTS FOR IMPLEMENTING OF RDP PROGRAMMES Enterprises regarded as *EMEs located within the Ehlanzeni District Municipality area of jurisdiction 2,00 ? A copy of a Full CSD report not older than 3 months NB: Points will only be awarded if the CSD physical address is the same as the address for the proof of residence required in 1.9 above. B-BBEE level 1 contribution 5,0 ? Certified Valid BBBEE certificate; or ? Certified Valid EME and SME a sworn affidavit; or ? Certified Valid CIPC issued certificate confirming annual turnover and level of Black Ownership. TOTAL PREFERENCE POINTS TO BE CLAIMED 20,0 *EME’s are Exempted Micro Enterprise with an annual turnover of R10 million or less. Received tenders will be evaluated for responsiveness based on mandatory requirements, functionality and bidders who obtain a minimum of 70 points out of a possible 100 points. Tender documents can be viewed and downloaded at no cost on the Document Sharing and Collaboration Platform or Portal (NEPTUNE): http://edmservices.ehlanzeni.gov.za and National Treasury Portal from Monday, 02 November 2026. Further information regarding the downloading and uploading of documents will be explained at the compulsory briefing session. A compulsory briefing session will be held on Friday, 06 November 2026, at 10h00 at the Hectorspruit Wetland Precinct, Nkomazi Local Municipality (Meet at the Engen Garage). Where bids should be submitted - Completed tender and other returnable documents must be submitted only in PDF format on the Document Sharing and Collaboration Platform or Portal: http://edmservices.ehlanzeni.gov.za on or before Tuesday, 17 November 2026 not later than 12h00. Tender Documents received by telegram, fax and post will not be considered. Enquiries: Contact Person - ADMINISTRATION: Mr. S P Khumalo at 013 759 8573 [email protected] Contact Person – TECHNICAL: Mrs. R Ntusi at 013 759 8500 or [email protected] Employer: Acting Municipal Manager: Ms S S Madlopha Ehlanzeni District Municipality P. O. Box 3333, MBOMBELA 1200
DIGITAL PLATFORMS, MAINTENANCE, OPTIMIZATION, AND SUPPORT - South African
Appointment of a Service Provider for Provision of Microsoft Power Platform Licensing and the Design, Implementation and Support of the FPB Public Engagement and AI Chatbot Platform for Three (3) Years
THE APPOINTMENT OF A CONTRACTOR FOR THE DESIGN, SUPPLY, INSTALLATION, AND MAINTENANCE OF THE INTELLIGENT OPERATION CENTER AND AI PLATFORM FOR PRASA, AS AND WHEN REQUIRED, FOR A PERIOD OF 36 MONTHS.
PROCUREMENT OF A DIGITAL PLATFORM FOR IDEA MANAGEMENT AND PUBLIC PARTICIPATION 2028/29, 2029/30, 2030/31
SERVICING, DIAGNOSTIC TESTING, FAULT FINDING AND REPAIRS (HYDRAULIC AND STRUCTURAL) OF AERIAL PLATFORMS, CRANES, TAIL LIFTS, FORKLIFTS, WASTE COMPACTORS AND MISCELLANEOUS ASSET TYPES FOR THE CITY OF CAPE TOWN’S FLEET
Want to see all available tenders?
Browse All Tenders →Share this article
Why Use the Native Windows App for Your Tender Desk?
The Tenders-SA Desktop app is a focused Windows 10/11 workspace, not a replacement for the web platform. Learn what it does, what stays on the web, and how the security and offline model actually work.