Keep the education and employment chronologies distinct and accurate. The experience requirement needs evidence of actual relevant work, not an assumption based on time since enrolment.
Record dates, duties and supporting sources
Provide programme records and employment or engagement evidence showing when work occurred and what was performed. Identify overlap without counting simultaneous projects as additional calendar years. Ask the reviewer how the actual qualification alternative applies. Do not modify dates or claim every technology task as systems-analysis experience merely to reach a total.
Hypothetical example: a warehouse-automation consultant completed a part-time data course while working two concurrent contracts for a retail integrator. Build a month-by-month chronology that shows the programme dates, each contract, hours where available, and specific analytical outputs. The point is not to maximize a tally by counting overlapping work twice; it is to show reliable evidence for the experience being claimed. Useful records include signed contracts, payroll, tax records, client letters, deliverables, and contemporaneous project descriptions. Ask each former supervisor to state what the person did, not just that the person was employed. If a letter is written long after the fact, compare it with records created during the engagement. Start with the education record, then assemble employment proof, then prepare the employer’s description of the proposed duties. Inconsistencies in dates, job title, or location should be addressed directly. An unsupported statement that every technical task was analytical can damage credibility more than a narrower, accurately documented claim.