Documentation Clerk PSD 26-068 / 114430
M1 Support Services · Columbus, MS · 1 mo ago
Management$30.28/hrFull-time
We need to output HTML fragment with sections: Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Job title: Documentation Clerk (already shown, not repeat). Location: Columbus, MS. Job Posting No 114430. Start Date TBD (should not include as heading if TBD). Contract AETC Acft. Mx. Support Svc. Salary Range $30.28/hr (Pay). Posting Date 09/08/2026 (metadata). Union Yes. FLSA Status Non-Exempt. Shift Work Possible FT/PT Full-time. Relocation Possible. Travel Possible.
Job Summary: M1 is looking for a Documentation Clerk Primary responsibilities include but are not limited to the following: then list of responsibilities.
We need sections: About the role (maybe job summary). Responsibilities (list). Qualifications And Experience (list). Skills? Could be derived from qualifications: proficiency in computer use, Microsoft Office, data entry, typing speed, English, communication, reading technical data. Could be separate Skills section. Benefits: they mention comprehensive benefits package including medical, dental, vision, life, dependent life, AD&D, short- and long-term disability, flexible spending accounts, free Employee Assistance Program. That's specific. So Benefits section.
Pay: Salary Range $30.28/hr (specific). So Pay section.
Schedule: Shift Work Possible FT/PT Full-time. Also mention may be required to work day shift, night shift, or weekend duty as required. So we have schedule info. So Schedule section.
We should not include headings with filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO statements, equal opportunity, etc. Also remove navigation, cookie, legal, application instructions (the line about outside bar and apply button). Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content.
Job Summary: "M1 is looking for a Documentation Clerk Primary responsibilities include but are not limited to the following:" Actually the sentence seems truncated. We'll treat as About the role: M1 is looking for a Documentation Clerk. Could also include location? Not needed.
Responsibilities: list bullet points after "Primary responsibilities include but are not limited to the following:" then many items separated by periods. We'll need to split into list items.
Let's list responsibilities:
- Maintains all equipment historical maintenance records IAW AETCI and AFI directives.
- Maintains the Integrated Maintenance Data System (IMDS) data base.
- Upon completion of equipment inspections, verifies all documents are present and complete.
- Responsible for entering data correctly into appropriate data base system, including IMDS, MMS, MSAT, or other applicable systems.
- Ensures proper documentation of TCTOs, maintains the resulting documentation and reports status.
- Prepares and distributes AF Forms 2005 (Issue/Turn-In Receipt).
- Submits AFTO Forms 223 (Time Change Requirements Forecast).
- Inputs time change item work orders in IMDS.
- Manages and controls the Time Compliance Technical Orders (TCTO), inspections, and time change IAW -6 requirements into IMDS.
- Manages the Job Master Listing (JML).
- Manages locally directed, one-time special inspections, and J-coded inspections or modifications for documentation purposes.
- Maintains and files aircraft/engine records.
- Responsible for inputting and maintaining all 00-25-107 requirements.
- Prepares all job flow packages and schedules jobs into IMDS.
- Attends pre-dock and post-dock meetings.
- May be required to rotate and be knowledgeable of all MDS aircraft/engines assigned.
- Complies with all AFI and AETCI publications related to assigned section.
- Ensures all forms are complete and filed on aircraft/engines.
- Processes all suspense files related to aircraft/engines.
- Performs duties as listed in TO directives for PS&D, Engine Management (EM), and Consolidated Engine Management Section (CEMS), as assigned.
- Within CEMS, updates engine scheduling boards, monitors, and updates engine status in the CEMS and ensures all time change, Low Cycle Fatigue Cycle (LCFC), and TCTOs are accomplished on completed engines.
- Practices good housekeeping and safety at all times.
- Performs tasks with minimum supervision.
- May be assigned to maintain AF publications and TO files.
- May be assigned additional duties, to include Building Custodian.
- Shall assist other personnel and work centers as directed.
- Must promote Company values, policies, and standards of conduct.
- Must be customer oriented and ensure professional coordination with Operations and other base agencies.
- Shall perform other duties assigned to include TDY and travel.
- Must be able to work day shift, night shift, or weekend duty as required.
- Receives cross-utilization training (CUT) and is qualified to perform those administrative tasks.
That's a lot; we can keep them as list items.
Qualifications And Experience: list:
- Two years recent experience in CEMS/PS&D, as applicable.
- High school diploma or the equivalent is required.
- Must be proficient in computer use and proficien in Microsoft Office programs, to include Excel and other applicable programs.
- Must be proficient in data entry.
- Formal courses in Microsoft Office programs are desired.
- Must have experience and be proficient in Files/Records Management.
- Must have experience in tracking and inventory methods and maintaining status.
- Must be able to type at a rate of 40 words per minute.
- Must be able to read, write, speak, and understand English.
- Must have good communication skills and the ability to read and interpret technical data.
Also "Working Conditions . Physical exertion requirement is medium". Could be part of Qualifications or maybe a separate section? Not in headings list. Could be included under Requirements? But we have no specific heading for Working Conditions. Could put under Requirements? Not defined. Probably we can include as part of Qualifications or maybe as a separate section "Requirements". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Requirements section for things like physical exertion, maybe also shift work? But shift work is schedule. We'll treat physical exertion as Requirements.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Skills: we can extract from qualifications: proficiency in computer use, Microsoft Office, data entry, typing 40 wpm, English, communication, reading technical data. Could be separate Skills.
But we might combine some. However we need to avoid thin sections. Let's decide:
- About the role: short paragraph.
- Responsibilities: big list.
- Requirements: physical exertion medium (maybe also other requirements like must be able to work day/night/weekend? That's schedule though). We'll keep physical exertion.
- Qualifications: education, experience, proficiency in computer use, data entry, files/records management, tracking/inventory, typing speed, language, communication, technical data interpretation.
- Skills: maybe Microsoft Office proficiency, data entry, typing, communication, etc. But that overlaps with qualifications. Could combine qualifications and skills? But we need to follow instruction: use headings when posting has real specific content. We have both qualifications and skills content. We'll keep both.
- Benefits: list of benefits.
- Pay: salary range.
- Schedule: shift work possible, full-time, may require day/night/weekend duty.
Now we need to output HTML fragment only, no markdown.
We'll produce:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Job title: Documentation Clerk (already shown, not repeat). Location: Columbus, MS. Job Posting No 114430. Start Date TBD (should not include as heading if TBD). Contract AETC Acft. Mx. Support Svc. Salary Range $30.28/hr (Pay). Posting Date 09/08/2026 (metadata). Union Yes. FLSA Status Non-Exempt. Shift Work Possible FT/PT Full-time. Relocation Possible. Travel Possible.
Job Summary: M1 is looking for a Documentation Clerk Primary responsibilities include but are not limited to the following: then list of responsibilities.
We need sections: About the role (maybe job summary). Responsibilities (list). Qualifications And Experience (list). Skills? Could be derived from qualifications: proficiency in computer use, Microsoft Office, data entry, typing speed, English, communication, reading technical data. Could be separate Skills section. Benefits: they mention comprehensive benefits package including medical, dental, vision, life, dependent life, AD&D, short- and long-term disability, flexible spending accounts, free Employee Assistance Program. That's specific. So Benefits section.
Pay: Salary Range $30.28/hr (specific). So Pay section.
Schedule: Shift Work Possible FT/PT Full-time. Also mention may be required to work day shift, night shift, or weekend duty as required. So we have schedule info. So Schedule section.
We should not include headings with filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO statements, equal opportunity, etc. Also remove navigation, cookie, legal, application instructions (the line about outside bar and apply button). Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content.
Job Summary: "M1 is looking for a Documentation Clerk Primary responsibilities include but are not limited to the following:" Actually the sentence seems truncated. We'll treat as About the role: M1 is looking for a Documentation Clerk. Could also include location? Not needed.
Responsibilities: list bullet points after "Primary responsibilities include but are not limited to the following:" then many items separated by periods. We'll need to split into list items.
Let's list responsibilities:
- Maintains all equipment historical maintenance records IAW AETCI and AFI directives.
- Maintains the Integrated Maintenance Data System (IMDS) data base.
- Upon completion of equipment inspections, verifies all documents are present and complete.
- Responsible for entering data correctly into appropriate data base system, including IMDS, MMS, MSAT, or other applicable systems.
- Ensures proper documentation of TCTOs, maintains the resulting documentation and reports status.
- Prepares and distributes AF Forms 2005 (Issue/Turn-In Receipt).
- Submits AFTO Forms 223 (Time Change Requirements Forecast).
- Inputs time change item work orders in IMDS.
- Manages and controls the Time Compliance Technical Orders (TCTO), inspections, and time change IAW -6 requirements into IMDS.
- Manages the Job Master Listing (JML).
- Manages locally directed, one-time special inspections, and J-coded inspections or modifications for documentation purposes.
- Maintains and files aircraft/engine records.
- Responsible for inputting and maintaining all 00-25-107 requirements.
- Prepares all job flow packages and schedules jobs into IMDS.
- Attends pre-dock and post-dock meetings.
- May be required to rotate and be knowledgeable of all MDS aircraft/engines assigned.
- Complies with all AFI and AETCI publications related to assigned section.
- Ensures all forms are complete and filed on aircraft/engines.
- Processes all suspense files related to aircraft/engines.
- Performs duties as listed in TO directives for PS&D, Engine Management (EM), and Consolidated Engine Management Section (CEMS), as assigned.
- Within CEMS, updates engine scheduling boards, monitors, and updates engine status in the CEMS and ensures all time change, Low Cycle Fatigue Cycle (LCFC), and TCTOs are accomplished on completed engines.
- Practices good housekeeping and safety at all times.
- Performs tasks with minimum supervision.
- May be assigned to maintain AF publications and TO files.
- May be assigned additional duties, to include Building Custodian.
- Shall assist other personnel and work centers as directed.
- Must promote Company values, policies, and standards of conduct.
- Must be customer oriented and ensure professional coordination with Operations and other base agencies.
- Shall perform other duties assigned to include TDY and travel.
- Must be able to work day shift, night shift, or weekend duty as required.
- Receives cross-utilization training (CUT) and is qualified to perform those administrative tasks.
That's a lot; we can keep them as list items.
Qualifications And Experience: list:
- Two years recent experience in CEMS/PS&D, as applicable.
- High school diploma or the equivalent is required.
- Must be proficient in computer use and proficien in Microsoft Office programs, to include Excel and other applicable programs.
- Must be proficient in data entry.
- Formal courses in Microsoft Office programs are desired.
- Must have experience and be proficient in Files/Records Management.
- Must have experience in tracking and inventory methods and maintaining status.
- Must be able to type at a rate of 40 words per minute.
- Must be able to read, write, speak, and understand English.
- Must have good communication skills and the ability to read and interpret technical data.
Also "Working Conditions . Physical exertion requirement is medium". Could be part of Qualifications or maybe a separate section? Not in headings list. Could be included under Requirements? But we have no specific heading for Working Conditions. Could put under Requirements? Not defined. Probably we can include as part of Qualifications or maybe as a separate section "Requirements". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Requirements section for things like physical exertion, maybe also shift work? But shift work is schedule. We'll treat physical exertion as Requirements.
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Skills: we can extract from qualifications: proficiency in computer use, Microsoft Office, data entry, typing 40 wpm, English, communication, reading technical data. Could be separate Skills.
But we might combine some. However we need to avoid thin sections. Let's decide:
- About the role: short paragraph.
- Responsibilities: big list.
- Requirements: physical exertion medium (maybe also other requirements like must be able to work day/night/weekend? That's schedule though). We'll keep physical exertion.
- Qualifications: education, experience, proficiency in computer use, data entry, files/records management, tracking/inventory, typing speed, language, communication, technical data interpretation.
- Skills: maybe Microsoft Office proficiency, data entry, typing, communication, etc. But that overlaps with qualifications. Could combine qualifications and skills? But we need to follow instruction: use headings when posting has real specific content. We have both qualifications and skills content. We'll keep both.
- Benefits: list of benefits.
- Pay: salary range.
- Schedule: shift work possible, full-time, may require day/night/weekend duty.
Now we need to output HTML fragment only, no markdown.
We'll produce:
About the role
M1 is looking for a Documentation Clerk.
Responsibilities
- ... ...
Requirements
- Physical exertion requirement is medium.
Qualifications
- Two years recent experience in CEMS/PS&D, as applicable.
- High school diploma or equivalent required.
- Proficient in computer use and Microsoft Office programs (including Excel).
- Proficient in data entry.
- Formal courses in Microsoft Office programs desired.
- Experience and proficiency in Files/Records Management.
- Experience in tracking and inventory methods and maintaining status.
- Ability to type at 40 words per minute.
- Ability to read, write, speak, and understand English.
- Good communication skills and ability to read and interpret technical data.
Skills
- Microsoft Office proficiency (Excel, etc.).
- Data entry.
- Typing 40 wpm.
- Effective communication.
- Reading and interpreting technical data.
Benefits
- Medical, dental, vision, life and dependent life insurance.
- AD&D coverage.
- Short- and long-term disability.
- Flexible spending accounts for health and dependent care.
- Free Employee Assistance Program.
Pay
Salary range: $30.28 per hour.
Schedule
- Full-time position.
- Shift work possible; may require day, night, or weekend duty as required.
or drop it." So we could include a short paragraph at top with location and posting date etc. But not required. Could include a short
with location and posting date. However we must not repeat job title. It's okay to add a small paragraph with location and posting date. Let's include a short
after the heading? Actually we have no heading for metadata; we can just include a
before first heading. The instruction: "fold minor metadata into a short
or drop it." So we can add a
containing location, posting date, etc. Let's do:
Location: Columbus, MS • Posting Date: 09/08/2026 • Job ID: 114430
But we should not include Job ID? It says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. So we can include it in a short p. That's fine. We also have contract, union, FLSA status, relocation, travel. Could also include but might be too much. We'll keep it brief: location, posting date, contract type (maybe "Contract: AETC Acft. Mx. Support Svc."), union status, FLSA, relocation, travel. But that may be too long. The instruction says prefer a few substantive sections over many thin ones. Metadata is not a section; we can include a short p with some key info. Let's include location, posting date, contract, union, FLSA, relocation, travel. But that may be long but still a short p. It's okay. Let's craft:
Location: Columbus, MS • Posting Date: 09/08/2026 • Contract: AETC Acft. Mx. Support Svc. • Union: Yes • FLSA Status: Non-Exempt • Relocation: Possible • Travel: Possible
Now output HTML. Check we didn't include any