Supply Chain Management in Government Projects Summaries (UNISA, CPUT & CUT-Style Exam Notes)

Supply chain management (SCM) in government projects is the practical system of planning, procurement, logistics, inventory control, and vendor coordination that turns budgets into delivered public value. In the South African context, SCM links directly to public procurement compliance (e.g., PFMA and Treasury Regulations), demand visibility, contract performance, and accountability for service delivery outcomes. These exam notes summarise how government SCM works in practice, while also showing what examiners usually test: process control, risk management, legal/ethical boundaries, performance metrics, and common failure points in project environments.

UNISA MNG 0001 / MNG 3202 Exam Notes: Foundations of SCM in Government Projects (Policy, Planning, Compliance)

University of South Africa (UNISA) style questions in project management and supply chain often test your ability to connect core SCM concepts to public sector governance, and to explain how procurement and logistics processes support project delivery. These notes cover the foundation: terminology, the SCM cycle in government projects, and compliance logic. While university modules differ (e.g., MNG 0001 as an introductory management module and MNG 3202-type management/project operations themes), the underlying exam logic is similar: demonstrate structured understanding, correct terminology, and practical application.

Understanding SCM as a Delivery System (Not Just Buying)

In government projects, SCM should not be treated as “procurement department activity.” It is a delivery system covering the complete path from identifying a need to ensuring that the right goods/services arrive, are accepted, and are supported throughout the asset’s lifecycle.

A useful exam-ready framing is to describe SCM as five interconnected streams:

Demand and requirements planning (what is needed, when, and how much)
Sourcing/procurement (how government buys legally and efficiently)
Logistics and delivery management (transport, receiving, warehousing)
Inventory and asset/working capital management (stock levels, obsolescence)
Performance measurement and continuous improvement (contract KPI monitoring, audits)

Government projects often fail not because procurement is “illegal,” but because one stream is weak—e.g., poor requirements definition leads to rework; weak contract management causes late deliveries; missing asset integration causes operational non-acceptance.

Exam focus keywords (commonly tested):

Value for money (VfM)
Transparency and fairness in competitive procurement
Specifications and requirements management
Delivery monitoring and acceptance processes
Internal controls and segregation of duties

SCM in the Project Lifecycle: Where It Fits

A typical exam prompt asks: “Explain the role of supply chain management in a project lifecycle.” The best responses map SCM to stages (initiation → planning → execution → closure). In government projects, SCM must also align to procurement governance timing.

A practical lifecycle mapping:

Initiation / Concept Stage
- Define broad scope and outcomes (what service delivery improvement the project supports)
- Establish procurement strategy at a high level (e.g., framework vs once-off tendering)
- Identify early risks: market constraints, lead times, funding availability
Planning Stage
- Translate project scope into detailed requirements
- Develop procurement plan (what to procure, when, estimated quantities)
- Create contract strategy (local content, pricing format, delivery schedule)
- Confirm logistics feasibility (warehousing capacity, transport routes)
Execution Stage
- Run procurement processes according to approved plan
- Monitor supplier performance (delivery, quality, compliance)
- Manage receiving, inspection, and acceptance
- Handle variations/claims/contract amendments properly
Closure Stage
- Final acceptance and handover
- Close contracts, settle invoices, reconcile stock
- Capture lessons learned for future projects and audits

Why this matters: SCM timing directly affects project schedules. If procurement starts late, construction/installation cannot begin. If goods are delivered early but storage is weak, items deteriorate or go missing, causing downstream schedule slips.

Requirements Definition and Specifications: The Backbone of VfM

A recurring UNISA-style exam theme is that value for money depends on quality of requirements. In government procurement, poor specifications are a root cause of:

costly amendments,
disputes over deliverables,
non-conformance during acceptance,
vendor claims for variations,
or litigation/complaints.

To explain requirements properly, distinguish:

Functional requirements: what the system must do
Example: “Install and commission solar street lights such that output meets specified lumens at defined operating conditions.”
Performance requirements: measurable criteria
Example: “Minimum luminous flux of X lumens, operating temperature range Y–Z, expected lifetime at least N years under standard conditions.”
Technical specifications: standards/materials/design constraints
Example: “Compliance with IEC safety standards, corrosion resistance ratings, cable gauge requirements.”

Exam-ready best practice steps:

