G2 Computing is a new subject for the 2027 Singapore-Cambridge Secondary Education Certificate, with SEAB syllabus code K237 and its first examination in 2027. It is not simply a coding club or a test of whether a student can use a computer confidently. The syllabus covers computer fundamentals, networking, the impact of computing, spreadsheets, media software and programming. Students must understand concepts and apply software skills to produce practical digital work. Both written knowledge and hands-on performance count for half of the overall assessment.

Parents should pay particular attention to the examination format. Paper 1 is an e-Examination that tests all six modules. Paper 2 is a lab-based examination that tests spreadsheets, media software and programming. A learner who enjoys using apps may still need to learn how to solve structured problems, debug code, organise spreadsheet formulas and follow a practical task brief accurately. The best preparation is therefore a balance of conceptual understanding, repeated software practice and careful checking.

• 2027 SEC subject: G2 Computing, syllabus code K237; first year of examination 2027.
• Six modules: Computing Fundamentals, Networking, Impact of Computing, Spreadsheets, Media Software and Programming.
• Paper 1: e-Examination, 1 hour 30 minutes, 70 marks, 50%; 20 MCQs and structured questions; all modules assessed.
• Paper 2: lab-based examination, 2 hours 15 minutes, 80 marks, 50%; three practical tasks in media software, spreadsheets and programming.
• Practical tasks require candidates to submit softcopies of their work; the allotted time includes saving the required files.
• Programming uses Scratch blocks in Papers 1 and 2; MakeCode blocks are assessed in Paper 1 only.
• Paper 2 centres provide the required hardware and software; candidates should have individual laptop use during the examination.
• Students need both computing concepts and practical ability; familiarity with a device alone is not sufficient.

1. What the G2 Computing syllabus aims to teach

The K237 aims include knowledge of computer systems, networks, application software and programming. Students develop computational thinking, including abstraction and decomposition, by creating computational artefacts. They also develop media software skills and an awareness of cybersecurity, emerging technology and the impact of computing. The syllabus values critical, adaptive and inventive thinking, collaboration, communication, perseverance, accuracy and thoroughness.

Computational thinking is a way of approaching a problem so that a solution can be designed and expressed systematically. Abstraction means focusing on the details that matter and setting aside irrelevant information. Decomposition means breaking a larger problem into manageable parts. A student may use these ideas when creating a game, designing a spreadsheet, editing a video or debugging a program.

The subject also considers the consequences of technology. Students should understand that digital systems affect individuals, organisations and society. Questions about security, privacy, online behaviour and the use of emerging technologies require more than memorising a definition. Learners should be able to recognise situations, identify risks and explain sensible responses.

2. Module 1: Computing Fundamentals

Computing Fundamentals introduces the key components of a computer system, including the central processing unit (CPU), graphics processing unit (GPU), main memory and secondary storage. Students need to describe what these parts do and compare systems using their specifications. The syllabus also distinguishes integrated and dedicated graphics in relation to whether memory is shared between the CPU and GPU.

Students compare magnetic and solid-state storage in terms of durability, portability, typical capacities, cost and speed. They also compare data units from bits and bytes through kilobytes, megabytes, gigabytes, terabytes and petabytes. Input and output concepts help learners understand how users and systems interact. The focus is not to memorise a list of hardware names but to explain why one specification matters in a given use case.

A practical example is comparing two computers for school video editing. The learner should identify which specifications relate to processing, graphics, memory and storage, then explain the trade-offs. The more expensive device is not automatically the better choice for every purpose. The task is to match the requirements to the system and justify the decision.

3. Module 2: Networking

Networking introduces how devices communicate and share information. Students should understand the purpose of networks, how data moves between devices and the role of relevant network components and services described in the syllabus. They should be able to distinguish a network arrangement from the devices and software used to access it.

A useful way to learn networking is to trace a simple example: a student opens a website on a laptop connected to a home or school network. What devices and services help connect the user to the resource? What information is exchanged? What could interrupt access? The student should use the syllabus terms accurately and understand the relationship between components rather than learn isolated labels.

4. Module 3: Impact of Computing

The Impact of Computing module develops awareness of how digital technology changes work, communication and everyday life. The syllabus includes cybersecurity and emerging technology as part of the wider understanding of computing. Students should recognise that technology creates opportunities while also introducing risks and responsibilities.

Cybersecurity learning should connect a risk with a sensible protection. A weak password, suspicious message or untrusted download can expose a user or organisation to harm. Students should understand good security practice and why personal information needs protection. They should also consider the effects of digital activity on other people, including respectful communication and the consequences of sharing or using information carelessly.

Parents can support this module by discussing ordinary digital choices. Ask what information an app collects, why a link might be suspicious, what a person should do after receiving an unexpected request and why online content should be checked before it is shared. These conversations build sound judgement without requiring a student to become an expert in every technology trend.

