For a Secondary 4 student preparing for 2027 SEC G2 Computing (K237), practice must include both understanding computing concepts and using software to create working outputs. The examination is unusual compared with a conventional written subject: Paper 1 is an e-Examination, while Paper 2 is a supervised lab-based examination using a computer. Students need to understand computer systems, networking and the impact of computing, but must also build competence with spreadsheets, media software and Scratch programming. Parents can help by arranging a regular practice routine on suitable software and asking the teenager to explain how a solution works, rather than simply checking whether it looks finished.

The official K237 scheme has Paper 1: 1 hour 30 minutes, 70 marks, 50%, and Paper 2: 2 hours 15 minutes, 80 marks, 50%. Paper 1 covers all six modules through 20 multiple-choice questions and short structured questions. Paper 2 has three practical tasks—media software (about 30 marks), spreadsheets (about 25 marks) and programming (about 25 marks)—and candidates submit softcopies of their work for marking. The first SEC examinations begin in 2027; this is a new G2 subject with no earlier reference code. Good preparation means practising on the specified software, debugging patiently, saving files correctly and following the school’s arrangements for the lab examination.

• Confirm the code: K237 is the new 2027 G2 Computing syllabus; it has no earlier reference code.
• Paper 1: e-Examination, 1h 30m, 70 marks, 50%; 20 MCQ (20 marks) plus structured questions (50 marks).
• Paper 2: lab-based, 2h 15m, 80 marks, 50%; three practical tasks.
• Software listed: Microsoft Office (Excel and PowerPoint) and Scratch.
• Practical weighting: media software about 30 marks, spreadsheets about 25, programming about 25.
• Six modules: computer fundamentals, networking, impact of computing, spreadsheets, media software and programming.
• Practice the workflow: create, edit, test, debug, save and submit files in the required format.
• Use school-approved arrangements: the examination centre provides a laptop and approved software for Paper 2.
• Protect wellbeing: short, regular hands-on sessions are more effective than a last-minute marathon.

What K237 G2 Computing is designed to assess

K237 is a new G2 SEC subject designed to develop knowledge of computer systems, networks, application software and programming. It also develops computational thinking skills such as abstraction and decomposition through the creation of computational artefacts. Students learn media software skills and consider cybersecurity, emerging technology and the impact of computing.

Computing is not just learning where buttons are located in a software application. A student needs to understand the purpose of an operation, select a suitable tool, produce a correct result and explain the logic. For example, using a spreadsheet formula requires understanding what values are being calculated and how cell references behave when a formula is copied.

The assessment has three objectives: knowledge and understanding of computing concepts, application of knowledge in context, and practical application of software skills to produce computational solutions. Paper 1 focuses on the first two; Paper 2 focuses on practical application. This explains why a student can know what a spreadsheet function does but still need practice using it accurately under time pressure.

Parents should treat the practical paper as a real examination component, not merely an informal computer lesson. Saving files in the correct place, following task requirements and checking the output are part of reliable performance. At the same time, the theory paper requires more than memorising software menu names.

The wider value of Computing is that students learn to understand technology as systems, tools and human choices. They should be able to use technology creatively while recognising that security, privacy, reliability and responsible use matter.

The exact K237 examination structure

Paper 1 is an e-Examination lasting one hour and thirty minutes, worth 70 marks and contributing 50% of the final result. It assesses all six modules. Section A contains 20 multiple-choice questions worth 20 marks. Section B contains a variable number of short structured questions worth 50 marks. All questions are compulsory.

Paper 2 is a lab-based examination lasting two hours and fifteen minutes, worth 80 marks and contributing the other 50%. Candidates use a computer and submit softcopies of the required work for marking. The allotted time includes saving the required work on the candidate’s computer.

Paper 2 comprises three tasks: media software worth approximately 30 marks, spreadsheets approximately 25 marks, and programming approximately 25 marks. It assesses practical application of skills in Modules 4, 5 and 6. Students should therefore practise all three practical areas, not assume that strength in one can compensate for neglecting another.

The examination centre is required to provide adequate hardware and software. Each candidate should have sole use of a laptop and access to media, spreadsheet and programming software. The approved software must be installed. The school will communicate operational arrangements; students should not assume they can use their own device or install a preferred application on the examination computer.

An approved calculator may be used in both papers. The calculator is not a substitute for understanding spreadsheet formulas, interpreting data or testing program logic. Practice should match the syllabus and the school’s approved software environment.

