G1 Computing Paper 2 in the 2027 Singapore-Cambridge Secondary Education Certificate (SEC) is a two-hour, 90-mark lab-based practical examination worth 60% of syllabus K127. Students use a computer to complete three practical tasks covering media software, document processing and spreadsheets, and programming. The indicative task allocations are about 30 marks for media software, 35 marks for document processing and spreadsheets, and 25 marks for programming. All three tasks are compulsory.
For 2027 G1 Computing K127, Paper 2 assesses Modules 4–7, and the candidate must submit the required softcopy files. The official two-hour time allowance includes saving the work on the candidate’s computer. The examination centre provides approved software and suitable hardware, and each candidate should have the sole use of a laptop. The other examination, Paper 1, is a 75-minute e-examination worth 40% and covers all seven Computing modules. Paper 2 is not an essay or a purely theoretical coding test.
This reader-first guide to How G1 Computing Paper 2 Works | SEC Examination Preparation helps students:
- Understand the three task groups and actual 2027 requirements.
- Practise creating clean documents, accurate spreadsheets, useful charts, graphics and videos.
- Build and debug simple programs in the syllabus’s visual programming scope.
- Avoid the expensive mistake of producing good work but saving or submitting the wrong file.
- Distinguish concept errors, software-operation errors and file-management errors.
- Prepare through original worked exercises and a practical, school-software-aligned revision plan.
The exact subject and its first examination year
G1 Computing is K127 under the SEC 2027 directory. SEAB identifies it as a new subject, with the first examination in 2027. Its learning goals include understanding computer systems and networks, developing computational thinking, working with documents and media, programming and using computing responsibly.
Under Full Subject-Based Banding, G1 is a subject level, not a description of a child’s intelligence or all subjects on the timetable. The SEC combines previously separate GCE certificate labels from the 2027 graduating cohort but preserves subject-level differences.
Paper 2 preparation should therefore focus on K127 Modules 4–7, not on a random professional software course or a G3 Computer Science curriculum. Students should use the school’s approved applications and official specimen resources, where available, rather than assume their personal devices will have identical features.
The key practical question is “Can the learner produce, verify, save and submit the required artefact independently under a changed brief?”
What the three practical tasks cover
Task group 1: Media software — approximately 30 marks
Candidates may work with relevant graphics, presentation or video tasks, within the Module 6 requirements. This can involve arranging content, manipulating images, shapes, layers or text, creating coherent presentation layouts, or using a storyboard and media elements to produce a digital sequence.
The target is a correct, purposeful digital artefact. Adding effects that were not asked for can waste time or reduce clarity.
Task group 2: Document processing and spreadsheets — approximately 35 marks
Candidates use appropriate document and spreadsheet functions from Modules 4 and 5. They may need to format text and pages, place graphics, create tables or linked content, calculate with formulas, work with spreadsheet functions, format or analyse data, and create charts.
The main risk is doing something that looks right without using the correct underlying function. A total typed manually rather than calculated with a formula can fail when the task expects the spreadsheet to update.
Task group 3: Programming — approximately 25 marks
Candidates work with Module 7’s visual programming concepts: variables, events, conditions, loops, sprites, coordinates, randomness, messages and debugging. They may create or adjust a simple interactive program or game according to the task.
The job is to make the program behave as required, not merely to produce attractive screens or name many programming blocks.
The mark allocations are approximate, as stated in the published scheme. A candidate should follow the actual paper rather than treating them as a fixed per-item scoring template.
Two hours include saving the files
SEAB explicitly states that Paper 2’s allotted time includes saving the required work. This makes file management a first-class examination skill.
A student might produce a correct chart but leave the final workbook in an unapproved directory. Another might make a working game but save only a screenshot. A third might export an image while leaving required editable working files unsaved.
The correct output depends on the actual exam instruction. A screenshot, exported PDF, compressed image or rendered video is not automatically interchangeable with an editable project or document.
The candidate should practise:
Reading the requested format.
Naming the file exactly as instructed.
Saving in the designated location.
Checking the file contents.
Confirming that the required file, not a temporary draft, is present.
The examination centre’s directions govern the actual submission procedure. Do not invent a USB-upload or cloud-storage process that the official paper has not supplied.
How to prepare when different software packages exist
K127 specifies skills, while the school and examination centre provide the approved software environment. Functions such as text boxes, section breaks, charts, image transparency or a programming block may look different across applications.
Students should be able to explain the purpose of a function, then operate it in the chosen school application. Learning a memorised screen-click sequence without understanding what it does can fail if the interface, layout or source data changes.
Ask the school’s Computing teacher which software version and specimen materials should be used for the actual 2027 K127 course.
The useful approach is: task requirement → software concept → correct operation → verify output. The exact button positions come from the approved software.
The three independent success checks
Every practical task should pass three checks:
Functional correctness: Does it do what the instructions require? Is the spreadsheet calculation correct? Does the game trigger the right result?
Presentation and clarity: Is the document readable, the chart labelled and the video sequence understandable?
Submission integrity: Are all required files saved correctly, with the right formats and content?
A beautiful project with broken formulas fails the first check. A correct computation embedded in an unreadable chart weakens the second. Perfectly functioning work not submitted correctly fails the third.
Train all three. Do not make aesthetics the only measure of digital competence.
Module 4: document processing is about structure
The syllabus includes document layout and editing features such as text formatting, paragraph indents, tabs, section breaks, page breaks, multiple columns, headers, footers, page numbers, text boxes, linked text boxes, graphics and embedded charts.
A common mistake is using repeated spaces to position content. That may appear correct until the font changes or a line wraps. The candidate should instead use the appropriate formatting and layout features.
For example, a two-column handout should be created using the application’s intended column function if that is what the brief requests. It should not be simulated with a row of spaces.
Good document processing separates content from structure. Headings should behave like headings where the application supports styles, not merely look slightly larger.
Original document exercise: the school event guide
Invented task, not an official SEAB specimen:
A school event requires a two-page guide. The first page contains a title, introduction, two-column programme and image. The second contains a wide table, with page numbers and a suitable header.
A clear working plan is:
- Type or import the supplied information accurately.
- Create a consistent heading and paragraph hierarchy.
- Apply the requested columns rather than manual spacing.
- Insert the image and adjust its size without obscuring text.
- Use a section break when a later page needs different orientation or layout.
- Insert page numbering through the correct feature.
- Check each page for overflow, missing information and alignment.
- Save the editable file in the required location.
The important skill is meeting the written specification. A student should not add an unnecessary decorative cover that forces the required information onto another page.
Section breaks and page breaks are not the same
A page break moves following content to a new page. A section break can define a new section so that suitable layout properties, such as orientation, can differ from another section.
Students often confuse the two and accidentally rotate the entire document when only one page should be landscape.
Original task: “Place the wide programme table on a landscape page, while retaining portrait orientation for the introduction.” The candidate needs to manage the relevant section boundaries in the authorised application.
The best checking method is to inspect both sides of the affected section. If the first page changes orientation unexpectedly, the task is not yet complete.
Practise on a simple two-page document before adding images, headers and charts.
Headers, footers and page numbers need actual functions
A student might type “Page 1” at the bottom of the first page and “Page 2” at the bottom of the second. That may look adequate, but when the document changes, the labels may not update as real page-number fields.
If a task requests page numbers, use the application’s proper feature. Likewise, headers and footers should be placed in the intended document region.
A correct document should remain understandable after ordinary editing. Checking whether page numbers remain accurate after adding a paragraph is a useful way to test the underlying structure.
Do not assume that visual resemblance alone proves that the software requirement has been met.
Module 5: spreadsheets are not decorative tables
A spreadsheet stores values, formulas and relationships. It can calculate new results when source values change.
The syllabus expects the learner to use formulas involving arithmetic and comparison operations, relative and absolute cell references, functions, charts, sorting, filtering and suitable validation or formatting features.
A spreadsheet practical is therefore different from manually typing totals into a word-processing table. The question may require actual reusable formulas.
Before entering a formula, the learner should state which cells represent inputs and what mathematical relationship is required.
This turns a software instruction into a clear plan.
Original spreadsheet exercise: a school supply order
Imagine a fictional order table:
Column A: item name.
Column B: quantity.
Column C: unit price.
Column D: line total.
For row 2, the formula is **=B2*C2. If the quantity in B2 is 4 and the unit price in C2 is $2.50, the line total is $10.00**.
Copying the relative formula down should adjust the row references, so row 3 ordinarily uses **=B3*C3**.
The student should test this by changing a quantity and observing whether the result updates. If the answer is a fixed typed number, it may remain unchanged after the input changes.
This simple test distinguishes a genuine spreadsheet calculation from a decorative table.
Relative references: why copied formulas can work
A reference such as B2 is relative. When a formula is copied down one row, it normally becomes B3, assuming the usual spreadsheet reference behaviour.
This is useful when every row follows the same rule, such as quantity × unit price.
A common error is placing a dollar sign in the wrong location and freezing a reference that should move. The student’s first question should be “Which data changes from row to row?”
Do not memorise the dollar sign as a mysterious symbol. Learn its role in controlling a reference during copying.
Absolute references: when a value must remain fixed
Suppose a fictional spreadsheet stores a constant classroom exercise rate in cell F1. Each row uses that rate.
A formula might be **=D2*$F$1. Copying it down changes D2 to D3, but the absolute reference $F$1** remains fixed.
If the student writes **=D2*F1** and copies it, the reference may shift to F2 or F3, producing incorrect results or blanks.
The useful test is to copy the formula into several rows and inspect the referenced cells. When one value is supposed to remain constant, the formula should reflect that requirement.
The rate is an exercise input, not an assertion about any current Singapore tax or service charge.
SUM, AVERAGE and the meaning of a formula
Suppose a fictional table has scores in B2:B6. =SUM(B2:B6) adds them, while =AVERAGE(B2:B6) calculates the arithmetic mean of numeric values.
They answer different questions. SUM measures a total; AVERAGE measures a central tendency.
A candidate should identify whether the task asks for the total number of units, the mean price, the largest value or the number of filled cells before choosing a function.
The K127 list includes SUM, AVERAGE, MEDIAN, MIN, MAX, COUNT, COUNTA, COUNTIF, ROUND, IF, LEFT, MID, RIGHT, LEN and VLOOKUP (exact match). Practise these with small datasets and learn the purpose of each.
The syntax may vary slightly in presentation across applications, so use the approved school’s platform conventions.
COUNT and COUNTA: similar names, different jobs
COUNT counts numeric entries in a range. COUNTA counts non-empty cells, including text values.
Original teaching table:
A2 = "Mira"
A3 = "Rahim"
A4 = 12
If the range contains these three non-empty cells, COUNTA(A2:A4) gives 3, while COUNT(A2:A4) gives 1 because only one entry is numeric.
The student should distinguish the type of data being counted. A question about how many records have any entry is different from one asking how many numerical measurements were recorded.
Check whether blank cells, text representations of numbers or other specific cell types affect the actual question. Do not assume every displayed digit is stored as a numeric value.
COUNTIF: count only the records meeting a criterion
Original example: values in B2:B11 represent ten fictional attendance percentages.
The formula =COUNTIF(B2:B11,">=75") counts numeric cells in the range that are at least 75.
The result depends on the actual data. The important feature is the condition, not the number 75.
If the task asks for values greater than 75, the comparison operator must be >, not >=. A one-character difference changes which records qualify.
The same precise reading skill is useful in Mathematics and in the computer programming task.
IF: choose between two outputs based on a condition
Original spreadsheet formula:
=IF(B2>=60,"Meets target","Review")
If B2 contains 72, the displayed result is Meets target. If B2 contains 54, the result is Review.
A student should understand the three parts of the function: logical test, value if true, and value if false.
K127 teaches basic IF use and excludes complex nested-IF constructions in the specified scope. Learning a simple correct IF is more valuable than memorising advanced formulas from unrelated professional analytics tutorials.
When copying the formula to other rows, check whether the intended reference changes.
VLOOKUP: exact matches require care
The syllabus explicitly includes VLOOKUP with exact matching.
Original teaching table: item codes occupy the first column of A2:B20 and descriptions occupy the second. Cell E2 holds the code to find.
A typical formula is =VLOOKUP(E2,A2:B20,2,FALSE).
This instructs the spreadsheet to find E2’s code in the first column of the table and return the corresponding second-column entry using exact matching.
If the searched code is absent, the function may produce an error rather than inventing the nearest product. The candidate should know what that outcome means.
A common mistake is searching the wrong first column or omitting FALSE, thereby changing the matching behaviour. The repair is to understand each argument, not merely memorise a formula string.
Text functions: when numbers are not the whole spreadsheet
A spreadsheet may contain item codes, category labels, names or other text requiring simple manipulation.
LEFT can take characters from the beginning of a text value. RIGHT takes characters from the end. MID extracts characters from a specified interior position, while LEN counts characters in a text string.
Original teaching example: A2 = "SEC2027".
=LEFT(A2,3) produces "SEC".
=RIGHT(A2,4) produces "2027" as text output in the relevant context.
=LEN(A2) gives 7 characters.
The goal is to select the correct operation for the task. Students should not apply text functions to a numeric problem where ordinary arithmetic is more appropriate.
Charts must represent the right data
The syllabus includes chart creation and combination charts involving columns and a line, along with chart selection and formatting.
A line chart may suit a sequence of weekly measurements. A column chart may help compare distinct categories. A pie chart may be useful for parts of a whole where the data are appropriate.
A student who adds a chart without correct source data, labels or scale has not necessarily created an informative result.
Before finishing, check:
Title: what does the chart describe?
Axes: which quantities and units are displayed?
Legend: can the viewer distinguish series?
Source range: are all required rows included without unwanted totals?
Appropriateness: does the chart communicate the requested relationship?
An attractive chart with incorrect units can be more misleading than a plain correct one.
Original chart exercise: comparing activity attendance
Imagine a fictional school event records attendance:
Monday: 18.
Tuesday: 24.
Wednesday: 21.
Thursday: 29.
Friday: 31.
A line or column chart can show the change over these five days. The largest recorded attendance is 31 on Friday.
Do not claim that attendance will continue increasing forever. The dataset contains only five observations and includes a decline from Tuesday to Wednesday.
A student should verify that the vertical axis represents number of attendees, not percentage, and that the categories appear in the correct day order.
This exercise teaches the difference between what the graph shows and what the data cannot establish.
Sorting, filtering and data validation
Sorting rearranges records into a particular order. Filtering temporarily shows entries meeting a condition. Data validation can restrict or guide allowable data entry, depending on the software feature.
A frequent mistake is deleting records the student meant to filter. That permanently changes the dataset instead of simply changing what is visible.
Another is sorting one column without preserving row relationships. A product code can become detached from its price if the whole table is not handled correctly.
A candidate should inspect the data before and after the operation and understand what the task requires. A correct-looking sorted column is not enough if its corresponding information no longer matches.
Module 6: graphic design as a practical task
K127 covers raster and vector graphics, relevant file types, shapes, layers, grouping, text, colours, transparency and layout.
A raster image is built from pixels and can lose apparent quality when enlarged too much. A vector image uses paths and shapes that can be resized with different characteristics. Both are useful for different purposes.
A classroom illustration may benefit from editable vector shapes. A photograph is naturally raster. The candidate should choose based on the requested work and output, not because one category is always better.
An important digital habit is to distinguish source file, editable project and exported graphic. The final task may request one or more of these. Check the actual instructions.
Original media exercise: a library information card
Invented brief: produce a clean library information card containing a heading, three short instructions, an icon and a suitable visual contrast.
The student should begin by identifying the reader and message, not by selecting every available font. A large heading establishes visual hierarchy. Suitable spacing helps readers find the details. A clean icon can support comprehension without obscuring the text.
If the software task specifically requires grouping two shapes and exporting with transparency, the candidate should demonstrate those functions correctly. Merely drawing something attractive will not satisfy a missing technical instruction.
Review the finished output at a realistic viewing size. Small labels may become unreadable after scaling, even when they appeared acceptable while editing.
Presentations: control the sequence
The syllabus includes presentation software, including relevant theme or slide-master features, text and media placement, transitions and coherent layout.
A student may be asked to create a short set of slides explaining an event or process. The sequence should make sense: introduction, relevant information, action or conclusion.
One recurring failure is inconsistent formatting—different heading sizes, colours and alignment on every slide without reason. Using a master or consistent style can improve reliability.
Another is excessive animation that distracts from the message. Use effects when they serve the task and follow the question’s explicit directions.
An effective presentation is measured by clarity, technical correctness and compliance with the brief, not the number of effects used.
Video creation: a storyboard saves time
Module 6 also covers video creation using relevant images, clips, text, transitions, sound and a planned sequence.
A storyboard identifies what viewers should see in each segment and why. For a fictional school safety reminder, the sequence might include the issue, a safe action and a concise final reminder.
A student who imports random media and only later decides on the message may run out of time editing transitions while leaving the meaning unclear.
Practice the distinction between source media, editing timeline and final exported file. The examination may require a particular output format, which must be followed. A video that plays in the editor is not automatically proof that it has been exported correctly.
Use school-authorised or original media, with respect for copyright and any academic-integrity rules.
Module 7: visual programming is about behaviour
The practical programming scope includes sprites, the stage and coordinates, variables, events, conditionals, loops, operators, messages, sound and debugging in a Scratch-style environment.
A candidate may be given a partially completed project, a specification for a small game or a set of behaviour changes to implement. The goal is to make the instructions work under the stated conditions.
A student should begin by answering:
What event starts the program?
What inputs does the program receive?
Which state must be stored in variables?
What conditions control the outcome?
Which behaviour repeats?
How will success be tested?
This is computational thinking in practical form. It is more useful than collecting many unrelated code blocks.
Original programming exercise: score and reset
Invented game specification: a player sprite catches falling stars. Each successful catch increases a score by one. When the user starts a new game, the score must begin at zero.
The student’s plan should include:
Start event: set score = 0 before play begins.
Repeated action: move the falling star according to the game rule.
Condition: detect whether the star touches the player.
Update: increase score by one for a completed catch.
Reset: move or otherwise reset the caught star so the same contact is not counted repeatedly.
Output: display the current score.
This is a conceptual description, not official examination block code. It teaches variables, event sequencing, conditions and state changes.
A common failure is forgetting the initial reset, leaving the score from an earlier attempt. Another is counting one contact repeatedly because the condition remains true.
Debugging: correct the cause, not the most visible symptom
Suppose the player’s score increases by three after what appears to be one catch. The student might assume the displayed number is wrong.
But the real issue could be that the increment block runs several times while the sprites remain touching. Fixing the text size would not repair the program.
A sound debugging cycle is:
Describe the expected result.
Reproduce the observed failure.
Locate the condition or repeated action that could cause it.
Change one relevant element.
Run the same test and a changed test.
This prevents the student from randomly moving blocks until the program appears to work once.
Conditions: AND and OR answer different questions
Imagine a fictional program should start a bonus round only if the score is at least 10 and the remaining time is greater than zero.
The correct logical relationship is an AND: both conditions must be true.
If the rule were “show a reminder if the score is low or the time is almost finished”, that would use an OR relationship.
These small differences matter because the program can appear correct during one ordinary test while failing at a boundary case. Students should translate English conditions into unambiguous logic before choosing blocks.
Practice with changed scores and times to confirm the behaviour.
Coordinate systems and sprite movement
In a visual programming stage, positions can be represented by x and y coordinates. Changing x typically moves horizontally in the usual stage coordinate system, while changing y moves vertically.
A student should understand how position changes relate to movement, not simply copy a block that says “change x by 10”.
For example, a sprite meant to move to the right may require a positive horizontal change in the standard coordinate arrangement. If the sprite moves upward instead, the wrong coordinate may have been altered.
Check the actual stage axes and the task’s instructions. Avoid assuming every software environment uses an identical coordinate origin or direction.
A two-hour rehearsal: a practical time-budget example
The official examination lasts 120 minutes and includes saving. It does not prescribe one compulsory split for all candidates. A practice-only approach might assign:
10 minutes: scan all three tasks, identify required outputs, start the correct files and note submission names.
35 minutes: complete the media task, with a quick functional check.
40 minutes: complete document and spreadsheet work, including formula and layout verification.
25 minutes: complete and test the visual programming task.
10 minutes: save, inspect and confirm all required files in the specified locations.
These numbers are illustrative and need to be adapted to the actual question and learner strengths. A student may benefit from tackling the programming task earlier, or reserving more time for an especially demanding document.
The principle is to attempt all compulsory tasks and protect submission time. Do not spend most of the examination perfecting a decorative image while two other task files remain empty.
Save-check rehearsal with an unfamiliar task
A realistic practice session should not end the moment a result looks correct on screen. Ask the learner to:
- Save the editable document with the specified filename.
- Save the spreadsheet and inspect whether its formulas still calculate.
- Save the programming project in the required format and reopen or test it where appropriate.
- Export any requested media output in the specified format.
- Confirm the destination folder and the number of expected files.
- Inspect one reopened output to check that content was not lost.
The exact examination process may differ, so use the school-approved directions rather than relying on generic “save to desktop” advice.
This test identifies a different kind of weakness from formula understanding. The learner may be technically capable yet need a dependable submission routine.
File extensions, formats and compatibility
A file’s extension indicates the intended format, but changing the extension alone does not necessarily convert the underlying data.
For example, renaming a word-processing file to end in .pdf does not create a valid PDF. A proper export operation is needed when the actual task requires that format.
Likewise, a rendered video may have different properties from its editable project, and an image exported as a raster file differs from its vector source.
A candidate should understand what kind of file is being requested and how to produce it in the approved software. Do not submit an image screenshot as a substitute for a required editable workbook or program unless the question explicitly allows it.
The six recurring Paper 2 failure families
1. Task-reading error
The student produces a visually attractive result but ignores a required function, field, chart or output. Repair: turn the prompt into a small deliverables checklist before starting.
2. Software-operation error
The student knows the desired outcome but cannot use the correct feature, such as a section break or proper chart insertion. Repair: practise the underlying function in the school’s approved application.
3. Logical or formula error
A spreadsheet references the wrong cell, or a program uses the wrong condition. Repair: explain the input-to-output relationship, then test changed inputs.
4. Design and communication error
The task technically runs but has unreadable labels, inconsistent layouts or a confusing media sequence. Repair: state the intended reader or user and revise only the elements affecting clarity.
5. Incomplete testing
The program works under one starting condition but fails when a variable changes. Repair: test normal, boundary and changed cases.
6. Submission error
The correct files are not saved in the required format or location. Repair: build a repeatable final-save and inspection routine.
A strong tutor distinguishes these error types. Repeating twenty spreadsheet worksheets cannot fix a student who already knows formulas but consistently forgets to submit the workbook.
Eight-week Computing Paper 2 preparation plan
Weeks 1–2: diagnose practical foundations
Give the learner an unfamiliar small document, spreadsheet, graphic and program task. Observe the earliest failed steps without supplying the clicks. Record weaknesses in software use, reasoning or file management.
Weeks 3–4: stabilise the core operations
Practise document sections and formatting, spreadsheet formulas and functions, chart ranges, simple media edits and visual-program events or conditions. Require a correct save at the end of every session.
Weeks 5–6: build small integrated projects
Use a fictional school event brief involving an information sheet, attendance workbook, simple media output and interactive game. Change the data or constraints after the first attempt so the learner must adapt rather than replay a memorised sequence.
Weeks 7–8: rehearse all three task groups
Complete school-approved two-hour practical practice with realistic saving requirements. Review repeated mistakes, retest changed tasks and consolidate the most important software operations. Confirm the actual examination centre’s approved software and instructions.
This is an educational plan, not an official SEAB preparation timetable or a guarantee of results.
A weekly routine for students who also have other subjects
A learner can practise one 20–30-minute software skill on three weekdays, followed by a longer combined task once a week.
For example, Monday can focus on relative and absolute references. Wednesday can focus on document sections. Friday can focus on a program condition. On the weekend, use a small brief combining one or two of the skills and require correct file submission.
Rotate the skills across weeks. The goal is independent competence, not endless repetition of the exact same instructions.
The most useful final question is: “Can you do it with different data and without the tutor telling you where to click?”
A fictional diagnostic comparison
Student A can format documents beautifully but enters spreadsheet totals as fixed numbers. Student B creates correct formulas but frequently saves only the image output and forgets the editable workbook.
Both may lose practical marks, but Student A needs to understand formulas and dependencies. Student B needs file requirements and verification.
Giving both a lecture on cybersecurity does not repair their Paper 2 difficulty. The subject also includes cybersecurity within the full K127 syllabus, but Paper 2’s immediate skill demands should be diagnosed specifically.
This is why a practical guide must show the actual failure mode rather than assume all computer errors come from a lack of theoretical knowledge.
What parents can observe without completing the work
Ask the student to show how changing a spreadsheet input affects a result. Ask why a page break differs from a section break. Ask what event triggers the program and how they know it works.
A useful parent question is: “Where is the file you would submit, and have you checked it?”
Parents need not know every software menu. They can observe whether the child can explain the decision and complete the task independently.
If the student uses tuition, a suitable tutor should prepare with the right K127 scope and school software. More expensive software or an advanced coding syllabus does not automatically improve performance in these specified practical tasks.
Academic integrity and safe digital use
Students should use original or properly authorised media and respect school rules on digital assistance, copyright and source attribution.
A generated image is not evidence that a candidate manually created the required vector shapes. A ready-made spreadsheet may not demonstrate that the candidate understands the formulas. A copied completed Scratch project cannot substitute for the candidate’s own programming when the examination assesses those skills.
Use learning tools to explain concepts and practise outside the assessment under permitted conditions. During the actual examination, only approved resources and candidate actions are allowed.
Also protect private data. Use fictional names, scores or product details for home exercises instead of copying real classmates’ personal information into unapproved applications.
Examination-day checklist
- Confirm 2027 G1 Computing K127, not another G-level or external qualification.
- Paper 2 is two hours, 90 raw marks, 60%, with three compulsory practical tasks.
- Prepare media (~30 marks), documents and spreadsheets (~35 marks), and programming (~25 marks).
- Use the approved school or examination-centre software and laptop.
- Follow the exact required file names, formats, output and destination instructions.
- Save during the task and reserve time for final checking.
- Test formulas and programs with changed inputs where time permits.
- Use only an approved calculator or other allowed materials under the official rules.
- Follow invigilator instructions if a technical issue occurs; do not improvise an unauthorised transfer method.
Frequently asked questions
Is G1 Computing Paper 2 written or practical?
It is a lab-based practical examination completed on a computer, not a standard handwritten theory paper.
How long does it last?
Two hours, including the time to save the required work.
How much of the subject does it count for?
60% of G1 Computing K127, with 90 raw marks.
Are all seven syllabus modules included?
Paper 2 focuses on Modules 4–7: Document Processing, Spreadsheets, Media Software and Programming. Paper 1 covers all seven modules.
Is the programming task advanced Python?
The stated G1 syllabus emphasises visual programming concepts such as sprites, variables, events, conditions, loops and debugging. Prepare for the actual approved software and scope.
Are students allowed to use calculators?
The official K127 syllabus permits an approved calculator in Paper 1 and Paper 2.
Are specific software programs guaranteed?
The examination centre provides approved software. Follow current SEAB and school instructions rather than assume every personal app is acceptable.
What happens if the student forgets to save?
The syllabus explicitly requires softcopy submission and includes saving time in the two-hour paper. A missing or incorrect file can prevent the work from being assessed as intended. Treat saving as a core examination skill.
Can students prepare only by watching tutorials?
Tutorials can teach features, but practical competence must be demonstrated by independently creating, testing, saving and retrieving the required output from a changed brief.
Is Paper 2 offered for private candidates?
The official 2027 G1 private-candidate syllabus directory also lists Computing K127, but private candidates must check their own eligibility, approved software and examination arrangements separately. Do not assume the school-candidate process applies unchanged.
The final readiness exercise
Give the learner an original brief requiring one formatted two-page document, one spreadsheet with formulas and a chart, one media output and one short visual program. The learner must interpret the instructions, create the artefacts independently, test them, and identify each file ready for submission.
After the first attempt, change the quantities, document layout and programming condition. A learner who can adapt and still submit valid work has demonstrated more than memorised button presses.
That is the practical standard this guide encourages: interpret accurately, build correctly, verify honestly and save reliably.
For the complete subject overview, read How G1 Computing Works | SEC Examination Preparation. For digital Science examination comparison see How G1 Science Paper 1 Works | SEC Examination Preparation. For the diagnosis–repair–independent-performance teaching approach see Secondary 1 Mathematics Tutor Clementi | Small Groups Tutorials.
Official sources and editorial scope
- SEAB — 2027 G1 syllabuses for school candidates.
- SEAB — G1 Computing K127 2027 official syllabus PDF.
- SEAB — 2027 G1 syllabuses for private candidates.
Examination facts were checked against official 2027 syllabus information on 13 November 2026. All datasets, formulas in context, software briefs, games and sample outputs are original educational illustrations, not actual SEC specimen or past-paper tasks. Practice-only timings are not official per-task limits. Current school and SEAB candidate instructions control software, formats, equipment and submission. No grade is guaranteed.