5. Module 4: Spreadsheets

Spreadsheets are a practical way to organise information, perform calculations and present results. Students need to work with spreadsheet features and use formulas to solve defined tasks. They should understand cell references, data layout, calculations and the use of charts or other visual presentations specified by the syllabus. A spreadsheet is not merely a grid for typing numbers; its value comes from structuring data and using formulas accurately.

A simple school budget can illustrate the process. The learner enters item names, quantities and costs, uses formulas to calculate totals and creates a chart to communicate the information. If a value changes, the spreadsheet should update appropriately. Students should learn to check whether formulas refer to the correct cells and whether the result makes sense.

Common problems include typing a formula as plain text, selecting the wrong range, using an incorrect cell reference and creating a chart that does not represent the intended data. Students should practise checking formulas, labels and outputs. A chart can look attractive and still be misleading if its title, axes or selected data are wrong.

6. Module 5: Media Software

Media software develops students’ ability to produce digital content such as computer graphics and videos. The syllabus assesses practical application rather than only recognition of buttons or tool names. Learners should follow a brief, organise assets, use suitable tools and produce an output that meets the task requirements.

A graphics task may require students to combine visual elements, adjust a layout and create a coherent image. A video task may require arranging clips, working with text or audio and exporting an appropriate result. The details of the examination task are determined by the syllabus and the examination brief. Students should practise the software skills used by their school rather than assume that every editing application has identical controls.

Digital production also involves file management. Students should understand naming, saving, organising files and checking the final output. A finished project can lose value if the wrong file is submitted, an asset is missing or the export settings are unsuitable. Build a habit of saving versions and verifying the submitted file before completing the task.

7. Module 6: Programming

Programming develops the ability to describe a solution through instructions that a computer can execute. The K237 syllabus uses Scratch blocks for programming in Papers 1 and 2, and MakeCode blocks for Paper 1 only. Students should understand variables, conditions, loops, logical and relational operators, random numbers, mathematical operators, lists or arrays, and functions or custom blocks within the stated scope.

Students also learn game programming in Scratch. This includes positioning and moving sprites, controlling execution, adding waits, switching backdrops and costumes, showing or hiding sprites, displaying text and playing sounds. They may use variables, text input, messages, keyboard or mouse events and contact between sprites or coloured areas to control program behaviour.

Programming questions reward understanding of sequence and logic. A student should be able to trace a program, explain what a block does, predict an outcome and identify why a program does not behave as intended. Debugging means locating and correcting the error. It is not random clicking until the output seems right. Students should trace values and conditions one step at a time.

The use of lists or arrays requires students to create and initialise them, insert or delete items at an index, read and write items, test whether an item is present and join lists, according to the syllabus. A student who only knows how to move a sprite may need further work on data and logic. Build programming knowledge progressively, beginning with simple sequences before introducing nested decisions or longer programs.

8. Paper 1: the e-Examination

Paper 1 lasts 1 hour 30 minutes and is worth 70 marks or 50% of the subject. Section A consists of 20 multiple-choice questions worth 20 marks. Section B contains a variable number of short structured questions worth 50 marks. All questions are compulsory. The paper assesses knowledge, understanding and application of concepts and skills across all six modules.

Because this paper covers all six modules, students should not revise programming alone. A learner may enjoy coding and still lose marks on networking, computer components or the impact of computing. Use the syllabus module list as a checklist and ensure the student can explain the main concepts and apply them to examples.

9. Paper 2: the lab-based examination

Paper 2 lasts 2 hours 15 minutes and is worth 80 marks or 50%. Candidates use a computer and complete three practical tasks: media software, spreadsheets and programming. The approximate mark allocation is 30 for media software, 25 for spreadsheets and 25 for programming. Students submit softcopies of the required work. The allotted time includes saving the work for submission.

The examination centre is responsible for providing sufficient hardware and software facilities. Each candidate should have sole use of a laptop for the examination and access to the required media, spreadsheet and programming software. Approved software must be installed on the candidates’ laptops. Schools will need to explain the exact tools and procedures used for their cohort.

Practical preparation should reproduce the complete workflow: read the brief, identify required outputs, plan steps, create the work, check it against the instructions, save the correct files and verify submission readiness. Students should not spend all their time exploring optional effects or improving decorative details when the required tasks are incomplete.

10. How parents can identify the real Computing gap

A student may have different strengths across theory and practical work. One learner may understand computer concepts but take too long to create a spreadsheet. Another may build an attractive graphic but struggle to explain the choices or manage file submission. Review the work by module and assessment objective rather than simply asking whether the student is good at computers.

