From the Campus Operations edition of October 13, 2026
Feng Chia University HR-run competition draws 79 staff teams building AI administrative tools; winner built with Microsoft 365 Copilot and Claude Code automates student-assistant scheduling
Feng Chia University, Office of Human Resources · Higher education administration / staff-built AI workflow tools · Taichung, Taiwan (private university)
- Publisher
- Feng Chia University News
- Original publication
- Feng Chia University news, October 5, 2026; winners announced September 30, 2026
- Source retrieved
- 2026-10-14
- Event date
- 2026-09-30
What happened
Feng Chia's Office of Human Resources ran its second 'AI Leadership: Smart University Administration Innovation Competition', with 79 faculty and staff teams nominated by first-level units. The Office of Academic Affairs won with a Student Assistant Intelligent Management System built with Microsoft 365 Copilot and Claude Code: it imports class schedules to avoid conflicts, generates regulation-compliant labour attendance PDFs in one click, offers a mobile app for task selection and auto-scheduling, and is said to simplify payroll reimbursement. Runners-up were an AI website quality dashboard (Secretariat) and a venue, maintenance and cost platform (campus management). The chair said several systems are already in practice and added NT$10,000 bonuses.
Why it matters
A concrete model for surfacing administrative AI use cases from staff themselves, with HR as sponsor, and a sign that staff are now building working tools with coding agents rather than only using chat assistants. Facilities and payroll-adjacent workflows are in scope.
Evidence and measured results
Institutional news release naming teams, tools and features. No time savings, error rates, user counts, cost or security review details are given; 'already implemented in practice' is not quantified. International context with limited transferability.
Limitations and uncertainty
Self-reported; no metrics; unclear governance of staff-built code; Taiwanese private university context.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-13; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Staff are building AI tools for administrative work faster than the institution can review, host or support them.
- Stakeholders
- HR / staff development
- CIO and application owners
- Information security
- Unit administrators
- Payroll and facilities leads
- Discovery questions
- How many staff-built AI tools are in use?
- Who reviews them before they touch records?
- Where is the code hosted and who maintains it?
- Which prototypes do you want to scale campus-wide?
- Value hypothesis
- A light review-and-scale path could convert staff prototypes into reusable services while lowering risk, but this source gives no outcome evidence.
- Potential engagement
- A 6–8 week review of a few staff-built AI tools with a scale-up checklist and ownership model.
- Unsupported claims
- Time or cost savings
- Error reduction
- That tools passed security or privacy review
Pre-sales engineering
Role takeaway
- Fit
- Suits institutions licensing Microsoft 365 Copilot or coding agents with staff already experimenting.
- Architecture and integration
- Staff tools reading class schedules and producing attendance PDFs; integration with student and payroll systems unspecified.
- Prerequisites
- Inventory of staff-built tools
- Hosting and authentication standard
- Data-classification rules
- Constraints
- Unknown code quality and maintainability
- Records-retention rules for attendance and payroll
- Different national data-protection law
- Security
- Requires code and access review before tools touch personnel or payroll-related records.
- Proof of value
- Security review of one scaled tool
- Baseline versus post-tool processing time
- Maintenance hand-off test
Delivery
Role takeaway
- Work
- Create a pathway from staff-built AI prototypes to supported administrative services.
- Dependencies
- IT hosting standards
- Security review capacity
- Unit sponsorship
- Ownership
- Central IT application owner per scaled tool, with HR running the innovation intake.
- Skills and adoption
- Pair builder teams with IT developers during hand-off; publish reusable patterns for other units.
- Governance checkpoints
- Data and records review before production
- Code review
- Annual review of tool ownership
- Acceptance criteria
- Proposed: each scaled tool has a named owner and documented data flows
- Proposed: measured processing-time change against a pre-tool baseline
- Risks
- Orphaned tools
- Unreviewed access to personnel data
- Duplicate tools across units
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Staff-built systems using Copilot and Claude Code that touch class schedules, attendance records and payroll create shadow-application risk unless hosting, integration and maintenance are owned by IT.
Governance
Who approves, reviews and stays accountable for outcomes?
A competition is an intake channel for use cases, but the release does not mention review for data protection, records compliance or long-term support before tools go live.
Security and privacy
What data, permissions and controls need testing?
The winning tool handles student-assistant schedules, attendance and payroll-related records; the release is silent on access control, data storage and code review.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Builds staff AI capability through practice and incentives, run by HR; teams were unit-nominated, so participation may skew toward already-confident staff.
Procurement
What should contracts, pricing and exit terms secure?
Shows build-with-assistants as an alternative to buying point solutions for scheduling, facilities booking and web QA; tool licences (Copilot, Claude Code) become the procurement decision.
Operating model
Which teams own the service once it runs?
HR-sponsored, unit-nominated innovation with plans to share winning systems across units; scaling requires a hand-off from team-built prototypes to supported services.
Publication history
- 2026-10-13Campus Operations · Issue 364 resources
Stable resource ID: feng-chia-ai-smart-administration-competition-20261005