Front Office Coordinator
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to extract content: The job description includes Main Work Location, Work Arrangement, Budgeted Salary Range, Position Summary, Responsibilities (list), Work Schedule, Financial Operations, Building & Facilities Management, Staff, Special Guest, and Administrative Support, Responsibilities Core Duties (maybe duplicate), Minimum Education And Experience, Knowledge, Skills And Abilities.
We need to avoid repeating job title as heading. No Job ID etc. Remove boilerplate like "To be considered, please include a cover letter and resume..." (application instructions) - remove. Also remove note about not all unique aspects covered? Might be considered boilerplate? It's a note but maybe keep? It's not substantive? Probably remove.
We need to preserve all substantive info.
We need to create sections: About the role (maybe from Position Summary). Responsibilities (list of duties). Requirements (maybe Minimum Education And Experience). Qualifications (maybe Knowledge, Skills And Abilities). Skills (maybe part of Knowledge, Skills And Abilities). Benefits (none given). Pay (Budgeted Salary Range). Schedule (Work Schedule). Also maybe include Work Location and Arrangement? Could be part of About the role.
We must not create sections with filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to ensure we don't duplicate content.
Let's extract:
Position Summary paragraph: "The Office for Religious and Spiritual Life (ORSL) seeks a self-motivated, highly-organized Front Office Coordinator (FOC) to serve as the primary administrative professional responsible for overseeing the financial, logistical, and facility operations of the ORSL at Stanford University. Under the direction of the Director of Events and Operations, the FOC is a key team member and first point of contact in the office to both colleagues and the public. This vital role supports the smooth functioning of ORSL’s programs, staff operations, and physical spaces. Responsibilities include: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, and compliance with university policies and procedures. The FOC must be able to prioritize, multi-task, and keep a calm, welcoming demeanor. A high level of professionalism and dependability is required for this role."
We can put that as About the role.
Work Schedule: "Work Schedule: 8:30am – 5:30pm, Monday – Friday."
Budgeted Salary Range: "The expected pay range for this positions is $40.10 to $44.88 per hour."
Main Work Location: "Historic Stanford Campus". Work Arrangement: "On-site". Could be included in About the role or separate? Probably include in About the role as prose.
Responsibilities: There's a list after "Responsibilities include:" then later sections: Financial Operations, Building & Facilities Management, Staff, Special Guest, and Administrative Support, Responsibilities Core Duties. We need to combine into a single list? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with items covering all duties. Might be long but okay.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include each duty as separate - . Let's extract duties:
From Position Summary: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, compliance with university policies and procedures, prioritize, multi-task, keep a calm, welcoming demeanor, high level of professionalism and dependability.
But some are more like requirements. We'll keep them.
Financial Operations: Manage all purchasing and financial logistics for the department, including procurement of supplies, services, and equipment. Process payments for vendors, contractors, and guest speakers, including honoraria, travel reimbursements, and speaker arrangements. Serve as department lead for university financial coordination, liaising with central university office to ensure accurate processing and Compliance. Reconcile all purchasing and travel cards on a monthly basis, ensuring proper documentation and compliance with university policy. Review invoices for accuracy and initiate purchase requisitions. Coordinate ORSL charity collection process: oversee donation intake, recognition, reconciliation, gift transmittals, and deposit procedures.
Building & Facilities Management: Serve as ORSL’s building manager for Memorial Church and associated ORSL spaces, submitting work orders to coordinate facility maintenance, custodial services, repairs, and equipment upkeep. Take daily visual inventory of Memorial Church grounds and report items needing attention. Complete the daily formal lock-up procedure for Memorial Church and its office spaces. Track facility and office equipment such as keys, ID cards, golf carts, and IT assets, and schedule repairs as needed. With the Director of Events and Operations, lead emergency preparedness efforts and ensure safety protocols are in place and reviewed regularly. Liaise with university departments such as Environmental Health & Safety, Facilities, and Land, Buildings & Real Estate.
Staff, Special Guest, and Administrative Support: Assist with onboarding and offboarding of staff and affiliates. Coordinate guest speaker logistics: issue formal invitation letters, manage travel arrangements, process payments, and serve as liaison throughout the engagement. Set up guest speakers and short-term visitors in university financial systems. As directed by the Director of Events and Operations, provide event support logistics as needed in coordination with other ORSL staff. Other duties may be assigned, as needed.
Responsibilities Core Duties: Act on behalf of the supervisor, department manager, or chair in regards to establishing priorities and identifying and resolving problems that are administrative in nature. Oversee and/or perform duties associated with scheduling, organizing, and operating complex conferences, seminars, and events, including arranging with vendors for services, overseeing the production and distribution of materials, administering logistics, and managing event within budget. Compose and draft documents and correspondence for presentations, course handouts, grants, conferences, seminars, and reports. Perform substantial editing and fact checking. Create, maintain, modify, and/or ensure accuracy of content in various unit documents, displays, reports, brochures, social media, and/or websites. Plan and schedule calendar(s) with limited consultation, resolve calendaring conflicts, and arrange travel in compliance with unit, university, and sponsor policies. Create complex reports and spreadsheets which may utilize specialized software and systems. Oversee and/or process a variety of complex financial transactions; produce, monitor, and reconcile budget statements; research, identify, and resolve discrepancies. May assist with capital or special equipment requests and/or vendor selection. Coordinate and monitor routine maintenance services completion. Plan and coordinate office moves and/or minor renovation projects. May lead staff or supervise day-to-day work of student and/or temporary workers, including scheduling, assigning, and prioritizing workloads, setting appropriate deadlines, reviewing work for quality and timeliness, and providing performance review input.
We need to avoid duplication; many items repeat earlier. But we must preserve all substantive info; duplication may be okay but we could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid deduplication, but we should not lose detail. If we deduplicate we might lose some nuance but likely still preserve. Safer to keep all items as they appear, even if duplicate. However that could be huge. But we can combine similar items but risk losing nuance. Probably better to keep as is but maybe we can merge similar bullet points.
Given the length, we can produce a long
with many - . That's okay.
Now Requirements: Minimum Education And Experience: "High school diploma and four years of administrative experience, or combination of education and relevant experience."
Qualifications: Knowledge, Skills And Abilities list: "Advanced computer skills and demonstrated experience with office software and email applications. Demonstrated success in following through and completing projects. Excellent organizational skills and attention to detail. Excellent Strong verbal and written communication skills. Excellent customer service and interpersonal skills. Ability to prioritize, multi-task, and assign work to others. Ability to take initiative and ownership of projects. Ability to routinely and independently exercise sound judgment in making decisions."
Note there is a typo: "Excellent Strong". We'll keep as is.
Skills section: Could be part of Qualifications; but we have separate Skills heading allowed. We could put Skills as list of skills from Knowledge, Skills And Abilities. But we already have Qualifications heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Qualifications and Skills. We need to decide what goes where. Usually Qualifications includes education/experience, Skills includes abilities. But we have Minimum Education And Experience as Requirements. Knowledge, Skills And Abilities as Qualifications and Skills. Could split: Qualifications: Knowledge, Skills And Abilities (maybe as prose). Skills: maybe list of specific skills like Advanced computer skills, etc. But to avoid duplication, we could put Knowledge, Skills And Abilities under Qualifications, and Skills maybe empty? But we must not create a heading with filler. So we should only include Skills if there is real specific content for it. The posting includes "Knowledge, Skills And Abilities". That could be considered Qualifications. We could treat that as Qualifications and not create separate Skills heading. Or we could split: Qualifications: Minimum Education And Experience; Skills: Knowledge, Skills And Abilities. But then Requirements would be empty? Actually we have Requirements heading for education/experience. So we can put Minimum Education And Experience under Requirements. Then Qualifications could be something else? But the posting doesn't have separate Qualifications beyond that. So we could omit Qualifications heading and just have Requirements and Skills. However the instruction list includes Qualifications as optional; we only include if posting has real specific content. The posting has "Knowledge, Skills And Abilities". That could be considered Qualifications. So we can put that under Qualifications. Then Skills maybe not needed. But we could also put Skills under Qualifications as part of same list. To be safe, we can have Requirements (education/experience) and Qualifications (knowledge, skills, abilities). No separate Skills heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
We need to include Work Location and Arrangement maybe in About the role.
Now Benefits: none given, so omit.
Now Pay: include the salary range.
Schedule: include work schedule.
Now we need to output HTML fragment only.
Let's craft:
About the role
Main Work Location: Historic Stanford Campus. Work Arrangement: On-site. The Office for Religious and Spiritual Life (ORSL) seeks a self-motivated, highly-organized Front Office Coordinator (FOC) to serve as the primary administrative professional responsible for overseeing the financial, logistical, and facility operations of the ORSL at Stanford University. Under the direction of the Director of Events and Operations, the FOC is a key team member and first point of contact in the office to both colleagues and the public. This vital role supports the smooth functioning of ORSL’s programs, staff operations, and physical spaces. Responsibilities include: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, and compliance with university policies and procedures. The FOC must be able to prioritize, multi-task, and keep a calm, welcoming demeanor. A high level of professionalism and dependability is required for this role.
Responsibilities
- greeting and directing visitors
- staffing the front office
- answering routine inquiries
- verifying financial transactions
- procurement
- managing and communicating facility needs
- compliance with university policies and procedures
- prioritize, multi-task, and keep a calm, welcoming demeanor
for prose. We need to ensure we don't duplicate content. Let's extract: Position Summary paragraph: "The Office for Religious and Spiritual Life (ORSL) seeks a self-motivated, highly-organized Front Office Coordinator (FOC) to serve as the primary administrative professional responsible for overseeing the financial, logistical, and facility operations of the ORSL at Stanford University. Under the direction of the Director of Events and Operations, the FOC is a key team member and first point of contact in the office to both colleagues and the public. This vital role supports the smooth functioning of ORSL’s programs, staff operations, and physical spaces. Responsibilities include: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, and compliance with university policies and procedures. The FOC must be able to prioritize, multi-task, and keep a calm, welcoming demeanor. A high level of professionalism and dependability is required for this role." We can put that as About the role. Work Schedule: "Work Schedule: 8:30am – 5:30pm, Monday – Friday." Budgeted Salary Range: "The expected pay range for this positions is $40.10 to $44.88 per hour." Main Work Location: "Historic Stanford Campus". Work Arrangement: "On-site". Could be included in About the role or separate? Probably include in About the role as prose. Responsibilities: There's a list after "Responsibilities include:" then later sections: Financial Operations, Building & Facilities Management, Staff, Special Guest, and Administrative Support, Responsibilities Core Duties. We need to combine into a single list? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
- with items covering all duties. Might be long but okay.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include each duty as separate
- . Let's extract duties:
From Position Summary: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, compliance with university policies and procedures, prioritize, multi-task, keep a calm, welcoming demeanor, high level of professionalism and dependability.
But some are more like requirements. We'll keep them.
Financial Operations: Manage all purchasing and financial logistics for the department, including procurement of supplies, services, and equipment. Process payments for vendors, contractors, and guest speakers, including honoraria, travel reimbursements, and speaker arrangements. Serve as department lead for university financial coordination, liaising with central university office to ensure accurate processing and Compliance. Reconcile all purchasing and travel cards on a monthly basis, ensuring proper documentation and compliance with university policy. Review invoices for accuracy and initiate purchase requisitions. Coordinate ORSL charity collection process: oversee donation intake, recognition, reconciliation, gift transmittals, and deposit procedures.
Building & Facilities Management: Serve as ORSL’s building manager for Memorial Church and associated ORSL spaces, submitting work orders to coordinate facility maintenance, custodial services, repairs, and equipment upkeep. Take daily visual inventory of Memorial Church grounds and report items needing attention. Complete the daily formal lock-up procedure for Memorial Church and its office spaces. Track facility and office equipment such as keys, ID cards, golf carts, and IT assets, and schedule repairs as needed. With the Director of Events and Operations, lead emergency preparedness efforts and ensure safety protocols are in place and reviewed regularly. Liaise with university departments such as Environmental Health & Safety, Facilities, and Land, Buildings & Real Estate.
Staff, Special Guest, and Administrative Support: Assist with onboarding and offboarding of staff and affiliates. Coordinate guest speaker logistics: issue formal invitation letters, manage travel arrangements, process payments, and serve as liaison throughout the engagement. Set up guest speakers and short-term visitors in university financial systems. As directed by the Director of Events and Operations, provide event support logistics as needed in coordination with other ORSL staff. Other duties may be assigned, as needed.
Responsibilities Core Duties: Act on behalf of the supervisor, department manager, or chair in regards to establishing priorities and identifying and resolving problems that are administrative in nature. Oversee and/or perform duties associated with scheduling, organizing, and operating complex conferences, seminars, and events, including arranging with vendors for services, overseeing the production and distribution of materials, administering logistics, and managing event within budget. Compose and draft documents and correspondence for presentations, course handouts, grants, conferences, seminars, and reports. Perform substantial editing and fact checking. Create, maintain, modify, and/or ensure accuracy of content in various unit documents, displays, reports, brochures, social media, and/or websites. Plan and schedule calendar(s) with limited consultation, resolve calendaring conflicts, and arrange travel in compliance with unit, university, and sponsor policies. Create complex reports and spreadsheets which may utilize specialized software and systems. Oversee and/or process a variety of complex financial transactions; produce, monitor, and reconcile budget statements; research, identify, and resolve discrepancies. May assist with capital or special equipment requests and/or vendor selection. Coordinate and monitor routine maintenance services completion. Plan and coordinate office moves and/or minor renovation projects. May lead staff or supervise day-to-day work of student and/or temporary workers, including scheduling, assigning, and prioritizing workloads, setting appropriate deadlines, reviewing work for quality and timeliness, and providing performance review input.
We need to avoid duplication; many items repeat earlier. But we must preserve all substantive info; duplication may be okay but we could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid deduplication, but we should not lose detail. If we deduplicate we might lose some nuance but likely still preserve. Safer to keep all items as they appear, even if duplicate. However that could be huge. But we can combine similar items but risk losing nuance. Probably better to keep as is but maybe we can merge similar bullet points.
Given the length, we can produce a long
- with many
- . That's okay.
Now Requirements: Minimum Education And Experience: "High school diploma and four years of administrative experience, or combination of education and relevant experience."
Qualifications: Knowledge, Skills And Abilities list: "Advanced computer skills and demonstrated experience with office software and email applications. Demonstrated success in following through and completing projects. Excellent organizational skills and attention to detail. Excellent Strong verbal and written communication skills. Excellent customer service and interpersonal skills. Ability to prioritize, multi-task, and assign work to others. Ability to take initiative and ownership of projects. Ability to routinely and independently exercise sound judgment in making decisions."
Note there is a typo: "Excellent Strong". We'll keep as is.
Skills section: Could be part of Qualifications; but we have separate Skills heading allowed. We could put Skills as list of skills from Knowledge, Skills And Abilities. But we already have Qualifications heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Qualifications and Skills. We need to decide what goes where. Usually Qualifications includes education/experience, Skills includes abilities. But we have Minimum Education And Experience as Requirements. Knowledge, Skills And Abilities as Qualifications and Skills. Could split: Qualifications: Knowledge, Skills And Abilities (maybe as prose). Skills: maybe list of specific skills like Advanced computer skills, etc. But to avoid duplication, we could put Knowledge, Skills And Abilities under Qualifications, and Skills maybe empty? But we must not create a heading with filler. So we should only include Skills if there is real specific content for it. The posting includes "Knowledge, Skills And Abilities". That could be considered Qualifications. We could treat that as Qualifications and not create separate Skills heading. Or we could split: Qualifications: Minimum Education And Experience; Skills: Knowledge, Skills And Abilities. But then Requirements would be empty? Actually we have Requirements heading for education/experience. So we can put Minimum Education And Experience under Requirements. Then Qualifications could be something else? But the posting doesn't have separate Qualifications beyond that. So we could omit Qualifications heading and just have Requirements and Skills. However the instruction list includes Qualifications as optional; we only include if posting has real specific content. The posting has "Knowledge, Skills And Abilities". That could be considered Qualifications. So we can put that under Qualifications. Then Skills maybe not needed. But we could also put Skills under Qualifications as part of same list. To be safe, we can have Requirements (education/experience) and Qualifications (knowledge, skills, abilities). No separate Skills heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
We need to include Work Location and Arrangement maybe in About the role.
Now Benefits: none given, so omit.
Now Pay: include the salary range.
Schedule: include work schedule.
Now we need to output HTML fragment only.
Let's craft:
About the role
Main Work Location: Historic Stanford Campus. Work Arrangement: On-site. The Office for Religious and Spiritual Life (ORSL) seeks a self-motivated, highly-organized Front Office Coordinator (FOC) to serve as the primary administrative professional responsible for overseeing the financial, logistical, and facility operations of the ORSL at Stanford University. Under the direction of the Director of Events and Operations, the FOC is a key team member and first point of contact in the office to both colleagues and the public. This vital role supports the smooth functioning of ORSL’s programs, staff operations, and physical spaces. Responsibilities include: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, and compliance with university policies and procedures. The FOC must be able to prioritize, multi-task, and keep a calm, welcoming demeanor. A high level of professionalism and dependability is required for this role.
Responsibilities
- greeting and directing visitors
- staffing the front office
- answering routine inquiries
- verifying financial transactions
- procurement
- managing and communicating facility needs
- compliance with university policies and procedures
- prioritize, multi-task, and keep a calm, welcoming demeanor
- . That's okay.
Now Requirements: Minimum Education And Experience: "High school diploma and four years of administrative experience, or combination of education and relevant experience."
Qualifications: Knowledge, Skills And Abilities list: "Advanced computer skills and demonstrated experience with office software and email applications. Demonstrated success in following through and completing projects. Excellent organizational skills and attention to detail. Excellent Strong verbal and written communication skills. Excellent customer service and interpersonal skills. Ability to prioritize, multi-task, and assign work to others. Ability to take initiative and ownership of projects. Ability to routinely and independently exercise sound judgment in making decisions."
Note there is a typo: "Excellent Strong". We'll keep as is.
Skills section: Could be part of Qualifications; but we have separate Skills heading allowed. We could put Skills as list of skills from Knowledge, Skills And Abilities. But we already have Qualifications heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Qualifications and Skills. We need to decide what goes where. Usually Qualifications includes education/experience, Skills includes abilities. But we have Minimum Education And Experience as Requirements. Knowledge, Skills And Abilities as Qualifications and Skills. Could split: Qualifications: Knowledge, Skills And Abilities (maybe as prose). Skills: maybe list of specific skills like Advanced computer skills, etc. But to avoid duplication, we could put Knowledge, Skills And Abilities under Qualifications, and Skills maybe empty? But we must not create a heading with filler. So we should only include Skills if there is real specific content for it. The posting includes "Knowledge, Skills And Abilities". That could be considered Qualifications. We could treat that as Qualifications and not create separate Skills heading. Or we could split: Qualifications: Minimum Education And Experience; Skills: Knowledge, Skills And Abilities. But then Requirements would be empty? Actually we have Requirements heading for education/experience. So we can put Minimum Education And Experience under Requirements. Then Qualifications could be something else? But the posting doesn't have separate Qualifications beyond that. So we could omit Qualifications heading and just have Requirements and Skills. However the instruction list includes Qualifications as optional; we only include if posting has real specific content. The posting has "Knowledge, Skills And Abilities". That could be considered Qualifications. So we can put that under Qualifications. Then Skills maybe not needed. But we could also put Skills under Qualifications as part of same list. To be safe, we can have Requirements (education/experience) and Qualifications (knowledge, skills, abilities). No separate Skills heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule.
We need to include Work Location and Arrangement maybe in About the role.
Now Benefits: none given, so omit.
Now Pay: include the salary range.
Schedule: include work schedule.
Now we need to output HTML fragment only.
Let's craft:
- . Let's extract duties:
From Position Summary: greeting and directing visitors, staffing the front office, answering routine inquiries, verifying financial transactions, procurement, managing and communicating facility needs, compliance with university policies and procedures, prioritize, multi-task, keep a calm, welcoming demeanor, high level of professionalism and dependability.
But some are more like requirements. We'll keep them.
Financial Operations: Manage all purchasing and financial logistics for the department, including procurement of supplies, services, and equipment. Process payments for vendors, contractors, and guest speakers, including honoraria, travel reimbursements, and speaker arrangements. Serve as department lead for university financial coordination, liaising with central university office to ensure accurate processing and Compliance. Reconcile all purchasing and travel cards on a monthly basis, ensuring proper documentation and compliance with university policy. Review invoices for accuracy and initiate purchase requisitions. Coordinate ORSL charity collection process: oversee donation intake, recognition, reconciliation, gift transmittals, and deposit procedures.
Building & Facilities Management: Serve as ORSL’s building manager for Memorial Church and associated ORSL spaces, submitting work orders to coordinate facility maintenance, custodial services, repairs, and equipment upkeep. Take daily visual inventory of Memorial Church grounds and report items needing attention. Complete the daily formal lock-up procedure for Memorial Church and its office spaces. Track facility and office equipment such as keys, ID cards, golf carts, and IT assets, and schedule repairs as needed. With the Director of Events and Operations, lead emergency preparedness efforts and ensure safety protocols are in place and reviewed regularly. Liaise with university departments such as Environmental Health & Safety, Facilities, and Land, Buildings & Real Estate.
Staff, Special Guest, and Administrative Support: Assist with onboarding and offboarding of staff and affiliates. Coordinate guest speaker logistics: issue formal invitation letters, manage travel arrangements, process payments, and serve as liaison throughout the engagement. Set up guest speakers and short-term visitors in university financial systems. As directed by the Director of Events and Operations, provide event support logistics as needed in coordination with other ORSL staff. Other duties may be assigned, as needed.
Responsibilities Core Duties: Act on behalf of the supervisor, department manager, or chair in regards to establishing priorities and identifying and resolving problems that are administrative in nature. Oversee and/or perform duties associated with scheduling, organizing, and operating complex conferences, seminars, and events, including arranging with vendors for services, overseeing the production and distribution of materials, administering logistics, and managing event within budget. Compose and draft documents and correspondence for presentations, course handouts, grants, conferences, seminars, and reports. Perform substantial editing and fact checking. Create, maintain, modify, and/or ensure accuracy of content in various unit documents, displays, reports, brochures, social media, and/or websites. Plan and schedule calendar(s) with limited consultation, resolve calendaring conflicts, and arrange travel in compliance with unit, university, and sponsor policies. Create complex reports and spreadsheets which may utilize specialized software and systems. Oversee and/or process a variety of complex financial transactions; produce, monitor, and reconcile budget statements; research, identify, and resolve discrepancies. May assist with capital or special equipment requests and/or vendor selection. Coordinate and monitor routine maintenance services completion. Plan and coordinate office moves and/or minor renovation projects. May lead staff or supervise day-to-day work of student and/or temporary workers, including scheduling, assigning, and prioritizing workloads, setting appropriate deadlines, reviewing work for quality and timeliness, and providing performance review input.
We need to avoid duplication; many items repeat earlier. But we must preserve all substantive info; duplication may be okay but we could deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid deduplication, but we should not lose detail. If we deduplicate we might lose some nuance but likely still preserve. Safer to keep all items as they appear, even if duplicate. However that could be huge. But we can combine similar items but risk losing nuance. Probably better to keep as is but maybe we can merge similar bullet points.
Given the length, we can produce a long