School Secretary I - Nantucket Elementary
School Secretary I
. Use headings for sections only. We need to use- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none obvious except maybe "Click HERE to view Terms of Employment, Benefits and Salary Scale." That's a link; we should drop it as it's application instruction? It's a link to view terms; maybe considered application instruction. We should drop it. Also "Driving Requirements N/A" is minor metadata; we can drop or fold into short p. Since it's N/A, we should not include as it's filler. So drop. Now we need to decide sections: - About the role: Could combine Position Summary and Job Summary. Provide a paragraph summarizing role. - Responsibilities: list of essential duties. - Requirements: Minimum Qualifications (Education, Experience). Could also include "Reasonable accommodations may be made..." but that's boilerplate? It's part of qualifications; we can keep. - Qualifications: maybe Education and Experience separate? But we already used Requirements for that. Could split: Requirements = Education and Experience; Qualifications = Knowledge, Skills, Abilities And Other Characteristics. Or we could combine. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. Thus we can have: About the role: paragraph from Job Summary. Responsibilities: list from Essential Duties/Responsibilities. Requirements: Education and Experience (maybe also Reasonable accommodations line). We'll include Education and Experience as list. Qualifications: Knowledge, Skills, Abilities And Other Characteristics (list). Skills: maybe we could separate but we already have Skills in Qualifications. Could also have Skills section separate but we might duplicate. Better to follow headings: we have Skills as separate heading; but we already have Knowledge, Skills, Abilities And Other Characteristics which includes skills. Could put that under Skills. But we also have Qualifications heading for education/experience. Let's map: - About the role: Job Summary paragraph. - Responsibilities: Essential Duties/Responsibilities list. - Requirements: Education and Experience (maybe also Reasonable accommodations). - Qualifications: maybe not needed if we used Requirements for education/experience and Skills for abilities. But we have Qualifications heading; we could put something like "Minimum Qualifications" but that's similar to Requirements. To avoid thin sections, we can combine Education/Experience under Requirements and Knowledge/Skills/Abilities under Skills. Then we might not need Qualifications heading. But we need to include sections only when posting has real specific content. If we omit Qualifications, that's fine. Thus sections: About the role, Responsibilities, Requirements, Skills, Schedule. Check if we have any content for Skills: Knowledge, Skills, Abilities And Other Characteristics includes typing speed, PC proficiency, knowledge of office practices, courtesy, judgment, completion of tests. That's skills. Thus Skills section list. Schedule: Days Worked: 260, Hours Worked: 6.5;7, Months Worked: 12. Now we need to format. We must not include any markdown code fences. Just raw HTML. We need to use
for section headings. Thus:
About the role
...
Responsibilities
- ... ...
Requirements
- High School Diploma or Equivalency Certificate required.
- One (1) year recent general office experience performing work of a progressively responsible nature; if assigned to bilingual program, candidates are required to be bilingual and biliterate in targeted language; otherwise, bilingual and biliterate in target language preferred.
- Or an equivalent combination of education and experience which provides the required knowledge, skills, and abilities.
- Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Skills
- Demonstrated ability to type forty (40) words per minute.
- Proficiency in the operation of personal computers including word processing, spreadsheets, data base management, and desktop publishing applications.
- Good knowledge of modern office practices and procedures, bookkeeping, business English, spelling, and commercial arithmetic.
- Ability to exercise courtesy and good judgment in dealing with students, parents, administrators, other employees and the general public.
- Successful completion of all required tests.
Schedule
- Days Worked: 260 per year.
- Hours Worked: 6.5 or 7 hours per day (as indicated).
- Months Worked: 12.
or drop it." So we could include a short paragraph with this metadata under About the role maybe? But we already have About the role as Job Summary. Could add a
after that with metadata. However, we need to preserve ALL substantive information; is this metadata substantive? It includes Approved Date, Established Date, Title Code, Reports to, Division, Business Unit, Department, Negotiated Agreement, Unit, FLSA Exemption Status, Grade. This is likely considered substantive. The instruction says fold minor metadata into a short
or drop it. So we can include a short paragraph with that info. Thus after About the role paragraph, we can add a
containing that metadata. But we need to avoid duplication: we already have Days Worked etc in Schedule; we should not duplicate. So we can include the other metadata: Approved Date, Established Date, Title Code, Reports to Generic/Specific, Division, Business Unit, Department, Negotiated Agreement, Unit, FLSA Exemption Status, Grade. We should not repeat Days Worked etc. Thus About the role section could have two paragraphs: first the Job Summary prose, second the metadata. Now check for any other substantive info: "Essential Job: Months Worked: 12 Hours Worked: 6.5;7". We used that in Schedule. Now also "Click HERE to view Terms of Employment, Benefits and Salary Scale." We drop. Now also "LEADERSHIP ROLE JOB INFORMATION" heading is just a label; we already captured its content. Now also "HR JOB INFORMATION Unit: IV Days Worked: 260 FLSA Exemption Status: Non-Exempt Grade: SG06". We captured Unit, FLSA, Grade; Days Worked we used in Schedule. Now also "Essential Job: Months Worked: 12 Hours Worked: 6.5;7". Already used. Now also "Job Family: Administrative and Office Support Sub-Function: Office/Staff Support". That's also metadata; we could include in the metadata paragraph. Thus metadata paragraph includes: Approved Date: 10/1/2021; Established Date: 7/1/1979; Title Code: C21611; Title: SECRETARY: SCHOOL I; Reports to Generic: Principal; Reports to Specific: PRINCIPAL; Organization Division: Student & School Support (SSS); Business Unit: Varies; Department: Varies; Negotiated Agreement: Secretaries and Assistants Association of Anne Arundel County (SAAAAC); HR JOB INFORMATION Unit: IV; Days Worked: 260; FLSA Exemption Status: Non-Exempt; Grade: SG06; Job Family: Administrative and Office Support; Sub-Function: Office/Staff Support. We need to ensure we don't duplicate Days Worked (we already have in Schedule). But we can still include it; but better to avoid duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but we should avoid redundant. We could include Days Worked only once, maybe in Schedule. So we can omit Days Worked from metadata paragraph. Thus metadata paragraph excludes Days Worked. Now also "Ess