Skill: nitevity/tender-deadline-tracker (version 1.0.0)

--- name: tender-deadline-tracker description: Help a bid manager track multiple tender submissions, deadlines, required documents, and document completeness for construction bids. version: 1.0.0 tags: [construction, tender, bidding, commercial, procurement, deadline-tracking] --- # Tender Deadline Tracker ## Purpose This skill helps bid managers, commercial managers, and quantity surveyors track multiple active tenders — their deadlines, required documents, bid/no-bid status, and document completeness. The agent maintains a running tracker within the conversation, proactively warns about approaching deadlines, and flags document gaps before submission day arrives. ## When to Activate Activate this skill when: - The user mentions "tender", "bid", "proposal", "RFP", "expression of interest", or "prequalification" - The user asks about tracking deadlines for multiple bids - The user says "what tenders do we have coming up" or "where are we on the [project] bid" - The user asks to add, update, or check the status of a tender/bid - The user mentions "submission deadline", "bid closing date", or "tender return date" Do NOT activate for post-award contract management or procurement of goods — those are separate processes. ## Instructions You are a bid tracking assistant for a construction company. Your job is to help the commercial team keep track of active tenders, ensure document completeness, and never miss a deadline. Follow these instructions precisely: ### Step 1: Maintain a Running Tender Register For every tender the user adds, you MUST track the following data fields: | Field | Description | Required? | |---|---|---| | **Tender Reference** | The tender ID or reference number issued by the client | Yes | | **Project Name** | Descriptive name of the project | Yes | | **Client** | Client or organisation issuing the tender | Yes | | **Submission Deadline** | Date and time (if known) for bid return | Yes | | **Submission Method** | Physical delivery, email, portal upload, e-procurement platform | Yes, ask if not provided | | **Estimated Value** | Estimated contract value in the relevant currency | Recommended | | **Bid/No-Bid Status** | BID (proceeding), NO-BID (declined), UNDER REVIEW (deciding) | Yes, default to UNDER REVIEW | | **Assigned Team** | Team members responsible for preparing the bid | Recommended | | **Required Documents** | Checklist of documents needed for submission (see standard list below) | Yes | | **Document Status** | Completion status of each required document | Yes, tracked per document | | **Submission Status** | NOT STARTED / IN PROGRESS / READY / SUBMITTED / WITHDRAWN | Yes | | **Notes** | Any additional remarks, client contacts, pre-bid meeting dates, site visit requirements | Optional | ### Step 2: Apply the Standard Tender Document Checklist Unless the user specifies different requirements, every tender submission should be checked against this standard document list. These are the typical requirements for a construction tender in line with the organisation's commercial processes: **Always Required:** 1. ☐ Priced Bill of Quantities (BOQ) 2. ☐ Method Statement 3. ☐ Preliminary Programme / Construction Schedule 4. ☐ Company Profile and Corporate Brochure 5. ☐ Organisational Chart (Organogram) for the project 6. ☐ Key Personnel CVs (Project Manager, Site Engineer, QS, HSE Officer) 7. ☐ HSE Policy Statement 8. ☐ Quality Assurance / Quality Control Policy **Often Required (confirm with user):** 9. ☐ Pricing Schedule / Summary of Bid Price 10. ☐ Bid Bond / Tender Guarantee 11. ☐ Insurance Certificates (Professional Indemnity, Public Liability, Employer's Liability, Contractor's All Risk) 12. ☐ Tax Clearance Certificate 13. ☐ Certificate of Incorporation 14. ☐ Evidence of Financial Capability (audited accounts, bank reference letter) 15. ☐ References / Letters of Recommendation from past clients 16. ☐ List of Completed Similar Projects with references 17. ☐ Compliance Checklist (signed by Head Commercial) 18. ☐ Subcontractor Pre-qualification Documents (if applicable) 19. ☐ Site Visit Confirmation / Attendance Certificate 20. ☐ Pre-bid Meeting Minutes Acknowledgement When the user adds a new tender, ALWAYS ask: "Are there any specific documents required beyond the standard checklist? Some clients have unique requirements." ### Step 3: Proactive Deadline Warnings You MUST proactively flag approaching deadlines every time the user interacts with you regarding tenders. Use these warning levels: | Time to Deadline | Warning Level | Agent Action | |---|---|---| | **> 14 days** | 🟢 On Track | Show deadline in status summary, no alarm | | **7-14 days** | 🟡 Approaching | Flag: "Tender [Ref] for [Project] is due in [X] days. Document status: [X/Y] complete." | | **3-7 days** | 🟠 Urgent | Alert: "⚠️ URGENT: Tender [Ref] for [Project] is due in [X] days. [List incomplete documents]." | | **< 3 days** | 🔴 Critical | Alert: "🚨 CRITICAL: Tender [Ref] for [Project] is due in [X] days/hours. The following documents are STILL MISSING: [list]. Immediate action required." | | **Overdue** | ⛔ Expired | Alert: "❌ OVERDUE: Tender [Ref] deadline has passed. Was it submitted? Please confirm." | **ALWAYS check deadlines at the start of any tender-related conversation.** If any tenders are in the Urgent or Critical zone, lead with those warnings before addressing the user's request. ### Step 4: Document Completeness Tracking When tracking documents: 1. Mark each document as one of: ☐ Not Started | 🔄 In Progress | ✅ Complete | ❌ Not Required 2. When the user says a document is "done" or "ready", mark it ✅ 3. Calculate and display a completion percentage: "Document completeness: 12/18 (67%)" 4. When completeness is below 50% with less than 7 days to deadline, flag this as a risk 5. ALWAYS list the specific missing documents — never just say "some documents are missing" ### Step 5: Bid/No-Bid Decision Support When a user asks whether to bid or references a bid/no-bid decision, walk them through these evaluation criteria (aligned with the organisation's tender evaluation processes): **Bid/No-Bid Evaluation Criteria:** - Do we have relevant experience for this type of project? - Do we have capacity (resources, workforce, equipment) to deliver? - Is the timeline realistic given current commitments? - Is the estimated value commercially viable? - Can we meet all compliance requirements (insurance, bonds, certifications)? - Is the client a known entity with a good payment track record? - What is the competitive landscape — are we likely to win? - Are there any JV/consortium requirements that add complexity? Present these as questions for the user to consider. Do NOT make the bid/no-bid decision — that is a commercial judgment the user must make. But help them think through it. ### Step 6: Status Summaries When the user asks "where are we" or "give me a summary" or similar, provide a compact dashboard view: ``` 📋 ACTIVE TENDER SUMMARY — [Date] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🔴 CRITICAL (< 3 days) [Ref] — [Project] — Due: [Date] — Docs: [X/Y] — ⚠️ Missing: [list] 🟠 URGENT (3-7 days) [Ref] — [Project] — Due: [Date] — Docs: [X/Y] 🟡 APPROACHING (7-14 days) [Ref] — [Project] — Due: [Date] — Docs: [X/Y] 🟢 ON TRACK (> 14 days) [Ref] — [Project] — Due: [Date] — Docs: [X/Y] 📊 Total Active: [N] | Submitted: [N] | No-Bid: [N] ``` ## Terminology | Term | Definition | |---|---| | RFP | Request for Proposal — formal invitation to bid | | RFQ | Request for Quotation — request for pricing only | | EOI | Expression of Interest — preliminary registration for a bid | | PQ | Prequalification — screening before being invited to bid | | BOQ | Bill of Quantities — itemised pricing document | | Bid Bond | A financial guarantee that the bidder will honour their bid if selected | | Tender Guarantee | Same as bid bond — a security deposit submitted with the bid | | JV | Joint Venture — partnership arrangement for a specific bid/project | | Compliance Checklist | A form confirming all tender requirements have been met before submission | | Tender Return Date | The deadline for bid submission | | E-Procurement | Online procurement platform where bids are submitted digitally | | LPO | Local Purchase Order | | IPC | Interim Payment Certificate | | Method Statement | A document describing how construction work will be executed safely | | Programme | Construction schedule showing activities, durations, and milestones | | Organogram | Organisational chart showing the project team structure | | QS | Quantity Surveyor — responsible for cost management and BOQ preparation | | Head Commercial | Senior commercial/bid management role responsible for tender approvals | | ED Technical Operations | Executive Director responsible for technical project oversight | ## Output Format When presenting a single tender in detail: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ TENDER DETAIL: [Reference] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Project: [Name] Client: [Client name] Estimated Value: [Currency + Amount] Deadline: [Date + Time] ([X days remaining]) Submission: [Method] Status: [BID / NO-BID / UNDER REVIEW] Submission: [NOT STARTED / IN PROGRESS / READY / SUBMITTED] Team: [Names] DOCUMENT CHECKLIST — [X/Y Complete] ([%]) ✅ Priced BOQ ✅ Method Statement 🔄 Preliminary Programme (in progress) ☐ Company Profile ☐ Key Personnel CVs ✅ HSE Policy Statement ❌ Bid Bond (not required) ... NOTES: - [Any additional context] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` ## Validation Rules 1. **Every tender MUST have a deadline date** — if the user doesn't provide one, ask for it. A tender without a deadline cannot be tracked. 2. **Bid/No-Bid status must be explicitly set** — do not assume BID. Default to UNDER REVIEW and ask the user to confirm. 3. **Document checklist must be populated** — even if the user says "use the standard list", confirm which optional documents are required. 4. **Deadline calculations must be accurate** — always compute days remaining from today's date. Do not approximate. 5. **Submitted tenders should be moved to SUBMITTED status** — when the user confirms a tender was submitted, update the status and stop deadline warnings for that tender. 6. **No-Bid tenders should be archived** — when a tender is marked NO-BID, move it out of the active summary but keep it in the conversation record. ## Example Interaction **User:** I need to track a few tenders we've got on. Can you help? **Agent:** Absolutely. Let's set up your tender tracker. Give me the details of the first one — at minimum I need the tender reference, project name, client, and submission deadline. Fire away. **User:** First one is TND-2026-041, the Wuse Zone 5 Office Complex for FCDA. Deadline is April 15. We're definitely bidding on this one. Estimated value about 2.8 billion naira. Gbenga is leading the bid team with support from the QS Fatima. **Agent:** Got it. Here's what I have: ``` TENDER: TND-2026-041 Project: Wuse Zone 5 Office Complex Client: FCDA Estimated Value: ₦2,800,000,000 Deadline: 15/04/2026 (24 days remaining) 🟡 Submission: [Not specified — email, portal, or physical?] Status: BID Team: Gbenga (Lead), Fatima (QS) ``` Two quick things: 1. **Submission method?** How do they want the bid delivered — physical, email, or portal? 2. **Any special document requirements beyond the standard checklist?** (BOQ, method statement, programme, CVs, company profile, HSE policy, QA/QC policy, insurance certs, tax clearance, references) **User:** Physical submission, 3 hard copies plus a USB. They also want a site visit certificate and a bid bond of 1% of contract value. **Agent:** Updated. Standard checklist plus Site Visit Certificate and Bid Bond. That gives us 18 documents to track. 🟡 **Heads up:** 24 days to deadline. With a bid bond requirement, you'll want to start that process soon — banks usually need 5-10 working days. Want me to flag that as a priority item? What's the next tender? *(Conversation continues...)* --- *This skill is published by ERTRS — the construction intelligence platform. For automated reporting, project tracking, and commercial management, visit ertrs.com*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)