Build a requirements register (item/service, quantity, timing, acceptance criteria)
Validate requirements with end-users and technical departments
Align requirements to budget and procurement strategy
Conduct market research to test feasibility and lead times
Freeze specifications or manage controlled change processes

Public Sector Compliance Logic (Controls, Accountability, and Procurement Fairness)

Government SCM is built around controls and accountability. In South Africa, procurement is governed by the PFMA and Treasury Regulations, supported by internal procurement policies and delegated authorities. Even if an exam doesn’t ask for specific clause numbers, it often expects knowledge of the compliance pillars.

Core compliance pillars (write these as exam points):

Legality: procure only according to approved legal frameworks and delegations
Transparency: competitive processes, document traceability, audit trails
Fairness: consistent evaluation criteria and impartial bid evaluation
VfM: not just lowest price, but total cost and lifecycle value
Accountability: documented decisions and segregation of duties

A common exam scenario: a project uses “quick procurement” to avoid delays, but later finds suppliers are not approved, acceptance evidence is missing, and payments lack supporting documentation. The correct exam answer explains that speed must be balanced with compliance through:

approved procurement plans,
proper quotations/tender pathways,
documented deviation procedures where allowed,
and strict invoice/receiving controls.

Procurement Planning: The Most Tested “Planning-to-Execution” Link

Procurement planning is frequently tested because it is where project objectives become purchasable items.

A procurement plan typically contains:

list of items/services to procure,
estimated quantities,
estimated values (to choose procurement methods),
lead times and delivery schedules,
procurement method for each category,
responsibilities and timelines,
evaluation criteria (technical + financial),
and contract management plan.

For exams, you should show ability to reason through the procurement plan logic. For example:

If delivery must occur before a construction phase, procurement must start early enough for manufacturing/shipping lead time.
If items are standardized and frequently used, government can consider framework agreements to reduce time and cost.

Risk in Government SCM Projects: Where SCM Fails in Real Life

Exam questions often ask you to identify SCM risks and propose mitigation. In government projects, typical SCM risks include:

Requirements risk: scope creep, unclear specs, unrealistic quantities
Market risk: supplier shortages, price volatility, currency depreciation
Contract risk: ambiguous deliverables, weak KPIs, poor performance remedies
Logistics risk: delayed shipping, damage in transit, customs delays
Governance risk: delays in approvals, incomplete documentation
Quality risk: non-compliant materials or poor workmanship from suppliers
Fraud/corruption risk: conflicts of interest, bid rigging, collusion

Mitigation measures:

requirements validation and controlled change management,
market/supply chain intelligence and supplier engagement,
robust contract clauses (acceptance criteria, penalties/bonuses),
logistics planning (transport routes, packaging, receiving capacity),
compliance checklists and audit-ready documentation,
performance scorecards and formal vendor reviews.

Mini-Case Example (Exam-Style): Water Infrastructure Delivery

Consider a hypothetical municipal water infrastructure project in South Africa needing:

pipes and fittings,
pumps,
electrical cabling,
and installation materials.

A typical failure chain in government SCM:

Requirements are not detailed (e.g., pipe grade not specified precisely)
Procurement goes ahead but technical evaluation is weak
Goods are delivered, but acceptance testing fails
Supplier disputes cost and delivery timelines
Project schedule slips, and additional procurement costs occur

A strong exam answer would show the corrected approach:

define acceptance standards,
validate specifications with engineers,
include inspection and test procedures in the contract,
plan lead times and storage,
and ensure receiving and acceptance documentation.

CPUT CPUT PMB/Project Management Exam Notes: Procurement Method Selection, Contract Management & Supplier Performance

Cape Peninsula University of Technology (CPUT) and similar technical universities often emphasize applied process thinking: how to select procurement routes, how contracts manage delivery, and how to manage performance. This section focuses on procurement method logic and the “after tender” reality: contract administration, delivery verification, claims, and corrective action.

Procurement Method Selection: Matching Method to Context

A common exam prompt: “Explain why procurement methods differ and what factors influence method selection.” In government projects, method selection depends on:

urgency and time constraints,
procurement value/threshold rules,
complexity and market competition,
standardization vs bespoke requirements,
risk profile,
availability of qualified suppliers,
and need for framework agreements.

Applied reasoning (write like exam logic):