Module 1: computer fundamentals

Computer fundamentals begins with the function of key computer components: the central processing unit, graphics processing unit, main memory and secondary storage. Students should be able to describe what each component does and compare computer specifications in relation to these components.

The CPU performs instructions and coordinates processing. The GPU handles graphics-related processing and may be integrated or dedicated. Main memory provides working storage for active tasks, while secondary storage retains data for longer-term use. Students should know the differences at the level required by the syllabus rather than memorise marketing descriptions.

The syllabus includes integrated and dedicated graphics in terms of whether memory is shared between the CPU and GPU. It also covers magnetic and solid-state storage in relation to durability, portability, typical capacity, cost and speed. A comparison question should identify the relevant criterion rather than simply state that one type is ‘better’.

Students also need to compare data units: bits, bytes, kilobytes, megabytes, gigabytes, terabytes and petabytes. Be consistent with the unit conventions taught in school. A common error is to confuse a bit with a byte or overlook the unit in a data-size calculation.

Input, processing and output form another foundation. A computer system receives input data, processes it according to instructions and produces output. Meaningful information depends on correct input and suitable processing. Students should be able to identify input and output devices and explain their purpose in a particular application.

Input, output and the quality of information

Common input devices include keyboards, mice, touchpads, scanners, barcode readers, digital cameras or webcams and microphones. Output devices include displays, printers, speakers, headphones and projectors. Students should understand the purpose of each device and select suitable examples for a given situation.

The important idea is the relationship between input, process and output. A barcode scanner supplies data; a system processes the data; a display or printer presents the result. If the input is wrong, the output may be misleading even if the computer performs the programmed steps correctly.

Ask the student to describe a familiar application as an input-process-output system. For example, a school attendance system receives identification information, checks a record and updates an attendance list. The explanation should identify the information and processing, not merely list the hardware.

Practice should include scenarios. A microphone is appropriate for voice input, while a printer produces hard-copy output. A touchscreen can serve as both an input and output interface. Students should explain the function in context rather than learn a rigid list that cannot be applied.

Module 2: networking and connected systems

Networking covers why computers are connected and how networks support communication and sharing of documents, hardware and software. Students should know common network devices, including network interface cards, wireless routers and modems, and understand their purposes.

The syllabus distinguishes wired from wireless communication, and local area networks from wide area networks. A LAN covers a limited geographical area such as a home or school, while a WAN spans a wider area and can connect multiple networks. The internet is an example of a WAN formed through the connection of many networks.

Students should understand the difference between an intranet and the internet. An intranet is a private network used within an organisation, while the internet is a global network of connected networks. The distinction is important when answering questions about access, users and information sharing.

Client-server networks involve clients requesting services or resources from servers. Students should know the roles and how communication takes place. Use an example such as a computer accessing a file stored on a school server, but focus on the underlying relationship between the requesting device and the service-providing system.

Parents can help by asking the learner to sketch a simple home network and explain how a router and modem are used. A labelled diagram is a good revision tool because it makes the connection between hardware and network function visible.

MAC addresses, IP addresses and cloud computing

The syllabus requires students to understand that MAC addresses direct data within the same LAN, while IP addresses direct data across different LANs. They should compare the purpose and permanence of these addresses. Do not teach them as interchangeable labels for a device.

Cloud computing refers to computing resources such as storage and applications accessed over the internet. Cloud storage and local storage differ in where files are held and in their advantages and disadvantages. Students should consider access, connectivity, sharing, control, capacity and dependence on the service.

Cloud-based applications run through online services, while local applications are installed and run on a computer. Each approach has advantages and limitations. For example, cloud access can support collaboration but depends on network availability and account security. Local applications may be usable offline but require suitable device storage and maintenance.

Scenario questions should be answered against the circumstances. A school that needs collaboration between students may value shared cloud documents, while a task requiring offline access may favour locally available files. A generic statement that cloud is always superior is not a sound explanation.

Use safe examples and avoid sharing personal login information in demonstrations. Computing education should reinforce secure account practices, not normalise using another person’s credentials or bypassing access controls.

Module 3: impact of computing and responsible use

Students examine the impact of computing in communication, education, transportation and retail. They should understand how technology changes activities, creates opportunities and introduces limitations. Answers should explain an effect rather than only name an application.

