How to survive G1 Computing? | e-Exam, Spreadsheets, Media and Scratch Lab Skills

To survive G1 Computing, learn to make digital work that someone else can open, understand and use. A spreadsheet should calculate the right result when data changes. A document should follow its format. A graphic should communicate a message, and a Scratch program should work on more than one lucky run. The new 2027 Singapore–Cambridge SEC G1 Computing syllabus, K127, places 40% on a 75-minute electronic theory-and-application paper and 60% on a two-hour practical laboratory examination. Make both knowledge and hands-on confidence part of the weekly study plan.

G1 Computing is a real 2027 SEC subject, not a description of a student’s future or intelligence. It introduces transferable digital skills used in administration, logistics, design, retail, data handling, creative media, technical support and many other sectors. Digital literacy can complement almost any course or career, but choosing this subject alone neither guarantees a specific qualification nor replaces programme entry requirements. Keep the entire subject combination and official post-secondary rules in view.

The official 2027 K127 G1 Computing syllabus sets out seven modules and exact assessment objectives. The SEAB G1 directory identifies Computing as new in 2027. Check the student’s school offering and registered examination year before preparing materials; a national syllabus does not mean every school offers the subject. This guide provides independent examples rather than specimen questions or access to a real examination environment.

Your ten-minute start: check the task, not just the software

Confirm the subject name, G1 level and K127 code for the student’s examination year.
Open one recent school task and identify exactly what finished file the instructions require.
Test a basic spreadsheet formula and change an input; check whether the output updates correctly.
Make one small Scratch interaction and test at least three different input conditions.
Practise saving, reopening and confirming the correct version of a file before calling the task complete.

The 2027 K127 examination map

Paper	Actual format	Time, marks and weighting
Paper 1: electronic examination	20 multiple-choice questions for 20 marks, plus short structured responses for 40 marks; concepts from all seven modules	1 hour 15 minutes; 60 raw marks; 40%
Paper 2: computer laboratory examination	Three task groups: media software about 30 marks, document processing and spreadsheets about 35 marks, programming about 25 marks	2 hours; 90 raw marks; 60%
Paper 2 submission	Candidates save required digital work as softcopies; time for saving is inside the examination	Use the approved software and official examination instructions

The seven modules are computing fundamentals, networking, impact of computing, document processing, spreadsheets, media software and programming. In Paper 2, the emphasis is on Modules 4–7 because the candidate must make usable files and computational artefacts. Paper 1 still asks candidates to reason about the whole subject. A student who only enjoys playing with Scratch while ignoring document and spreadsheet tasks risks losing many practical marks.

The core habit: input, process, output, test

Almost every digital task begins with input, processing and output. The input might be prices typed into a spreadsheet, instructions entered in a game, text pasted into a document or images placed into a video timeline. The software applies rules and produces an output. The student then checks whether that output matches the actual brief.

One correct-looking output is not proof that the process works. A spreadsheet may display the right amount for a single row because someone typed the answer manually. When a price changes, the result will not update. A Scratch character may move correctly once but continue beyond the boundary on a later run. Testing changed inputs reveals the difference between appearance and reliability.

1. Understand hardware, memory and storage

Computer fundamentals should not become a memorisation contest about brand names. A processor performs operations, main memory supports active work and secondary storage retains data across sessions. The important distinction is what each component does. Random-access memory is generally volatile; saved documents on suitable non-volatile storage remain available after an ordinary shutdown. These ideas explain why a computer can slow down or lose unsaved changes.

Use a familiar example: a pupil edits a document in an application. The working program uses computing resources while the file must be saved to suitable storage for later retrieval. Ask what happens if the device loses power before saving. This reveals why ‘I finished typing’ and ‘I successfully saved the file’ are not the same claim. Discuss different storage capacities and transfer needs without obsessing over a manufacturer.

For practice, draw a simple device diagram and label one input device, processing role, output device and storage option. Explain one real scenario for each. Then ask the student to compare two machines for a stated task rather than choose whichever has the flashiest advertisement. Reasoning from requirements is a transferable habit.

2. Make file saving part of finishing work

