Processes for the Development of a Business Concept

WM-01-WE01 exists because the most common failure point for new entrepreneurs is not a lack of enthusiasm for their idea, but a lack of structured, evidence-based interrogation of that idea before resources are committed. The element forces a candidate to do four things that are individually easy to skip but collectively essential: describe the offering with enough precision that others can evaluate it, go out and test whether real buyers actually exist in accessible places, measure viability against real numbers rather than optimistic assumptions, and then consolidate what was learned into a brief that will guide everything that follows.

In the context of the broader Entrepreneur qualification, this element occupies the critical transition point between classroom learning and real commercial action. A candidate who has studied PM-02 and KM-06 in their knowledge modules knows what a viability tool looks like and what a product brief should contain — but knowing the structure of a tool is not the same as applying it to a real, uncertain situation where the outcome is not predetermined. WE01 is where that application happens, under the supervision of a real or realistic host-employer, with the messiness and unpredictability of actual market conditions.

The element also exists to create a permanent, dated record of thinking. One of the most valuable things an entrepreneur can do early in a venture is maintain a honest record of what they believed at each point and what changed their mind. When things go wrong later — or when things go unexpectedly right — that record becomes the evidence base for better decisions next time. The logbook structure mandated by this element is not bureaucratic overhead; it is the early habit of evidenced decision-making that separates durable businesses from those that collapse when the founder's initial assumptions turn out to be wrong.

WE01 is explicitly bounded at both ends. At its entry point, it assumes that the candidate already has foundational knowledge from PM-02 (which includes the viability tool used in WA0103) and from KM-06 (which defines the product/service/experience brief structure used in WA0104 and the overview required in WA0101). The element does not re-teach those frameworks — it requires the candidate to apply them. A candidate who arrives at their placement without having engaged seriously with those knowledge modules will find this element significantly harder, because the tools referenced throughout are assumed rather than introduced.

At its exit point, WE01 hands off directly to WE02, which covers goal-setting and business-plan review. This boundary is precise and important. WE01 ends the moment a viable idea and a completed product brief exist. What happens next — translating that brief into a business plan, setting measurable goals, and reviewing progress against them — belongs entirely to WE02. A candidate who starts drafting a full business plan as part of their WE01 portfolio is working beyond this element's scope, and conversely a candidate who mistakes goal-setting for the kind of selling-opportunity identification required here is conflating two separate activities.

Within WE01 itself, the four activities are sequenced but not siloed. WA0101 (business overview) must come first because it defines what is being evaluated. WA0102 (selling opportunities) tests whether the offering described in the overview has accessible buyers. WA0103 (viability evaluation) uses the real data gathered in WA0102 as its inputs — the Nkosi's Fresh Kitchen example makes this explicit: the viability check on 18 August directly uses the trial result from 14 August. WA0104 (product brief) then reflects the conclusions of WA0103. Any portfolio in which these four activities appear as independent documents, with no visible connection between them, has failed to demonstrate the developmental process the element actually requires.

The element also explicitly excludes impressionistic or assumption-based viability assessment. Using a recognised tool — specifically the KM-06 viability self-check or the PM-02-PS02 viability tool — is not optional. A candidate who writes a thoughtful paragraph about why they believe the concept is viable, without applying a structured tool to real numbers, has not met the requirement for WA0103 regardless of how persuasive the paragraph is.

Within the Work Experience module, WE01 is the first substantive activity the candidate undertakes at their placement. It sets the evidential and methodological standard for everything that follows. The module's overall purpose is to bridge the gap between theoretical knowledge and real commercial practice, and WE01 is where that bridge is first crossed.

The element mirrors the practical work already completed in PM-02, which means the candidate should not be encountering the viability tool or the brief structure for the first time during placement. Instead, placement is where those tools are used on real, uncertain problems rather than on case studies with predetermined answers. This mirroring is deliberate: the qualification designers understood that using a tool on a textbook problem and using it on a real problem where the answer might be uncomfortable are genuinely different cognitive tasks.

WE01's outputs — specifically the product brief produced in WA0104 — feed directly into WE02. The goal-setting work in WE02 only makes sense if there is a defined, viable offering to set goals around. A product brief that is vague, internally inconsistent, or not grounded in the viability conclusion reached in WA0103 will create problems downstream in WE02, because the goals set there will be anchored to an unclear offering. This forward dependency is one of the practical reasons why the assessment of WE01 looks so carefully at internal consistency: a poorly constructed product brief does not just lose marks in this element, it undermines the candidate's ability to do credible work in the next one.

Across the broader qualification, WE01 represents the entrepreneur's first encounter with the discipline of evidence-based iteration — the cycle of proposing, testing, evaluating, and refining that characterises how successful ventures are actually built. The Palesa Prints example in the source curriculum makes this concrete: her original general-apparel concept was narrowed, during the placement, into a fast-turnaround small-batch offering. That narrowing is not a failure — it is exactly what the element is designed to produce. An idea that has been genuinely tested and refined is worth more, commercially and evidentially, than an idea that has only ever been described.

The following sequence describes how a candidate should work through WE01 in a real or realistic placement setting. Each step corresponds to one of the four activities and should produce both a dated logbook entry and a supporting document.

Step 1 — WA0101: Prepare the business overview (first days of placement) Before any market testing or financial analysis can happen, the candidate needs a clear, written description of what the offering actually is. This is not a vision statement or an elevator pitch — it is a structured document that covers what the product or service is, who it is for, how it will be delivered, and at what approximate price point. The KM-06 brief structure should guide the format. At this stage, the overview will be a first draft, and it should be dated as such. The candidate should resist the temptation to over-refine this document before any market feedback has been gathered: the whole point is to have something concrete enough to test, not something polished enough to publish.

Logbook entry: Record what the overview documents, what the key assumptions embedded in it are, and any specific uncertainties the candidate already recognises at this stage. The entry should be specific enough that a reader can see what was actually decided, not just that the candidate sat down and thought about it.

Step 2 — WA0102: Identify or evaluate selling opportunities With a clear overview in hand, the candidate moves to testing whether real selling opportunities exist. This requires going out — physically or through direct communication — to the places and people who might stock, distribute, or buy the offering. The selling-opportunity types and methods from KM-05-KT02 should be applied explicitly: the candidate should be able to name which type of selling opportunity they are testing (e.g., direct retail, consignment, B2B supply) and which method they are using to evaluate it (e.g., direct visit, phone interview, observation of competitor stocking patterns).

For each selling opportunity evaluated, the candidate records a specific outcome: not 'the shop owner seemed interested' but 'agreed to trial at X units/week' or 'declined, citing reason Y.' The Nkosi's Fresh Kitchen logbook entry from 14 August is a model for what this specificity looks like in practice. At minimum, two prospective opportunities should be evaluated, because a single data point is too thin a basis for a viability conclusion.

Logbook entry: Record the date, what was done, who was spoken to (name and specific context where possible), and what specific outcome was reached. Vague entries like 'visited potential customers' do not meet the requirement.

Step 3 — WA0103: Evaluate viability Once real market data exists from Step 2, the candidate applies the KM-06 viability self-check and/or the PM-02-PS02 viability tool to the actual numbers. The key discipline here is using the data from Step 2 as inputs — the selling-opportunity results are not just context, they are the demand-side evidence the viability tool needs. The candidate should calculate or estimate: revenue at the volume indicated by the selling-opportunity evaluation, fully-loaded cost per unit (not just materials), and the resulting margin. They should also assess non-financial viability factors: is the candidate's time available? Are suppliers accessible? Are there regulatory requirements?

The conclusion reached should be specific and conditional where appropriate — as in the 18 August Nkosi's Fresh Kitchen entry, which reached a 'marginally viable at current volume, conditional on securing a second stockist within two months' conclusion, rather than a simple yes or no. This conditional form is often more honest and more useful than a binary verdict.

Logbook entry: Record the tool used, the key inputs, the calculation or assessment performed, and the specific conclusion reached, including any conditions or flags.

Step 4 — WA0104: Prepare the final product brief The product brief is produced last because it should reflect everything learned in Steps 1 through 3. A brief that reads as if it were written before the viability work was done — with optimistic volume assumptions that contradict the selling-opportunity findings, or a price point that the viability evaluation showed was unworkable — fails the internal consistency test that assessors specifically look for.

The brief should follow the KM-06 brief structure and should explicitly incorporate the viability conclusion: if the viability evaluation found that the concept is viable only above a certain volume, the brief should state that minimum volume as a launch condition. If the selling-opportunity evaluation found that one channel type is accessible and another is not, the brief should reflect the accessible channel.

Logbook entry: Record what the brief contains, how it differs from the initial overview document prepared in Step 1, and why — specifically, what changed as a result of the market testing and viability evaluation.

WE01 has some of the most specific documentation requirements of any element in the Work Experience module, and those requirements exist for a clear reason: they are the only thing that distinguishes genuine, developing evidence from a retrospective write-up produced after the fact.

The minimum documentation set consists of four logbook entries and four supporting documents. The logbook entries must be dated, must correspond one-to-one with the four activities (WA0101 through WA0104), and must record specific, completed outcomes rather than planned intentions. An entry that says 'I plan to visit two spaza shops next week' is not evidence of WA0102 — it is evidence that WA0102 has not yet happened. The entry must be written after the activity is completed, but it must be written at or near the time of completion, not weeks later.

The four supporting documents are: (1) a dated business overview consistent with the KM-06 brief structure; (2) a record of selling opportunities identified or evaluated, with specific detail including names, locations, outcomes, and volumes or conditions where relevant; (3) a completed viability evaluation using either the KM-06 self-check or the PM-02-PS02 tool, showing actual inputs and a specific conclusion; and (4) a final product/service/experience brief. These documents should be internally consistent — someone reading all four should see a single, developing story, not four independent documents that could have been written in any order.

In addition to these four documents, the element requires a supervisor-signed WE record. This is not optional. A portfolio without the supervisor signature is incomplete regardless of the quality of the other documents. The supervisor signature serves two purposes: it confirms that the placement actually happened and that the activities described were carried out in a real or realistic context, and it provides the candidate with an independent corroborating witness whose account can be checked if questions arise about authenticity.

Dating discipline is more important here than candidates sometimes appreciate. Dates should be specific (day, month, year) rather than approximate ('mid-August'). They should form a logical sequence: the overview should be dated before the selling-opportunity record, which should be dated before the viability evaluation, which should be dated before the final brief. A portfolio where these dates are out of sequence, or where multiple documents share the same date, raises questions about whether the development process was genuine.

For candidates who are conducting their placement remotely or in a partially virtual context — for example, Sipho Radebe's scenario, where selling opportunities are spread across a wide geographic area — documentation of the selling-opportunity evaluation needs to be especially specific about how those remote contacts were made: call logs, email chains, voice-message records, or notes from video calls all serve as supporting evidence that the conversations actually happened.

The Nkosi's Fresh Kitchen placement scenario, drawn directly from the curriculum, provides the clearest illustration of how WE01 should work in practice. Thabo Nkosi is formalising a meal-prep concept — a business that prepares ready-to-eat meals and supplies them to local retail outlets on a consignment basis. The candidate placed with Thabo supports him in working through all four WE01 activities.

WA0101 — Business overview: Thabo's business offering is documented as a weekly meal-prep consignment service providing a specific number of meal units per week to local spaza shops within a defined delivery radius. The overview specifies the product (ready-to-eat meals), the delivery mechanism (consignment to stockists), the target customer (spaza-shop owners who resell to end consumers), and the approximate price point. It is not a general description of 'healthy food' — it is specific enough that a stockist could evaluate whether it fits their shop.