Artificial Intelligence is described in the syllabus as the ability of a computer to perform complex tasks without constant human guidance. Examples include face recognition, voice recognition, image classification, spam filtering, game playing and content generation. Students should recognise that AI systems work within the capabilities and limits of their design and data.

Responsible use includes online risks such as scams and malware. The syllabus names viruses, worms, trojans, spyware and ransomware. Students should understand the nature of these risks and measures that reduce exposure, such as strong passwords, firewalls, updated anti-malware tools and recognising scam attempts.

Data loss prevention includes making backups so information can be recovered if original files are damaged. Students should understand why a backup should be separate from the only copy of a file and why recovery needs to be considered before a problem occurs.

Responsible use also includes copyright and privacy. Students should understand how to use copyrighted materials appropriately and consider a website’s privacy policy and settings before disclosing personal information. A practical computing student should respect intellectual property and the privacy of others.

Module 4: spreadsheets—formatting, charts and formulas

Spreadsheets form part of Paper 1 theory and Paper 2 practical work. Students need to format cells as numbers, currency or percentages with specified decimal places, and apply date formats. Formatting helps the user interpret a value correctly; it should not be confused with changing the underlying number.

Conditional formatting can change a cell’s fill or font colour based on its contents. The syllabus limits this to greater than, less than and equal to. Students should practise setting the condition accurately and checking that the rule applies to the intended cells.

Charts include bar, column, pie and line charts. Students should know the purpose of each type and create charts from contiguous or non-contiguous cell ranges. They should customise titles, data labels, axes, axis titles and legends. A chart should communicate the data rather than simply decorate a worksheet.

Combination charts are included, limited to line and column charts. Students should understand why two forms of information may be displayed together and how a chart’s data table affects the chart when edited. Use a small practice dataset and check that the visual output matches the source values.

Spreadsheet formulas include arithmetic operators, relational operators and text concatenation. Students should understand the difference between a formula and a displayed value, and recognise that cells using formulas recalculate when referenced cells change.

Spreadsheet references, functions and data handling

Absolute and relative cell references are essential. A relative reference changes when a formula is copied to another cell; an absolute reference remains fixed as specified. Students should practise copying formulas across rows and columns and checking that each reference behaves as intended.

Logical functions include OR, AND, NOT and IF, with up to one level of nested IF. Students should understand how a condition controls a result. A function is not a decorative formula: it translates a decision rule into a repeatable calculation.

Mathematical and statistical functions include QUOTIENT, MOD, POWER, ROUND, CEILING.MATH, FLOOR.MATH, SQRT, SUM, SUMIF, AVERAGE, AVERAGEIF, MEDIAN, MODE.SNGL, MIN, MAX, RANK.EQ, LARGE, SMALL, COUNT, COUNTBLANK, COUNTA, COUNTIF, RAND and RANDBETWEEN. Learn what each function is for and practise the ones included in school tasks.

Text functions include LEFT, MID, RIGHT, LEN, CONCAT, FIND and SEARCH. Lookup functions include HLOOKUP, VLOOKUP, INDEX and MATCH, with exact matching for the lookup functions specified. Date functions include TODAY, NOW and DAYS. Students should know the purpose and syntax required by the syllabus.

Sorting and filtering organise records. Data validation sets criteria for cell input and can display a custom error message when invalid data is entered. These features support data quality. Students should be able to explain why validation matters and demonstrate how to set the criteria.

Do not memorise a formula by appearance alone. Ask what range it uses, what condition it tests and what result it returns. Test it on a small dataset where the correct output can be checked manually.

Module 5: media software—vector and raster graphics

Media software includes vector graphics, raster graphics, presentations and videos. Students need to create and manipulate media outputs with the specified tools, and understand the basic properties of each media type.

Vector graphics are created using nodes and paths and can be resized without loss of quality. Students should create drawings using lines, curves, text, ellipses and polygons, then move, resize, rotate, flip, duplicate, copy and delete objects.

Layering and grouping are important. Students should set the front-to-back arrangement of objects, group multiple objects and ungroup them when needed. They should recognise solid, gradient and pattern fills, set colours and styles, adjust transparency and outline thickness, and place text along a curved path.

Complex shapes can be created using operations such as union, intersect, fragment, subtract and combine. Students should also manipulate nodes and node handles directly. These tools help refine a graphic and create a specific form rather than merely move ready-made pictures around.