A practical examination judges submitted work, not the effort the examiner imagines happened. A student might create a useful video but save it in the wrong format, use a confusing filename or leave the latest version in an unsaved editor. The K127 Paper 2 time includes saving. Students must build a complete workflow that ends with a valid, accessible output, not simply a screen that looks finished.

Practise with an ordinary folder and teacher-approved naming convention. Create a document, edit it, save, close, reopen and confirm that the correct changes remain. Repeat with a spreadsheet and a Scratch project using the form the approved school software supports. Do not assume that home cloud storage, autosave or external drives are available in the controlled examination environment.

Keep an honest distinction between working and final copies. Check which submission files are actually required, whether linked assets remain available and whether exported media can be opened. A final review can catch a missing file more quickly than a last-minute embellishment catches a formatting weakness.

3. Understand networks without turning into a technician

Networking in G1 Computing includes why computers communicate, what routers and modems do, and how local and wide-area networks differ. Students should understand a client requesting a resource from a server, and the distinction between local storage and cloud services. These ideas explain ordinary experiences such as sending files to classmates or accessing a school application through the internet.

Use a simple drawing of a classroom, a school network and a remotely hosted service. Ask where a document is stored, how a user reaches it and what might happen if the network connection becomes unavailable. A file stored only in one device has different accessibility and backup risks from a copy held in an approved online service. There are benefits and limitations to both.

Practise explaining a technology choice. A school team may need to collaborate on a file, so shared access is useful, but they also need permissions and privacy safeguards. A correct answer should connect a network feature to an actual use, rather than merely define ‘cloud’ as something that is ‘on the internet’.

4. Stay safe and responsible online

The impact-of-computing module includes cyber risks, privacy, malware, data backup and responsible use of copyrighted work. These are everyday capabilities, not separate moral lectures. A convincing fake login message can trick someone even if their spreadsheet skills are excellent. A copied photograph may be technically easy to use but still lack the necessary permission or attribution.

Practise inspecting a fictional message for suspicious urgency, unexpected requests for credentials and links that do not match the apparent sender. Never enter actual passwords into a classroom simulation. Use strong, unique passwords, approved protection and two-factor authentication where supported. Respect the privacy settings of platforms and avoid sharing other people’s personal information in practice files.

A reliable learner can explain why backups matter: accidental deletion, device damage and malicious software can destroy the only copy of important work. Build the habit of saving to approved destinations and checking that a copy can be restored. Real digital competence includes protecting both information and people.

5. Use documents to communicate, not decorate

Document processing asks for precise format decisions: indents, columns, headers, footers, section breaks, page numbering, graphics and linked text boxes. The common difficulty is using repeated spaces and manual line breaks to imitate a layout instead of applying the document’s proper features. That approach falls apart as soon as the text length changes.

Try an invented task: prepare a two-page club information sheet with a title, a list of activities, a graphic and a page number. Use paragraph and page features rather than pressing the space bar repeatedly. If the second page must have a different orientation, learn the actual section-break process in the software the school uses. Compare the finished page with the instructions, not with your personal aesthetic preference.

Before submitting, edit one sentence and see whether the document remains stable. If everything shifts unexpectedly, investigate how the formatting was constructed. The goal is a reusable document structure that accommodates change. That is also valuable for future reports, applications and workplace communications.

6. Understand why styles and layouts matter

Visual consistency helps readers navigate information. A title should look different from a section heading, and a long report should not resemble a wall of identical text. G1 Computing includes the ability to use page settings, graphics and structured elements deliberately. Good design means making the content easier to read, not using every colour and effect available.

Give a student an untidy event notice and a clear specification. Ask them to organise the same content with a heading, sections and an image placed beside the relevant text. Then make one factual change. Does the reader still know the date, venue and action? A document is successful when it preserves meaning as well as appearance.

Ask a classmate to review the file without coaching. If they cannot find the registration deadline, reconsider the information hierarchy. This connects computing with practical English: the software features become tools for clearer communication. The learner should be able to explain each important format decision.

7. Treat spreadsheets as systems of relationships

A spreadsheet is more than a table with colours. It stores data and uses references, formulas and functions to calculate or organise information. A common mistake is typing what the final result should be instead of writing a formula that responds to changed inputs. A robust sheet links the result to the correct cells and recalculates as expected.

