Define the Competency Mentor (CM) framework and role used by Technology Consulting, and adapt it for the BC and QA teams, so the Competency Lead can offload assessment and career-development work.

Write-up + latest update dated 3 August 2026 — no update filed in the 3+ weeks since.

Role definition updated and sent for review.

Creation of a CM slide pack that can be used across all competencies.

• 22 July 2026: CM role for BC to be launched by 14 August 2026, communicated in the BC monthly session on 19 August 2026. — Need to free up some of James' time ASAP due to delivery demand.
• 3 August 2026: CMs for BC confirmed: Jacques and Faiek. — CM roles had not been finalised.

CM role definition needed finalising before 14 August, pending feedback from Willo, James and Cathy — status of that feedback is unconfirmed as no update has been filed since.

No change — continue as planned (as at 3 August).

Embed Saratoga's 2026 strategic theme of Personal Excellence — Consulting Mindset behaviours, Personal Excellence, and the Saratoga Way of Work — into targeted employee training with real-world examples.

Write-up + latest update dated 17 August 2026 — no update filed for the current week.

Reviewed Saratoga Way of Work document; created updated slide pack on new content (shared with Bharn); drafted Personal Excellence content and slide pack.

Continue refining the Saratoga Way of Work slide pack; continue work on Personal Excellence slide pack and draft script for Cathy.

• 14 July 2026: AI to be included in the Way of Work. — AI has become part of our delivery approach and this isn't reflected in the current version of the WoW.
• 14 July 2026: Personal Excellence session to leverage Consulting Mindset and WoW content rather than introducing new concepts. — Don't want to overload employees with too much content — pull existing concepts together instead.
• 24 July 2026: Include "spotting and validating opportunities" considerations in training material. — To build commercial awareness in consultants and help grow the opportunity pipeline.
• 19 August 2026: Feedback from the Consulting Mindset breakaway sessions to be incorporated into the Personal Excellence content. — To help bridge gaps and share information about existing support processes.

None logged in the latest update.

No change — continue as planned.

No write-up or brief has been filed for this project yet — goal not formally documented. Based on update content: build and productionise an MCP server exposing Enabill (time/billing) reports as tools usable from Claude.

No write-up/brief filed for this project — goal above is inferred from update content, not from an authoritative source document.

Completed Production Container Apps deployment (registry, logging, managed identity, role assignments) via guarded Terraform pipeline. Completed Production Entra/Claude access setup (Server + Client registrations, tenant consent, Enabill MCP Prod Users security group). Diagnosed and fixed a Production 404 (duplicated Activity Report route) via a reviewed, safe Terraform change. Completed end-to-end Production validation: health checks, single-row and multi-row Activity Report retrieval, and Excel workbook generation from Production data.

Begin Under Allocation Report MCP tool integration — investigate existing report logic/data source/filters, define the MCP contract, implement and validate through the lower-environment workflow before any Production rollout. Complete the Production Activity Report lessons-learned reference in parallel.

• 27 Aug 2026: Configure ACTIVITY_REPORT_API_BASE_URL as the Production host only (client appends the route). — Prevents a duplicated report path and the resulting HTTP 404/non-JSON tool failure.
• 27 Aug 2026: Control Production MCP access via the Enabill MCP Prod Users group on the Server enterprise application. — Gives an explicit Production access list while keeping QA and Production membership separate.
• 27 Aug 2026: Make the Under Allocation report the next report exposed as an MCP tool. — Extends the proven Activity Report integration pattern to the next agreed reporting use case.

None. On track — no blockers or decisions currently required. Remaining Production cold-start clarification will be captured as an operational lesson and does not block delivery.

No change — continue as planned. Shift active delivery to the Under Allocation report as the next MCP tool, while completing the Production lessons-learned record in parallel.

Validate basic introductory AI training as a scalable, commercially viable new service offering by running a pilot training programme for the Kay Mason Foundation.

Write-up + latest update dated 27 August 2026 (week of 24 August).

Conducted first training session on 25 Aug; collected training feedback; expanded Saratoga training strategy documents; prepared material for the second training session.

Prep for and deliver the second training session on 1 Sep; collate feedback from the first session; complete analysis of Skills Development Levy implications for AI training.

• 4 Aug 2026: Training will be conducted over four 2-hour sessions, one per week. — Staff availability, and to provide opportunity for retention.
• 4 Aug 2026: Training will start the week of 17 Aug. — Staff availability.

