The 2027 Singapore–Cambridge SEC G2 Computing K237 Paper 2 is a 2-hour-15-minute, 80-mark computer-laboratory examination worth 50% of the subject grade. Every candidate completes three compulsory practical tasks: Media Software (about 30 marks), Spreadsheets (about 25 marks), and Programming (about 25 marks). The examination time includes saving the required softcopy files for marking.
This is not a general computer-literacy quiz or an ordinary written test. Students must use approved applications to produce working digital outputs. They can lose marks because a spreadsheet calculates the wrong value, a media file misses a required feature, a Scratch program behaves incorrectly or the right work is never saved in the specified form. The goal is to understand the task, produce the result, test it and submit it correctly.
Essential preparation points: Know the three practical tasks and their approximate marks; understand spreadsheet formulas, references and charts; develop media outputs for their stated purpose; debug Scratch-style programs systematically; reserve time to verify saved files. This guide uses SEAB’s official K237 2027 G2 Computing syllabus and the 2027 G2 syllabus directory. All sample tasks below are original educational examples, not actual SEC specimen questions.
Quick navigation
- Paper 2 official scheme, marks and permitted environment
- Spreadsheets: formulas, functions, references and charts
- Media software: graphics, presentations and video
- Programming: Scratch, variables, loops and debugging
- Saving files, checking deliverables and avoiding loss
- How to organise 135 minutes without rushing
- Common mistakes and targeted repair
- A four-week lab preparation cycle
- Frequently asked questions and official references
K237 Paper 2: official examination structure
| Practical task | Approximate marks | Syllabus module | Required kind of ability |
|---|---|---|---|
| Media Software | About 30 | Module 5 | Create and edit visual, presentation or video outputs for the task |
| Spreadsheets | About 25 | Module 4 | Use data, calculations, functions, formatting and charts correctly |
| Programming | About 25 | Module 6 | Develop, complete, test or debug a visual program |
| Paper 2 overall | 80 | Modules 4–6 | All three compulsory tasks, 2h 15m and 50% of subject grade |
The mark values for the three tasks are approximate; SEAB marks them with a tilde and does not promise that a particular media or spreadsheet operation will always be assigned the same marks. Paper 2 has no optional topic to skip. A candidate cannot replace the programming task with an additional spreadsheet.
Paper 1 is a separate 90-minute electronic written examination worth the other 50%. It covers all six syllabus modules: Computing Fundamentals, Networking, Impact of Computing, Spreadsheets, Media Software and Programming. The practical paper focuses on Modules 4–6. This distinction helps students allocate revision time accurately.
Where is the practical completed?
The examination centre arranges the required hardware and approved applications. SEAB says candidates should have sole use of a laptop for the lab and access to media, spreadsheet and programming software installed by the centre. The centre may administer the examination over up to two shifts on the day.
Students should use their school’s authorised familiarisation and approved applications. Do not assume that personal laptops, online accounts, cloud drives, unapproved applications or internet access will be available in the actual examination. The school and official exam instructions determine the precise environment.
What assessment objective does Paper 2 cover?
Paper 2 assesses AO3 Practical Application of Skills. Students must produce computational solutions rather than merely define a programming term. An approved calculator may be used, but it does not replace the correct spreadsheet functions, digital outputs or program behaviour.
Spreadsheets: get the calculation and the meaning right
A spreadsheet is a computational model, not only a grid
Spreadsheet cells hold values, labels or formulas. A useful spreadsheet can recalculate when inputs change, sort or filter data and present a chart for a reader. The exam may assess formula selection, data validation, chart construction and appropriate formatting. Entering numbers neatly is only a starting skill.
A practical task might ask students to calculate totals for school activities, use a discount rate from a designated cell and display results by group. The program is doing mathematical work: the student must translate the problem into cell relationships before applying a tool.
Relative and absolute cell references
Suppose price is in cell B2 and a common rate is in E2. In an Excel-like spreadsheet, the illustrative formula =B2*(1+$E$2) uses a relative reference B2, which changes as the formula is copied down, and an absolute reference $E$2, which remains fixed on the shared rate.
If the student instead uses E2 without fixing the reference, a copied formula may move to E3, E4 and beyond, producing unexpected results. During practice, change the input in E2 and check whether all result rows update coherently. That tests the model more reliably than looking at one correct first row.
Know what the requested function means
| Function or skill | Example task | What to verify |
|---|---|---|
| SUM / SUMIF | Add amounts, possibly only for a specified category | Range, condition and number format |
| COUNT / COUNTA / COUNTIF | Count numbers, non-empty values or those meeting a condition | That the requested population is counted |
| IF / AND / OR | Choose an outcome based on one or more conditions | The logic handles both true and false cases |
| AVERAGE / AVERAGEIF | Find average overall or for a subgroup | The right values and condition are selected |
| VLOOKUP / HLOOKUP | Retrieve a value from a reference table using exact matching | Correct lookup range, key and result column/row |
| LEFT / MID / RIGHT / LEN | Extract or measure parts of text | Start position and character count |
| Sorting, filtering and validation | Organise records or reject invalid input | Rows stay intact and criteria fit the task |
The 2027 K237 syllabus lists specific functions and limits, including up to one level of nested IF, exact-match HLOOKUP and VLOOKUP, and functions such as SUMIF, COUNTIF, INDEX and MATCH. Students should work within these specified outcomes rather than trying to memorise every function in a professional spreadsheet package.
Original formula example: count qualifying results
Imagine a fictional score table in cells C2 to C11. A task asks how many scores are at least 50. The illustrative spreadsheet formula is =COUNTIF(C2:C11,">=50"). This counts qualifying entries; SUMIF would add values matching a condition instead. Both function names look related, but the question’s output decides which is correct.
For debugging, ask what the output represents. If the student produces 320 when the task asks how many people qualified, the issue may be summing rather than counting. Label the expected unit of the result before choosing the function.
Choose a chart that answers a question
The syllabus includes bar, column, pie and line charts, plus specified combination charts of a line and column. A chart should be chosen to represent the intended comparison. Bar and column charts can compare categories; a line chart can display a sequence or trend; a pie chart can show proportions of a whole when appropriate.
Candidates should be able to set appropriate titles, axes, axis titles, legends and data labels. A chart with the right numbers but the wrong scale or absent units may mislead. Check it against the task: can a reader accurately understand which variable is being compared?
Data validation is different from formatting
Cell formats may show percentages, currency or dates. Data validation restricts what input is accepted and can display an error message when a value fails the rule. Conditional formatting changes appearance based on values. These tools solve different problems even if the same cell is involved.
A student who uses conditional colouring instead of restricting invalid entries has not implemented validation. Under exam conditions, read whether the requirement is to display, highlight or prevent a type of input.
Media Software: produce something that communicates
Vector and raster graphics serve different purposes
Vector graphics use nodes, paths and geometric objects, which can usually be resized without the pixel-based quality loss associated with enlarging raster images. Raster files consist of pixels; editing may involve cropping, adjusting dimensions, brightness, contrast or sharpness. The syllabus includes operations on both types.
In a practical task, a learner might need to construct a symbol from shapes and merge them, adjust the fill and outline and export a graphic. Another might need to crop a photograph to a specified aspect or alter its appearance. The output should meet the requirement, not simply look attractive.
Original vector example: a simple information icon
Imagine creating a clear icon for a fictional reading-club notice. The task requires a single graphic built from a circle, rectangle and text, with specified colours and arrangement. A good process is to create shapes, position them accurately, check front-to-back layering and group or merge only when the instructions call for it.
If the task specifies editing nodes or using a particular fill type, a finished-looking picture alone may not demonstrate the intended operation. During revision, inspect whether each explicit feature has been implemented and whether the exported output can be opened.
Presentation slides: structure before transitions
K237 includes using a slide master for a consistent style and layout and producing presentations from storyboards. A slide should communicate a meaningful idea to its audience. Random animations and unrelated pictures can obscure information even when they show familiarity with the software.
For an invented presentation about managing electronic waste, a storyboard could allocate separate slides to the issue, relevant data and a practical recommendation. Students should use a readable hierarchy, consistent typography and visuals that support the message. The exact content must, of course, follow the assessed task.
Video output: the export is not an afterthought
The syllabus includes creating a video from still images and video clips, with text, transitions and sound. Students should understand frame rate at a simple conceptual level: higher rates can appear smoother and may take more storage. During preparation, practise assembling the sequence and verifying the exported result.
A video-editing project can look complete in the timeline while the final exported file lacks an audio track, contains a missing image or ends before the required final message. Check the actual saved deliverable when permitted, not only the editing application preview.
Copyright, source materials and privacy
The assessment may supply assets for use in a task. Outside school exams, students should respect copyright and privacy when sourcing media and not assume online images can be reused without permission or acknowledgement. For the real practical exam, use only the files and resources allowed by the centre’s instructions.
Programming: a working Scratch project, not pretty blocks
Build a mental model of the program
In visual programming, each block has a function: starting an event, changing a variable, repeating steps, checking a condition or controlling an object. The 2027 K237 syllabus includes Scratch-style variables, conditions, loops, lists, custom blocks, sprites, backdrops, movement, messages and interactions. Students should understand expected behaviour before rearranging blocks.
A program can be visually tidy yet still wrong. For example, a score variable may increase before a player actually catches an object, or a sprite may be hidden when it should be visible. The error is logical, not cosmetic.
Original game example: catch an object to score
Imagine a classroom exercise asking for a character that moves to catch falling objects. The program needs at least an event that starts the game, movement controls, a condition that detects contact, a score variable and a way to update and display the score. Divide the problem into those parts before adding complex visuals.
To test, deliberately miss an object, catch one object and catch several in sequence. Does the score increase only when required? If not, identify the first event or condition at which actual behaviour differs from the expected behaviour. Change one relevant part, then retest.
Variables should be initialised intentionally
If a score begins at an old value from the previous run, the variable may not have been reset when the program starts. Adding or correcting the initialisation block can fix the state. The same principle applies to timer values or other stored game information.
During practice, write the expected starting state on paper: score zero, selected backdrop, sprites visible or hidden as required. When the program runs, compare that expected state with the observed state. This makes debugging systematic.
Use conditions and loops for the correct purpose
A loop repeats a set of instructions. A conditional branch selects a path based on a specified condition. A list stores related items. An event can trigger code when a key is pressed, a message is received or another supported condition occurs. Students should choose the block based on the behaviour required.
A loop that runs forever when the task needs to end may keep the game running after its expected finish. A conditional placed in the wrong event can cause a sprite to respond at the wrong time. Test the timing and state as well as the numerical result.
Scratch and microcontrollers have different paper scopes
The syllabus’s programming-block list distinguishes Scratch blocks examinable in Papers 1 and 2 from MakeCode and microcontroller material assessed in Paper 1 only. Students should not assume the practical Paper 2 requires building or programming a physical microcontroller.
This does not mean microcontrollers are irrelevant to the G2 Computing subject. They remain in the published Paper 1 syllabus content. It means a Paper 2 lab revision session should focus on the modules and tools the practical actually assesses.
File saving and verification: the final operational step
The official clock includes saving
SEAB explicitly states that the 2-hour-15-minute practical includes time to save the required work on the candidates’ computer. A solution that works only inside an unsaved temporary application state may be unmarkable or incomplete. File-management discipline should therefore be practised alongside formulas and programs.
Understand project files and output files
A video editor may store a project that points to external media; its exported video is a different output. A graphics package may have an editable project format and a separately exported image. A programming task may depend on a saved project with its assets. The actual exam question determines which file or files are required.
Do not assume that a screenshot is an acceptable replacement for the required editable project, or that saving only the editable project satisfies a request for exported media. Use the exact file naming, format, destination and submission process specified in the examination.
A pre-submission check that is realistic
- Identify every required deliverable from the practical task.
- Save to the location specified by the examination centre, not an invented personal folder.
- Use the required filename and file type.
- Where permitted, inspect or reopen the saved file and verify it contains the latest work.
- For spreadsheets, check formulas and charts; for media, check output; for Scratch, run the saved program.
- Follow authorised submission and invigilator instructions without unapproved workarounds.
A student should not rely on auto-save, cloud synchronisation or a personal email account unless the examination instructions expressly support them. If equipment behaves unexpectedly, report it to the invigilator and follow the official procedure rather than attempting an unapproved fix.
Time management across three practical tasks
There is no universal compulsory minutes-per-task allocation
The 135-minute paper includes three compulsory tasks and saving time. One illustrative rehearsal budget is 45 minutes Media, 40 minutes Spreadsheets, 40 minutes Programming and 10 minutes final checking. That adds to 135 minutes. This is an optional practice framework, not a SEAB mandate or prediction of the exact difficulty of any task.
Students should adjust their budget after practising with realistic tasks. If a media requirement is time-consuming, reserve additional time while protecting the spreadsheet and programming components. The paper gives approximately 30, 25 and 25 marks for the tasks, but the actual parts may vary.
Avoid polishing one task forever
A visually attractive animation can be tempting to refine repeatedly, but the marks depend on the required output. It is usually better to complete core functions correctly across all three tasks before adding non-required decoration to one. Ask the student which edits satisfy an explicit task instruction.
During practice, use milestone checks: after the first portion of time, confirm an assessable version exists; later, add remaining specified features; finally, save and verify. The exact sequence depends on the task and the centre’s rules.
Common practical mistakes and targeted corrections
| Repeated error | What it suggests | Better exercise |
|---|---|---|
| A formula changes incorrectly when copied | Relative and absolute references are confused | Test formulas in three changed rows |
| A conditional total is mistaken for a count | Function does not match requested output | Compare SUMIF and COUNTIF on the same dataset |
| A chart lacks units or has the wrong type | Data communication is not understood | Ask another student what the chart means |
| Vector objects appear in the wrong order | Layering and grouping are insecure | Rebuild a simple icon with specified arrangement |
| Video looks correct in editor but export is incomplete | Output verification was skipped | Inspect the actual saved video |
| Scratch score changes at the wrong moment | Event or condition is misplaced | Test start, success, failure and reset cases |
| Right output was created but not saved correctly | File-handling procedure is weak | Rehearse authorised save and verification steps |
| Candidate practises microcontroller hardware for Paper 2 | Assessment scope has been confused | Review Paper 1-only MakeCode notation |
A 90-minute small-group lab lesson
- Retrieve one spreadsheet reference rule and one programming event concept.
- Diagnose a broken file or inaccurate practical output.
- Explain the relevant formula, visual feature or block relationship.
- Guide a changed task, checking why each step is necessary.
- Require an independent save and output test.
- Review the actual resulting file and assign a small next task.
This diagnosis–explanation–guided practice–independent transfer sequence adapts the teaching logic illustrated by eduKateSG’s immutable Clementi 3-pax Mathematics reference. That page demonstrates a learning approach and does not confirm availability of a G2 Computing laboratory tuition programme.
Four-week practical examination preparation cycle
| Week | Media task | Spreadsheet task | Programming and saving check |
|---|---|---|---|
| 1 — Diagnose | Create and inspect one simple graphic or slide output | Build a small table, formula and chart | Run one short Scratch project; identify weak skills |
| 2 — Repair | Practise one missing graphic, slide or video operation | Fix a repeated formula/reference/validation issue | Correct one event or variable logic gap |
| 3 — Transfer | Produce a different media output from an unfamiliar brief | Use new data and function conditions | Debug a new script; verify save and reopen |
| 4 — Integrate | Timed task under a realistic overall plan | Timed task and output review | Timed program plus final file-verification rehearsal |
Four weeks are a repeatable improvement cycle, not a claim that the entire six-module G2 Computing syllabus can be learnt from scratch in a month. Paper 1 theory still requires ongoing study. School-authorised software, authentic practice and specific feedback should guide the student’s progress.
Frequently asked questions
What is G2 Computing Paper 2 worth in 2027?
80 marks and 50% of the SEC K237 Computing subject grade.
How long does Paper 2 last?
Two hours and fifteen minutes, including time to save required softcopy work.
Which practical tasks are compulsory?
Media Software, Spreadsheets and Programming. All three are required.
Are the task marks exactly 30, 25 and 25 every year?
SEAB lists them as approximate values: about 30 Media, 25 Spreadsheets and 25 Programming. Do not treat these as guaranteed exact subtask allocations.
Is Paper 2 the same as Paper 1?
No. Paper 1 is a 90-minute electronic written exam covering all six modules. Paper 2 is the lab-based practical covering Modules 4–6.
Does Paper 2 include Scratch?
The programming outcomes include Scratch blocks and game programming assessed in both Papers 1 and 2.
Are microcontrollers and MakeCode assessed in Paper 2?
No. The published syllabus specifies microcontroller and MakeCode-related outcomes for Paper 1 only.
Can candidates use personal cloud storage to submit work?
Do not assume this. Candidates must follow the examination centre’s prescribed file-saving and submission instructions.
Can a correct but unsaved answer still earn full marks?
The practical requires submission of softcopy work for marking. Saving and providing the specified deliverable is therefore essential.
Can a calculator be used?
The syllabus permits an approved calculator in Papers 1 and 2, but formulas and digital tasks still need to be completed using the appropriate application.
Official sources and related learning
- SEAB: 2027 G2 Computing K237 syllabus and Paper 2 lab specification
- SEAB: 2027 G2 syllabus directory and Computing specimen papers
- How G2 Computing K237 Works — All Six Modules and Both Papers
- How G2 SEC e-Examinations Work — Electronic Delivery and File Handling
- How G2 Mathematics Works — Reading Quantities and Graphs
Reviewed 6 November 2026. The official SEAB syllabus and school instructions govern practical task formats, approved applications, filenames and examination arrangements. Examples and timing allocations here are for learning only.
The next useful lab practice
Give the learner one small spreadsheet task, one simple media output and one Scratch program using unfamiliar data or instructions. Ask the student to explain what each output should do, complete it independently, test the result and save the specified file. Correct the first failure in that chain rather than adding more unrelated tutorials.
For a learning diagnosis or enquiry about appropriate Computing support, contact eduKate Singapore or enquire on WhatsApp. Confirm subject expertise, suitable software and actual class availability. No result is guaranteed.