WA0102 — Selling opportunities (14 August): The candidate visits two spaza shops within the host-employer's delivery radius. The visits are documented with specific detail: Mrs Dlamini on Vilakazi Street agrees to a two-week trial at 8 units per week; the second shop declines, citing existing supplier loyalty. Both outcomes are recorded honestly. The second outcome — a refusal — is as evidentially valuable as the first, because it provides a real data point about the limits of the accessible market. The logbook entry is dated 14 August and records who was spoken to, what was discussed, and what specific outcome was reached.

WA0103 — Viability evaluation (18 August): Using the trial result from 14 August as the demand-side input, the candidate applies the KM-06 viability self-check to Thabo's numbers. The key calculation checks whether the trial volume of 8 units per week generates a positive margin after fully-loaded costs. The conclusion is specific and conditional: the trial is marginally viable at 8 units per week, but Thabo needs a second stockist within two months to reach his target margin. This is not a simple 'yes, this is viable' — it is an evidenced, conditional verdict that points directly to what needs to happen next. The logbook entry is dated 18 August and records the tool used, the inputs (specifically the 8-unit trial volume and the fully-loaded cost per meal), and the conditional conclusion.

WA0104 — Product brief: The final brief reflects the conclusions of both WA0102 and WA0103. It documents the offering as viable at a minimum of two stockist outlets, specifies the consignment arrangement, and sets the minimum viable volume as a launch condition. It does not describe a general meal-prep business — it describes Thabo's specific, tested, evaluated concept. Crucially, someone reading the brief alongside the viability evaluation can see that the brief's minimum-volume condition comes directly from the viability evaluation's conditional conclusion. The internal consistency is visible.

What makes this example valuable as a model is not just that each document is complete — it is that the documents tell a single, developing story. The overview set the stage; the selling-opportunity visits generated real data; the viability evaluation used that data to reach a specific, conditional conclusion; and the brief incorporated that conclusion. The Blessing Mthembu counter-example shows what the absence of this development looks like: a single unsigned summary produced retrospectively, with no evidence of the idea ever being tested or refined.

The Radebe AgriTech Supplies scenario presents a meaningfully different set of challenges from Nkosi's Fresh Kitchen, and working through it carefully illustrates how the WE01 activities adapt to different business contexts.

Sipho Radebe's concept is a bundled advisory-plus-product offering for farmers — he does not just sell agricultural inputs, he packages them with advice and support tailored to the farmer's specific context. The two distinctive complications identified in the curriculum are: (1) selling opportunities are scattered across a wide geographic area rather than concentrated in a local retail environment, and (2) demand is seasonal and weather-dependent rather than steady.

WA0101 — Business overview for AgriTech: The overview must capture the bundled nature of Sipho's offering. It is not enough to describe 'agricultural supplies' — the brief structure requires specificity about what the advisory component includes, how it is delivered (in-person farm visits? Remote consultation? Scheduled seasonal check-ins?), what products are bundled with the advice, and at what price point. The geographic dispersal of customers needs to be addressed: the delivery mechanism for advisory services to farmers spread across a wide area is fundamentally different from delivering meal packs to nearby spaza shops.

WA0102 — Selling opportunities for AgriTech: Because Sipho's farmer network is geographically dispersed, the selling-opportunity evaluation cannot rely on a simple walk-in visit. Instead, the candidate must map Sipho's existing farmer network explicitly — identifying which farmers are in which areas, which are already regular customers, which have expressed interest in advisory services, and which represent new leads accessible through the existing network. The specific selling-opportunity types from KM-05-KT02 that apply here are likely to include B2B supply relationships and referral-based channel development through the existing network. The evaluation records, for each contact, whether the farmer is interested in the bundled offering and at what level of engagement — perhaps some want full advisory support, others only want discounted bulk-purchase pricing.

The key contrast with Nkosi's Fresh Kitchen is that the geographic dispersal means some selling opportunities cannot be physically visited during the placement period. The candidate and Sipho might evaluate these remotely — by phone or voice message — and the documentation must reflect this: dates, contact names, method of contact, and specific outcomes.

WA0103 — Viability for AgriTech: The viability evaluation here must grapple with the seasonal demand complication in a way that the Nkosi's Fresh Kitchen scenario did not. A meal-prep business has relatively stable weekly demand; an agri-advisory-plus-product bundle does not. Sipho's revenue will spike around planting season and potentially again around harvest, and could be severely affected by drought or flood in ways that meal-prep is not. The viability tool should be applied at seasonal extremes: what does the margin look like in peak season? What does cash flow look like in the off-season? Is there enough working capital to survive the gaps? The conclusion might be conditional in a different way from Thabo's: 'viable in aggregate across the year, but requires a cash-flow management mechanism to bridge the off-season.' This is a specific, evidenced conditional conclusion that reflects the real complication of the business model.

WA0104 — Product brief for AgriTech: The brief must reflect both the bundled nature of the offering and the seasonal viability condition. A brief that describes Sipho's business as 'agricultural supplies with advice' without specifying how the advisory component is structured, how pricing accounts for seasonal variation, and what minimum engagement level is needed for viability has not met the specificity requirement.

Comparing this scenario to Nkosi's Fresh Kitchen makes a crucial point: WE01's activities are not a fixed script — they are a framework that must be applied thoughtfully to the specific conditions of the placement. The same four activities, applied to a geographically dispersed, seasonally volatile business, produce very different evidence from the same activities applied to a steady local retail business. Both are valid applications of the element; neither is easier or harder in absolute terms — they are different.

The most common mistakes in WE01 are not accidental — they have predictable causes, and understanding those causes helps candidates avoid them.

Mistake 1: The retrospective write-up. This is the single most common and most serious mistake. A candidate completes their placement, returns home, and writes up their logbook entries from memory — or, worse, writes a single comprehensive narrative of what they did rather than four separate dated entries. The curriculum explicitly names this pattern through the Blessing Mthembu counter-example: a single unsigned summary produced the night before submission, with no evidence of the idea being tested or refined during real placement time. Why does this happen? Because maintaining a logbook during a busy placement feels like administrative overhead when the candidate is focused on the actual work. The fix is simple in principle but requires discipline: make the logbook entry on the same day as the activity, or within 24 hours at most. Dated entries written close to the events they describe are far more credible than entries that all share the same date or that describe past events in retrospect.

Mistake 2: Describing planned rather than completed work. A logbook entry that says 'I intend to visit two shops next week' is not evidence of WA0102 — it is a plan. The element requires evidence of completed activities with specific outcomes. Why does this happen? Often because a candidate writes up the entry before undertaking the activity, either from poor timing or from wanting to appear prepared. The outcome recorded must be a real result, not an anticipated one.

Mistake 3: Vague business overview. Describing the offering as 'a food business' or 'agricultural consulting' without the specific detail the KM-06 brief structure requires is insufficient. Assessors look for specificity: what exactly is the product or service, who exactly is the customer, how exactly is it delivered, at what approximate price. Why does vagueness happen? Because vagueness feels safer — a specific description can be wrong, but a vague one cannot be contradicted. The curriculum is explicit that vagueness is a failure mode, not a safe default.

Mistake 4: Impressionistic viability assessment. Writing a persuasive paragraph about why the concept seems viable, without applying the KM-06 viability self-check or the PM-02-PS02 tool to actual numbers, does not meet the requirement for WA0103. Why does this happen? Because running actual numbers requires real data — costs, margins, volumes — that candidates sometimes find it difficult to obtain from their host-employer. The right response to this difficulty is to ask: the host-employer is a real or realistic business, and a placement supervisor who is unwilling to share even approximate cost information is not providing a genuine placement context. If real numbers are unavailable, estimated numbers with clearly stated assumptions are acceptable, but the tool must still be applied.

Mistake 5: The disconnected portfolio. Four documents that could each have been written in any order, with no visible connection between them, fail the internal-consistency test. A product brief that does not reflect the viability evaluation's conclusion; a viability evaluation that does not use data from the selling-opportunity record; an overview that is never revised despite significant market feedback — these are all symptoms of the same failure: treating the four activities as independent rather than sequential. Why does this happen? Because it is easier to write four separate documents than to maintain the discipline of having each one genuinely inform the next.

Mistake 6: Missing the supervisor signature. The WE record signed by a supervisor is explicitly required and cannot be substituted by any other document. A portfolio without it is incomplete regardless of quality. Why is this missed? Sometimes because candidates forget to arrange it before leaving the placement, and a supervisor who has already moved on is harder to reach. The fix is to get the signature at the placement itself, before leaving.

Both candidates and assessors should be alert to specific warning signs that indicate WE01 evidence is not genuine or not meeting the standard.

All logbook entries share the same date. This is the clearest signal of a retrospective write-up. Four activities spread across a placement period should produce four entries spread across that period. If all four are dated the same day — or if they are undated — the developmental progression the element requires is absent.

The product brief reads as if it was written before the viability work. If the brief describes the concept in exactly the same terms as the initial overview, with no modification based on selling-opportunity or viability findings, it suggests the brief was not actually produced last. Assessors specifically look for this: a brief that ignores the conditional conclusion of the viability evaluation, or that assumes market conditions the selling-opportunity evaluation found to be unavailable, has not been informed by the work it was supposed to reflect.

Selling-opportunity entries lack names, places, or specific outcomes. An entry that describes 'consulting with potential customers' without identifying who was spoken to, where, and what they said is insufficient. If the candidate genuinely carried out the selling-opportunity evaluation, they will have names and specific responses. Absence of specificity suggests the visits may not have happened.

The viability conclusion is a simple 'yes.' Real viability evaluations almost always surface conditions, risks, or minimum requirements. A viability evaluation that concludes 'yes, this is viable' with no qualifications or conditions should prompt an assessor to ask what tool was used and what inputs were applied. The Nkosi's Fresh Kitchen example is instructive: even a genuinely viable concept (in that case, marginally viable at 8 units per week) came with a specific condition attached.

The supervisor signature is absent or the supervisor is uncontactable. A missing signature is a definitive gap. An absent supervisor who cannot be reached to confirm the placement details raises questions about whether the placement was real.

The candidate cannot discuss the choices made in their brief. If an assessor asks 'what changed between your initial overview and your final brief, and why?' and the candidate cannot answer with specifics, this suggests the brief was not produced through a genuine developmental process. A candidate who genuinely worked through the four activities will have a clear answer to this question.

The following checklist consolidates the standard that WE01 requires. Candidates can use it as a self-check before submission; assessors can use it as a marking reference.

Logbook entries: ☐ Four separate dated logbook entries exist, one per activity (WA0101, WA0102, WA0103, WA0104) ☐ Entries are dated on or close to the date of the activity (not all on the same date) ☐ Each entry records a specific, completed outcome — not a plan or intention ☐ The sequence of dates is logical (overview before selling-opportunities before viability before brief)

WA0101 — Business overview document: ☐ Follows the KM-06 brief structure (not a vague description) ☐ Specifies what the offering is, who it is for, how it is delivered, and at what approximate price ☐ Is dated on the same day as the WA0101 logbook entry

WA0102 — Selling-opportunity record: ☐ Identifies the specific type(s) of selling opportunity tested, per KM-05-KT02 ☐ Records at least two prospective opportunities evaluated ☐ Includes specific details: names, locations, method of contact, and specific outcome for each ☐ Records both positive and negative outcomes honestly