Imagine a class fundraising record with units sold in column B and price per unit in column C. The revenue in row 2 should be calculated from the two inputs, for example =B2*C2 in column D. When the units sold change from 4 to 6, D2 should update. If it does not, check whether the learner entered a formula, referenced the correct cells or accidentally formatted a number as text.

Teach the student to identify the intended relationship before clicking a function. Once a simple multiplication works, copy it to additional rows and inspect whether the references change sensibly. Formula literacy improves fastest when calculations are linked to a familiar task and tested through changed data.

8. Master relative and absolute references

Relative cell references change when a formula is copied. Absolute references stay fixed. This distinction is central when a spreadsheet uses a shared parameter, such as a fixed discount rate or tax rate, with many rows of varying figures. Without the correct fixed reference, a copied formula might begin reading an empty cell and produce a wrong result.

Suppose B2 contains a price and F1 contains a percentage applied to all items. A formula such as =B2*(1-$F$1) keeps the percentage reference fixed when copied down the list. The location B2 changes for the next item, while $F$1 remains the same. In a teaching exercise, change the percentage and confirm that every row responds consistently. Explain the mathematics as well as the symbols.

Do not memorise dollar signs without understanding the reason. Ask which information varies from item to item and which information is shared. Then select the cell reference based on that decision. This turns a technical feature into a controlled, logical design.

9. Choose spreadsheet functions by their job

The syllabus includes functions such as SUM, AVERAGE, MEDIAN, MIN, MAX, COUNT, COUNTA, COUNTIF, ROUND, IF, LEFT, MID, RIGHT, LEN and exact-match VLOOKUP. Instead of memorising a function list in isolation, group them by question. Are you adding values, measuring a typical value, counting entries, making a condition-based decision or extracting text?

Consider ten attendance figures. SUM gives the total, AVERAGE gives the arithmetic mean and MAX identifies the largest count. COUNTA counts populated cells, while COUNT focuses on numeric entries. A conditional count might answer how many figures meet a specified criterion. Each result answers a different question, so students should read the task’s meaning before choosing the formula.

Practise one function family at a time and verify it on a dataset small enough to check manually. Then change the data, including a blank and an unexpected entry, to see whether the chosen approach remains appropriate. Understanding the job of a function is more durable than remembering where its menu button sits.

10. Use charts honestly

Charts can clarify data but can also mislead when poorly chosen or labelled. A bar chart compares categories; a line chart often shows a trend; a pie chart divides a meaningful whole into parts. G1 Computing includes creating, customising and interpreting several chart types, including a line-and-column combination chart. The student should understand the audience and question before selecting one.

Imagine a canteen record of meals sold across five days. To compare the days, a column chart may be useful. To show how sales change across time, a line chart might also work. Ensure that the axes, title and units represent the underlying data honestly. A graph without labels may look attractive but leave the reader uncertain about what was measured.

Change one value in the source table and check that the chart updates. If it does not, inspect the selected range or whether the chart was copied as a static image. The check demonstrates that the visualisation is linked to the data, not merely a decoration.

11. Validate and filter data rather than trust every input

Data validation places sensible limits on what a user enters. If a column is meant to contain a number between one and ten, allowing a value of two hundred without warning may distort a report. The syllabus includes setting validation criteria and custom error messages. It also covers sorting and filtering using specified comparisons. These tools help users work with information more reliably.

Design a practice class activity log with date, activity and participant count. Ask the learner to set a suitable rule for the count, then enter a value that should be rejected. Can the error message explain the problem clearly? Afterward, filter the table to see only activities above a particular participant count and check whether every visible row meets the condition.

Explain why data quality matters in real workplaces. Inventory, bookings and invoices can all be affected by mistaken entries. A computing student who notices a logical error before making a graph is practising an important form of responsibility.

12. Media software begins with a message

The media module includes vector and raster graphics, presentations and video. A learner can spend hours experimenting with effects while producing a message that is hard to understand. Begin with the audience and purpose. Is the task to teach a safety rule, promote a school event or explain a process? Choose suitable media elements only after that decision.