If requirements are standard and repeatedly purchased, a framework or panel approach can reduce time and improve price consistency.
If the project is unique (e.g., bespoke IT solution for a government call centre), a competitive process may be necessary to obtain the best technical response.
If urgency is genuine (e.g., disaster response), government may use faster mechanisms permitted by policy, but must still preserve documentation and fairness.

Evaluation Criteria and VfM: Beyond Lowest Price

Examiners often dislike “lowest price only” thinking in VfM discussions. You should explain VfM as a combination of:

life-cycle cost,
quality and reliability,
delivery performance,
maintenance/operating costs,
and total risk transferred or retained.

A typical evaluation structure:

Technical evaluation: compliance with specs and capability to deliver
Functionality score: how well the solution meets performance outcomes
Price and preference points: financial comparison within fair scoring

In exams, you can illustrate how vendors are scored (without needing exact preference point rules unless your course requires them). A safe approach is to describe method and principles:

evaluation criteria must be pre-defined,
scoring must be consistent across bidders,
and committee decisions must be documented for auditability.

Contract Management: Turning Procurement Into Delivery

A contract is a tool to convert requirements into enforceable deliverables. In government project SCM, contract management includes:

Contractor/supplier onboarding
delivery schedule management
quality assurance and inspection
variation control
payment verification and invoice support
performance monitoring
claims, disputes, and termination/step-in rights where applicable
close-out documentation

Exam-friendly contract management checklist (structured):

Ensure contract has clear scope of work / deliverables
Define delivery milestones and acceptance criteria
Include service level requirements (for services) or test/inspection plan (for goods)
Include reporting requirements (progress reports, delivery notes)
Include remedies and consequences for late/poor delivery
Ensure document control: contract, amendments, correspondence
Ensure a contract register and responsible contract owner

Supplier Performance Measurement: KPIs That Matter

To manage suppliers effectively, government projects should track measurable indicators. Common SCM performance KPIs include:

On-time delivery (OTD): % of deliveries meeting scheduled date
Quality acceptance rate: % passing inspection on first delivery
Complete order rate: % orders delivered without shortages
Response time: time to resolve defects or delivery issues
Cost variance: deviation from contracted pricing or forecast costs
Claim frequency and value: how often suppliers submit claims and their magnitude
Schedule adherence: how procurement milestones influence project milestones

Why KPIs matter: They provide objective basis for corrective action. Without KPIs, contract management becomes subjective, which increases disputes and reduces audit defensibility.

Corrective Action and Supplier Development

In government procurement, corrective action should be systematic rather than emotional. A typical progressive corrective action process:

Identify non-conformance (during inspection, testing, or performance review)
Notify supplier with evidence (inspection reports, defect logs)
Require a corrective action plan (CAP) with root-cause analysis
Set verification/verification timelines
Apply contract remedies (withhold payment where allowed, repair/replace, penalties/bonuses)
Update supplier risk rating and future procurement eligibility

Supplier development can also be appropriate where long-term capability building is needed, especially for SMEs and historically disadvantaged suppliers—subject to compliance and capability requirements.

Case-Style Example: School Furniture Procurement

Imagine a district education infrastructure project requiring desks and chairs delivered to multiple schools. SCM issues commonly arise:

partial deliveries (some schools receive earlier than others),
damaged items due to poor packaging,
mismatches (wrong model or dimensions),
delays in installation because delivery is not sequenced with classroom readiness.

A strong CPUT-style answer would propose:

milestone-based delivery schedule aligned to school readiness dates,
acceptance inspection at receiving points (where possible),
packaging/spec requirements to prevent damage,
a delivery/installation coordination plan between procurement and school facilities teams,
and a defect resolution timeline (e.g., replacement within 10 working days).

Payment Controls: Linking Invoices to Evidence

A frequent exam topic in public administration is control of payments. Payments should be tied to:

goods received notes / delivery notes,
inspection and acceptance certificates,
invoice matching to contract price and quantities,
and proof that services were rendered or work completed.

A failure pattern:

supplier invoices submitted without acceptance evidence,
receiving documentation incomplete,
and contract variations not approved through delegated authorities.

To score well, explain that payment controls are not “administrative bureaucracy,” but a risk control preventing irregular expenditure and ensuring accountability.

CUT Public Administration Exam Notes: Logistics, Inventory, Warehousing, and Demand Forecasting for Government Infrastructure Projects