Vector graphics can be exported as raster graphics. Students should understand why the exported version may be appropriate for a particular use and what information can be lost when moving between formats.

Raster graphics, image editing and presentation design

Raster graphics are composed of individually coloured pixels. The syllabus includes PNG, GIF, TIFF, BMP and JPEG and asks students to know whether transparency is supported for each format. It also addresses the loss of quality that can occur when raster graphics are resized.

Resolution is measured in dots per inch when printed on paper or pixels per inch when displayed on a screen. Students should understand the relationship between resolution and image output. A larger pixel dimension does not automatically make every image appropriate for every use.

Image editing includes adjusting sharpness, brightness, contrast and dimensions through resizing and cropping. Students should practise preserving the main subject and avoiding excessive changes that make the image unclear. The task requirements should determine the edit.

Presentation software includes the slide master feature for consistent style and layout. Students should produce slide presentations based on storyboards. A storyboard plans the sequence and content before slides are built, helping the presentation communicate a clear message.

Video creation uses still images and video clips with text, transitions and sound. Students should understand that frames are individual images in a video and that higher frame rates may take more storage while appearing smoother. Practical work should be organised so that media assets, timing, text and sound support the intended message.

Module 6: programming with Scratch

The programming module uses visual programming languages and Scratch. Students should recognise graphical symbols, interpret flowcharts and understand the purpose of variables. A variable stores a value that a program can use or update while it runs.

Students need to create and name variables, initialise them and update their values. They should understand how the value changes as the program executes. Use small examples such as keeping a score or counting completed actions, while following the syllabus scope.

Conditional instructions include if and if-else, with up to one level of nested ifs. Basic loops include repeat, forever and for; conditional loops include repeat-until and while. Students should know when a loop is appropriate and how a condition affects execution.

Logical operators OR, AND and NOT, and relational operators greater than, less than and equal to, are used in conditions or loops. Students should understand how the combination of conditions changes the program path. Test with true and false examples rather than trying to memorise a block arrangement.

Programming also includes mathematical operators, random numbers, and list or array operations. Students need to create and initialise a list, insert or delete an item at a given index and use the prescribed operations. They must be able to identify and correct errors in programs.

Practise by writing a small program, predicting its output, running it, observing behaviour and debugging. A program that runs once is not necessarily correct. Test normal cases, boundary conditions and situations where the input changes.

Computational thinking: decomposition and abstraction

Computational thinking helps students break a problem into smaller parts and focus on the information that matters. Decomposition divides a large task into manageable components. Abstraction identifies the important features and ignores details that do not affect the solution.

Before programming, describe the problem and identify inputs, processes and outputs. Then decide which variables are required, what conditions must be checked and what repeated actions need loops. This plan helps reduce errors when building the Scratch project.

Flowcharts represent the sequence and decisions in a program. Students should trace the flow and explain what happens when a condition is true or false. This can expose logic mistakes before the program is run.

Debugging is a process, not random clicking. Reproduce the error, identify the stage where the behaviour diverges from the intended result, change one relevant part and test again. Keep track of what changed so that the student can explain the correction.

Parents can ask the student to describe the program in ordinary language before opening Scratch. If they cannot explain the intended sequence, they may not yet have a sufficiently clear design for the code.

Paper 2 practical examination: three tasks under time pressure

Paper 2 lasts two hours and fifteen minutes and contains three practical tasks. Media software is worth approximately 30 marks, spreadsheets approximately 25 and programming approximately 25. Candidates submit softcopies of required work for marking, and the allotted time includes saving the files.

Students should practise switching between tasks without losing track of requirements. Read each task carefully, identify the expected output, note any file or naming requirements and plan the sequence. Avoid spending too long polishing one element while leaving another task incomplete.

Use the exact software environment specified by the school and syllabus. The listed software includes Microsoft Office (Excel and PowerPoint) and Scratch. The examination centre provides a laptop and the approved software. Students should ask their teacher about any updates to the software arrangement or practical familiarisation.

File management is an assessed practical habit. Save work in the correct location, use the required names and formats, and check that the final file opens. Do not assume that an unsaved or incorrectly submitted file will be recovered because the screen previously displayed the correct work.

Time should be monitored throughout the session. A simple checklist for each task can help: requirement understood, output created, output checked, file saved, submission confirmed. Practise this routine at home using school tasks, while following school guidance.

Common Computing mistakes and a correction method