Classify errors: concept misunderstanding, incorrect terminology, poor spreadsheet formula, weak data organisation, media workflow issue, program logic error, debugging difficulty or file-management mistake. Then select a practice task that addresses the cause. If the student does not understand a loop, another graphic editing session will not solve the problem.

Parents should also ask whether the learner has reliable access to the required software outside school. If not, discuss arrangements with the school rather than assuming the family must purchase every application or device. The centre provisions for Paper 2 are specified by SEAB, and schools should clarify how students practise the relevant skills.

11. How to prepare through the school years

In the early stages, develop the habit of explaining how a computer system works, organising files carefully and following instructions in digital applications. Students can learn basic logic through simple sequences and block-based programs. The important skill is to think through what should happen and why, not to collect the largest number of software features.

As students progress, practise more complex spreadsheet tasks, debugging and media production. Ask learners to describe their process and explain how they know the output meets the brief. Students should become comfortable with saving versions, checking errors and adapting a solution when the first attempt does not work.

In the examination year, cover the six modules and practise the two paper formats. Paper 1 requires recall and application under e-examination conditions. Paper 2 requires speed, accuracy and a complete practical workflow. Review the official syllabus and school instructions about software, devices and submission procedures. Do not assume that an old school assignment uses exactly the same format as the SEC examination.

12. What parents should consider before choosing G2 Computing

Consider whether the student is interested in how technology works, enjoys solving problems and is willing to practise carefully. Prior experience in coding is not a guarantee of success, and limited experience does not mean a student cannot learn. The subject combines conceptual knowledge with practical work. A student who is patient, willing to debug and attentive to task requirements can develop these skills through teaching and practice.

Ask the school how Computing is offered, what resources are available and how the practical skills are taught. Availability and class arrangements may differ between schools. Under Full Subject-Based Banding, a student can take different subjects at different levels, so a G2 Computing choice does not automatically determine the student’s level in other subjects.

13. A practical study routine

• Keep a six-module checklist and track the concepts that have been taught.
• Explain one computer or networking concept in plain language, then apply it to a fresh example.
• Practise spreadsheet formulas using a small data set and check the results after changing an input.
• Complete a media task from brief to saved output, checking every requirement.
• Write or trace a short Scratch program and predict its output before running it.
• Debug by tracing variables, conditions and loop steps rather than changing blocks randomly.
• Practise file naming, saving and submitting the correct softcopy.
• Use a timed practice only after the software workflow is familiar and reliable.

14. Questions to ask the Computing teacher or tutor

• Which of the six K237 modules is the student’s strongest and weakest?
• Which software and programming environments are used for practice?
• Can the student explain program logic and trace values accurately?
• Can the student create spreadsheets with correct formulas and charts?
• Can the learner complete a media task from brief to export without constant help?
• How are file management and submission habits taught?
• How will practice prepare the student for both Paper 1 and the lab-based Paper 2?
• Does the student have access to appropriate practice opportunities at school?

15. Frequently asked questions

Is G2 Computing just coding?

No. Programming is one of six modules. Students also study computer fundamentals, networking, the impact of computing, spreadsheets and media software.

Is Paper 2 a written paper?

No. Paper 2 is a lab-based examination using a computer. Candidates complete three practical tasks in media software, spreadsheets and programming and submit softcopies.

Do students use Scratch and MakeCode in both papers?

The syllabus specifies Scratch blocks for Papers 1 and 2, while MakeCode blocks are assessed in Paper 1 only.

Does a student need to own a laptop?

The syllabus states that the examination centre provides the required infrastructure and each candidate should have sole use of a laptop during Paper 2. Ask the school about practice access and its arrangements.

Can tuition guarantee a grade?

No responsible tutor can guarantee a grade. Support should build understanding, practical fluency and independent problem-solving, and progress should be checked on new tasks.

16. The best preparation develops capable problem-solvers

G2 Computing brings together knowledge of systems, digital responsibility and practical creation. Students should learn how to understand a problem, break it into parts, use the right software, test the result and improve it. Parents can support the learner by asking how a solution works rather than only whether it looks finished.

The Clementi small-group teaching reference reflects the site’s information-first approach: give families the essential requirements early, then explain how to act on them. Applied to Computing, that means checking the correct syllabus and paper format, identifying the student’s actual skill gap, providing guided practice and verifying independent performance.

Use the SEAB 2027 G2 syllabus index and the official K237 G2 Computing syllabus PDF as the authority for the examination requirements. As this is a new subject with its first SEC examination in 2027, families should avoid relying on unrelated older course outlines.

17. Computational thinking in everyday learning

Computational thinking can be practised without a computer. A student organising a school event can break the task into smaller jobs, identify the information needed and decide which steps depend on earlier steps. A program uses a similar structure: instructions have an order, conditions determine what happens next and repeated actions can be handled by loops. Once the student understands the logic away from the screen, it becomes easier to represent that logic with blocks and test it.