Central University of Technology (CUT) and similar public administration programmes often emphasize operational effectiveness: how goods and materials move, how stock is managed, and how demand forecasting supports delivery schedules. This section covers logistics and inventory as project-critical systems, including warehouse design, stock control methods, and contingency planning.

Logistics Planning: The “Move and Meet” Function

Logistics in government projects includes:

transport planning (road/rail/air where applicable),
routing and delivery windows,
handling and packaging requirements,
warehousing and storage conditions,
staging areas for installation,
and reverse logistics (returns, repairs, disposal).

A logistics plan should align with project schedule. For example:

If installation teams need materials “just in time” to reduce staging costs, procurement and logistics must coordinate delivery windows tightly.
If storage is limited (small municipal warehouses), delivery must be sequenced carefully to avoid overflow and damage.

Exam point: Logistics is not just transportation; it includes storage and coordination.

Warehousing and Storage: Preventing Loss, Damage, and Non-Compliance

Warehousing supports inventory accuracy and quality preservation. Key warehousing topics include:

layout and location coding,
receiving and issuing controls,
stocktaking and cycle counting,
damage logging,
quarantine area for items failing inspection,
and document control for audit trails.

Typical warehouse controls used in government environments:

GRN (Goods Received Notes) systems
bin cards or digital inventory records
barcode/QR tracking (in more mature environments)
segregation of roles: goods receiving vs stock updating vs approvals
regular stock counts (cycle counts + annual full stocktake)

A strong exam response explains why this matters for project delivery:

inaccurate inventory causes “false availability,” resulting in installation delays,
damaged goods increase replacement cost and cause schedule slips,
and poor traceability complicates warranty claims.

Inventory Management: Balancing Service Level and Cost

Inventory in government projects includes:

raw materials for construction,
spare parts for operations,
consumables supporting service delivery (e.g., cleaning supplies, PPE),
and equipment components awaiting installation.

Inventory costs include:

holding costs (storage, insurance, obsolescence),
ordering costs (procurement overhead and administration),
and stockout costs (delays, emergency procurement, penalties).

A common exam question asks you to explain inventory control tools. You can discuss:

ABC analysis (classify items by value/usage)
EOQ (economic order quantity) concept (where relevant)
reorder points with lead time buffers
safety stock to manage uncertainty

ABC Analysis (Exam-Style Explanation)

A items: high value, low-to-medium frequency; require tight control
B items: medium value; standard control
C items: low value but high volume; simplified replenishment

In government projects, A items might include specialized pumps or high-cost electrical components. C items might include common fasteners and cable ties. This classification helps focus management effort where it matters most.

Demand Forecasting: From “Need” to “Orderable”

Demand forecasting in government projects is challenging due to:

fluctuating user needs,
schedule changes,
funding cycles and approvals,
and end-user changes.

However, forecasting is still essential. The aim is to reduce uncertainty and align procurement timing with delivery needs.

Forecast inputs can include:

historical consumption or installation rates,
current project schedule milestones,
planned expansions or service changes,
and approvals/funding timeline.

Exam-ready explanation: Forecasting reduces stockouts and prevents excess inventory that ties up funds.

Lead Time Management and Safety Stock

Government SCM must consider lead time variability:

supplier production delays,
port congestion or transport delays,
customs delays for imported components,
and unexpected delivery disruptions.

A concept examiners like is the reorder point. You can explain it using a simple formula-based approach (without requiring advanced math):

Reorder Point (ROP) = (Average daily demand × Lead time in days) + Safety stock

Where:

safety stock covers variability in lead time and demand.

Even if your course does not demand the formula, the idea earns marks: reorder must occur early enough to prevent stockouts, while safety stock must not be excessive.

Contingency Planning: Handling Disruptions Without Losing Compliance

Disruptions happen: supplier insolvency, delayed shipping, damaged shipments, or regulatory delays. A strong CUT-style exam answer describes contingency steps while maintaining compliance.

Contingency measures include:

pre-approved alternate suppliers (where allowed by framework or contract),
emergency response procedures with documented approvals,
alternative delivery routes or staging arrangements,
quality re-inspection and replacement rules,
and escalation protocols with clear roles.

Example scenario (transport failure):

Goods expected for installation on Day 30 arrive late due to transport breakdown.
The project triggers an escalation meeting with supplier logistics.
If contract allows, alternative shipping is requested.
Delivery is rescheduled and installation plan revised to use alternative materials/components first.
Documentation supports any delay claims or schedule adjustments.

