Compliance SPHF-HRD-035
Validation Checks by Instafill.ai
1
Position Applied and Department are present and not placeholder text
Validates that both the Job Title (Position Applied) and Department fields are completed with meaningful values (not blank, not 'N/A', not generic text like 'see CV'). This is important because routing and eligibility screening depend on the exact position and department. If validation fails, the submission should be rejected or returned to the applicant to complete these fields before processing.
2
English name fields contain valid characters and are not swapped
Checks that Surname (English) and Given Name(s) (English) are populated and contain only expected characters (letters, spaces, hyphens, apostrophes) and do not include numbers or symbols. Also flags likely swaps (e.g., surname field containing multiple given names while given-name field contains a single family name) using simple heuristics. If validation fails, the system should prompt the applicant to correct the name fields to match official documents to avoid payroll/ID mismatches.
3
Chinese name format validation (if provided)
Validates that Name in Chinese, when entered, contains Chinese characters and is not entered in English/romanization. This helps ensure the field is usable for local HR records and identity matching. If validation fails, the system should request correction or allow the applicant to leave it blank if not applicable, depending on policy.
4
HKID / Passport number format and exclusivity check
Validates that the HKID/Passport field matches an acceptable pattern: HKID typically like 'A123456(7)' (with optional parentheses) or a passport number pattern (alphanumeric, length constraints). It should also prevent obviously invalid values (too short, all zeros, or containing disallowed characters). If validation fails, the submission should be blocked because identity verification and background checks rely on a valid identifier.
5
Date of Birth is a valid date and indicates plausible age
Ensures Date of Birth is a real calendar date in the required dd/mm/yyyy format and is not in the future. Adds a plausibility rule (e.g., applicant age between 14 and 80) to catch data entry errors like wrong year. If validation fails, the system should request correction because DOB is used for identity checks and employment eligibility.
6
Daytime contact number format and reachability constraints
Checks that the Daytime Contact No. contains only digits plus optional leading '+' and separators, and meets minimum/maximum length rules (e.g., 8 digits for HK local numbers, or 8–15 digits internationally). This is important to ensure HR can contact the applicant for interviews and clarifications. If validation fails, the system should prompt for a corrected phone number and prevent submission if phone is required.
7
Email address format validation and normalization
Validates that the E-mail Address follows standard email syntax (local@domain), has a valid domain structure, and does not contain spaces or invalid characters. Optionally normalizes case and trims whitespace to reduce bounce risk. If validation fails, the applicant should be asked to correct the email because it is the primary channel for recruitment communications.
8
Correspondence address completeness check
Ensures the Correspondence Address is not empty and contains sufficient detail (e.g., at least a minimum character count and multiple components such as street/building and city/region). This matters for sending written offers, contract documents, or verification letters. If validation fails, the system should request a more complete address or require structured address fields if available.
9
Academic attainment rows: date component validity and allowed 'Present' usage
Validates that each Academic Attainment row uses valid months (01–12) and valid years (two- or four-digit per system rules), and that 'Present' is only allowed in the 'To' fields (not 'From'). It also checks that if any field in a row is filled, the institution and qualification fields are also provided to make the entry meaningful. If validation fails, the system should highlight the specific row and require correction to maintain consistent education history.
10
Academic attainment chronology and non-overlap consistency
Checks that within each Academic Attainment row, the 'From' date is not after the 'To' date (unless 'To' is blank/Present), and that the overall list is in chronological order as requested by the form. Optionally flags overlapping study periods that are likely accidental (while allowing legitimate overlaps if explicitly confirmed). If validation fails, the system should request reordering or date correction to avoid misinterpretation during screening.
11
FT/PT field validation for education and work entries
Validates that FT/PT fields accept only allowed values (e.g., 'FT', 'PT', 'Full-time', 'Part-time') and rejects ambiguous entries. This is important for assessing workload and experience equivalency. If validation fails, the system should prompt the applicant to select a valid option from a controlled list.
12
Professional qualifications: year range and issuer/qualification completeness
Ensures each Professional Qualification row has a valid year (not in the future and not unreasonably old, e.g., earlier than 1900) and that Issuing Authority and Qualification title are present when a row is used. This prevents incomplete credentials that cannot be verified. If validation fails, the system should require missing details or remove the partial row before submission.
13
Work experience rows: date validity, ordering, and required fields per used row
Validates that work experience months are 01–12 (or 'Present' only in 'To' fields where allowed), years are valid, and 'From' is not after 'To'. For any row with dates entered, Organization/Company and Position must be present, and Reason for Leaving should be required when an end date is provided. If validation fails, the system should block submission or request row-level corrections to ensure the employment history is interpretable.
14
Expected salary is numeric HK$ and within reasonable bounds
Checks that Expected Salary is a numeric value (no currency symbols beyond optional 'HK$' prefix, no text like 'negotiable' unless explicitly allowed) and falls within configured bounds (e.g., >0 and below a high ceiling to catch extra zeros). This is important for compensation screening and budgeting. If validation fails, the system should request a corrected numeric amount or provide an allowed 'Negotiable' option if policy permits.
15
Date of availability format and logical relation to signature date
Validates Date of Availability is a real date in dd/mm/yyyy format and is not unreasonably far in the past. Also checks it is on/after the Signature Date (or at least not earlier than the application signing date) unless the applicant indicates immediate availability. If validation fails, the system should prompt for correction because start-date planning depends on accurate availability.
16
Vacancy source selection consistency (Online Recruitment/Others require specification)
Ensures at least one 'How did you learn of this vacancy?' checkbox is selected, and if 'Online Recruitment' is selected then the site name/URL is provided; if 'Others' is selected then the 'specify source' field is provided. This is important for recruitment channel tracking and compliance reporting. If validation fails, the system should request the missing selection or required details before accepting the form.
17
Declaration fields: mutually exclusive Yes/No selections and conditional details
Validates that for 'Previously employed by St. Paul’s Hospital' exactly one of Yes/No is selected, and if Yes is selected then Position and From/To dates are completed with valid dates. Also validates that for the criminal conviction declaration exactly one of 'have' or 'have not' is selected (including preventing both English/Chinese duplicates being checked inconsistently). If validation fails, the system should block submission because these declarations affect eligibility checks and downstream HR actions.
18
Signature and signature date presence and date validity
Ensures the Signature field is present (typed name, digital signature, or captured signature per system design) and the Signature Date is a valid dd/mm/yyyy date not in the future. This is important because the declaration statements require applicant attestation and may be legally relied upon. If validation fails, the system should not accept the application as complete and should request the missing/invalid attestation.