For an invented health-themed poster, a headline might communicate a handwashing reminder, supported by simple illustrations and short readable instructions. Avoid filling every empty area with icons. White space, clear contrast and a logical sequence make the material easier to use. The student should be able to explain why each visual element belongs.

When reviewing, show the design to someone who has not seen the brief. Ask what the main message is and what action they would take. If they misunderstand, improve the layout or wording instead of adding another animation. Effective media is communication, not a catalogue of features.

13. Know when vector and raster graphics differ

Vector drawings are constructed from paths and shapes, making them suitable for artwork that may need to scale without the same pixelation as a raster image. Raster images contain coloured pixels and may lose clarity when enlarged excessively. G1 Computing asks students to recognise and manipulate both. The important decision is choosing a form suitable for the task and output.

Create a simple sign icon using vector shapes. Resize it and see how the edges behave. Compare this with enlarging a small photograph beyond its useful resolution. Ask which format is more appropriate for an adjustable logo and which for a realistic image of an actual place. The answer should cite structure and purpose, not a slogan that one format is always superior.

Practise placing, grouping and aligning objects, then checking whether an export preserves the required design. Always use assets you have rights to use. Copyright awareness and technical skill belong together; software convenience does not automatically provide permission.

14. Make presentations and videos from storyboards

A storyboard forces the creator to decide what the audience needs to see and in what order. A clear three-scene message may be more effective than a ten-scene video full of transitions. G1 Computing includes producing presentations from storyboards and creating videos from still images, clips, text and sound. Think about sequence before opening the editor.

Try an original thirty-second video explaining how to sort classroom recycling. Scene one introduces the materials; scene two shows the sorting decision; scene three summarises the rule. Check that text can be read in the available time and that sound does not drown out essential information. The aim is an understandable message, not professional film production.

Review the finished media on the device and at the size likely to be used. A tiny subtitle may look fine in the editor but become unreadable in a presentation. Save the requested editable and exported files where instructed, and verify that the final product plays without missing components.

15. Begin Scratch with sequence before complexity

Scratch is a visual programming environment, but blocks still follow logic. Students should understand sequences, events, variables, conditions and loops. A simple game with clear rules is better preparation than copying a complicated project whose scripts the learner cannot explain. Begin with one sprite, one event and one observable result.

For example, a character might move right when the right-arrow key is pressed. Ask what happens after one press, then after five. Add a condition that checks a meaningful boundary rather than letting the character disappear off the stage. Students should trace which blocks run and why, not merely drag instructions until something appears to work.

Once the basic behaviour is reliable, introduce a changing variable such as score. Explain when the value starts at zero, when it increases and when the display updates. A variable is not magic storage; its value changes only as directed by program logic.

16. An original Scratch bug: score resets inside a loop

Imagine a small game in which the player earns one point each time a sprite touches a star. The intended process is to start a new game at zero, detect a valid contact and increase the score by one. A common bug puts ‘set score to zero’ inside a repeated checking loop. Each time the loop runs, the score returns to zero, so previously earned points are lost.

Trace the instructions rather than guessing. At game start, set score to 0. Inside the repeat-or-forever checking logic, use an appropriate condition for contact and change score by 1 when a new valid hit is registered. Prevent the same continuous contact from being counted repeatedly—for example, by separating the objects or waiting until contact ends. The exact Scratch block arrangement depends on the game design.

Test with zero hits, one hit and several separate hits. A correct output after the first hit does not prove that later hits accumulate correctly. The key debugging habit is identifying which instruction alters a variable and when it runs. This reasoning transfers to counters, timers and interactive media systems.

17. Test conditions and boundaries, not just the happy path

A good program should behave sensibly when a user does something unexpected. In Scratch, test a sprite near the edge of the stage, a repeated keypress, an empty response to an input prompt and the point where a game should stop. The objective is not to create the most sophisticated game; it is to show that the specified rules work in realistic circumstances.

Build a tiny test table with columns for input, expected behaviour, observed behaviour and correction. If pressing a key twice causes the sprite to cross a forbidden area, record that rather than claiming success because the first press was fine. Introduce a condition or change the movement rule, then repeat exactly the test that failed.