Worked Example (Inventory + Lead Time) for Exam Practice

Suppose a municipality plans installation materials for a health facility upgrade. One component—say, electrical conduits—is required at 50 units per week. The average lead time from supplier is 3 weeks, and the project sets safety stock equivalent to 1 week of demand.

Average demand per week: 50 units
Lead time demand: 50 units/week × 3 weeks = 150 units
Safety stock: 50 units/week × 1 week = 50 units
Reorder point: 150 + 50 = 200 units

Therefore, ordering should be initiated when stock falls to 200 units to cover demand during lead time plus safety stock. This example demonstrates structured inventory reasoning, which many SCM exam questions reward.

UNISA/CPUT/CUT Integrated Exam Notes (Public Administration Focus): Performance Monitoring, Auditing, Fraud Risk Controls, and Continuous Improvement in Government SCM

This final section integrates the full SCM chain—planning, procurement, contract management, logistics, and inventory—into governance outcomes. Public administration exam questions often test your ability to connect SCM to accountability: how to monitor performance, reduce irregular expenditure, and use improvement cycles to prevent recurrence. Even when different universities are listed earlier, examiners across institutions value an integrated perspective grounded in public sector realities.

Monitoring and Evaluation (M&E): Ensuring SCM Supports Project Outcomes

Supply chain performance should be monitored at multiple levels:

Operational level: delivery schedules, inspection results, warehouse accuracy
Contract level: supplier KPIs, variation approvals, claims management
Project level: impact on construction/implementation milestones and service delivery
Organisational/governance level: compliance metrics, audit findings, spend management

A strong exam response proposes a performance dashboard with:

on-time delivery rate,
quality acceptance rate,
average lead time vs planned lead time,
number of variations per contract,
procurement cycle time (from requisition to contract award),
order fill rate,
stock accuracy (difference between physical stock count and system record),
and invoice processing time.

Why these indicators matter: They show whether SCM is producing value (not merely “activity”). For public projects, value must be linked to service delivery outputs and compliance requirements.

Procurement Cycle Time: A Hidden Driver of Schedule Slips

A common public project failure is not just late delivery—sometimes procurement itself takes too long. Exam answers should differentiate:

time from requisition to tender publication,
time from tender closing to evaluation completion,
time from evaluation to award approval,
and supplier mobilization time.

Reducing cycle time without violating compliance requires better planning:

pre-approved requirement documentation,
timely bid evaluation scheduling,
trained bid evaluation committees,
and effective document management.

A simple exam-friendly improvement plan:

Standardize requirement templates and technical spec checklists
Build evaluation committees early
Conduct pre-bid briefings to reduce clarifications
Maintain contract registers and delegated authority trackers
Use e-procurement where feasible to improve audit trails

Audit-Readiness: Evidence Management Through the SCM Process

Auditors evaluate whether:

procurement followed the correct method and approvals,
documentation exists for bid evaluation and award,
goods/services were delivered and accepted,
and payments match accepted deliveries.

Therefore, SCM evidence must be complete and consistent. Common audit evidence includes:

procurement plan and approvals,
bid documents and bid opening records,
bid evaluation reports,
contract awards and signed contracts,
delivery documentation (GRNs, delivery notes),
inspection and acceptance certificates,
variation orders and approvals,
invoices and payment records,
and stock movement records.

A typical exam scenario: a project struggles during audit because inspection certificates are missing. Strong answers explain the corrective action:

implement inspection checklists,
assign responsibility for evidence compilation,
and adopt document control systems with version tracking.

Fraud and Corruption Risk Controls: Practical Governance

Examiners may ask: “Discuss fraud risk in government SCM and how to mitigate it.” In government SCM, fraud risk often appears in:

bid rigging or collusion,
conflicts of interest in evaluation,
fake supplier invoicing,
delivery of inferior goods but payment approved,
manipulation of quantities during receiving,
and misuse of emergency procurement methods.

Mitigation controls (use as exam points):

segregation of duties (requesting, approving, receiving, paying)
conflict of interest declarations
secure bid processes and controlled access to bids
random audits and verification of deliveries
supplier performance monitoring across multiple contracts
use of technology for invoice matching and inventory reconciliation
ethics training for procurement and contract staff
whistleblowing channels with protections