One common mistake is practising only the theory modules and leaving the practical work until near the examination. Paper 2 is half of the total marks. Students need regular hands-on practice with spreadsheets, media software and programming.

Another mistake is learning formulas without testing cell references. A spreadsheet can look correct while formulas point to the wrong range. Check the formula, test with known data and verify copied references.

Media tasks can lose time when students adjust minor visual details before meeting the main requirements. Start with the required structure and objects, then refine appearance. Keep a consistent style and ensure text and graphics remain readable.

Programming mistakes often arise from uninitialised variables, incorrect conditions, loop boundaries or list indexes. Trace the program step by step and test different inputs. Fix the first logical error rather than changing several blocks at once.

Finally, students sometimes finish the visible task but forget to save or submit the file. Build a submission checklist and practise it every time.

• Read and mark every required output before starting.
• Complete the essential structure before polishing.
• Test formulas with known values and verify references.
• Run programs with more than one input and debug logically.
• Save, reopen and confirm required files are ready for submission.

An eight-week K237 preparation programme

Week 1 — Baseline and setup. Confirm K237, check the school’s software environment and identify strengths in theory, spreadsheets, media and programming. Complete a short practical task and one Paper 1 knowledge check.

Week 2 — Computer fundamentals and networks. Review CPU, GPU, memory, storage, input/output, data units, network devices, LAN/WAN, MAC/IP and cloud concepts. Use diagrams and scenario explanations.

Week 3 — Impact and responsible computing. Revise technology impact, AI examples, scams, malware, passwords, firewalls, backups, copyright and privacy. Practise structured explanations.

Week 4 — Spreadsheets. Practise formats, conditional formatting, charts, formulas, references, functions, sorting, filtering and data validation. Test with a small dataset and verify each output.

Week 5 — Media software. Practise vector objects, grouping, node edits, fills, raster editing, file formats, resolution, slide masters, storyboards and simple video creation.

Week 6 — Scratch programming. Practise variables, conditions, loops, logical operators, random values, lists and debugging. Trace flowcharts and explain program behaviour.

Week 7 — Integrated lab practice. Attempt three-task practical sessions using a time plan. Include file saving and submission checks. Separately practise a Paper 1 e-Exam section.

Week 8 — Retest and exam readiness. Revisit weak modules, repeat practical tasks with changed data or requirements, and check the school’s approved software and lab arrangements. This is a suggested home-learning cycle, not an official SEAB timetable.

A weekly practice plan that develops genuine independence

A realistic week may include a short theory session, an Excel practice task, a media task, a Scratch exercise and a later correction session. The student should not attempt to master all six modules in a single evening. Regular, focused practice helps the learner remember where tools are located and understand why each operation is used.

Separate learning from timed simulation. Early practice should allow the student to consult notes and understand an operation. Later practice should use a fresh task under time limits. This distinction prevents the student from mistaking familiarity with a demonstrated solution for independent skill.

Parents can support by providing access to the school-approved software where permitted and a suitable practice time. They should not complete the spreadsheet, edit the video or debug the assessed task for the student. Ask the learner to explain their solution and show how they checked it.

Do not neglect Paper 1 while practising software. All six modules are assessed in Paper 1, including computer concepts and software knowledge. A balanced programme maintains theory retrieval alongside practical application.

• One theory review with short scenario questions.
• One spreadsheet task with formulas and charts.
• One media task using vector or raster tools.
• One Scratch task with a condition, loop and debugging step.
• One timed mini-practical followed by file and output checks.

Exam anxiety and the digital examination environment

Students may feel anxious because the practical paper requires several software tasks within one sitting. Reduce uncertainty by practising the full workflow: read the task, plan the steps, create the required output, check it and save it. The student should understand what the school-provided computer environment will look like.

Do not tell the child that Computing is easy because it uses a computer. Practical tasks require accuracy, logic and time management. A student who is confident with games or social media may still need explicit practice with spreadsheets, graphics tools and programming.

Parents can ask what task feels least predictable. If it is a spreadsheet formula, practise that skill. If it is saving files, use a checklist. If the child freezes when a program behaves unexpectedly, practise a calm debugging process. Identify the actual source of anxiety.

If stress persistently affects sleep, attendance or daily functioning, speak with the form teacher or school counsellor and seek appropriate professional support when needed. More screen time is not necessarily the solution to significant distress.