After repairing one example, change the starting position and test again. Debugging by evidence is more efficient than randomly deleting blocks. It is also the habit used in more advanced computing careers: a solution becomes trustworthy through repeatable checks.

18. Practise logical flowcharts before programming

Flowcharts and simple diagrams help students understand an algorithm without wrestling with the software interface. Draw a decision for a quiz game: show a question, collect an answer, check correctness, update score, then continue or finish. The path for a correct answer differs from the path for an incorrect answer. Ask the learner to trace both.

Use words such as sequence, condition and loop accurately. A sequence executes in order. A condition selects behaviour based on whether a statement is true. A loop repeats, sometimes until a condition changes. Give two sample inputs and ask which blocks execute. If the student cannot predict the program, the logic needs clarification before additional graphics are added.

Transfer the flowchart to Scratch in small stages. Confirm one stage before adding the next. If a game behaves unexpectedly, return to the diagram and ask where actual behaviour departed from the intended steps. This creates a bridge between abstract reasoning and a visible result.

19. Understand the lab-paper clock

Paper 2 lasts two hours and covers three task groups. Candidates must perform actual software operations and save the required files within the allocated time. It is unwise to spend nearly the whole examination making an exquisite picture and then rush the spreadsheet and program. A rehearsal should reveal how long the learner needs for setup, each task, checking and final submission.

Students can practise a personal sequence using school guidance: read all instructions first, identify necessary output files, do a quick saving check, complete tasks with checkpoints, and reserve time for reopening or verifying the submitted work. There is no universal minute allocation, because one candidate may be stronger in programming and another in graphics. Record realistic times from several practice sessions.

Paper 1 likewise deserves its own pacing practice: twenty multiple-choice questions plus structured responses in seventy-five minutes. Students should not let one unfamiliar networking detail consume time needed for later reasoning questions. Timed practice is most productive after concepts are understood.

20. A six-week G1 Computing improvement plan

In Week 1, attempt a small baseline spanning a document task, a spreadsheet formula, a basic media design and a Scratch behaviour test. Record the first failure in each. Week 2 repairs the most fundamental issue—perhaps file handling, cell references or recognising an event in Scratch. Use a worked demonstration followed by a fresh attempt without prompts.

Week 3 combines skills within a practical brief, such as preparing a club report containing a chart generated from spreadsheet data. Week 4 introduces an unfamiliar dataset or game rule to test transfer. Week 5 adds timed practical trials and checks whether files are named, saved and reopened correctly. Week 6 repeats a comparable baseline with different content and uses the evidence to plan the next month.

The target is not an overnight grade jump. Useful progress might be fewer broken formulas, better structured documents, a program that handles edge cases or a faster, more reliable submission routine. If the pattern does not improve, adjust the diagnosis rather than adding hours without purpose.

21. Prepare for Secondary 1 through Secondary 4

In Secondary 1, build foundational digital confidence: organise files, understand input and output, create simple documents and learn respectful technology use. In Secondary 2, progress to spreadsheet relationships, structured media and basic programming logic where the school programme allows. Students should practise describing their reasoning, not merely clicking familiar buttons.

In Secondary 3, connect the seven syllabus modules with purposeful tasks. Use small assignments that combine information, formulas and communication. Introduce systematic testing for Scratch and a clearer routine for saving work. In Secondary 4, rehearse the correct K127 examination formats and use fresh practical tasks to stabilise execution speed, accuracy and confidence under time pressure.

These are broad priorities, not a mandated yearly scheme. A school may teach the topics in another order, and students may enter the examined course at different points. Ask teachers how their actual sequence maps to the student’s subject level and registered exam year.

22. What G1 Computing can mean for further study

Computing builds competencies in data handling, digital administration, technical support, automation concepts, multimedia and structured problem solving. These are relevant across ITE and other possible education routes, but entry decisions depend on the complete student profile and programme rules. The SEC displays attained subjects at their levels; the way subjects are counted for particular admissions calculations must be checked separately.

SEAB’s SEC grade-mapping explanation includes a specific example in which a G1 Computing grade is not mapped for the ELMAB3 calculation. Families should not assume that taking this elective substitutes for English, mathematics or other required subjects in an admission score. From 2028, the new post-secondary admissions exercise will affect relevant cohorts, so consult current MOE and institution guidance when making actual applications.