Variation Management: Preventing Scope Drift and Cost Blowouts

Variations are common in construction and service projects. In SCM terms, variations often lead to:

increased costs,
changed delivery schedules,
and disputes about responsibility.

A strong exam response describes:

controlled variation processes,
documented change requests,
assessment of cost and schedule impact,
approval in accordance with delegation limits,
and contract amendments with proper recordkeeping.

Counterpoint you should acknowledge in exams:
Some variations are necessary (unknown site conditions, changes in regulatory requirements). The key is not to ban variations but to ensure variations are justified, evaluated, and approved correctly.

Continuous Improvement: Lessons Learned as a Procurement Asset

Continuous improvement in government SCM can include:

post-contract reviews (supplier performance and process performance),
capturing root causes of delays/defects,
updating specifications based on past inspection results,
refining procurement planning timelines,
improving warehouse layouts to reduce picking time and errors,
and revising training needs for evaluators and receiving teams.

A useful exam structure is to present a Plan–Do–Check–Act cycle for SCM improvement:

Plan: identify issues (e.g., stockouts, late deliveries), set targets
Do: implement changes (e.g., reorder point buffers, revised contract KPIs)
Check: measure outcomes (OTD, acceptance rate, cycle time)
Act: institutionalize successful changes or rework failed interventions

Integrated Mini-Case: Disaster-Proofing a Municipal Fleet Project

To integrate all SCM stages, consider a municipal fleet upgrade project requiring vehicles, spare parts, and maintenance services. The project includes:

procurement of fleet vehicles,
procurement of spares for the first year of operations,
and a maintenance service contract for reliability.

Common SCM risks:

vehicle lead times longer than planned due to supply disruptions,
spare parts not matching the vehicle models delivered,
maintenance contract starting late due to onboarding delays,
warehouse capacity issues for spares,
and invoice disputes due to acceptance evidence gaps.

Integrated corrective approach (high exam value):

initiation: confirm vehicle model and technical requirements, validate supplier capability
planning: revise procurement schedule to account for vehicle lead time variability; define spares list aligned to delivered models
procurement and contract: include delivery milestones and acceptance testing for spares and vehicles; set service commencement conditions
logistics and inventory: allocate warehouse storage for spares; set reorder points for consumables
monitoring: track on-time delivery, acceptance rate, and service KPIs; enforce evidence-based payments
governance: maintain audit-ready documentation and escalate non-performance early

This integrated example shows that SCM success is not a single action; it is a chain of coordinated controls and performance management.

Exam-Ready Summary of Key Takeaways (Memorise These Themes)

SCM in government projects is a delivery system: demand planning → procurement → contract management → logistics → inventory → performance and auditing.
Requirements definition drives VfM: functional/performance specs and clear acceptance criteria prevent rework and disputes.
Procurement planning is the schedule enabler: cycle time and lead times determine whether project milestones can be met.
Contract management is where delivery becomes enforceable: milestones, KPIs, variation control, and evidence-based payment.
Logistics and warehousing protect value: prevent damage, stockouts, and traceability failures.
Inventory control requires structured methods (ABC analysis, reorder points, safety stock) tuned for lead time uncertainty.
Governance and audit readiness require evidence discipline across GRNs, inspections, approvals, invoices, and stock movements.
Fraud risk controls depend on segregation of duties, conflict-of-interest management, and verification of deliveries.
Continuous improvement reduces repeat failures through post-contract reviews and performance dashboards.

Quick Practice Questions (Short-Answer Style for Revision)

Explain the difference between functional requirements and technical specifications in government procurement.
Discuss three reasons poor requirements definition leads to cost escalation in project SCM.
Outline the major activities that fall under contract management after a tender is awarded.
List at least five logistics/warehouse controls that improve audit defensibility and reduce loss/damage.
Describe an inventory reorder point concept and explain why safety stock is needed in government SCM.
Identify fraud risk points in procurement and receiving, and propose one control for each risk.
Explain how procurement cycle time can affect overall project schedules even when suppliers deliver correctly.
Describe a corrective action process for non-conformance found during inspection/acceptance.

If you want, I can also produce separate add-on exam packs that mirror specific South African module codes (e.g., MNG 0001 and related management/operations modules, or public administration procurement units) with memorisation tables, marking-rubric style answers, and scenario-based questions.