G2 Computing Paper 2 under the 2027 Singapore-Cambridge Secondary Education Certificate (SEC) is the practical lab-based examination in SEAB syllabus K237. Candidates work on a computer to produce digital outputs using Media Software, Spreadsheets and Programming. Parents should first check that the child is enrolled in the school’s G2 Computing course, identify which of those three practical skills is weakest, and teach the child to create, test, save and reopen their own files without outside assistance.
The K237 Paper 2 lab lasts two hours and fifteen minutes, carries 80 raw marks and contributes 50% of G2 Computing. Its three compulsory tasks are approximately 30 marks in Media Software, 25 in Spreadsheets and 25 in Programming; the allotted time includes saving the required softcopies. Paper 1 is a separate 90-minute, 70-mark e-Exam worth the other 50%. This parent guide turns the official syllabus into a Secondary 1–4 and twelve-week skills timeline without inventing additional SEAB modules or claiming that buying expensive hardware guarantees success.
- Official 2027 G2 Computing is syllabus K237, a new G2 examination subject; do not confuse it with G3 Computing K349.
- Paper 2: lab-based, 2 hours 15 minutes, 80 marks, 50% of the subject grade.
- All three Paper 2 tasks are compulsory: Media Software about 30 marks, Spreadsheets about 25 and Programming about 25.
- Paper 1: 1 hour 30 minutes, 70 marks, 50%, comprising e-Exam MCQs and structured questions across six modules.
- Paper 2 assesses Modules 4–6; its softcopy files must be saved according to official school and examination instructions.
- Prioritise functional output, correct formulas, debugging, file verification, digital responsibility and school-approved software access.
Official starting points: SEAB SEC G2 2027 school-candidate syllabus list and K237 full 2027 official syllabus PDF. Independently written for parents, checked 20 November 2026.
Quick parent route: which part do you need?
- Subject levels and the 2027–2028 SEC timeline
- Exact lab paper format and official requirements
- Spreadsheets, media, programming and saved files
- Original lab tasks, errors and corrections
- Secondary 1–4 milestones and a twelve-week plan
- When school or extra support helps
- Parent FAQs and official source links
Full SBB and the first SEC examination timeline
Full Subject-Based Banding has applied in Singapore mainstream secondary schools since 2024. A Posting Group used at Secondary 1 admission is not the same as the G1, G2 or G3 level in an individual subject. A pupil may have a mixture of subject levels. Parents should check the computing course actually offered by the school and the child’s subject level rather than infer it from the PSLE Posting Group.
The first Full SBB cohort entered Secondary 1 in 2024 and is expected to sit the first SEC examinations in 2027, with results released in January 2028. Written English and local Mother Tongue papers occupy a September window; other written and specialised papers follow official subject timetables, generally through October–November. Computing lab examinations have specific centre arrangements and equipment. The school’s candidate notice, not a generic tuition timetable, determines the day and procedures.
A child entering Secondary 1 in 2027 would normally reach Secondary 4 in 2030. The K237 2027 code is a current official point of reference, not a guarantee that the syllabus or exact software remains identical for later cohorts. The family should use its defined skills to understand the learning destination while following the teacher’s current course sequence and permitted technology.
- Secondary 1: computer literacy, folders, small spreadsheets and safe digital habits.
- Secondary 2: more independent tasks using media, charts, conditions and simple programs.
- Secondary 3: confirm the K237 course allocation and practise the three compulsory lab modules.
- Secondary 4: prepare Paper 1 concepts and Paper 2 practical outputs under school-approved conditions.
- 2028 pathways: use the full SEC subject-level and grade profile when reviewing JC/MI, Polytechnic, PFP and ITE requirements.
See SEAB’s SEC examination information and MOE’s 2028 post-secondary admissions announcement for national rules, which must be read alongside school notices.
The real K237 exam: three compulsory lab tasks
SEAB’s K237 Paper 1 is a 90-minute computer-based examination with 20 multiple-choice questions worth 20 marks and a set of short structured questions worth 50 marks. It covers all six modules: Computer Fundamentals, Networking, Impact of Computing, Spreadsheets, Media Software and Programming. Paper 2 is not a substitute for Paper 1: students need conceptual knowledge as well as practical ability.
Paper 2 is the 2-hour-15-minute lab-based assessment of Module 4 Spreadsheets, Module 5 Media Software and Module 6 Programming. Its three tasks are compulsory. The official blueprint gives approximately 30 marks to media software, 25 to spreadsheets and 25 to programming. These numbers are approximate topic allocations, not promises that every subtask has the same difficulty from year to year.
Paper 2 tests the practical assessment objective AO3: producing computational solutions with appropriate software. A candidate submits softcopies of required files for marking. The published examination duration explicitly includes time for saving work on the examination computer. The child must learn the required naming, output formats and checks from school familiarisation rather than rely on an assumed automatic submission process.
SEAB states the examination centre is to provide an individual laptop per candidate and approved software for the media, spreadsheets and programming work. The centre may conduct at most two shifts on the day of the examination. Families should not assume that the software or screen layouts are identical to whatever happens to be installed on the home device. The school’s official arrangements matter.
An approved calculator is permitted in both K237 papers. This does not make a spreadsheet formula correct, and the examination is not about copying a calculator number into a cell. Practical tasks reward producing working digital artefacts according to the prompt. Students should check the source data and result, not just the appearance of the worksheet or graphics.
The broader K237 content also includes cyber safety, responsible use of copyrighted materials, privacy, cloud storage and awareness of artificial intelligence. These concepts appear in Paper 1 rather than as additional named Paper 2 modules, but they inform good habits during preparation. A child should not expose real classmates’ names or use unlicensed images simply to practise a media task.
Older guides to computing may focus only on text-based programming or another subject level. K237 is a specific G2 subject first offered in the SEC framework from 2027. Follow the correct year and module outcomes; the school will provide appropriate practice, actual software choices, examination access and deadlines.
How to master each practical skill without unnecessary software costs
Begin with a digital output, not a software menu
A useful question is ‘What must the final file communicate or do?’ rather than ‘Which buttons did we click?’ For a spreadsheet, the outcome may be an accurate total and chart; for media, a readable visual sequence; for a program, the required response to a user action. Ask the student to describe the desired result in two sentences before opening the application. Then check whether the completed file meets that description. Learning an interface without understanding the output produces fragile skills.
The three-task work plan
Media, spreadsheets and programming are all compulsory. Students should practise estimating how long each task will take, reading every instruction, noting required file names and reserving time for saved-file checks. There is no SEAB rule that all candidates must divide 135 minutes into exactly three equal blocks, so a student’s timing plan should follow the practice questions, marks and personal strength. An extra minute verifying an output can be valuable when a working file is otherwise ready.
File management: name, save, reopen, verify
A beautiful presentation saved under an incorrect name or left outside the required directory can be difficult to assess. Teach the child to distinguish a working copy from a final export and to follow the precise instructions for location, extension and naming. In ordinary practice, ask them to close a file and reopen the correct one. If the expected content is missing, fix the save process before teaching more advanced animation or formulas. Examination saving instructions always take priority.
Understand the folder structure and avoid duplicate files
A learner may create draft-final, final-new, final2 and actual-final without knowing which is the correct submission. Practise using a small controlled folder with clearly named task files. If a programme generates an export and an editable project, explain what each is used for. Do not delete or overwrite exam files unless the invigilator’s instructions permit it. Good preparation makes file organisation deliberate and reduces confusion at the final checkpoint.
Spreadsheet data types and suitable formatting
An integer, percentage, date and currency amount represent different things even if a spreadsheet initially shows them as plain numbers. When a price is stored as text, a total may fail. When a percentage is entered as 8 rather than 8%, a formula can produce a wildly wrong result. Practise formatting fictional tables and ask the child to predict whether values will be treated as numbers, labels or dates. Correct data representation is part of computing, not decoration.
Cell references: relative versus absolute
A formula copied down a column may change references automatically. That behaviour is useful for each row’s own value but wrong for a fixed rate stored in one cell. For an original practice task, prices in B2:B6 could use a rate stored in F1 with a formula such as =B2*(1+$F$1). Ask why F1 stays fixed and how the reference would behave without the dollar signs. The lesson is understanding cell relationships rather than memorising a screenshot of a formula bar.
Spreadsheet validation and conditional formatting
Good tables reduce mistakes before they spread. A validation rule can restrict acceptable values or display an error message when input fails a condition; conditional formatting can draw attention to a threshold. Ask what the rule is intended to prevent and which legitimate entries it might reject. A brightly coloured cell is not evidence of correct arithmetic. The child should inspect the source data, rule and formula independently and check unexpected cases.
Charts: select the right visual question
A line chart is often useful for change over time; a bar or column chart for comparing categories. Pie charts can communicate a composition but may obscure small differences. The student should identify what a viewer needs to understand, select the appropriate data, add meaningful titles and units, and examine whether axes are misleading. A chart that looks professionally formatted yet uses a wrong data range is still incorrect. Practise rebuilding the chart from changed sample data.
Lookup, text and statistical functions
The syllabus includes spreadsheet operations beyond basic addition. A function should be chosen because it addresses the task: finding a matching code, counting qualifying rows, extracting text or summarising values. Test on a tiny fictional dataset where the answer can be checked manually. If a lookup returns the wrong student’s score because the key is mismatched, the interface may have operated perfectly; the model of the data was wrong. Good practice separates input, formula, expected result and verification.
Vector graphics: nodes and paths
Vector shapes are constructed from points, lines and curves and can usually be resized without the same pixelation problems as raster images. Have the learner create a simple original icon from circles, curves and polygons, then resize and rotate it. The question is whether the shape still communicates the intended idea and meets size or alignment requirements. Copying a finished graphic from the internet does not demonstrate the ability to construct or edit the required vector elements.
Raster images: pixels, dimensions and cropping
Raster images consist of pixels and are appropriate for many photographs, but repeated enlargement can reduce visible quality. A pupil should understand why cropping changes composition, what aspect ratio is and how to retain the required visual content. Give an original or appropriately licensed picture and ask for two variants serving different purposes. Check that text, logos or subject matter are not clipped. Media editing should respect authorship and privacy rather than use classmates’ images without permission.
Presentation layouts and storyboards
Before building a slide sequence, outline what the audience should understand in three or four stages. A storyboard can describe the opening, information, explanation and closing. Teach the student to use consistent alignment, readable text and a logical visual hierarchy. Transitions may support understanding but excessive effects can distract. A presentation is successful when the viewer can follow the message, not when every available animation has been added.
Video timing, sequence and export
Video tasks involve ordering clips or still images, controlling duration, adding text and exporting a usable output. Ask the child to check whether titles are readable for long enough and whether sound, timing and transitions serve the story. Higher frame rate can appear smoother but does not correct confusing content. Verify the exported file by playing it once under the school’s allowed practice conditions; the editable project and exported video may be different required deliverables.
Visual programming events and sequencing
K237 visual programming can be taught through an age-appropriate block-based environment. Begin with a sprite that responds to an input event. Ask which event starts the code, what happens first and what changes when a condition is met. Students should be able to predict the behaviour before pressing the start button. If they copy a game but cannot explain why it moves, they have reproduced an artefact without mastering computational logic.
Variables, conditionals and boundary tests
A variable stores a value that may change during execution. A condition controls which action occurs. Imagine a game that displays ‘Level complete’ when points are at least ten. Test scores of nine, ten and eleven. If the code triggers only when points are greater than ten, the boundary case exposes the mistake. Teach students to compare expected output with observed output, then modify one condition. This is more robust than changing random blocks until something looks correct.
Loops and the cause of repeated actions
A loop repeats an operation according to a condition or count. A novice may accidentally put a score update inside a repeating block that runs many times for one event. Teach the pupil to trace the sequence one step at a time, predict how many repetitions should occur and inspect where the variable changes. Moving one action outside a loop can be the correct fix. The goal is logical tracing rather than memorising a favourite project layout.
Functions and custom blocks reduce repetition
A short program may repeat the same set of instructions in several places. A custom block can name that repeated operation and make the logic easier to understand. Ask which inputs or conditions are needed and whether changing one shared block should affect all occurrences. Students should not create functions merely for sophistication. Use them when they clarify structure, make debugging easier or match the specific school task.
Debugging without rewriting everything
Begin with a clear expected outcome, reproduce the fault, inspect the inputs and relevant blocks, change one element, then retest both normal and edge cases. A game that resets unexpectedly may have a duplicated start event; a chart that changes incorrectly may use a wrong cell reference. The general method is the same: narrow the location of the error and record why the correction works. Ask the child to explain the fix in their own words.
Use AI as a tool to question, not a substitute for original work
A student might ask an AI assistant to explain an error, but they should understand any suggested formula or program, test it on simple cases and follow school rules on permitted assistance. An AI-generated project cannot simply be presented as independent examined work. In a school practice setting, encourage the child to state what they tried and what the machine’s answer failed to explain. Data security and copyright matter whenever external tools receive files or prompts.
Plan practical access without expensive purchases
SEAB requires the examination centre to supply appropriate equipment and approved software. The school should tell families which applications and versions are used during preparation. If a child lacks a computer at home, ask about school laboratory access, loan devices or supervised practice. A powerful gaming laptop is not a guaranteed advantage in the K237 lab. Familiarity with the correct tasks, applications and file procedures is more useful than hardware status.
Do not forget Paper 1 while preparing for the lab
Paper 2 accounts for half the result, not the entire subject. Computer fundamentals, networking and impact of computing remain relevant through Paper 1, alongside the same spreadsheet, media and programming concepts. Make a small weekly slot for structured explanations: what is a network, why is a backup useful, how does data privacy affect a project? This helps students make informed practical choices and prevents their preparation from becoming only menu-clicking.
Six original practice tasks to build reliable digital work
The following are original educational illustrations, not past SEC examination questions. They do not prescribe particular file naming rules or claim that every application has the same interface. Follow the school’s actual software and supervision requirements for formal practice.
A formula copied down five fictional rows
Imagine column B contains item costs and cell F1 contains a tax rate used only for arithmetic practice. The formula =B2*(1+$F$1) uses the current row’s amount while keeping the rate cell fixed. Copy it down and check each row. Then remove the dollar signs and observe how the calculation may point to the wrong cell. This original task is designed to teach reference logic; it is not a published SEC examination item.
A chart from a small transport dataset
A fictional dataset gives journeys of 12, 15, 18, 14 and 20 minutes across five days. A line chart can show variation over time. Give it a title and label the vertical axis ‘Minutes’. Then ask whether a column chart might more clearly compare the five days. The student must justify the choice and verify that all rows were selected; attractive colours cannot fix a missing data point.
A vector icon scaled for two outputs
A student creates an original directional arrow using polygons and a curved path. They place it on a small square sign and a wide slide. If the shape becomes stretched or hard to read, adjust proportions and contrast while preserving the message. Ask whether a raster screenshot of the icon would behave the same way when enlarged. This practises meaningful media decisions without reproducing copyrighted artwork.
A three-scene storyboard
An original presentation encourages pupils to return library books. Frame one introduces the issue, frame two gives practical instructions and frame three explains where and when to return books. The child can create a short slide or video sequence, checking text duration and the exported file. The task is not scored as official K237 practice; it teaches clarity, order, media output and final-file verification.
A block program with a boundary mistake
In a fictional score-tracking game, the character must advance when the score reaches ten. The programmer uses ‘if score > 10’, so the screen fails to advance at exactly ten. Testing scores of nine, ten and eleven reveals the boundary problem. Change the condition to ‘score >= 10’, then test again. Ask why the original program behaved as written; that reasoning is more important than the change of one symbol.
A final file that cannot be opened
A student creates a good graphic and submits only a preview image when the task requires an editable source document. In ordinary practice, ask which files are required, where each was saved, and whether each opens in the relevant application. A final checklist should include file name, correct format, expected content and reopen test. On examination day, obey the actual SEAB and school submission rules, not a homemade assumption.
Common errors that waste marks or time
- Practising only a favourite game or video editor and ignoring the other compulsory modules.
- Assuming a saved preview is always an acceptable editable source-file submission.
- Copying a formula without knowing whether a cell reference should stay fixed.
- Creating a beautiful chart from the wrong data range or with misleading units.
- Using copyrighted or private images without permission in practice media.
- Fixing a program by random block changes instead of identifying the faulty condition.
- Using AI-generated files as though they were independent examination work.
- Leaving all saving, naming and reopen checks to the last second.
- Buying expensive equipment without asking what the school and examination centre provide.
- Neglecting the 50% Paper 1 theoretical and structured portion.
The useful correction process is to reproduce the fault, identify the exact requirement and test a small changed example. For example, when a copied spreadsheet formula breaks, compare the references rather than retyping every output number. When a game triggers twice, trace the event logic. When an image loses quality, examine its source type and scaling. A good explanation can be repeated by the pupil without the adult taking over the keyboard.
An achievable Secondary 1–4 preparation sequence
The following is a family planning guide rather than an official week-by-week MOE subject schedule. Schools choose their own lesson sequence and software arrangements. A younger child may need less time; a Secondary 4 K237 candidate can apply the same principles in longer timed labs.
Secondary 1 — confident digital foundations
Secondary 1: learn folders, file names, basic spreadsheets, responsible online behaviour, presentation clarity and short visual-programming tasks. A student at this stage should not be expected to complete the full national lab under timed conditions. Focus on confidence in creating and checking small outputs.
Secondary 2 — independent software choices
Secondary 2: improve formula references, chart selection, simple media editing and the logic of events and conditions. Ask which computing electives the school offers and what software access it provides. A pupil who enjoys making videos may still need stronger spreadsheet foundations before selecting a subject.
Secondary 3 — integrated task creation
Secondary 3: after K237 course allocation, develop routine across all three practical modules. Practise a media deliverable, spreadsheet task and short visual program each month, with a consistent saving and correction checklist. Keep conceptual Paper 1 topics in the rotation. Learn to debug by explaining the cause rather than replacing entire projects.
Secondary 4 — exam format and saved-file reliability
Secondary 4: practise appropriate 135-minute Paper 2 scenarios with official school software and file handling; check the compulsory three-task format. Review Paper 1 understanding, code comprehension and digital responsibility. Confirm actual national lab time, equipment and assessment arrangements with the school.
A twelve-week repair and mastery plan
Week 1: Check the child’s actual K237 class, software access and one current lab work sample. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 2: Make a small fictional dataset and use accurate number, currency and date formats. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 3: Practise two relative/absolute reference formulas and predict copied behaviour. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 4: Create a chart from changed data and verify all axes, titles and series. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 5: Build an original vector icon from basic shapes, explaining why the medium fits. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 6: Edit a supplied licensed image with appropriate crop and dimensions. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 7: Storyboard and produce a three-slide presentation with consistent hierarchy. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 8: Create a short school-approved media sequence and verify export playback. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 9: Build a visual program using events, conditions and one variable. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 10: Debug a boundary-value error and trace an unintended loop. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 11: Complete a mixed three-task mini-lab including careful saving. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
Week 12: Reopen final files, review Paper 1 concepts and agree on next school priorities. Record which file was created, what the child predicted it would do, and whether it worked after reopening. Aim for independent understanding rather than a screenshot of a completed task.
How much should the child practise?
One short spreadsheet task, one small media task and one ten-minute programming or debugging exercise can form a sensible starting weekly rhythm, if school demands allow. The child also needs time for Paper 1 concepts, sleep, CCA and offline activities. Do not extend screen time merely to satisfy a quota; work toward one identifiable skill and a saved, correct result. Ask teachers what is already being practised during computer-lab lessons.
After every school assessment, distinguish knowledge errors from execution errors. A child may know what a condition means but choose the wrong block; another may make a correct project but save it improperly. One has a logic weakness, the other a file-procedure weakness. Correct each with its own intervention and test it on an unrelated project a fortnight later.
What parents can decide next
Four useful questions for the Computing teacher
Ask which software the school uses for the 2027 syllabus, what kind of access the child has outside class, which of the three Paper 2 modules is weakest, and what submission process the school teaches. Bring one real student-created file and the teacher’s feedback rather than a perfect online tutorial example. If the school suggests extra support, ask how the student can demonstrate progress independently in four weeks.
Outside help is optional and should be specific
A tutor may be helpful when a student cannot understand references, media workflow or program logic and needs careful correction. It should teach a principle and let the learner repeat it on an unfamiliar task. Outside help should never produce the examined file for the child or promise a particular SEC grade. Many pupils will do well with their school facilities, structured independent practice and occasional teacher consultation.
The immutable eduKate Clementi Mathematics tutorial reference illustrates close tutor attention and guided correction. For Computing, the same principle means watching how a pupil reasons and checks a file—not merely showing them the correct sequence of clicks.
Do not infer post-secondary admission from one Computing result
The new 2028 Post-Secondary Admissions Exercise coordinates major post-secondary paths after the first SEC cohort. JC, Millennia Institute, Polytechnic, PFP and ITE course requirements depend on the entire eligible subject combination, relevant grades and current admission criteria. A high G2 Computing result alone does not guarantee an IT diploma, and admission eligibility cannot be inferred from owning advanced hardware. Help the child explore interests with realistic course information and the school’s guidance.
Seven-day parent checklist
- Confirm K237 and the current school computing subject and software.
- Ask the child to create a file and save it under a sensible practice name.
- Open an existing spreadsheet and explain one formula before changing it.
- Create or edit a small original graphic, checking its intended audience.
- Trace a short visual program with one variable and a conditional.
- Ask the child to explain and fix one error without an adult controlling the computer.
- Review the weakest module and arrange suitable school-supported practice if needed.
Parent FAQs, official documents and related learning
Is K237 Computing available at G2 for SEC 2027?
Yes. It is listed as a new G2 SEC subject with its own exam code. Schools decide which subjects they actually offer.
What is the Paper 2 exam time?
Two hours and fifteen minutes, including time to save the required work.
Are there optional lab tasks?
No. The official scheme lists three compulsory tasks: Media Software, Spreadsheets and Programming.
How much is each task worth?
Approximately 30, 25 and 25 raw marks respectively. Paper 2 totals 80 marks and contributes 50% of K237.
Does the school provide laptops and software?
SEAB says the examination centre must provide appropriate individual laptop access and approved software. Confirm the arrangements through your school.
Can a child rely only on Scratch games?
No. Visual programming is part of the subject, but spreadsheets and media are compulsory in Paper 2, and all six modules appear in Paper 1.
Do students need Python for G2 Computing?
Do not confuse K237 with a different subject level. Follow the visual-programming and software requirements in the exact K237 syllabus and school instructions.
Can a student use AI to finish the lab work?
Exam and school integrity rules control permitted assistance. The student must independently understand and create the assessed digital outputs.
What if the child has no suitable computer at home?
Ask the school about laboratory access, loan equipment and approved practice resources before buying costly devices.
Will a good Computing grade guarantee a polytechnic IT course?
No. Eligibility depends on the complete SEC subject-level and grade profile and the course-specific requirements in the application year.
Primary sources
- 2027 SEAB G2 Computing K237 official syllabus PDF
- SEAB 2027 G2 syllabus directory
- SEAB SEC national framework and examinations
- MOE 2026 announcements on 2028 admissions
Source and safety note: task mark allocations are approximate as specified by the 2027 K237 syllabus. This guide is independent educational guidance and does not supersede examination instructions, school software policies, candidate privacy and copyright requirements. Later cohorts must recheck their own applicable syllabus.
