How TenderFlow handles every tender at scale
The full electronic tender-management process used by large, multi-region tender teams — from opportunity capture through allocation, briefing, pricing sign-off, submission and award.
From opportunity to award
Every tender flows top-to-bottom through this pipeline. Decisions, branches and the role responsible for each action are shown inline.
Opportunities Spider Feed
automated · external APIDaily ingestion from gazettes and tender portals.
Central Email Account
automated · panel emailsTender notifications emailed by buying entities or panels.
Manual Capture
(Tender Manager)Tenders learned about from newspaper articles or other ad-hoc sources.
Tenders
Central collection point · one record per tender
Identification
(Tender Identifier)The Tender Identifier reviews each new tender and decides whether it is worth pursuing. Identifiers are optionally scoped to a region so each region only triages its own opportunities.
Do Not Pursue
Reason captured for audit. Tender stays in the database and can be reallocated later.
Daily Email Notification
9am · sent to Tender Group membersIdentifier picks the right Tender Group; a digest goes out at 9am the next morning.
Review
(Group Admin)Group Admin reviews the allocated tender. Three possible outcomes:
Do Not Pursue
Rejection reason / comments captured.
Loops back to Daily Email Notification
Tender is reassigned to a different Tender Group and re-enters the queue.
Continue to briefing
Group commits to bidding. Responsible Person, Admin Person, Proposal Person and Briefing Attendee are assigned.
Assign Briefing Session Attendee & Notes Template
(Tender Executor)A named Briefing Attendee and a Briefing Template from the Reference Library are recorded on the tender.
Tender Briefing Reminder Emails
automated · 2 days priorReminder lands in the attendee's inbox two days before the session, with the template attached.
Scan & Attach Briefing Notes and Briefing Document
(Briefing Attendee)Attendee uploads the completed notes back to the tender's Document Manager and ticks Briefing Notes Attached. The daily digest flags any tender with a compulsory briefing where notes are still missing.
Identify Mandatory Requirements & Risks
(Tender Executor)Mandatory requirements (returnables, certifications, B-BBEE level, CIDB grade) and any bid risks are captured on the Risks tab.
Proceed?
(Group Admin)Once the requirements and risks are clear, the Group Admin makes a go/no-go call.
Do Not Pursue
Reason / comments captured.
Proceed to pricing
Tender enters the costing phase.
Propose Pricing
(Tender Executor)Pricing built as structured line items — description, line type, cost category, unit, quantity, unit cost, unit price. Rate cards auto-fill role-based costs; deviations are tracked. Historical benchmarks from the API show where the bid sits relative to past winners. AI Extract, Gap Check and Generate Pricing Notes shortcuts pull the line skeleton, flag coverage gaps and draft narrative pricing notes against the tender document.
Pricing Review
(Group Admin)Group Admin reviews the proposed pricing. Three possible outcomes.
Do Not Pursue
Reason / comments captured.
Loops back to Propose Pricing
Tender Executor refines the pricing based on Group Admin comments.
Proceed to document prep
Bid pricing is locked in for the proposal.
Prepare Tender Documents
(Tender Executor)SBD forms, returnables, compliance pack — assembled via the Document Manager (WebDAV-mountable so editors work in Word/Excel without download/re-upload churn).
Prepare & Upload Proposal for Comments
(Tender Executor)Draft proposal goes up for Group Admin review.
Get Pricing Sign-off
(Account Administrator)Each Tender Group has a configurable bid approval threshold (default R500,000). When the bid amount climbs above that ceiling, the Pricing tab locks and the Account Administrator must approve the final amount. A later edit that pushes the bid above the most recently approved figure re-engages the lock automatically — no number can quietly slip past the threshold.
Submission Deadline Reminder Emails
automated · intensifying as deadline approachesMark Tender as “Submitted”
(Tender Executor)Tender physically or electronically submitted; status moves to Submitted.
Tender Opening Reminder Emails
automatedReminders prompt attendance at the public opening.
Capture Tender Opening Results
(Tender Executor)Attendees, their bid amounts and any commercial intel from the opening are captured on the Opening tab; status moves to Adjudication.
Followup Reminder Emails
automated · starts 2 weeks post-closingDaily nudges to chase the award outcome until it lands.
Capture Final Award Result
(Tender Executor)Final outcome: Awarded, Awarded To Other, Not Awarded or Missed. If awarded to another party, the winning company is picked from the captured opening attendees.
Lodge & Capture Appeal Details
(Tender Executor)Tick Appealed on the tender and record who lodged the appeal and the date it was submitted to the awarding institution. The full grounds for the appeal live in the tender's Notes / Document Manager so the audit trail is complete.
Capture Appeal Response & Outcome
(Tender Executor)When the awarding institution responds, the response date and full response text are captured on the Appeal tab. The Tender Executor then records one of three outcomes.
Original award stands
No change — the original award outcome holds. Appeal is on record for audit.
Award terms changed
Scope, value or evaluation outcome was adjusted. Update the relevant fields on the tender to reflect the new position.
Original award overturned
Award is set aside. If the tender now lands with the organisation, switch the final status to Awarded.
Process Completed
Outcome feeds win-rate intelligence for future bids in the same category / institution / province.
Who does what
Eight named roles split the work. Most people wear several hats — a Proposal Person is usually a Tender Executor first, and may also be the Responsible Person on the same tender.
Tender Identifier
Triages the incoming opportunity feed and decides which tenders to pursue. One Identifier per region is typical.
Group Admin
Head of a Tender Group. Accepts or rejects allocated tenders, assigns the team, oversees execution and sign-off.
Tender Executor
Standard group member who works on accepted tenders day-to-day — requirements, documents, proposal, submission.
Responsible Person
Owns one tender end-to-end through the lifecycle (WIP → Submitted → Adjudication → Award).
Admin Person
Completes the SBD / returnables paperwork and the compliance pack.
Proposal Person
Writes the technical and commercial proposal.
Briefing Attendee
Attends the compulsory briefing session on behalf of the group and uploads the completed notes back to the tender.
Reference Library Manager
Maintains the shared library of CVs, reference letters, rate cards, legislation, templates and panels.
Built for nationally-distributed tender teams
A small firm can have one person watching the feed and managing the work. That breaks the moment an organisation is geographically distributed, departmentally split or volume-heavy.
Right tender, right team
A Western Cape infrastructure tender never lands in the Gauteng professional-services team's inbox. Identifiers make the call once; routing happens for everyone downstream.
Decisions stay local
Each region's Group Admins — the people who actually know the local market, capacity and conflicts — own the accept / reject call. Head office is not a bottleneck.
Nothing falls through
Every accepted tender has explicit owners for paperwork, proposal writing and briefing attendance. Daily 9am digests guarantee newly allocated tenders land in front of the right group within hours.
Full audit trail
Every transition is stamped with who did it and when. Rejected tenders keep their reason — essential for compliance-heavy sectors and answering “why didn't we go for that one?”
Visibility without micromanagement
Because every action updates a central status, executives get reports across all regions (allocation volume, acceptance rate, win rate, turnaround time) without having to ask anyone for an update.
Scales with the organisation
Adding a new regional office is just a new Tender Group and a new Identifier — no workflow changes, no code, no retraining.
Shared supporting material every bid draws on
Maintained once by the Reference Library Manager, pulled into every tender automatically. Eliminates the “whose version of Joe's CV is the latest?” problem.
Briefing Templates
Pre-built question sheets that every Briefing Attendee takes into a session so different attendees at different briefings capture the same information in the same shape.
Employee CVs
Two formats per employee — company format for private-sector bids, Treasury format for SBD forms. Effective-dated rate history so historical tenders see the rate that was in force at pricing time.
Rate Cards
Named rate cards (e.g. “Standard 2026”, “Gauteng Public Sector”) with role-based cost / charge rates and default overhead / markup. Tender Groups nominate a default; deviations are audited and require a reason above a threshold.
Client Information
Background notes on buying entities — procurement quirks, contact people, past project history, language preferences. Consulted before drafting so the pitch lands in the client's own vocabulary.
Legislation Documents
PFMA, MFMA, PPPFA, B-BBEE codes, sector-specific regulations — one place, always the current version, ready to cite in any proposal.
Panel Appointments
Register of every panel the organisation is appointed to — with reappointment dates and conflict-of-interest checks so no panel lapses accidentally and no team member ends up on the evaluation panel for their own bid.
Frequently asked questions
Move your tender team onto TenderFlow Enterprise
Set up Tender Groups, Identifiers and the Reference Library once. Then every tender that lands in the feed flows through this pipeline automatically — with full visibility, audit trail and accountability.
Start Free Trial See Pricing