The 2027 SEC G1 Computing K127 Paper 2 is a two-hour laboratory-based examination worth 90 raw marks and 60% of the subject result. Every task is compulsory. It contains three practical tasks, with approximately 30 marks for media software, 35 marks for document processing and spreadsheets, and 25 marks for programming. Students must submit the required softcopies. Crucially, the two-hour time limit includes time for saving the required work. A project that appears finished on screen but is not saved in the required form is not a reliable final deliverable.
For the frequent questions “How do I pass G1 Computing practical?”, “What Scratch programming blocks are tested?” and “What Excel formulas should I know?”, use the official SEAB 2027 Computing K127 syllabus as the source of truth, then practise complete tasks: read the brief, choose the correct tools, produce the result, test it, save it and reopen it. This page concentrates on Paper 2’s operational weaknesses—broken spreadsheet references, incomplete Scratch games, unreadable media exports and missing files—rather than duplicating the general K127 seven-module subject overview.
- 2027 G1 Computing code: K127, a new syllabus first examined in 2027.
- Paper 2: 120 minutes, 90 raw marks, 60% of final grade.
- Three tasks: media software around 30 marks, document + spreadsheet around 35 marks, Scratch programming around 25 marks.
- Programming uses the specified Scratch visual blocks; core scope includes variables, loops, conditionals (no nested if), events, messages, coordinates, sprites and debugging.
- Spreadsheet syllabus includes SUM, AVERAGE, MEDIAN, MIN, MAX, COUNT, COUNTA, COUNTIF, ROUND, IF (no nested IF), LEFT, MID, RIGHT, LEN and VLOOKUP exact match, among other operations.
- File checks are compulsory habits: correct name, correct folder, correct format, saved final output and working logic.
- Paper 1 is separate: 75-minute e-Exam, 60 marks, 40% of final grade, covering all seven modules.
Official Paper 2 skills and approximate mark distribution
| Task | Syllabus modules | Approximate raw marks | Evidence of completion |
|---|---|---|---|
| 1: Media software | Vector/raster graphics, presentation and video editing | 30 | Appropriate graphic, edited media or presentation in specified form |
| 2: Document and spreadsheet | Document formatting, formulas, charts and data tools | 35 | Readable document plus functioning calculation or chart as required |
| 3: Programming | Visual Scratch code and debugging | 25 | Working game or program that satisfies the assigned logic |
| All tasks | Saving and required softcopy submission | 90 total | All requested files present and reopenable within 2 hours |
These are approximate task allocations, not promises that the practical examination will use a fixed number of subquestions or a particular product. SEAB specifies that candidates submit softcopies and that the allocated two hours include saving work. The examination centre supplies approved laptops and required software. The right preparation uses the school-authorised applications and procedures; an unrelated personal tablet, mobile app or cloud-storage workflow cannot be assumed identical to the national lab environment.
The written Paper 1 includes all seven modules and has twenty multiple-choice questions in Section A and structured questions in Section B. Paper 2 instead assesses modules 4–7: document processing, spreadsheets, media software and programming. A good candidate learns both, but preparing for a practical exam requires an observable functioning result, not merely the ability to describe an application feature.
A sensible Paper 2 workflow that protects the final files
| Stage | What the student should do | Practical mistake avoided |
|---|---|---|
| Read | Identify every output, file type, named folder and scoring requirement | Finishing an irrelevant or incomplete task |
| Plan | Allocate time to all three tasks and a final verification phase | Leaving a whole task untouched |
| Build | Use the stated source material, formulas and software | Inventing content or using incompatible tools |
| Test | Change inputs, run scripts and inspect actual media output | Assuming attractive screen previews prove function |
| Save | Use precisely the required file name, path and type | Unsaved or incorrectly submitted deliverables |
| Reopen | Inspect the file from the intended location | Confusing a live editor session with a recoverable final file |
| Finish | Review the official checklist and any submission action | Leaving a required component missing after two hours |
A practical time plan might reserve several minutes at the start to read and at the end to verify. It should be adjusted during realistic school simulations according to the student and the actual paper. SEAB does not prescribe the internal time distribution used in this guide. The important rule is to protect time for all tasks and their saved deliverables rather than polish one attractive graphic while an entire programming task remains unfinished.
A worked fictional spreadsheet: small school-event purchases
| Cell/field | Example value or formula | Purpose |
|---|---|---|
| B2 | 3 | Quantity of notebooks |
| C2 | 2.50 | Unit price |
| D2 | =B2*C2 | Calculated item total: 7.50 |
| B3 | 4 | Quantity of pens |
| C3 | 1.20 | Unit price |
| D3 | =B3*C3 | Calculated item total: 4.80 |
| D4 | =SUM(D2:D3) | Sum of totals: 12.30 |
The quantities and prices in this practice table are invented. The key observation is that formulas connect inputs to outputs. If the notebook quantity changes from three to five, the D2 formula should recalculate automatically, and the D4 total should respond. A manually typed 7.50 in D2 might look correct at first but would be a weak substitute when the task requires a calculation that updates. Students should test formulas with controlled changes rather than rely on whether a displayed total seems plausible.
For a conditional formula, the syllabus includes the IF function but excludes nested IFs. An illustrative formula such as =IF(D2>10,”Review”,”OK”) checks one logical condition and returns one of two texts. It is not an instruction to write advanced multilevel formulas the syllabus does not require. For a lookup, the K127 scope includes VLOOKUP with exact matching: understand which identifier is being searched, which column supplies the answer and what happens if a code is missing. Practice must stay aligned with the official learning outcomes.
Twenty focused Paper 2 skills and recovery drills
1. Convert the brief into output requirements
A practical task can contain several numbered instructions, each affecting a different file or part of a project. Students should first list expected outputs, given files, required content, formatting, formulas, scripts and any stated limits. A response can look attractive and still fail a specific criterion. Planning is most useful when it creates a checkable list, not a long essay about how the software works. The most important question is what someone can verify after opening the final result.
Worked practice scenario: A fictional task asks for an infographic with a title, two icons and a particular export type; a plain screenshot is not automatically the requested file. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Beginning with decorative changes before identifying the required file name and technical result. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Turn three practice briefs into a matrix of required output, source material, tools and final verification. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
2. Save early without treating drafts as final
Saving is not a single last-minute event. An early working copy protects progress in practice, while a clear final file and approved submission procedure protect the finished output. Avoid creating many confusing versions such as final-new2-last. In the actual exam, follow the precise saving path, filename and file-format instructions. Changing a filename’s extension without converting content is not a valid export. After a save, reopen it to confirm that the required information persists.
Worked practice scenario: A student edits a spreadsheet and sees correct results but closes the app before saving to the exam folder; the visible workspace was not a reliable deliverable. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Confusing an autosaved draft, a cloud link or a screenshot with the officially requested softcopy. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Use one authorised practice folder and deliberately save, close and reopen a project with a stated file type. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
3. Distinguish file extensions from file contents
An extension often indicates the type of data stored but is not proof that the file’s internal format matches it. Different tasks may request editable source work or an exported viewing copy. A screenshot of a vector editor does not preserve editable paths; a saved video project may not be a playable exported clip. The student’s final check should identify which file the examiner is meant to mark and whether the format is genuinely suitable.
Worked practice scenario: Renaming a document from .docx to .pdf without exporting it does not reliably create a valid PDF. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Assuming all ‘save as’ options preserve editable data, embedded media and correct formatting equally. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Take three original practice files and compare their editable project form with a valid exported output. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
4. Create a readable word-processing document
The document-processing syllabus includes page formatting, alignment, paragraph spacing, headings, columns, headers, footers, page numbering and tables. Good performance means accurately fulfilling the specified instruction, not selecting the most decorative style. A reader should find the main title, section divisions and details without confusion. Some tasks require exact dimensions or layout; the practical question controls them. Students should keep consistent formatting unless the instructions deliberately request variation.
Worked practice scenario: A fictional event notice needs a header, a two-column information section and numbered pages. The design should make all requirements visible. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Using repeated spaces to force alignment, leading to a broken layout when the font or margin changes. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Format a one-page practice notice with appropriate built-in document tools, then inspect it at normal page view. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
5. Use images and text wrapping accurately
Imported graphics may need to move, resize, rotate, flip, crop or wrap in relation to text. These are separate operations. A crop removes visible areas from a displayed frame, whereas resizing changes dimensions. A layout can fail if an image covers required text or distorts the main subject. The syllabus includes linking text boxes and embedding spreadsheet charts; students should practise these relationships within a meaningful document rather than as isolated buttons.
Worked practice scenario: A brochure’s photograph overlaps the registration paragraph after a layout change; an appropriate wrap setting restores readability. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Stretching a logo out of proportion or using a floating image that covers a table. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Use an original image in a practice document, test several wrapping settings and verify that important text remains visible. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
6. Format numbers and percentages in spreadsheets
A numeric cell can display as a decimal, currency or percentage without changing its underlying value. Students must understand the difference between stored number and display format. A cell containing 0.15 displayed as 15% is not the same as storing 15 and applying a percentage format. Decimal-place instructions should be followed exactly, and mathematical comparisons should be based on numeric data rather than decorative text.
Worked practice scenario: The value 0.2 can display as 20% when formatted properly; entering 20 and selecting percentage can produce an unintended display. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Assuming a cell displaying a percentage symbol contains the same underlying value as the visible digits suggest. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Create several formatted cells and compare what appears in the formula bar with what is shown on the worksheet. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
7. Use relative and absolute references deliberately
Relative references move when formulas are copied, while absolute references can keep a fixed parameter unchanged. This matters when multiplying every row by a common rate or looking up a fixed table. Students should trace a copied formula, not trust the first correct row. A wrong reference may produce believable but incorrect totals. The skill is recognising which elements should change and which should stay fixed.
Worked practice scenario: A common multiplier stored in F1 can be referenced as $F$1 where the formula must keep using that cell when copied. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Copying a correct first-row formula down without noticing the fixed parameter shifted to another cell. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Predict the references after copying three formulas, then test them by changing an input. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
8. Understand SUM, AVERAGE, MIN, MAX and MEDIAN
These functions answer different questions. SUM combines numeric values, AVERAGE finds their arithmetic mean, MIN and MAX identify extremes and MEDIAN describes the central ordered value. A practical task may include blanks or irrelevant rows, so selecting the correct range is as important as choosing the function. A total row accidentally included in the source range can double-count results and damage any later chart.
Worked practice scenario: A table of daily visits can use MAX to find the highest day; SUM answers the week’s total, a different business question. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Choosing AVERAGE when the instruction asks for a total or including the summary result within its source range. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: For one fictional data table, calculate all five measures and explain why each has a different interpretation. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
9. Distinguish COUNT, COUNTA and COUNTIF
COUNT counts cells containing numbers, COUNTA counts non-empty cells, and COUNTIF counts cells satisfying a stated condition. These functions are not interchangeable. Text labels, empty rows and numeric values can change which function is appropriate. The official K127 syllabus includes these functions, so the student should practise both meaning and correct argument ranges. When debugging, first inspect whether the cells contain values of the expected type.
Worked practice scenario: An attendance column containing names cannot be counted with COUNT as if those names were numeric measurements; COUNTA may be appropriate for non-empty entries. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Using COUNT for a list of text categories and concluding there are zero records. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Build a short mixed-type list with blanks and write the expected result of each counting function before entering it. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
10. Use IF for one clear logical condition
The K127 spreadsheet scope includes IF with one condition and two possible results; nested IF is excluded. First express the decision in ordinary language: if a value crosses a stated threshold, show one response, otherwise show another. Then write the formula with the correct comparison and references. The output can be text or a number depending on the task. Test a value just above, just below and equal to the boundary.
Worked practice scenario: A fictional inventory alert can show ‘Reorder’ when a quantity is below five and ‘OK’ otherwise, according to a stated rule. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Using a strict less-than comparison when the task says ‘five or fewer’ or reversing the true and false outputs. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Write one IF formula and test boundary values of four, five and six against the stated condition. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
11. Apply exact-match VLOOKUP without inventing a match
A lookup finds a value associated with a key in a specified table. The K127 syllabus covers exact-match VLOOKUP, so a non-existent code should not be silently assigned to a similar item. Students should understand which column holds the key, which holds the result and why the table range must be correct. This is useful in retail stock work, club registers and school event tracking. Approximate matching is a different behaviour and should not be substituted unknowingly.
Worked practice scenario: A fictional stock code A103 should return its own recorded item name, not the closest neighbouring code when A103 is absent. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Using approximate match by mistake or looking up a display name from the wrong column. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Create a four-row lookup table and test an existing code plus a missing code, explaining both results. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
12. Use text functions for structured data
The specified text functions include LEFT, MID, RIGHT and LEN. They help extract characters from known positions and measure text length. These operations are not intelligent interpretation: an extraction rule can fail when the input format changes. Students should read the task’s example strings carefully and verify that the selected characters are correct. A correct formula applied to the wrong cell can still give an unusable result.
Worked practice scenario: An invented product code ‘SG-204’ can be examined by extracting its prefix, but the prefix’s meaning depends on the stated coding rules. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Using LEFT when the task asks for characters in the middle or assuming all identifiers have equal lengths. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Practise four example codes, identify the exact character positions needed and test how one changed format affects the formula. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
13. Construct a chart from the right data range
The syllabus includes bar, column, pie, line and combination charts of line and column, with titles, axes, data labels and legends. A chart can look correct while its source range is wrong. Read what the comparison should show, select the relevant categories and values, and exclude totals when they would distort the display. A line chart is appropriate for some time-based changes; a bar chart may be clearer for unrelated categories. The output must be readable.
Worked practice scenario: A chart of monthly spending should not include the ‘Grand Total’ as another month unless the question deliberately asks for that comparison. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Selecting extra blank cells or summary rows and accepting the chart because it has attractive colours. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Create two charts from a fictional dataset, deliberately choose one incorrect range, then fix it and explain the difference. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
14. Use sorting, filtering and data validation correctly
Sorting reorders rows according to a field, while filtering displays only those matching stated conditions. A dangerous spreadsheet mistake is sorting one column independently from the rest, breaking the relationship between product, price and quantity. The syllabus also includes simple validation criteria and custom error messages. A student should know what invalid data the rule is meant to prevent and what the user experiences when entering a prohibited value.
Worked practice scenario: A quantity field intended for non-negative numbers should not accept a negative value if the task expressly prohibits it. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Sorting names separately from associated marks or applying a filter without understanding which rows remain hidden. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Create a small dataset with linked columns, sort complete rows, then design a validation rule for one column. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
15. Recognise vector versus raster graphics
Vector graphics use shapes defined by paths and nodes, whereas raster graphics use pixels. Resizing vectors generally preserves edge quality, while enlarging a small raster can expose pixelation. The practical syllabus includes drawing shapes, manipulating nodes, using fills, combining shapes and exporting vector work as a raster file. Students should choose an output based on the actual requirement rather than assume all image types behave the same.
Worked practice scenario: A simple icon intended for both a tiny label and large poster may be easier to keep crisp as vector source artwork. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Trying to edit individual pixels with vector tools or assuming a flattened export retains editable paths. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Create one original icon with basic shapes, scale it, and compare a low-resolution raster export against the editable version. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
16. Control layers, transparency and visual hierarchy
Media work can involve changing the front-to-back order of objects, grouping elements, editing transparency and applying fills or outlines. Each operation should support a visible requirement. A translucent shape can reveal an object beneath it, but too little contrast may make the message unreadable. Students should avoid flattening components before finishing edits if the task requires individual object control. Check the final visual at the intended size.
Worked practice scenario: A sign’s headline remains readable when placed above a simple illustration with sufficient contrast, whereas burying it behind a shape hides required information. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Confusing moving an object on the page with changing its layer order, or losing readability after a transparency change. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Build a three-layer fictional graphic and test front/back ordering, grouping and readability. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
17. Storyboard media and export a playable result
The K127 media module includes presentations and videos, using still images, video clips, text, transitions and sound. A storyboard defines sequence and purpose before editing. The completed project may need to preserve specific media order, timing and text. Verify the actual exported video or presentation, not only the editor’s timeline preview. Check for missing clips, unexpected blank frames and inappropriate resizing. Use only original or properly authorised assets in practice.
Worked practice scenario: An original school-event recap has three scenes and a clear closing message. The exported file should contain all three scenes in the intended order. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Assuming a screenshot of the editing timeline equals a working video output. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Write a three-scene storyboard, create a short original practice video and reopen the export to verify order. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
18. Scratch events, sprites and stage coordinates
Scratch uses sprites and a stage. Events can begin scripts when the green flag, a key press, a click or a received message occurs. The stage uses x/y coordinates; moving right or up changes particular coordinate values. A sprite’s costume or position may not reset automatically unless a script tells it to. Students should learn to predict program behaviour before running it rather than drag blocks until something appears to work.
Worked practice scenario: A game starts with a sprite at x=0, y=0 and moves it right after an arrow-key event. The change is in x, not automatically y. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Writing a movement script without a starting-position reset, causing a different outcome on the second run. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Draw a coordinate grid, predict positions after commands and then verify them in a school-approved Scratch project. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
19. Scratch variables, loops and conditions
The examinable Scratch blocks include creating, initialising and changing variables; repeat, forever and repeat-until loops; if and if-else conditions with no nested if statements; logical and relational operators; and random numbers. These blocks solve different problems. A countdown might use a variable and a loop, while a winning condition checks its value. A loop without a stop criterion can behave unexpectedly. Practise tracing the program’s state after each action.
Worked practice scenario: A score variable begins at zero, increases by one when an item is touched and triggers a success message when the target is reached. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Forgetting to initialise the score at the beginning, so the second play inherits the previous result. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: Trace a fictional five-event game by writing the variable’s value and active condition after each event. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
20. Scratch messages, collision checks and systematic debugging
A game may require sprites to coordinate through broadcast messages, react to key presses or respond when touching another sprite or colour. Multiple scripts can execute concurrently, so a bug may arise from event timing as well as arithmetic. Debugging begins by reproducing the failure and isolating the smallest relevant script. Test a change and run the game from its initial state. The official syllabus includes identifying and correcting errors, not simply building a game that works once.
Worked practice scenario: An item becomes invisible after the first play and never reappears. Investigate which start event should restore its visibility before changing unrelated artwork. This task is a newly written illustration of a general skill, not a released SEC question. Before choosing an application control or program block, the learner should state the target output, the information needed and how success will be verified after the file is saved.
Common practical failure: Changing several scripts simultaneously, losing the ability to identify what caused or fixed the problem. When reviewing, identify the first unreliable decision: wrong cell reference, source range, condition, event, state, file format or submission action. A correction is durable only when the student can explain why it fixes the problem rather than repeat a click sequence from memory.
Independent drill: For three fictional failures—wrong score, invisible sprite, missed broadcast—write one minimal hypothesis and a test. Complete the task with a new set of inputs after feedback, test the output and reopen the saved file. Use only the school-authorised examination applications and procedures in formal rehearsals; a personal program’s options may differ from the actual environment.
A six-week K127 Paper 2 practical improvement plan
Week 1: audit saving, naming and requirements
Check the K127 subject code and school software. Practise opening source files, reading all instructions, saving editable projects, exporting required outputs and reopening them. Identify whether the student habitually loses files, misunderstands formats or simply runs out of time. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
Week 2: documents and visual consistency
Practise headings, columns, page numbers, headers, image wrapping, tables and chart embedding. Score the work for exact task compliance, not decorative originality. Reopen the document at the end to ensure the intended layout persists. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
Week 3: core spreadsheet logic
Build small tables with relative and absolute references. Apply SUM, IF, COUNT, COUNTIF, AVERAGE and VLOOKUP exact match where appropriate. Change input values and check dependent results. Identify the first broken reference when the calculation fails. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
Week 4: graphics and video outputs
Practise vector objects, raster resizing and a short storyboard-driven project. Export correct playable or viewable files. Use original or authorised media. Check readability at the intended output size and avoid relying on one attractive editor screenshot. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
Week 5: Scratch state and debugging
Build a small original game with a start event, score, movement, condition and end state. Test multiple plays to confirm resets. Introduce one deliberate error at a time and correct it methodically, including broadcast, collision and variable logic. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
Week 6: full 120-minute simulation
Attempt a three-task practical under a two-hour school-approved rehearsal. Use the published approximate 30/35/25 mark map as a preparation guide, while allowing the actual paper to determine subquestions. Protect time for final saves, file reopen and completion checks. The student’s feedback record should include one completed file, one demonstrated function, the failure caught by testing and the action that prevented it next time. Practice is valuable only when the deliverables are available and work when reopened.
A practical final-submission checklist
- Check each named task in the question and ensure no entire task was overlooked.
- Confirm every required deliverable has the exact specified name and format; do not invent an alternative submission location.
- Open the saved document and check text, page layout, tables, images and important headings.
- Open the spreadsheet and test at least one controlled input change; look for broken formulas or chart source ranges.
- Open exported media and confirm readability, sequence, final frame or visible result, according to the task.
- Open the Scratch project from the start state and test the intended event, score, conditions and finish behaviour.
- Identify any files that exist only as editor drafts or unsaved windows and save as authorised.
- Use the paper’s official submission action and do not assume a local save is equivalent to submitting to the examiner.
The checklist is a learning aid. During the actual examination, the official instructions control whether students may reopen, test, edit or submit files at each stage and whether particular areas of the file system are accessible. Do not assume that external cloud storage, USB devices or online tutorials will be permitted. The exam centre provides approved software and a laptop for the practical paper; the student’s responsibility is to use that environment correctly.
Frequently asked questions about G1 Computing K127 Paper 2
How long is the 2027 G1 Computing practical examination?
Two hours. The duration includes saving the required softcopy files. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
How many marks is it worth?
90 raw marks and 60% of the G1 Computing subject result. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
How many tasks are there?
Three practical tasks covering media, document/spreadsheet work and programming. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Are task marks always 30, 35 and 25?
The official syllabus describes approximate allocations of 30, 35 and 25, not a guarantee of every subquestion’s marks. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Does Paper 2 include networking or cybersecurity theory?
The practical Paper 2 focuses on Modules 4–7. Paper 1 assesses all seven modules, including networking and the impact of computing. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Is Scratch the programming language?
The K127 syllabus specifies examinable Scratch blocks for visual game programming. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Are nested IF statements required?
No. The K127 spreadsheet IF and Scratch conditional scope exclude nested IF constructs as specified in the syllabus. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Is VLOOKUP included in the Excel syllabus?
The syllabus includes VLOOKUP with exact matching. The exact spreadsheet application used for assessment follows the school’s approved software. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Do students need data validation?
Yes. K127 includes setting validation criteria and custom error messages for invalid spreadsheet entries. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
What charts should students recognise?
Bar, column, pie, line and a combination of line and column charts are among the specified chart skills. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Do students need to create video?
The media module includes making videos using still images, video clips, text, transitions and sound, among other media skills. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Is saving the editable file enough?
It depends on the task. Some instructions may require an exported or differently formatted output; follow the exact exam requirements. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Is a finished on-screen Scratch game always submitted correctly?
No. The required project file must be saved according to the examination directions. Reopenable output and correct submission matter. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Can a student use any laptop or app?
The centre provides a laptop with approved software. Personal alternatives may not match the actual exam environment. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Does a successful Scratch game prove Spreadsheet mastery?
No. Each task assesses different skills. A strong student needs separate evidence of media, document, spreadsheet and programming competence. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Is K127 the official 2028 successor to K130 Mobile Robotics?
No such one-to-one successor is established by this syllabus. Computing and the MOE–ITE applied robotics qualification are different offerings. For the candidate’s exact software, system, file naming, reporting and permitted materials, follow school and SEAB instructions rather than a generic tutorial.
Official sources and related eduKateSG articles
- Official SEAB SEC 2027 G1 Computing K127 syllabus PDF
- SEAB 2027 G1 school-candidate subject catalogue
- Mastering G1 Computing K127: full seven-module examination overview
- Maths companion: reading spreadsheet data, statistical summaries and probability
- English companion: clear communication and accurate task responses
- Full SBB subject levels, SEC 2027 and future pathways
Editorial note (11 November 2026): K127’s paper scheme, task allocations, specified functions, Scratch scope and saving requirement have been checked against SEAB’s 2027 Computing syllabus. All coding scenarios, product identifiers, spreadsheet quantities and media examples are original. They are not official specimen paper questions or predictions of unseen tasks. Candidate-specific software and exam procedures remain controlled by the school and SEAB.