Career curiosity makes practice more interesting. A student who enjoys graphics may investigate design-related courses; a spreadsheet enthusiast may explore operations and administration; a game-building pupil may become curious about coding. These are avenues for exploration, not guarantees about individual job eligibility.

23. Avoid copying solutions without understanding

Tutorial videos and ready-made Scratch projects can be helpful demonstrations, but a student does not gain reliable skills by following clicks without understanding. Ask them to explain why each instruction was needed and to make one controlled change. If they cannot, reduce the project to a simpler example and rebuild from first principles.

Where assignments are assessed, follow the school’s rules on originality, collaboration and permitted digital assistance. Do not submit another person’s work as one’s own or claim an AI-generated product represents independent performance if the rules do not allow it. Practising with assistance is different from misrepresenting work.

A strong routine alternates model, practice and transfer. Show one formula, ask the learner to use it on a different table and then make them explain how they checked it. Show a Scratch condition, change the game goal and let the learner adapt the logic. The improvement should remain when the model is closed.

24. Decide when a tutor or extra course adds value

Not every G1 Computing learner needs tuition. Begin with school support, available practice software and a clear list of missed tasks. If the student struggles with fundamental spreadsheet references or computational logic, a targeted tutorial may help. If the primary obstacle is unfamiliarity with the school’s software, a short supervised familiarisation session could be more relevant than months of general programming classes.

Ask a tutor to demonstrate how they diagnose a bug, how they build test cases, and how they help the student work independently. A course that teaches an unrelated advanced programming language while ignoring K127 documents, media and spreadsheets may be interesting but poorly aligned with the immediate learning need. Examine the actual syllabus and the learner’s timetable.

Support should preserve agency. The adult explains the underlying idea and checks the next attempt, while the student creates and tests the file. Review progress after several weeks with a genuinely new task. Greater independence and reliable completion are more important than a growing folder of completed tutorial projects.

G1 Computing: short questions with direct answers

Is G1 Computing new in 2027?

Yes. SEAB identifies K127 as a new G1 Computing syllabus for the 2027 SEC. Check the school’s actual offering before making a subject-choice assumption.

Does G1 Computing only involve programming?

No. It includes seven modules from computer fundamentals and networking to documents, spreadsheets, media and programming. The practical paper gives substantial attention to non-programming tasks.

What is the Paper 1 format?

A 75-minute electronic exam worth 40%, with twenty multiple-choice questions and short structured questions covering all seven modules.

What is the Paper 2 format?

A two-hour lab exam worth 60%, with media, document/spreadsheet and programming tasks, and required digital files to save within the time.

Will any editing app be acceptable in the examination?

Do not assume so. Use software approved by SEAB and the examination centre and follow the school’s specific familiarisation instructions.

What is the most important spreadsheet habit?

Make results depend on formulas linked to the correct cells and test by changing inputs. A manually typed correct answer may not survive a changed dataset.

Is one successful Scratch run enough?

No. Test different inputs, boundaries and repeated actions. Use a small test log to distinguish accidental success from reliable logic.

Does G1 Computing automatically count in ELMAB3?

No such automatic assumption is justified. SEAB’s published SEC example shows G1 Computing not mapped in the ELMAB3 calculation; verify the applicable scoring rules for each actual pathway.

What should parents check before buying equipment?

Ask the school which software and devices are supported. Expensive hardware is not a substitute for understanding, and examination access is controlled by the centre.

Can students benefit from this subject without becoming programmers?

Yes. Information organisation, digital communication, data handling and careful testing are valuable in many technical, creative and administrative settings.

Official sources and eduKateSG learning connections

Families who want a learning-needs discussion can arrange a parent–student consultation with eduKate Singapore. The right next step depends on actual work and may be school guidance, independent practice or targeted teaching.

Independent October 2026 guide based on the official SEAB 2027 K127 specification. Software examples are educational illustrations, not official practical tasks. Check the current paper, approved applications, examination-centre instructions and admissions requirements for the actual cohort.