Should parents arrange Computing tuition or buy software?

Some students can prepare well through school lessons, authorised software access and independent practice. Extra tuition is not automatically required. If the teenager can complete tasks, explain errors and improve through feedback, additional lessons may add unnecessary workload.

External support may help when the student has repeated difficulty with logic, spreadsheet formulas or media workflows. Ask whether the tutor uses the K237 syllabus and the specified software. A generic coding class may teach useful skills but not necessarily match the exact SEC practical requirements.

Do not purchase an expensive computer or commercial software without checking the school’s instructions. The examination centre provides the required hardware and approved software. The student should practise the tools identified by the school, not become dependent on a different interface.

eduKate’s wider digital-learning approach encourages students to understand the structure behind a task, practise it and verify the outcome. Parents can use short projects such as a simple spreadsheet or Scratch game for interest, but should keep school assessment requirements central.

Preliminary tests: turn practical errors into a recovery plan

Read the Paper 1 results by module: computer fundamentals, networking, impact, spreadsheets, media software and programming. A student may know the theory of networks but lose marks on spreadsheet functions. Separate the patterns rather than treating the subject as one general ability.

For Paper 2 practice, inspect each of the three task outputs. Did the spreadsheet use correct references? Did the media output meet the brief? Did the program behave correctly for different inputs? Were the files saved and submitted as required? These questions reveal what needs repair.

Select no more than three repeated problems at a time. Practise the missing skill on fresh data or a new brief, then retest independently. Repeating the same task until it is memorised does not show that the student can adapt.

Ask the Computing teacher for help if the student is unsure about the approved software or task expectations. The school knows the environment and can advise on legitimate familiarisation. Avoid relying on online rumours about the exact lab setup.

The final month and examination-day checklist

During the final month, maintain one weekly theory review and regular practice in all three practical areas. Use at least some timed work so the student can manage the 1h 30m e-Examination and 2h 15m lab-based examination. Review the output quality and file handling after each practice.

In the final week, revise the module checklist, common spreadsheet functions, media editing operations and Scratch logic. Confirm the school’s approved software and examination arrangements. Do not install unfamiliar tools or change the student’s workflow at the last moment.

During the last forty-eight hours, keep practice short and familiar. Review a debugging method and a file-saving checklist, then rest. A tired student is more likely to overlook a requirement or save the wrong version.

On the day, follow the instructions and centre procedures. Read each task before starting, allocate time, check the output and submit the required files. The goal is not to produce the fanciest graphic or longest program; it is to satisfy the task accurately and completely.

Questions parents frequently ask about K237

Is G2 Computing a new SEC subject? Yes. K237 is listed as a new subject for 2027 and has no earlier reference code.

How many papers are there? Two compulsory papers: Paper 1 e-Examination (1h 30m, 70 marks, 50%) and Paper 2 lab-based (2h 15m, 80 marks, 50%).

What software is listed? Microsoft Office (Excel and PowerPoint) and Scratch. Follow the school’s approved software arrangement.

What happens in Paper 2? Three practical tasks: media software, spreadsheets and programming. Candidates submit softcopies of the required work.

Does the exam centre provide a computer? The syllabus requires the centre to provide a laptop for each candidate and install the approved software.

Can a student use their own laptop? Do not assume so. Follow the school’s and SEAB’s examination-centre instructions.

Is coding the whole subject? No. Programming is one module. Computer fundamentals, networking, impact of computing, spreadsheets and media software are also assessed.

Can a child improve without tuition? Yes, with regular school-aligned practice and correction. External support is an option for specific persistent gaps, not a requirement for every student.

The next seven days and official sources

Day one: confirm K237 and the approved software. Day two: review computer components and data units. Day three: draw a simple network and explain MAC/IP roles. Day four: create a spreadsheet with formulas and a chart. Day five: edit a vector or raster graphic. Day six: build and debug a small Scratch program. Day seven: practise saving and checking all outputs, then rest.

The authoritative source is SEAB’s 2027 G2 Computing K237 syllabus, listed on the official G2 SEC syllabus page. The school will provide candidate-specific practical arrangements and information about the approved software and lab environment.

Within eduKate’s learning ecosystem, Computing connects Mathematics through formulas and data, English through clear instructions and explanations, and the wider digital world through responsible use, privacy and cybersecurity. The aim is to help a teenager become a careful, creative and independent problem-solver—not merely a fast user of software.