18. Debugging as a method, not a guess

When a program produces an unexpected result, students should first reproduce the issue and identify the part of the program involved. They can trace the instructions in order, record variable values and check the conditions that control the flow. Change one thing at a time and test again. Randomly moving blocks may sometimes make a program appear to work, but it does not teach the learner how to locate an error or explain why the correction is valid.

19. Spreadsheet accuracy and presentation

A spreadsheet task should be checked at three levels. First, do the formulas calculate the intended quantity? Second, do the selected data and references include the correct cells? Third, does the presentation communicate the result accurately? A chart with a misleading scale or an unclear title can distort the message even when the data is correct. Students should use labels, units and suitable chart types where required by the task, then change an input value to see whether formulas update as expected.

20. Media production: brief, audience and output

Media software tasks are easier when the student reads the brief before touching the tools. Identify the intended audience, message, required assets and output conditions. Plan a simple sequence, place the visual and audio elements with a purpose, then review the final result. The student should check spelling, timing, consistency, visual balance and whether the output answers the task. Extra effects are not automatically improvements; they should support the communication purpose.

21. File handling and examination readiness

File management is part of reliable practical work. Students should know where work is saved, how files are named and which version is the final submission. During practice, simulate the full process: create the required files, save them in the specified location, reopen them and confirm that they are complete. A learner who can produce an excellent project but cannot locate or submit the correct file has not completed the task successfully. The Paper 2 time allocation includes saving the required work, so this should be practised rather than left until the examination.

22. Balancing theory and practical practice

Paper 1 and Paper 2 each make up 50% of the subject. A student should not allow enthusiasm for one component to crowd out the other. A weekly routine can rotate a short theory review across the first three modules and a practical task across spreadsheets, media software or programming. Every few weeks, review all six modules and identify where understanding has weakened. The final examination preparation should mirror the balance of the official assessment, not the student’s preferred activity.

23. How families can discuss digital responsibility

Parents can support the Impact of Computing module by discussing realistic digital situations without creating unnecessary fear. Ask whether a message is trustworthy, what personal information should be shared, how to check the source of an image or claim and what to do if an account seems compromised. Encourage the student to explain the reason for a safety step. A rule remembered without understanding may not transfer to a new situation; a reasoned habit is more likely to be used.

24. Review progress against the official K237 requirements

Because K237 is a new subject with its first SEC examination in 2027, families should pay close attention to the official document and school updates. Avoid assuming that an older elective, a private coding course or an online tutorial has exactly the same scope. The student may learn useful skills beyond the syllabus, but examination revision should prioritise the listed learning outcomes and specified software environments. Ask the teacher when any administrative or software detail is updated.

25. Practical rehearsal should include the complete task

Students should practise the whole workflow under realistic conditions, not only isolated software features. A spreadsheet exercise should include reading the brief, entering data, applying formulas, checking results, creating a suitable presentation and saving the file. A media exercise should move from planning to editing and final output. A programming task should include understanding the intended behaviour, writing or modifying blocks, testing and correcting errors. This reveals where time is lost and helps students establish a repeatable method.

26. The value of reflection after each task

After completing a practical task, ask the learner what worked, what failed and what they would do differently next time. A student may discover that a spreadsheet formula was correct but the data range was incomplete, or that a game program worked until two sprites interacted. The reflection should identify a specific change rather than simply say ‘I need to practise more’. Keep the note short and revisit it in the next practice session.

27. Choosing resources carefully

Use the official K237 syllabus and the software instructions provided by the school as the main references. Online tutorials can help students understand a feature, but they may use different software versions, different controls or material outside the examinable scope. Before spending money on a course or device, ask the school which applications and facilities are used. A good learning resource should support the stated syllabus outcomes and should not replace practical feedback from the teacher.

28. Help the student learn to explain a solution

After a practical activity, ask the student to explain the sequence of steps and the reason for the important choices. Why was a formula used? What condition triggers the loop? Why was a particular visual element placed there? What was changed during debugging? Being able to explain a solution is a strong sign that the learner understands more than a sequence of button presses. It also prepares the student for structured questions in Paper 1.

A computing learner also needs to understand that a digital artefact has a user and a purpose. A program should behave as intended, a spreadsheet should communicate accurate information and a media product should suit its audience. These are not separate from technical skill; they give the technical work direction. Encourage the student to test whether the output fulfils the task, explain the evidence and revise any part that does not meet the requirement.

The same principle applies to practical work: independence means the student can read a new brief, select a suitable approach, carry out the task and check the result. A tutor or parent may guide practice, but should gradually reduce prompts. Keep a record of the parts the learner can now complete alone. This evidence helps the family understand whether additional support is working and which module deserves attention next.