Edexcel IGCSE ICT 4IT1 Home Tutor in Dubai

The case for a visiting tutor in a practical subject looks strong until you watch one. Somebody arrives, sits next to the candidate, and within ten minutes is holding the mouse, because showing is faster than waiting. The hour produces a correct spreadsheet that the adult built and the candidate watched. That is a pleasant lesson and it transfers almost nothing, since the practical paper marks what the candidate can produce alone against a brief and a clock.

The market sells this at roughly AED 180 to 500 an hour with travel inside the rate, as advertised across Dubai in October 2026, and there are in-home tutors who resist the temptation to take over. IB Gram does not offer the format at all: there are no home visits anywhere in the UAE, and home visiting is a service we provide only in India. Saying so in the first section matters, because a page that targets this phrase and then explains itself in a footnote has misled whoever read only the heading.

What replaces it has a specific advantage for 4IT1. The candidate shares their own screen, works in their own installation, and leaves the files in their own folders with the names they gave them. That is the environment their practice between sessions will happen in, so nothing has to be transferred or recreated. The teacher sees the full screen at full size, which is a better view than leaning across a tilted laptop, and can stop the candidate at the click where the brief was misread. The table compares both on the measures that decide practical marks.

The practical component asks a candidate to complete tasks in real software to a stated brief and to produce the evidence of having done so. The examination centre supplies and configures the environment, so there is nothing to install on the day. What the candidate brings is a method, and the method that scores is mechanical: read the brief completely before touching anything, identify every separate instruction in it, carry them out, then check them off against the wording rather than against memory.

Almost nobody does this unprompted. The natural approach is to read the brief once, form a picture of the required output, and build that picture. The picture is usually close and reliably incomplete, because a brief contains instructions that a sensible person would not invent: a specific column width, a particular file format, a heading phrased in exactly those words. Those are the marks that disappear quietly, and the candidate has no sense of having lost them.

The second half of the method is evidence. Work that cannot be seen cannot be credited, so screenshots and saved files are part of the task rather than admin afterwards. Captures taken at the end, from memory, miss steps. Captures cropped to the active window omit the context that proves what was done. Files named generically cannot be matched to the task they answer. Building a fixed routine, capture as you go and name as you capture, takes about two sessions and protects every mark the candidate earned.

Lost practical marks in this subject are remarkably consistent across candidates, which is good news: the faults are known, finite and individually cheap to fix. The commonest by a clear margin is a typed value where a formula was specified. The candidate works out the answer, enters it, and the cell is marked wrong because the question was about building a model rather than about arithmetic. Candidates who do this once usually do it throughout, which makes it a single habit rather than many errors.

Formatting comes second. Currency symbols, decimal places, headings and axis labels are stated in the brief, so they are marked, and they are the instructions most often left at their defaults because the figures are already right. Database structure comes third and costs the most when it goes wrong, because field types chosen loosely mean queries cannot return what the structure cannot hold, and every later task inherits the problem.

Then there are the quieter ones, which add up to more than families expect. Query criteria approximated rather than matched exactly against the wording. Reports left in a default arrangement when sorting and grouping were specified in the brief. Images produced at the wrong dimensions or saved in the wrong file format. Evidence missing, cropped to a single dialogue box, or named in a way nobody else can interpret. The table below pairs each fault with what a single focused session can realistically change, because the useful question for a family with eight weeks left is not what is wrong in general but which one fault to spend the next hour on.

Evidence is the part of 4IT1 that feels like paperwork and behaves like marks. A practical task is credited on what can be seen, so a step completed perfectly and not captured is a step that did not happen as far as the marking is concerned. Candidates understand this in the abstract and forget it under time, because capturing evidence interrupts the flow of doing the task and the task feels like the real work.

The routine that solves it is small and it is the same every time. Finish a discrete step, capture the screen immediately, name the capture so that it identifies the step it belongs to, and only then move on to the next instruction. Captures should show enough of the surrounding context to prove what was actually done rather than being cropped tightly to a single dialogue box. File names should identify the task and the step in words, rather than being sequential numbers that mean nothing at all to a marker working through an unfamiliar folder under time pressure.

Building the habit takes about two sessions and it is best done early, in Year 10, when there is no pressure attached. A candidate who installs it then spends the practical paper thinking about the task rather than remembering to be organised, which is worth more than any single technique. It also carries forward: the applied and vocational computing courses that follow ICT at 16 include assessed units produced over weeks, and in those courses unevidenced work is a far more expensive mistake than it is here.