No internal review of the training material has happened yet — reviewers have been identified with an opportunity to review.

No change — continue as planned.

Using the 'Karpathy LLM Wiki' pattern as a guide, investigate architectures and paths to an AI-maintained documentation knowledge base for Saratoga (and potentially clients), aimed at BD users, supporting multi-user collaboration and reliably branded documents.

Write-up + latest update dated 27 August 2026.

Chatted with Charlene about re-prioritising effort towards Claude Developer Certification. Was on leave, so no additional progress on the KB initiative this week.

Claude Developer Certification is the new priority.

• 2026-07-27: Evaluate Falconer as a precursor to deciding direction. — Could save build effort.
• 2026-08-04: Create a tech-agnostic "zoom-out" 1-pager business architecture document aimed at shaping the conversation with external clients; compare Glean, Guru and Falconer. — Feedback from Mark; informs the build-vs-buy decision.
• 2026-08-27: Prioritise Claude Developer Certification; revisit KB work once achieved (end of September). — Claude Partner Certification exam set as a strategic priority.

None logged.

New priority track is the Claude Developer Certification exam — KB workflow work is paused until end of September.

Turn Charlene's hands-on experience building an LLM Wiki (Obsidian + Claude) for a live BC engagement into a validated, general-purpose pattern the wider BC team can adopt.

Write-up + latest update dated 6 August 2026 — no update filed in the 3+ weeks since.

Incorporated feedback on the three guides. Continued editing the presentation covering the three guides.

Submit guides and presentation for approval. Subject to approval, circulate the three guides more widely for a further round of feedback beyond the initial two reviewers. Upload the guides and presentation to SharePoint.

• 24 Jul 2026: CoWork positioned as the default interface across all guides, not Claude Code. — Reviewer feedback flagged the original drafts as implying rough equivalence between interfaces, when CoWork's review-first workflow is what's actually recommended.
• 25 Jul 2026: Descoped the detailed codebase-ingestion / implementation-status-tracking workflow from the guides. — Compelling for one engagement, but too narrow and heavy an addition for a general-audience BA guide.

No second live implementation to validate the guides against — needs a decision on whether to pilot with another BA before wider circulation. No formal deadline has been set for when the guides need to go live.

No change — continue as planned.

Determine, as early as possible, whether Saratoga's proposed Forensic Incident Management solution relies on TFG-proprietary functionality (requiring TFG approval/notice), then benchmark the top off-the-shelf FIM products against Saratoga's own capability (cost, features, South African market fit) to confirm whether Saratoga has a viable market offering.

Write-up (v2) used for goal — no Project Brief goal fallback needed, and no weekly update has ever been filed for this project.

No weekly update has ever been filed for this project — no progress data available.

No weekly update has ever been filed for this project — no plan data available.

No decisions logged.

Write-up flags a possible handover from Angela Walker to Jaco de Goede due to personal family matters, and notes the TFG proprietary-vs-standard determination is on the critical path to any Ackermans proposal — TFG conversations, if triggered, could take several weeks. No update has been filed to confirm current status against these risks.

Not reported.

Establish a secure, compliant, scalable platform (via a LiteLLM proxy demo) that lets employees adopt generative AI tools safely within the enterprise perimeter, minimising "Shadow AI" data-leak risk while showcasing how Saratoga can help clients mitigate it.

Write-up + final update dated 6 August 2026, status Completed — no further updates expected.

Checked in the repository. Added additional unit tests and moved keyword management into its own config file. Updated the costing method to read costs per model rather than global costs. Emailed out a document detailing the basic overview.

N/A unless stated otherwise — project marked Completed.

No decisions logged.

None.

No change — continue as planned.

Identify one or two viable UK business opportunities Saratoga can realistically pursue — building a tender log of reviewed opportunities and a shortlist for Karen van der Spuy to confirm before any expression of interest is submitted.

Write-up + latest update dated 20 August 2026 — no update filed for the current week.

Identified five potential tenders via Tender Finder. Registering Saratoga on the relevant external portals and reviewing detailed requirements for each tender to determine best fit. Aimed to share a recommended tender with Karen by close of business 21 August 2026.

Continue reviewing additional portals for leads and update the tender review log with any potential opportunities.

No decisions logged.

No risks, blockers, or input needed at this point (as at 20 August).

Nothing to re-prioritise at this stage.