WA0103 — Viability evaluation: ☐ Names the tool used (KM-06 self-check or PM-02-PS02) ☐ Uses real data from WA0102 as demand-side inputs ☐ Shows the key calculations or assessments performed ☐ Reaches a specific, evidenced conclusion — conditional where appropriate, not a bare yes/no ☐ Flags any non-financial viability concerns (resources, regulatory, supplier access)

WA0104 — Product brief: ☐ Follows the KM-06 brief structure in full ☐ Reflects the viability evaluation's conclusion — especially any conditions or minimum requirements ☐ Reflects the selling-opportunity findings — specifically which channels are viable ☐ Differs visibly from the initial overview in ways that reflect what was learned

Overall portfolio: ☐ Supervisor-signed WE record is present ☐ All four supporting documents are present ☐ The four documents are internally consistent — the same story told in four stages ☐ A reader can trace the development from overview to brief and see what changed and why

Working through WE01 rigorously — rather than treating it as an administrative hurdle — produces benefits that extend well beyond the qualification itself.

Real market intelligence before committing resources. The selling-opportunity evaluation in WA0102 is, functionally, a miniature market test. The candidate or host-employer goes out to real potential buyers, presents the offering, and records real responses. For a new venture, this kind of early-stage, low-cost market testing is enormously valuable: it surfaces real objections, real pricing expectations, and real channel constraints before any significant investment has been made. The fact that Mrs Dlamini agreed to a trial while the second shop declined due to supplier loyalty is not just evidence for an assessor — it is commercially useful information that Thabo Nkosi can act on. The second shop's reason for declining tells him something specific about the competitive landscape he is entering.

A viability conclusion grounded in real numbers. The structured viability evaluation in WA0103 forces the candidate to work through the financial logic of the concept explicitly, using real or realistic cost and volume data. Many new entrepreneurs operate on intuition rather than calculation, and the viability tool interrupts that pattern. The discipline of checking margin at actual trial volumes, rather than assumed optimistic volumes, is the difference between discovering a problem early (when it can be corrected) and discovering it after resources have been committed.

A brief that reflects reality. The product brief produced in WA0104 is not just an assessment document — it is a practical tool the candidate or host-employer can use in the next stage of development. The curriculum specifically mentions Thabo using his product brief in a funding application. A brief grounded in real market testing and a genuine viability evaluation is far more persuasive in that context than one produced in isolation.

The habit of evidenced iteration. Perhaps the most durable benefit of working through WE01 properly is the practised habit of testing, recording, and refining rather than asserting. Entrepreneurs who maintain this discipline throughout their ventures make better decisions because their decisions are based on evidence rather than assumption. The logbook habit instilled by WE01 is, in microcosm, the same discipline that effective venture management requires at scale.

WE01's requirements create some genuine practical risks that candidates should understand and manage.

The risk of a placement that does not provide real access. WE01 requires genuine, sustained engagement with a real or realistic business context. A host-employer who does not allow the candidate meaningful access to real customers, real cost data, or real selling-opportunity situations will produce a placement where WE01's requirements are structurally impossible to meet. Candidates should clarify, before starting their placement, that they will have the access the element requires. If a supervisor is unwilling to share even approximate cost information, the viability evaluation cannot be done with real numbers.

The risk of confirmation bias in viability evaluation. When a candidate has invested time and emotional energy in an idea, there is a natural tendency to interpret the viability evaluation optimistically. Applying the tool mechanically to real numbers is the guard against this — but the risk is that candidates choose inputs that confirm viability rather than inputs that test it. The conditional conclusion reached in the Nkosi's Fresh Kitchen example — 'marginally viable, requires a second stockist within two months' — is only reached if the candidate is genuinely honest about what the numbers show.

The risk that genuine market testing surfaces an unviable concept. This is not actually a risk to the candidate's assessment — it is a possible outcome that the element is explicitly designed to accommodate. An honest viability evaluation that concludes the concept is not viable at current conditions, with a product brief that honestly reflects that conclusion and specifies what would need to change, meets the element's requirements. What fails is pretending the concept is viable when the evaluation shows it is not. The commercial risk, however, is real for the host-employer: WE01 may surface findings that require significant re-evaluation of the business direction.

The administrative burden on a real host-employer. A real host-employer like Thabo Nkosi is managing a real business with real constraints. Asking them to support a candidate's documentation requirements — including signing off on a WE record, sharing cost data, and facilitating two selling-opportunity visits — is a genuine ask. Candidates should be respectful of this, prepare well before each interaction, and not treat the host-employer as a resource for their portfolio rather than a real person with a real business to run.

Several misconceptions about WE01 appear regularly in borderline portfolios, and addressing them directly helps candidates avoid the traps.

Misconception: 'The product brief is the main deliverable — the logbook entries are just supporting notes.' Correction: The logbook entries are co-equal evidence with the four supporting documents. A polished product brief with thin, vague, or retrospective logbook entries does not meet the standard. The element explicitly states that a portfolio with entries that only describe planned rather than completed work falls short regardless of how polished the final documents appear. The process is as important as the product.

Misconception: 'Viability evaluation means explaining why the idea is a good one.' Correction: Viability evaluation means applying a recognised tool to real data to reach a specific, evidenced conclusion about whether the concept is commercially viable under realistic conditions. It is not a persuasive essay — it is an analytical process with a structured input and a specific output. The tool from KM-06 or PM-02-PS02 must be used.

Misconception: 'A single selling-opportunity conversation is enough to demonstrate WA0102.' Correction: The element requires that at least two selling opportunities be identified or evaluated, because a single data point is too thin a basis for a viability conclusion. The Nkosi's Fresh Kitchen example explicitly involves two spaza-shop visits, producing two different outcomes. The different outcomes are both valuable — the refusal from the second shop is as evidentially useful as the agreement from the first.

Misconception: 'If my host-employer is enthusiastic about the idea, that is evidence of viability.' Correction: Enthusiasm from a host-employer is not a substitute for a structured viability evaluation. The viability tool checks financial viability (margin, volume, cost), resource viability (time, skills, supplier access), and potentially regulatory viability (compliance requirements). A host-employer's enthusiasm may mean the idea is genuinely good — or it may mean they are optimistic without having run the numbers. The tool finds out which.

Misconception: 'The product brief should present the business in its best light for the funding application.' Correction: The product brief should reflect the viability conclusion actually reached — including any conditions or minimum requirements. A brief that presents a rosier picture than the viability evaluation supports is internally inconsistent and will lose marks. It is also commercially dangerous: a funding application based on an over-optimistic brief may secure funding that the business cannot actually sustain.

Before beginning each WE01 activity, a candidate (or assessor) should work through a set of structured questions to ensure the activity will produce evidence that meets the standard.

Before WA0101 — Business overview:

• What specifically is the product or service? Can I describe it in one precise sentence?
• Who specifically is the target customer? (Not 'people who like food' — a specific customer type or segment.)
• How specifically will it be delivered or sold? What is the channel?
• At what approximate price? What is the basis for that price point?
• What does the KM-06 brief structure require, and have I addressed every element of it?
• Is this overview specific enough that a stranger could evaluate whether it fits their needs — or is it still a general description?

Before WA0102 — Selling opportunities:

• Which specific type(s) of selling opportunity, per KM-05-KT02, am I testing?
• Which specific potential buyers or channel partners am I approaching?
• How will I document the contact — notes, a voice recording (with consent), a written summary immediately after?
• What constitutes a specific, usable outcome from each contact? (Agreement to trial at a specified volume? Refusal with a stated reason? Conditional interest pending further information?)
• Have I planned to approach at least two opportunities, so that I have more than one data point?

Before WA0103 — Viability evaluation:

• Which tool am I using — the KM-06 self-check, the PM-02-PS02 tool, or both?
• What is the demand-side input from WA0102? (What volume did the selling-opportunity evaluation actually indicate?)
• What is the fully-loaded cost per unit? (Not just materials — all costs attributed to producing and delivering one unit.)
• Are there non-financial viability factors I need to address: regulatory requirements, supplier availability, time and skill requirements?
• Is my conclusion specific and evidenced, or am I still working at the level of general impression?

Before WA0104 — Product brief:

• Does this brief reflect the viability conclusion from WA0103, including any conditions?
• Does this brief reflect the selling-opportunity findings from WA0102, including which channels are accessible?
• Does this brief differ from my initial overview in ways that reflect what I learned — and can I explain what changed and why?
• Would someone reading this brief and my viability evaluation see a clear, consistent story?

Understanding where marks are typically lost in WE01 helps candidates prioritise their effort and helps assessors calibrate their feedback.

Trap 1: The polished brief without the developing record. Assessors are trained to look for the developmental process, not just the final document. A product brief that is well-structured and detailed but that is not supported by dated logbook entries and supporting documents showing how it developed will score poorly, regardless of its quality in isolation. The brief is worth 10 of the element's marks; the process of developing it is what determines whether those 10 marks are earned or lost.

Trap 2: Treating WA0103 as a qualitative judgment. WA0103 is worth 16 marks — the highest-weighted single activity in the element. Marks are lost when candidates write thoughtful but analytically vague assessments of viability rather than applying the specified tool with real inputs. An assessor looking at WA0103 will ask: 'Which tool was used? What were the inputs? What calculation was performed? What specific conclusion was reached?' If those questions cannot be answered from the evidence, marks are lost.

Trap 3: Selling-opportunity entries that lack specificity. WA0102 is worth 12 marks. An entry that records 'visited local businesses' without specifying which businesses, who was spoken to, what was discussed, and what specific outcome was reached will lose marks for lack of specificity. The curriculum explicitly flags this: 'not a vague description' and 'not generic' are stated requirements.

Trap 4: A product brief inconsistent with the viability conclusion. This is the internal-consistency failure that assessors look for most carefully. If the viability evaluation concludes that the concept is viable only above a certain volume, but the brief does not incorporate that minimum volume as a condition, the brief and the viability evaluation are telling different stories. This inconsistency is a mark-losing signal even if both individual documents are otherwise complete.

Trap 5: Missing the supervisor-signed WE record. This is a completeness failure rather than a quality failure, but it is absolute: a portfolio without the supervisor signature cannot be marked as complete. Candidates who lose marks here almost always lost them because they failed to obtain the signature during the placement itself and could not retrieve it afterwards.

Trap 6: Confusing this element with WE02. Goal-setting and business-plan review work belongs to WE02, not WE01. Including substantial goal-setting content in a WE01 portfolio does not earn extra marks — it may actually signal to an assessor that the candidate is unclear about the boundary between the two elements.

WE01's connections to the broader practical and workplace components of the Entrepreneur qualification run in multiple directions.

Connection to PM-02: The viability tool used in WA0103 (the PM-02-PS02 viability tool) was introduced and practised in PM-02. WE01 is the first occasion on which that tool is applied to a genuinely uncertain real-world problem rather than a case study. The connection is deliberate: PM-02 builds competence with the tool; WE01 tests whether that competence translates to real application.

Connection to KM-06: Both the business overview structure required in WA0101 and the product/service/experience brief required in WA0104 follow the KM-06 brief structure. KM-06 also provides the viability self-check used in WA0103. WE01 is the practical application of the conceptual content introduced in KM-06.

Connection to KM-05: The selling-opportunity types and methods applied in WA0102 come from KM-05-KT02. WE01 requires the candidate to apply those types and methods to a real or realistic context, recording which specific opportunities were identified — not just demonstrating that they know what the types are in the abstract.

