CompetencyLog
Guide

How to write the technical context of an LOR

The technical context is the first tab of a learning outcome review: one box for the tasks you performed, and the technical outcomes that work links to. Your reviewer reads it first, and it has to make every outcome you select look earned.

The box and its limit

There is one box per review, and it takes up to 5 000 characters, spaces included. It accepts pasted text, so draft it somewhere you can count, then paste. If a month will not fit, shorten it; a second box cannot be started.

A shape that works

  1. One paragraph per engagement. Open with the engagement type and your role on it, not the client's name.
  2. Say what you did, in the first person. Name the area, the standard and what you produced: the lead schedule, the working paper, the computation, the memo.
  3. Make each outcome visible. For every technical outcome you will select, there should be a sentence your reviewer can point to. If there is not one, either write it or drop the outcome.
  4. End with what came of it. A finding, an adjustment, a return filed, a point cleared.
One engagement paragraph (an invented example)
External audit, manufacturing client, year-end 28 February; audit trainee on the team. I performed the inventory count attendance at two sites and the subsequent cut-off testing, documenting the results in the inventory lead schedule. I recalculated the standard-cost overhead absorption against IAS 2 and found idle-capacity costs absorbed into stock, which I set out for my manager with the proposed adjustment.

The engagement, the role, the procedures, the standard and the finding, with no client named.

When it runs long

Cut the dates first, not the substance. Short dates (11 Sept) save more than you would think, and if the period is stated once at the top, the dates on each line can go. What should never go is the sentence that earns an outcome.

Choosing the technical outcomes

SAICA does not prescribe which technical competencies you must cover. Your training office is expected to give you enough range and depth, and technical work is tracked for exposure rather than rated. So select outcomes the paragraph genuinely shows, at the level of the lettered outcome (for example B1.2a), and do not stretch one task over many.

Where this comes from

SAICA's CA2025 training programme structure and technical exposure requirements (September 2021), and the assessment tool as trainees use it, last checked 2026-10-05.

Try it on a line of your own work

Type one thing you did this week and see which outcomes it evidences. It answers instantly from the built-in patterns. Log a whole month when you are ready.

CompetencyLog is an independent preparation tool. It is not part of SAICA and is not endorsed by it. Your reviewer, your training office and SAICA make every decision about your progress.