Spreadsheet work carries a large share of the practical marks and it is the most teachable part of the subject, because the faults are procedural. The first rule a candidate needs is that any cell the brief describes as calculated must contain a formula referring to other cells, not a number. This sounds obvious and is violated constantly, usually by strong candidates who can do the arithmetic in their heads and see no reason to make the spreadsheet do it.

The second rule concerns cell references. A model that works for one row and breaks when copied down has not been built correctly, and briefs often require exactly that copying. Candidates who have never had the difference between a reference that moves and one that is fixed explained properly will produce something that looks right in the first row and is wrong in the rest, which is a single mark in understanding and several in output.

The third area is conditional logic and the presentation that goes with it. Briefs commonly ask for a value that depends on a condition, and then for the result to be formatted in a stated way and charted with stated labels. Candidates get the logic and lose the formatting, or get both and mislabel the chart axes. Working through a brief's formatting requirements as a deliberate final pass, rather than as something done while building, recovers those marks reliably and takes a few minutes.

Database tasks punish loose thinking earlier than any other part of the paper, because everything downstream depends on the structure. If a field meant to hold a date is set as text, sorting breaks and date-range queries cannot work. If a field meant to hold a number is set as text, numeric criteria fail. Candidates who set everything loosely and expect to sort it out later find they cannot, because the query simply cannot return what the structure does not support.

Queries are the second gate and the fault there is approximation. A brief states criteria precisely, including ranges, exclusions and whether conditions combine. Candidates read the criteria, form a general sense of which records are wanted, and build a query that returns roughly those. Roughly is not a mark. The practice that fixes it is translation: write the stated criteria out as explicit conditions on paper first, then build the query from the written conditions rather than from the impression.

Reports are the third, and the losses there are almost entirely skipped instructions. A brief will specify which fields appear, how records are sorted, and sometimes how they are grouped. A default report containing the right data but in the wrong order misses those marks completely. For Dubai families there is also a practical constraint worth naming: the database package schools most often teach runs on Windows and has no macOS version, so a Mac-only household cannot practise this task area at home. Where that applies, the session plan should weight database work more heavily, and we will say so rather than pretend otherwise.

The written component of 4IT1 is where knowledgeable candidates underperform most visibly. Questions are set inside a scenario about a specific organisation, and the mark scheme credits answers that address that organisation. A candidate who writes an accurate textbook description of the technology has demonstrated knowledge and not answered the question, which feels unfair until you read the question stem again and notice it asked why the technology suits this particular situation.

There are a handful of recurring stems and each has a required answer shape. Why does this device suit this task wants a property of the device linked to the task. Describe a risk to the organisation's data wants a named threat with its mechanism. Explain how this measure reduces that risk wants the link between the safeguard and the threat already named. State an environmental impact wants a consequence attributed to a cause. Give an advantage and a disadvantage for the business wants both tied to the business in the question.

Learning those shapes is quick and it transfers across every topic in the written paper, which makes it the highest-return work available anywhere in the theory half of the course. The method is mechanical rather than clever: write an answer, mark it against the published criteria, identify the required element that is absent from it, and rewrite the answer, then repeat the cycle on a different topic until the shape becomes automatic under time. The table below sets out the stems that recur most often against what candidates tend to write instead of them.

No competitor page found in this market discloses a coverage limit, and several conceal non-UAE delivery behind a phone number. The position here is published instead, because a family that is told a specialist is available and then handed a generalist loses weeks discovering it. ICT specialists are fewer in number than maths or science teachers, and within ICT the database task area is the narrowest capability of all. That is the real constraint on matching, and it tightens sharply before a Pearson series.

What that means practically: outside the weeks immediately before a series, a match for written technique is usually quick and a match for practical work takes a little longer. In the eight weeks before a window, specialists book out first and the wait can exceed a fortnight. The honest options at that point are a waiting slot, a diagnostic only, or being told to look elsewhere. Substituting someone who can cover the theory but cannot supervise practical work is not one of them.

There is also a category of question that is not ours to answer. Where a private candidate needs a centre able to run the practical component, that is a matter for the centres themselves, and we will point you at them rather than acting as an intermediary. IB Gram does not perform, arrange or guarantee any examination entry, equivalency or attestation process. The table states coverage, match times and fallbacks so the position is visible before any payment rather than after.