Connection to WE02: WE01's outputs feed directly into WE02. The viable concept and product brief produced in WE01 become the foundation for the goal-setting and business-plan review work in WE02. A candidate who produces weak WE01 evidence will find WE02 harder, because the goals set in WE02 need to be anchored to a defined, viable offering — and if that offering is not clearly defined, the goals will be vague in turn.

The broader practical strand: Across the qualification's practical and workplace components, WE01 represents the first sustained encounter with the discipline of evidenced, sequential, documented decision-making. Later workplace elements will require the same discipline — dated records, specific outcomes, and demonstrated connections between activities — and the habits formed in WE01 either prepare the candidate for those requirements or leave them underprepared.

The following self-check questions mirror the kind of evaluative thinking an assessor applies to WE01 portfolios. Candidates should work through them honestly before submitting.

Question 1: Look at your four logbook entries. Can you tell, from the dates alone, that they were written during the placement rather than after it? Is there a logical date sequence, and are the dates spread across the placement period?

Model answer: A portfolio with four entries dated over at least two separate weeks, with dates that follow the logical sequence (overview → selling opportunities → viability → brief), is credible. A portfolio where all entries share the same date, or where dates are not given, is not — regardless of content quality.

Question 2: Look at your product brief alongside your viability evaluation. Can you identify at least one specific thing the brief says that came directly from the viability evaluation's conclusion? If the viability evaluation was conditional, does the brief incorporate that condition?

Model answer: A strong portfolio will have a clear, traceable link: for example, if the viability evaluation concluded 'viable only above 8 units/week, requires second stockist within two months,' the brief should include a minimum-volume condition of at least 8 units/week and should note the requirement for a second distribution channel. If the brief could have been written without the viability evaluation (i.e., the brief would read identically whether or not WA0103 had been completed), the internal-consistency requirement has not been met.

Question 3: Look at your selling-opportunity record. Does it name specific people and places? Does it record specific outcomes, including any negative outcomes? Could an assessor, reading this record, verify that the visits or contacts actually happened?

Model answer: A sufficient selling-opportunity record names at least two contacts with enough specificity to be verifiable: names, locations, dates of contact, and specific outcomes (including refusals and the reasons given). A generic entry describing 'two potential stockists' without names, locations, or specific outcomes is insufficient.

Question 4: Look at your viability evaluation. Which tool did you use? What specific numbers did you put into it? What conclusion did it produce? Is that conclusion stated explicitly, or does it have to be inferred?

Model answer: A sufficient viability evaluation names the tool (KM-06 self-check or PM-02-PS02), states the key inputs (volume, cost per unit, margin calculation), and states an explicit conclusion that includes specific conditions where relevant. An implied conclusion — where the reader has to infer viability from the numbers without the candidate stating a conclusion — is less clear and less convincing than an explicitly stated one.

Question 5: If your assessor asked you 'what changed about your original business idea between when you first documented it and your final product brief, and why?' — could you answer with specifics?

Model answer: A candidate who genuinely worked through the four activities should be able to identify at least one specific change: perhaps a price point that was revised downward based on stockist feedback, a delivery frequency that was adjusted based on the stockist's operational needs, or a minimum-volume condition added based on the viability calculation. If nothing changed between the initial overview and the final brief, that is a warning sign — not because change is required, but because it is unusual for a genuine testing-and-evaluation process to produce no refinement at all.

While WE01 is primarily an entrepreneurial ideation and viability element rather than a compliance element, the South African regulatory context shapes both the selling-opportunity landscape and the viability evaluation in ways candidates should understand.

Food business regulation: For host-employers like Nkosi's Fresh Kitchen, the regulatory context is highly relevant to viability. A meal-prep business that supplies food products to retail outlets in South Africa must comply with food safety requirements under the Foodstuffs, Cosmetics and Disinfectants Act (Act 54 of 1972) and may need to register with the local municipality as a food premises. The cost of compliance — including potentially a food premises inspection, labelling requirements, and storage and handling standards — should appear as a factor in the viability evaluation. The scenario in the curriculum specifically identifies regulatory requirements as a possible complication surfaced during viability evaluation: 'Your host-employer's viability evaluation surfaces a regulatory requirement not previously considered. Describe how you would incorporate this into the final brief.' The answer is that it becomes a condition in the brief: 'viable, subject to obtaining municipal food premises registration and complying with labelling requirements.'

Agricultural input regulation: For host-employers like Radebe AgriTech Supplies, relevant regulation includes the Fertilizers, Farm Feeds, Agricultural Remedies and Stock Remedies Act (Act 36 of 1947), which governs the registration and sale of agricultural inputs. A bundled advisory-plus-product offering that includes registered agricultural remedies or fertilisers must comply with this Act's requirements. The advisory component may also raise questions about whether the adviser is providing services that require professional registration (e.g., under the Agricultural Produce Agents Act if trading in fresh produce). These regulatory considerations should be part of the viability evaluation's non-financial assessment.

General business registration: Any South African business, once it moves beyond the planning stage, will need to be registered with CIPC (Companies and Intellectual Property Commission) if it operates as a company, or operate as a sole proprietor (which does not require formal CIPC registration but does require tax registration with SARS). A viability evaluation that does not consider the cost and timeline of business registration as part of the start-up requirement is incomplete, though for many early-stage concepts the registration itself is not a barrier to viability.

Consumer protection: The Consumer Protection Act (Act 68 of 2008) applies to any business supplying goods or services to consumers in South Africa. For a meal-prep business, this includes requirements around accurate product description, right of return, and food safety disclosure. For an agri-advisory business, it includes requirements around fair dealing and disclosure of potential conflicts of interest. Understanding that these obligations exist — even at a high level — is part of a complete viability assessment.

The South African economic context directly shapes both the selling-opportunity landscape and the viability calculation for the kinds of early-stage ventures WE01 is typically applied to.

Constrained consumer spending: South Africa's consumer spending environment is characterised by ongoing economic pressure, with high unemployment (officially above 30%), high food price inflation, and relatively low disposable income in the township and peri-urban markets where many WE01 host-employers operate. This context shapes selling-opportunity evaluation directly: a meal-prep concept that is priced for a market segment that cannot actually afford it at the margin it needs to survive is not viable regardless of how enthusiastic potential stockists seem. The viability tool should be calibrated against realistic consumer price points in the specific market, not against what the concept would need to charge to be viable in a higher-income setting.

The spaza economy: South Africa's township retail ecosystem — the network of spaza shops, tuck shops, and informal markets through which most low-income South Africans purchase everyday goods — is both an opportunity and a challenge for early-stage ventures. The spaza network provides existing, trusted distribution channels that do not require the capital investment of formal retail shelf space. However, spaza shops typically operate on very thin margins themselves and favour fast-moving, low-cost items. A meal-prep offering competing for shelf space in a spaza shop needs to demonstrate that it turns over quickly enough to justify the opportunity cost of the shelf space. This is exactly the kind of consideration that should appear in the selling-opportunity evaluation and the viability assessment.

Seasonal and weather-dependent demand: The Radebe AgriTech scenario highlights a feature of the South African agricultural economy that is particularly pronounced in drought-prone regions: demand for agricultural inputs and advisory services is highly sensitive to both the agricultural calendar and to rainfall patterns. In regions experiencing drought, farmers may reduce purchases of inputs they cannot finance without a reliable harvest. The viability evaluation for a business in this sector must model cash flow across the full agricultural year, not just at peak-season revenue.

Access to finance: For early-stage entrepreneurs in South Africa, access to start-up finance is a persistent constraint. The viability evaluation should assess whether the concept can be funded from the entrepreneur's own resources, or whether external funding is required — and if so, whether that funding is realistically accessible. The product brief's role in a funding application (as in Thabo's case) is a direct consequence of this constraint: the brief needs to be credible enough to support a funding application, which means it must reflect a viability evaluation that funders will find convincing.

WE01's four activities apply across all sectors in which the Entrepreneur qualification might be pursued, but the specific challenges, typical selling-opportunity types, and common viability complications vary significantly by sector. Understanding these variations helps candidates avoid applying a generic template where a sector-specific application is needed.

Food and beverage (Nkosi's Fresh Kitchen model): In this sector, selling opportunities typically involve either direct-to-consumer sales (at a market, event, or from a home-based setup), consignment supply to retailers (spaza shops, informal markets, small grocery stores), or formal retail supply (larger supermarkets, canteens). Viability evaluation must address food safety and shelf-life constraints that do not apply in other sectors: a meal-prep product with a two-day shelf life cannot be distributed across a wide geographic area. Regulatory requirements (food premises, labelling, cold-chain management) appear as non-financial viability factors. The key selling-opportunity type to test is typically consignment retail, as it requires the least upfront capital from the retailer and is the most accessible channel for a new, unproven food product.

Agricultural inputs and advisory (Radebe AgriTech model): In this sector, selling opportunities are typically B2B relationships with farmers, agricultural cooperatives, or farming associations. Geographic dispersal is a standard feature, not an exception. Viability evaluation must model seasonal cash flow rather than steady monthly revenue. The bundled advisory-plus-product model is increasingly common in this sector because it differentiates a supplier from commodity competitors — but the advisory component has cost implications (the adviser's time, travel, and expertise) that must be fully loaded into the cost-per-engagement calculation. Regulatory requirements around registered agricultural inputs add a compliance dimension to viability.

Apparel and fashion (Palesa Prints model): In this sector, selling opportunities typically involve fashion markets, pop-up retail events, social-media-driven direct sales, or small boutique consignment arrangements. The Palesa Prints example illustrates a sector-specific viability insight: a general-apparel concept faces intense competition from established mass-market suppliers, while a fast-turnaround small-batch offering can serve the event, corporate, and customisation segments where established suppliers cannot compete on speed. The shift from general to specialist within this sector is a common and commercially sensible refinement that WE01's concept-evaluation activity is designed to surface.

Service businesses (consulting, tutoring, event management): In service businesses, the product brief structure needs to address the intangible nature of the offering: what exactly is the service, how is it delivered, how is it priced (hourly, per-project, retainer?), and how is quality assured? Selling opportunities in service businesses are typically found through personal referral networks, professional associations, or digital platforms. Viability evaluation must address time as the primary resource constraint: a sole-provider service business is viable only if the provider's available time, multiplied by the rate per hour, exceeds the provider's costs — and that calculation changes as demand grows.

WE01 requires candidates to make several genuine trade-offs, and understanding how to weigh them is part of demonstrating the judgment the element requires.

Trade-off 1: Specificity vs. flexibility in the business overview. A more specific overview is more testable and produces more useful selling-opportunity feedback — but it also commits the concept to a more defined direction earlier, before all market feedback has been gathered. The right balance is to be specific enough to test (so that prospective stockists or buyers can evaluate a real offering, not a vague idea) while remaining genuinely open to refinement based on what the market feedback reveals. The Palesa Prints example illustrates this: an initial description of 'apparel' was specific enough to prompt market feedback, and that feedback led to the more precise 'fast-turnaround small-batch' refinement.

Trade-off 2: Depth vs. breadth in selling-opportunity evaluation. A candidate could invest more time with fewer prospective buyers, exploring their needs in depth, or could make briefer contact with more prospective buyers, getting a broader but shallower picture. The element requires at least two contacts, but the quality of those contacts matters more than the number. A deep conversation with one willing and knowledgeable prospective buyer (like Mrs Dlamini, who gave specific volume, pricing, and timing preferences) is more useful than five brief conversations that produce vague expressions of interest.

Trade-off 3: Optimism vs. caution in viability evaluation. An optimistic viability evaluation might approve a concept that is genuinely viable under the right conditions; a cautious evaluation might reject a concept that would in fact succeed. The right approach is neither to inflate assumptions nor to apply unrealistically conservative conditions — it is to use the actual data from the selling-opportunity evaluation and the actual cost data from the host-employer as inputs. If the data is genuinely uncertain (for example, if costs can only be estimated), the right response is to state the uncertainty explicitly and express the conclusion as conditional: 'viable if costs remain at the estimated level, with sensitivity to X.'

Trade-off 4: Completeness vs. timeliness in documentation. A logbook entry written immediately after an activity captures detail that will be forgotten within days; an entry written with more reflection might be better organised but less accurate. The right balance is to write a substantive entry at or near the time of the activity, even if it is not perfectly polished, rather than waiting until the end of the placement to write a retrospective account that misses important specific detail.

WE01's viability evaluation activity (WA0103) is, at its core, a financial analysis — and understanding its financial implications helps candidates take it seriously rather than treating it as a formulaic exercise.

The margin calculation at real volume. The most important financial question WE01 forces is whether the concept generates a positive margin at the volume that the selling-opportunity evaluation indicates is actually achievable — not at the volume the concept would need to be viable. In the Nkosi's Fresh Kitchen example, the relevant question is not 'is this concept viable if we sell 100 units per week?' but 'is this concept viable at the 8 units per week Mrs Dlamini has agreed to trial?' The answer might be yes, no, or marginally yes — but it is an answer grounded in real numbers rather than aspirational projections.

Fully-loaded cost vs. direct cost. A common financial error in early-stage viability analysis is calculating margin against direct cost only (materials, packaging) and ignoring indirect costs (the founder's time, transport, utilities, equipment depreciation). The curriculum specifically flags 'fully-loaded cost per meal' as the correct denominator in the Nkosi's Fresh Kitchen viability check. Using only direct costs will produce an artificially high margin that may not survive once indirect costs are properly attributed.

Cash flow vs. profitability. A concept can be marginally profitable on paper but cash-flow negative in practice if there is a timing mismatch between when costs are incurred and when revenue is received. A consignment arrangement, for example, typically means the producer bears the cost of the stock until the retailer sells it — which may take two to four weeks. If the producer's costs are due weekly but revenue arrives monthly, the business may be profitable in aggregate but cash-flow-constrained in a way that can cause operational problems. The Radebe AgriTech seasonal model makes this particularly acute: Sipho's costs may be relatively steady throughout the year, but revenue is concentrated in planting and harvest seasons.

The minimum viable scale condition. The conditional viability conclusion — 'marginally viable at current volume, needs a second stockist within two months' — is a specific financial statement: it identifies the minimum scale at which the concept covers its costs and generates the target margin. This minimum viable scale is a critical financial parameter for the product brief and for WE02's goal-setting activity. If the brief does not state this condition explicitly, and if WE02's goals do not address how to reach it, the concept is vulnerable to remaining stuck below its viable scale indefinitely.

Developing or reviewing a business plan, as understood in this workplace activity (WM-01-WE02), is the structured process by which an entrepreneur — supported by a candidate — translates an already-validated product or service concept (established in WE01) into a concrete operational roadmap. This roadmap consists of four interlocking outputs: specific and measurable goals and targets, a documented risk identification or review, a venture-level SWOT analysis with correctly separated internal and external factors, and a set of actionable recommendations that visibly connect back to all three preceding outputs.

The word 'develop' applies when no formal goals, risk records, or SWOT exist yet and the candidate is building these from a blank page alongside the host-employer. The word 'review' applies when earlier, informal, or partly unrealistic material already exists and the candidate's job is to critically evaluate, correct, and improve it — not simply to restate it in a neater format. This distinction is not cosmetic: the curriculum explicitly warns that treating a review activity as a develop-from-scratch activity is a specific error that undermines the evidence.

A business plan in this context is therefore neither a polished investor document nor a theoretical academic exercise. It is a living, evidenced record produced during a real placement, anchored to the specific venture of the host-employer, and demonstrably traceable to the product brief completed in WE01. Every claim in the plan must be supported by placement-gathered evidence; every recommendation must be traceable to a named SWOT entry or risk record.

The core purpose of WE02 is to bridge the gap between having a validated idea (WE01) and knowing what to do next in concrete, measurable terms. Without this step, a promising product brief remains an aspiration. With it, the entrepreneur has specific targets to pursue, known risks to manage, an honest picture of their competitive position, and a short list of prioritised actions.

For the candidate, the purpose is equally clear: to demonstrate that they can apply formal planning disciplines — the goal-and-target framework from PM-05-PS01, the risk categories from KM-04-KT03, and the SWOT methodology from PM-05-PS02 — inside a real business context, not just in a classroom. The workplace activity closes WM-01, which means it is the summative, integrated task that shows whether all the module's learning has been understood well enough to use under real conditions.

For the host-employer — Palesa Dlamini, Thabo Nkosi, or any real placement business — the purpose is genuinely practical: they receive a documented plan they can act on, produced with external support, which they would typically not have generated alone at this stage of their venture. The supervisor's signature on the evidence record is therefore not merely administrative; it signals that the host-employer finds the output credible and useful enough to endorse.

The element also exists to teach the discipline of honest, evidence-based planning. The reflection prompts, the warning against generic risks copied from templates, and the emphasis on showing corrections and refinements rather than first-draft documents all point toward a deeper professional habit: the willingness to test your assumptions against real evidence and change your plan accordingly.

WE02 covers exactly four activities: developing or reviewing goals and targets (WA0201), identifying or reviewing risks (WA0202), identifying and analysing strengths and weaknesses through a SWOT (WA0203), and preparing recommendations (WA0204). It closes WM-01 and does not extend into funding proposals, financial modelling, or market research beyond what is needed to evidence these four outputs — those topics belong to WM-02.

The element explicitly excludes the original idea-generation and viability work completed in WE01. A candidate who re-explains how the business idea was chosen, or who reproduces the viability analysis from WE01 as if it were new WE02 work, is operating outside the scope of this element and wasting evidence space on content that has already been assessed.

Within goals and targets, the scope is limited to goals that are specific, measurable, and consistent with the WE01 product brief. Aspirational statements ('we want to grow') do not meet the standard. Within risks, the scope requires specific, evidenced risks named from the real placement context — not a generic list of risk types that could apply to any business anywhere. Within the SWOT, the scope is venture-level, meaning the analysis addresses the actual venture being placed with, not a sector-wide analysis or a personal skills audit of the candidate.

The boundary around 'review' work is particularly important. Reviewing existing goals means critically evaluating them against real evidence, identifying which are unrealistic and why, and producing a corrected version. It does not mean reading existing goals and confirming they are fine. If the evidence record shows only that the candidate reviewed goals and found nothing to change, that record is likely either incomplete or dishonest — real informal goals set by early-stage entrepreneurs almost always contain assumptions that do not survive contact with evidence.

Before undertaking WE02 productively, a candidate must have internalised several bodies of knowledge from earlier in the qualification.

From PM-05-PS01, the candidate needs the goal-and-target discipline: specifically, the SMART framework (or its local equivalent) and the discipline of distinguishing a goal from a target. A goal states an intended outcome; a target specifies the measurable threshold that will confirm the goal has been reached. Without this distinction, WA0201 evidence tends to produce vague intention statements rather than measurable commitments.

Also from PM-05-PS01, the candidate needs the risk categories used in this qualification — the framework that organises risks by type so that a risk identification exercise does not simply list whatever dangers come to mind first but systematically checks each category. This is what makes WA0202 evidence 'specific and evidenced' rather than generic.

From PM-05-PS02, the candidate needs to understand the SWOT structure in detail: specifically, the critical distinction between internal factors (strengths and weaknesses, which the venture controls or at least influences directly) and external factors (opportunities and threats, which exist in the environment and cannot be changed by the venture's own actions). Conflating these two is the most common structural error in SWOT evidence.

From KM-04-KT03, the candidate needs the risk-category taxonomy that will be applied in WA0202.

From WE01 itself, the candidate must have the completed product brief in hand, because WE02 goals must visibly reference it by name or content. A candidate who cannot produce the WE01 brief cannot meet the standard for WA0201, regardless of how well-written their goals are.

From KM-01, the candidate needs the communication and professional etiquette principles that will govern how they present potentially uncomfortable recommendations to the host-employer — the scenario in the curriculum where a recommendation conflicts with the host-employer's own instinct tests exactly this knowledge.

WE02 is the closing element of WM-01 and functions as that module's integrating capstone. Everything taught in WM-01 — the knowledge content, the practical standards, and now the workplace activities — converges here. WE01 provided the product brief that grounds the planning; WE02 uses that brief as the foundation for goals, risk work, SWOT, and recommendations. Without WE01, WE02 has nothing to build on. Without WE02, WE01 remains an isolated document rather than the starting point of a coherent entrepreneurial planning process.

Within WE02 itself, the four activities (WA0201 through WA0204) are also sequentially dependent. Goals and targets (WA0201) must be set before risks can be meaningfully identified in context (WA0202), because risk significance depends on what you are trying to achieve. The SWOT (WA0203) draws on the same placement evidence as the risk work and adds the external-factor perspective. Recommendations (WA0204) synthesise all three prior activities into actionable next steps. A portfolio that completes each activity in isolation — ticking each box but showing no connections between them — is explicitly described in the curriculum as borderline, not full marks.

Looking forward, WE02 also sets up WM-02. The goals, targets, risk profile, and SWOT produced in WE02 become source material for the funding proposal developed in WM-02. A candidate who treats WE02 as a paperwork exercise rather than a genuine planning output will find that the foundations of their WM-02 work are weak. The two modules are designed to flow into each other, and the quality of WE02 evidence directly affects the quality of WM-02 work.

The following sequence describes how a candidate should approach WE02 in a real placement, working through the four activities in order.

Step 1: Locate and review the WE01 product brief. Before any WE02 work begins, retrieve the completed WE01 product brief and read it carefully. Note the positioning, target customer, and value proposition that were established there. Every goal written in WA0201 must be consistent with this brief. If the brief describes a fast-turnaround printing service for local businesses, goals about expanding into long-lead custom manufacturing would be inconsistent and therefore out of scope.

Step 2: Determine whether this is a 'develop' or 'review' engagement. Ask the host-employer whether they have any existing goals, targets, or risk lists — even informal ones written on paper or stored in a phone note. If informal material exists, this is a review engagement. If nothing exists, this is a develop-from-scratch engagement. The approach differs significantly: review requires critical evaluation of existing material, not just documentation of new material.

Step 3: Conduct WA0201 — goals and targets. Working with the host-employer, draft or review goals using the PM-05-PS01 framework. Each goal should name a specific outcome and a measurable threshold. For a review engagement, compare each existing goal against real placement evidence (sales data, customer feedback, operational observations) and identify which goals are realistic, which are overstated, and which are missing. Produce a documented goals-and-targets record that names the WE01 product brief explicitly. Log a dated entry in the placement logbook before moving on.

Step 4: Conduct WA0202 — risk identification or review. Apply the risk categories from KM-04-KT03 systematically, checking each category against the real placement context. Do not list risks that could apply to any business; name risks that are specific to this venture at this moment. For example, a supplier-negotiation gap at Palesa Prints is a specific, evidenced risk — it can be named, described, and linked to an operational observation made during the placement. Document at least two specific, evidenced risks. For a review engagement, identify which risks in any existing risk list are genuinely specific versus generic, and correct the generic ones. Log a dated entry.

Step 5: Conduct WA0203 — SWOT analysis. Produce a venture-level SWOT. Use a simple four-quadrant layout. Before entering anything, apply the internal/external test: a strength or weakness is something inside the venture (the owner's skill, the equipment, the cash position, the operational process). An opportunity or threat is something in the external environment (a competitor closing, a seasonal demand peak, a change in supplier pricing). Cross-check every entry. Move any internal factor mistakenly placed in opportunities or threats to the correct quadrant, and vice versa. Link each SWOT entry to specific placement evidence — a trial result, an observation, a conversation with the host-employer, a piece of data. Have the host-employer review and initial the completed SWOT. Log a dated entry.

Step 6: Conduct WA0204 — prepare recommendations. Draft three to five specific, actionable recommendations. For each recommendation, note which SWOT entry or risk record it responds to. A recommendation that cannot be traced to a specific finding is not acceptable. Each recommendation should name a concrete action, an approximate timeframe, and where relevant, the resource or person responsible. Review the recommendations against the goals set in WA0201: each recommendation should move the venture toward at least one of those goals. Present the recommendations to the host-employer professionally, explain the reasoning behind each, and be prepared to discuss alternatives. Have the host-employer review and accept (or formally note disagreement with) the recommendations. Log a dated entry.

Step 7: Compile the complete evidence record. Ensure the portfolio contains: a goals-and-targets document referencing WE01; a risk record naming at least two specific, evidenced risks; a correctly structured SWOT with entries linked to evidence; and a recommendations document traceable to SWOT and risk entries. Confirm the WE record is signed by the supervisor. Ensure every activity has at least one dated logbook entry describing completed (not intended) work.

The documentation requirements for WE02 are specific and non-negotiable. Each requirement exists to prevent the most common failure modes in this kind of workplace evidence.

Dated logbook entries for each activity. At minimum, one dated logbook entry per activity (WA0201, WA0202, WA0203, WA0204) is required. The entry must describe completed work, not intended work. 'I plan to conduct a SWOT next week' does not meet the standard. 'I worked through a venture-level SWOT with the host-employer today, producing a one-page analysis with each entry linked to specific placement evidence' does meet the standard. The date matters because it establishes the sequence of work and confirms the evidence was produced during the placement.

Goals-and-targets record referencing WE01. The goals document must visibly connect to the WE01 product brief. This can be achieved by naming the brief explicitly ('Building on the fast-turnaround positioning established in our WE01 product brief of [date]...') or by referencing its specific content in a way that makes the connection unmistakable. A goals document that could have been written by anyone with no knowledge of WE01 does not meet the standard.

Risk record naming specific, evidenced risks. A table listing risk types (financial risk, operational risk, market risk) with generic descriptions does not meet the standard. A record that names a specific risk ('Sole supplier cannot guarantee three-day turnaround during school-holiday periods, based on the stockout observed during week two of the placement') does meet the standard. At least two such risks must be documented.

Venture-level SWOT with correctly separated factors. The SWOT must be structured with four clearly labelled quadrants. Each entry must be linked to specific placement evidence. Internal factors (strengths and weaknesses) must be genuinely internal; external factors (opportunities and threats) must be genuinely external. The host-employer's initials on the document confirm it has been reviewed as accurate.

Recommendations traceable to findings. Each recommendation must be linkable to a named SWOT entry, a named risk, or both. A table with three columns — recommendation, source finding, timeframe — is a clean way to demonstrate this traceability. Recommendations accepted or actioned by the host-employer during the placement provide the strongest possible evidence.

Supervisor-signed WE record and viability assessment report. The WE record carries the supervisor's signature confirming the candidate performed the activities described. The viability assessment report functions as supporting evidence, connecting the WE02 outputs to the broader assessment framework. Both must be present in a complete submission.

The Palesa Prints placement provides the primary worked example in this curriculum, and it is worth unpacking in full operational detail.

Palesa Dlamini runs a small printing business positioned around fast turnaround — the core proposition established in her WE01-equivalent product brief. The candidate arrives for WE02 knowing this positioning and knowing that the WE01 brief is the foundation everything else must build on.

WA0201 — Goals and targets: Working with Palesa, the candidate develops goals for the coming six months that are explicitly consistent with the fast-turnaround positioning. A goal such as 'Maintain a maximum 48-hour turnaround on standard orders for 90% of jobs over the next six months' is specific, measurable, and consistent with the brief. It names the metric (turnaround time), the threshold (48 hours), the coverage (90% of jobs), and the timeframe (six months). The goals document names the WE01 product brief explicitly. This is not a coincidence — it is a deliberate structural requirement.

WA0202 — Risk identification: The candidate identifies a specific, placement-evidenced risk: a supplier-negotiation gap. This means Palesa does not have a formalised agreement with her primary paper and materials supplier covering minimum stock levels, pricing stability, or delivery commitments. The risk is specific (it names the gap), evidenced (it was observed during the placement), and consequential (it directly threatens the fast-turnaround proposition). A second specific risk might be the delivery-vehicle constraint that emerges in WA0204 — a capacity weakness that creates an operational risk to timely delivery. Both risks are named and described with enough specificity that a reader who knows nothing about Palesa Prints can understand exactly what the risk is and why it matters.

WA0203 — SWOT analysis: The SWOT draws on two weeks of trial results logged during WA0102 (from WE01 work). Positive customer uptake during the trial is correctly classified as an external opportunity — it tells us something about the market's willingness to buy, which is an external factor the venture does not control. Palesa's own delivery-capacity constraint is correctly classified as an internal weakness — it is something about how the business operates, which Palesa can potentially address. The SWOT is produced as a one-page document with each entry linked to specific placement evidence, reviewed and initialled by Palesa as accurate.

WA0204 — Recommendations: Three specific recommendations are produced: pursue a second stockist within two months (responding to the supplier-negotiation gap risk and the external-opportunity SWOT finding that demand exists to support growth); formalise the trial agreement with Mrs Dlamini in writing (responding to the legal/contractual gap identified in the risk and SWOT work); and set aside a specific contingency budget for delivery-vehicle maintenance (responding to the internal-weakness SWOT finding about delivery capacity). Each recommendation is traceable to a named finding. The written-agreement recommendation was actioned during the same week — providing concrete, real-world evidence of impact rather than a set of suggestions that disappeared into a folder.

The Thabo Nkosi engagement at Nkosi's Fresh Kitchen presents a genuinely different case that tests the 'review' rather than 'develop' side of this element.

Thabo had informally set goals for his meal-preparation and delivery business before the candidate arrived. These goals were recorded in rough notes — not a formal document, but a real set of intentions he had been working toward. The candidate's job is not to start fresh but to critically evaluate what already exists.

What review actually looks like: The candidate reads Thabo's existing goals and immediately notices problems. One goal reads: 'Double monthly revenue within three months.' Against the revenue data available from Thabo's records during the placement, this goal is not merely ambitious — it is arithmetically impossible given current customer acquisition rates, local market size, and Thabo's production capacity. The candidate does not simply note this as a concern; the review requires documenting why the goal is unrealistic (citing the specific evidence — customer acquisition rate, production capacity limit, market size observation from the placement) and proposing a corrected goal that is still ambitious but achievable. A revised goal might read: 'Increase monthly revenue by 25% within six months by adding two new regular corporate lunch clients, measured against the current monthly revenue baseline of [amount].'

The difference from a develop-from-scratch approach: In the Palesa Prints engagement, the candidate was helping to create goals where none existed. In the Thabo Nkosi engagement, the candidate is challenging and correcting goals that someone has already committed to emotionally. This requires a different skill set: the ability to present honest, evidence-based critique without undermining the host-employer's confidence or motivation. The curriculum's reference to KM-01 etiquette principles is particularly relevant here — the candidate must present the corrected goals as improvements supported by evidence, not as a verdict that Thabo was wrong.

Risk review, not risk identification: Similarly, Thabo had an informal sense of his risks but had not documented them formally. The candidate reviews what Thabo already thinks his risks are, then applies the risk-category framework from KM-04-KT03 to check for gaps. Thabo had identified cash-flow risk (correct and specific) but had not considered the seasonal purchasing pattern of his primary customer base — farm-supply businesses whose procurement slows significantly outside planting season. This seasonal timing risk, observed during the placement through actual purchasing data, becomes the second specific, evidenced risk in the record. The review adds what the informal thinking missed.

The Sipho Radebe extension: A third scenario involves Sipho Radebe, who experiences a real, unexpected seasonal delay affecting farmer purchasing timing during the placement itself. This is the most demanding version of the 'review' task: not reviewing historical material but revising a risk analysis in real time as new evidence emerges. The candidate updates the risk record to reflect the newly observed risk, documents the observation with a date, and connects it to a revised recommendation. This directly evidences the review half of the element's scope in the most authentic way possible — the plan was changed because reality demanded it.

The curriculum documents the failure-mode portfolio of Blessing Mthembu explicitly, which makes the common mistakes unusually well-defined for this element.

Mistake 1: Goals disconnected from the WE01 product brief. Blessing's hypothetical evidence shows goals that bear no traceable relationship to any prior brief. This happens because candidates treat WE02 as a standalone exercise rather than the second half of a two-part sequence. The mental model that leads to this error is: 'I need to write some goals for this business.' The correct mental model is: 'I need to write goals that follow logically from what was established in WE01.' The fix is simple but requires discipline: read the WE01 brief before writing a single WE02 goal, and name the brief explicitly in the goals document.

Mistake 2: Generic risks copied from a template. A risk list that reads 'Financial risk — the business may experience cash-flow problems; Operational risk — the business may face supply-chain disruption; Market risk — customer demand may decrease' is useless as evidence. These statements are true of every business that has ever existed. They tell the assessor nothing about the specific placement, the specific host-employer, or the specific risks identified through real observation. This mistake happens because identifying specific, evidenced risks requires actual observation and thought, whereas copying a generic list requires neither. The standard requires naming a risk so specifically that a reader can tell it came from this placement — the supplier-negotiation gap at Palesa Prints, the seasonal timing risk at Sipho Radebe's operation.

Mistake 3: Conflating internal and external factors in the SWOT. The most technically common SWOT error is placing internal factors in the external quadrants, or vice versa. 'Opportunity: The owner has strong customer relationships' is wrong — customer relationships built by the owner are an internal strength (the venture controls them, or at least influences them directly). 'Strength: The local market is growing' is wrong — market growth is an external opportunity (the venture does not control it). This error happens because the concepts of 'strength' and 'opportunity' both feel positive, so candidates place positive things in whichever quadrant feels natural. The fix is to apply the internal/external test explicitly to every entry before it is finalised.

Mistake 4: Recommendations not connected to findings. Producing a list of business advice that could apply to any venture, without tracing each recommendation to a specific SWOT entry or risk finding, fails the standard. This mistake happens when recommendations are written after the SWOT and risk work but independently of it — the candidate thinks 'what would be good advice for this business?' rather than 'what does the evidence from my SWOT and risk work specifically indicate this business should do?' The fix is to write each recommendation with an explicit 'This responds to [specific finding]' reference.

Mistake 5: Treating review as restatement. When a host-employer has existing goals or a risk list, a candidate who documents those goals neatly without critically evaluating them has not performed a review. The curriculum is explicit: a strong portfolio shows visible evidence of something being corrected or refined. If the existing goals are found to be entirely realistic and well-formed (which is rare for early-stage entrepreneurs), the evidence record must show the analysis that led to that conclusion, not just a clean copy of the goals. If corrections were made, the record must show what changed and why.

Mistake 6: Logbook entries describing intended rather than completed work. Writing 'I will conduct the SWOT tomorrow' as a logbook entry does not meet the minimum bar. The logbook records what was done, not what is planned. This mistake happens most often when candidates are behind on their logbook and write entries prospectively rather than retrospectively. The result is that evidence appears to exist for activities not yet performed — a form of misrepresentation that assessors are trained to detect.

Several persistent misconceptions surround business planning at this level, and they are particularly relevant to WE02's specific requirements.

Misconception 1: A business plan is a document you produce once and then follow. Many candidates approach business planning as a one-time exercise — you write the plan, and then you execute it. WE02's explicit inclusion of both 'develop' and 'review' in its title, and the Sipho Radebe example of revising a risk analysis mid-placement, corrects this. Business planning at the small-business level is a continuous process of checking your assumptions against real evidence and updating the plan when evidence contradicts assumptions. The plan is a working tool, not a finished document.

Misconception 2: The SWOT is a brainstorming exercise. Some candidates treat the SWOT as an opportunity to list whatever positive and negative things come to mind about the business. In WE02, every SWOT entry must be linked to specific placement evidence. The SWOT is an analytical tool that organises observed facts into a structured picture — it is not an opinion exercise.

Misconception 3: More risks identified equals better evidence. A risk record with twenty generic risks is weaker evidence than a record with two specific, evidenced risks. Quality of specificity outweighs quantity. The standard requires at least two specific, evidenced risks — the word 'specific' is doing more work in that requirement than the number two.

Misconception 4: Recommendations should be conservative and safe. The Palesa Prints example shows that a strong recommendation (pursue a second stockist within two months) is concrete and time-bound, which means it is also specific enough to be wrong. A recommendation that could never fail — 'the business should continue to focus on customer service' — is not actionable. WE02 recommendations should be specific enough that in six months you could check whether they were followed and what happened.

Misconception 5: The supervisor's signature is a formality. The WE record signature is evidence that a real host-employer found the work credible and useful enough to endorse. The Palesa Prints example notes that the host-employer initialled the SWOT as accurate and accepted all three recommendations, with one actioned in the same week. These are not formalities — they are evidence of real-world impact, which is the strongest possible confirmation that the planning work was genuinely useful.

During the placement itself, several warning signs indicate that WE02 evidence is likely to fall below standard.

Warning sign 1: The candidate cannot name the WE01 product brief's core positioning when asked. If a candidate cannot immediately describe the positioning, target customer, and value proposition from WE01, their WE02 goals will not be consistent with it. The brief must be actively present in the candidate's thinking, not filed away and forgotten.

Warning sign 2: The host-employer is not engaged in the process. WE02 is a collaborative activity between the candidate and the host-employer. If the candidate is completing all four activities alone while the host-employer passively observes, the evidence will lack the real-world grounding that makes it valid. The SWOT, in particular, depends on the host-employer's knowledge of their own business — the candidate cannot conduct a venture-level SWOT from the outside without the host-employer's active input.

Warning sign 3: All four activities are completed in a single session. Each activity has its own dated logbook entry requirement, which implies they should be spread across the placement in a way that reflects genuine engagement. A candidate who produces all four outputs in a single afternoon is likely not gathering real placement evidence for each step — they are filling in a template. The Palesa Prints example shows work logged across 22 August (SWOT) and 29 August (recommendations), at minimum a week apart, suggesting real engagement over time.

Warning sign 4: The recommendations could have been written before the placement began. If the recommendations read like generic business advice that anyone could have suggested without visiting the business, they are not sufficiently specific. Strong recommendations are possible only after specific SWOT and risk findings have been documented — they should feel like they could only have come from this specific placement.

Warning sign 5: The candidate is defensive when asked to justify a SWOT entry. If a candidate cannot immediately explain which piece of placement evidence supports a given SWOT entry, that entry is not evidenced. Every SWOT entry should have an immediate, specific answer to the question 'how do you know this?'

The business planning process in WE02, done well, delivers genuine benefits to both the host-employer and the candidate.

For the host-employer, the primary benefit is clarity. Early-stage entrepreneurs often operate with a strong sense of what they are trying to do but without a structured record of their goals, risks, and competitive position. The WE02 process forces this clarity into documented form. Palesa Dlamini, after the placement, has a written record of her six-month goals, a named risk about her supplier relationship that she might otherwise have left to chance, and a concrete recommendation she has already begun to action. These outputs have real operational value.

The SWOT in particular often surfaces strengths that the host-employer had not previously recognised in themselves — the curriculum's scenario prompt directly raises this possibility. An entrepreneur who is close to their own business often takes their strengths for granted while focusing on their problems. An external candidate who systematically documents strengths against evidence can help the host-employer see competitive advantages they are currently undervaluing.

For the candidate, the benefit of WE02 is the experience of applying formal planning tools in a real context where the outputs matter to someone. This is qualitatively different from applying the same tools in a classroom exercise. When a host-employer challenges a recommendation, or when a risk materialises during the placement (as in the Sipho Radebe scenario), the candidate experiences the feedback loop of real-world planning — the sense that their analysis was tested against reality and that they need to update their thinking accordingly. This is the kind of learning that persists.

The integration requirement — connecting goals, risks, SWOT, and recommendations into a coherent whole — trains a habit of systemic thinking that is directly applicable to any future planning task the candidate undertakes, whether as an entrepreneur or as a planning professional in another context.

The financial impact of well-executed business planning at the WE02 level is real, though it operates through improved decision-making rather than through direct financial outputs.

Specific, measurable goals replace vague aspirations with commitments that can be tracked. An entrepreneur who has committed to a specific revenue target for the next six months — with a baseline figure, a percentage increase, and a named mechanism (two new corporate lunch clients, for example) — is in a fundamentally stronger position than one who simply wants to 'grow the business.' The target creates a feedback mechanism: at the end of each month, the entrepreneur can check progress and adjust tactics accordingly. Without the target, there is no signal that adjustment is needed until the problem becomes severe.

Risk identification has a direct financial protection function. The supplier-negotiation gap at Palesa Prints is not a theoretical risk — if it materialises as a stockout during a high-demand period, Palesa loses orders, potentially permanently, to competitors who could deliver on time. Documenting the risk and developing a recommendation (pursue a second stockist) creates a specific action with a specific financial protection rationale. The cost of qualifying and establishing a relationship with a second stockist is almost certainly less than the cost of losing a major client relationship due to a preventable supply failure.

The contingency budget recommendation for delivery-vehicle maintenance at Palesa Prints is another financially concrete output. The internal-weakness finding about delivery capacity, translated into a budgeted contingency, converts an unmanaged risk into a managed one. This is straightforward financial risk management at the small-business level.

For the host-employer, the financial impact of a well-prepared set of recommendations that are actually actioned can be significant. The written-agreement recommendation at Palesa Prints, actioned within the same week, converts an informal trading relationship into a legally documented one — a financial protection that costs almost nothing to establish but could save significant amounts if the relationship later becomes disputed.

Use this checklist to evaluate WE02 evidence before submission. Each item corresponds to a specific standard from the curriculum.

Goals and Targets (WA0201) ☐ Each goal is specific — it names an outcome, not just a direction. ☐ Each goal is measurable — it names a threshold that confirms the goal has been reached. ☐ At least one goal names a timeframe. ☐ The goals document references the WE01 product brief by name or by specific content. ☐ No goal contradicts the positioning or scope established in WE01. ☐ A dated logbook entry describes the goals-and-targets work as completed.

Risk Identification or Review (WA0202) ☐ At least two risks are documented. ☐ Each risk is specific — it names a particular gap, constraint, or exposure, not a generic risk type. ☐ Each risk is evidenced — the record indicates how the risk was identified during the placement. ☐ The risk categories from KM-04-KT03 were applied systematically, not selectively. ☐ For a review engagement: the existing risk list was critically evaluated and corrected where needed. ☐ A dated logbook entry describes the risk work as completed.

SWOT Analysis (WA0203) ☐ The SWOT is venture-level — it analyses this specific business, not the sector generally. ☐ All strengths and weaknesses are genuinely internal factors. ☐ All opportunities and threats are genuinely external factors. ☐ Every SWOT entry is linked to specific placement evidence. ☐ The host-employer has reviewed and initialled the SWOT as accurate. ☐ A dated logbook entry describes the SWOT work as completed.

Recommendations (WA0204) ☐ At least three recommendations are documented. ☐ Each recommendation is specific — it names a concrete action, not a general direction. ☐ Each recommendation is traceable to a named SWOT entry, a named risk, or both. ☐ Each recommendation is consistent with at least one of the goals set in WA0201. ☐ At least one recommendation names a timeframe. ☐ The host-employer has reviewed and responded to the recommendations. ☐ A dated logbook entry describes the recommendations work as completed.

Overall Portfolio ☐ The WE record is signed by the supervisor. ☐ A viability assessment report is included as supporting evidence. ☐ All four activities show visible connections to each other and to the WE01 brief. ☐ No logbook entry describes only intended rather than completed work.

Before beginning any WE02 activity with the host-employer, a candidate should work through the following questions. Each one prevents a foreseeable problem.

Before WA0201 — Goals and targets: 'Do I have the WE01 product brief in front of me, and do I understand its core positioning, target customer, and value proposition?' If not, retrieve and read it before writing anything. 'Does the host-employer have any existing goals, even informal ones?' If yes, this is a review engagement. If no, this is a develop-from-scratch engagement. Decide which before beginning. 'Can I articulate the difference between a goal and a target, and can I give the host-employer an example?' If not, revisit PM-05-PS01 before the session.

Before WA0202 — Risk identification: 'Do I have the risk-category framework from KM-04-KT03 in front of me, so I can check each category systematically rather than listing risks that happen to come to mind first?' 'Have I observed anything during this placement that feels uncertain or fragile — a supplier relationship, a cash-flow pattern, a single-customer dependency — that might correspond to a specific risk?' 'Am I able to describe at least two risks in terms specific enough that a reader could tell they came from this placement rather than from a textbook?'

Before WA0203 — SWOT: 'Do I understand the distinction between internal and external factors well enough to classify every entry correctly without looking it up?' 'Can I link each entry I am about to add to a specific piece of placement evidence — a data point, an observation, a trial result?' 'Is the host-employer available to participate in this exercise, and do they understand their role is not just to confirm what I suggest but to actively contribute their own knowledge of the business?'

Before WA0204 — Recommendations: 'Can I trace each recommendation I am about to propose to a named finding in my SWOT or risk record?' 'Are my recommendations specific enough that in six months someone could check whether they were followed and assess what happened?' 'Am I prepared to present a recommendation that the host-employer may initially resist, and do I know how to do this professionally using the etiquette principles from KM-01?'

Success in WE02 can be evaluated at two levels: the quality of the evidence portfolio (which determines the assessment outcome) and the real-world impact of the planning work on the host-employer's business (which determines whether the work had genuine value).

Portfolio-level success metrics: All four activities have at least one dated logbook entry describing completed work. No entry describes only intended work. The goals document references the WE01 product brief explicitly. At least two specific, evidenced risks are documented. The SWOT correctly separates internal from external factors throughout. Every recommendation is traceable to a named finding. The WE record carries the supervisor's signature. All four activities show visible connections to each other.

Business-impact success metrics: At least one recommendation was actioned by the host-employer during or immediately after the placement — this is the strongest possible evidence of real-world utility. The host-employer can articulate their top two risks by name after the placement, having not been able to name them before. The goals set in WA0201 are being tracked by the host-employer at the three-month point after the placement. The SWOT is being used as a reference document in the host-employer's planning conversations, not filed and forgotten.

Review-engagement-specific success metrics: For review engagements, at least one existing goal was identified as unrealistic and corrected with supporting evidence. At least one risk from an existing list was identified as too generic and replaced with a specific, evidenced version. The host-employer acknowledges the value of the critical review process — ideally in writing as part of the supervisor sign-off.

Assessment of WE02 involves specific checks that catch candidates who have produced technically compliant evidence that is nevertheless weak at the integration and specificity levels.

Trap 1: The 'complete in isolation' borderline. A candidate who produces a well-structured goals document, a clean risk record, a correctly formatted SWOT, and a list of recommendations — but with no visible connections between them — sits at the borderline between pass and full marks. The assessor is specifically looking for goals, risks, SWOT, and recommendations that build on each other. If the risk record could have been written without ever reading the goals document, and the recommendations could have been written without ever reading the SWOT, the integration criterion has not been met.

Trap 2: The 'review as restatement' error. For any activity described as a review, the assessor is checking whether something was corrected or refined, not just documented. A candidate who documents an existing set of goals neatly but cannot show what changed (and why) has not met the review standard.

Trap 3: The 'no WE01 reference' in goals. A goals document that does not reference the WE01 product brief fails the most basic coherence test for WA0201. The reference must be explicit enough that the assessor can see it — not inferred from the fact that the goals are in the same sector as the WE01 brief.

Trap 4: Generic risks masquerading as specific ones. A risk that names a risk type ('supply-chain risk') followed by a generic consequence ('may delay production') is not specific. A risk that names the specific gap, the specific context, and the specific consequence is specific. Assessors are trained to distinguish these.

Trap 5: SWOT entries without evidence links. A SWOT entry that states a strength or opportunity without indicating how that entry was established during the placement is unverified. The assessor cannot confirm it is venture-level rather than generic. Every entry must be linkable to a specific placement observation.

Trap 6: Recommendations that read as general business advice. If a recommendation could have been made by someone who had never visited the business — 'focus on customer service,' 'manage cash flow carefully' — it is not acceptable WE02 evidence. Recommendations must be specific enough to trace back to named findings.

Self-check question: A candidate has completed their WE02 placement and produces the following evidence. Evaluate each item against the standards set out in this curriculum, and identify which items meet the standard and which do not.

Item A: A goals document for Thabo Nkosi's Fresh Kitchen that lists the following goals: (1) 'Increase monthly revenue by 25% within six months by adding two new regular corporate lunch clients, measured against the current baseline of R18,400 per month.' (2) 'Maintain a maximum next-day delivery standard for 95% of orders over the same period.' The document's opening paragraph states: 'These goals build directly on the positioning established in the WE01 product brief of 14 July, which identified same-day and next-day delivery as the primary differentiator.'

Item B: A risk record listing: (1) 'Financial risk — the business may experience cash-flow difficulties.' (2) 'Market risk — demand may fluctuate.' (3) 'Operational risk — the delivery vehicle may experience mechanical problems.'

Item C: A SWOT with the following entries — Strengths: 'Thabo's personal relationships with his five regular corporate clients (established through 18 months of consistent service, observed in client feedback during the placement).' Weaknesses: 'Single vehicle used for all deliveries, creating a single point of failure for the fast-delivery proposition (observed: vehicle was out of service for two days during placement, causing three late deliveries).' Opportunities: 'Growing interest in healthy workplace catering in the local business district, evidenced by two unsolicited enquiries during the placement period.' Threats: 'New meal-prep competitor recently opened 2km away, observed during placement week three.'

Item D: A logbook entry dated 3 September that reads: 'I plan to present my recommendations to Thabo tomorrow and will ask him to review them.'

Answer:

Item A meets the standard. Both goals are specific (each names a concrete outcome), measurable (each names a threshold — 25% increase, 95% delivery standard — and the first names a baseline figure), time-bound (six months), and the document explicitly references the WE01 product brief by date and by content (the delivery differentiator).

Item B does not meet the standard. All three risks are generic. Risk 1 names a risk type (financial) and a generic consequence (cash-flow difficulties) that applies to every business. Risk 2 is similarly generic. Risk 3 is slightly more specific (it names the delivery vehicle) but still lacks the evidence link that makes it a placement-specific risk. A compliant version of Risk 3 would read: 'Single-vehicle operational risk: the Fresh Kitchen's sole delivery vehicle was out of service for two days during placement week two, causing three late deliveries and one near-cancellation — evidencing a direct threat to the fast-delivery proposition and creating a specific risk of client loss if the vehicle fails during a high-volume period.'

Item C meets the standard. Every entry is linked to specific placement evidence. Internal factors (strengths and weaknesses) are correctly placed in the internal quadrants — Thabo's client relationships and the single-vehicle constraint are both things within the business's direct sphere. External factors (opportunities and threats) are correctly placed in the external quadrants — the market interest in healthy catering and the new competitor are both things in the environment that the business does not control. The SWOT is venture-level throughout.

Item D does not meet the standard. The logbook entry describes intended rather than completed work. 'I plan to present my recommendations tomorrow' records a future intention. The minimum bar requires an entry that describes what was actually done: 'I presented three specific recommendations to Thabo Nkosi, tracing each to a named SWOT finding or risk entry. Thabo accepted two immediately and requested one week to consider the third. One recommendation — formalising the delivery contract with the corporate client — was agreed and will be drafted this week.'

WE02 sits at the junction of the qualification's practical and workplace strands, which makes understanding these connections essential for both assessment and genuine learning.

The practical standards that WE02 applies are PM-05-PS01 (goal-and-target discipline and risk categories) and PM-05-PS02 (SWOT methodology). These practical standards were taught and assessed in their own right earlier in the qualification. WE02 is the proof that the candidate can apply them in a real placement — not just recall them in a controlled assessment environment. The assessor comparing WE02 evidence against these standards is essentially checking whether the learning transferred.

KM-04-KT03 (risk categories) is a knowledge module that provides the classification framework for WA0202. A candidate who completed KM-04-KT03 successfully should be able to apply those categories systematically in the placement — working through each category in turn rather than listing risks that happen to come to mind. If a risk type that KM-04-KT03 defines is absent from a risk record, the assessor will ask whether the candidate considered that category and found no applicable risk, or simply failed to apply the framework.

KM-01 (professional etiquette) is invoked in the scenario where a recommendation conflicts with the host-employer's instinct. This is not incidental — the qualification is training entrepreneurs and business advisors who will regularly need to deliver uncomfortable truths to people who have emotional investments in their existing views. The skill of presenting evidence-based recommendations respectfully but clearly is a professional competency that connects the workplace activity to the knowledge strand.

Looking forward, WE02 connects directly to WM-02. The goals, risk profile, and SWOT produced in WE02 become the analytical foundation for the funding proposal in WM-02. A candidate who understands this connection will approach WE02 with additional care — they will know that the quality of their WE02 evidence affects the quality of the work they will be doing in the next module. The qualification is designed as a progression, not a series of independent assessments.

The WE02 framework specifies particular tools — the PM-05-PS01 goal discipline, the KM-04-KT03 risk categories, and the PM-05-PS02 SWOT structure — and candidates are expected to use these tools. However, understanding why these tools were chosen, and what alternatives exist in broader practice, adds the kind of depth that separates a candidate who is following instructions from one who understands the discipline.

Alternative goal frameworks: The SMART framework (Specific, Measurable, Achievable, Relevant, Time-bound) is the most widely used goal-setting framework globally and is likely the foundation of the PM-05-PS01 discipline. Some practitioners use OKRs (Objectives and Key Results), which separate the qualitative objective from the quantitative key results. OKRs are common in technology companies and scale-up businesses but are less intuitive for early-stage small businesses where the language of 'objectives' and 'key results' can feel corporate. The SMART approach is better suited to WE02 placements because it is accessible to host-employers with no formal management training.

Alternative risk frameworks: More complex risk frameworks (PESTLE for external risk scanning, FMEA for operational risk in manufacturing contexts, full ISO 31000 risk management processes) exist in large-business and technical contexts. For an early-stage small business, these are disproportionately complex. The KM-04-KT03 categories provide a simpler, accessible structure that covers the most important risk types without overwhelming a host-employer who is running a business alone. The principle — systematically check each category rather than listing risks ad hoc — is the same regardless of which framework is used.

Alternative to SWOT: Porter's Five Forces is a more rigorous tool for competitive analysis, but it focuses entirely on external factors and does not address internal capabilities. The Business Model Canvas addresses both internal and external factors but in a different structure oriented toward value creation rather than planning-period analysis. SWOT is chosen here because it is widely understood, accessible, and directly separable into internal and external factors — which is the critical skill being taught in WA0203. A candidate who understands this trade-off (SWOT is simpler and more accessible; other tools are more rigorous but require more expertise to apply correctly) demonstrates analytical maturity that a full-marks portfolio should reflect.

Business planning in the South African small-business context has specific characteristics that candidates must understand to conduct WE02 work effectively in real placements.

Informal and semi-formal business context: Many small businesses in South Africa operate in a semi-formal context — they may have a business registration but operate largely on trust-based supplier relationships, informal customer agreements, and unwritten processes. The Palesa Prints example reflects this reality: the recommendation to formalise the trial agreement with Mrs Dlamini in writing responds directly to a gap between how the business is actually operating (informally) and how it needs to operate to manage risk properly. Candidates must understand that 'formalise this relationship in writing' is not a generic best-practice recommendation in this context — it is a specific, culturally resonant intervention that recognises the gap between informal operating norms and formal risk management.

Language and communication in planning sessions: Many host-employer placements will involve business owners whose primary planning conversations happen in a language other than English. The SWOT framework and goal-setting discipline may need to be explained and discussed in the host-employer's preferred language, with documentation then prepared in English for the portfolio. Candidates should be comfortable bridging this — the substance of the planning must be conducted in the language that allows genuine engagement, even if the documentation language is different.

Seasonal patterns specific to the South African context: The Sipho Radebe example of farmer purchasing timing disruption is specifically South African in character — planting seasons, school calendars, local public holidays, and load-shedding cycles all create seasonal patterns that affect small-business planning in ways that generic business planning frameworks do not anticipate. A candidate who identifies a risk that reflects genuine knowledge of the South African economic calendar (July school holidays affecting demand, load-shedding affecting production capacity, month-end payment cycles affecting cash flow) is demonstrating the kind of local specificity that makes WE02 evidence genuinely valuable.

Ubuntu and relationship-based business: In many South African small-business contexts, business relationships have a relational dimension that purely transactional frameworks miss. A recommendation that tells a host-employer to formalise a relationship that has been built on mutual trust and personal connection must be framed carefully — the recommendation is not replacing the relationship with a contract, it is protecting the relationship by making its terms explicit. A candidate who understands this distinction will present the recommendation very differently from one who sees formalisation as a purely legal exercise.