Rania Sanford, Ed.D. Assistant Dean Postdoctoral Affairs

1. Postdoc PeopleSoft Web Forms Campus Readiness Department Managers Meeting School of Humanities and Sciences Rania Sanford, Ed.D. Assistant Dean Postdoctoral Affairs

2. Agenda • Why Do This? • Current Process Overview and Its Issues • Scope of Project • Impact on Users: • Workflow Roles • Training Requirements • Questions

3. Why Do This? Current Process • Paper Forms and Template letters to appoint, extend, end or note changes in appointments (PIs, funding, locations) • Administrators prepare PDF of the paperwork • Administrators send PDF by email to an group email inbox: postdocaffairs@stanford.edu • No loop closure. Issues communicated back by email. Administrators, faculty and postdocs not knowing when paperwork will be completed.

4. Why Do This? Issues • Insecure handling of protected private information • Inefficiencies • Incomplete paperwork • Incorrect paperwork • Workflow • Status of transactions • Notification to postdocs • Tracking of problems

5. Project Scope, includes • Web Forms and interfaces to support all Postdoc administrative processes and system notifications • Document upload, storage, and management features to support submission and management of required documentation in electronic format • Tracking of current processes and of upcoming end dates of appointments, provisional appointments and other appointment holds • Tracking of International Activity for postdocs • Migration of historical data from OPA’s Filemaker database • Queries to support meaningful searches on Postdoc data within the PeopleSoft system

6. What Does It Mean For Common Tasks? 1. New Appointments • Administrator starts the appointment process online. • Postdoc enters his/her data. Uploads diploma, CV, external funding letters… • Administrator enters department/appointment data. Uploads any other necessary documents. • Faculty Mentor/PI approves online • Chair/Proxy/Department Manager reviews and approves • Offer Letter generated online. Accepted online by postdoc • Packet received and reviewed online by OPA • Upon Approval, Postdoc Record (EMPLID) is created in PS 2. Appointment Changes, and Leaves of Absence: submitted online. 3. At any time, administrator can query PS to search a particular transaction or a group of transactions

7. Impact on Users – Workflow Roles • Administrator (Admin Entry - required): entry of appointment information. Can be Administrative Associate in the lab. • Primary job: • gather documentation, review documentation and appointment information. • Submits information for review, approval and processing. • Required knowledge: • Standard policy and procedures of postdoctoral administration at Stanford. • PeopleSoft User Interface.

8. Coordinator (optional): review of AAs submissions when multiple Admin Entry roles exist within one department. Is typically a Student Services Manager in large departments. Primary jobis to review documentation and appointment information for adherence to university and department policy. Catch and address issues and mistakes before Department Manager or Chair Approval. Provide information to OPA supporting of any exception requests or unique situations. Required knowledge: Standard policy and procedures of postdoctoral administration at Stanford. Non-Standard Policy and procedures. How to handle and manage exceptions and unique situations. PeopleSoft Interface. Impact on Users – Workflow Roles

9. Sponsoring Faculty Member must approve online before process can proceed. Chair/Proxy/Manager Approver (required):signs-off on Department commitment to appoint a postdoc. Faculty member has the funding, has the project(!), term of appointment, off-campus work locations, teaching arrangements. This step creates the Offer Letter. Some Common Issues: Salary equity; funding source doesn’t exist; statements made in offer that are not implementable or are non-compliant with policy: visa-related; salary-related; against policy; Conflict of Interest Impact on Users – Department Approvers

10. Impact on Users – Training Requirements • For Administrators – all of the following: • PeopleSoft Concepts and Compliance (online) • PeopleSoft Postdoctoral Administration: • In-class attendance required pre GoLive (3 sessions to-be-scheduled) Post GoLive--- UPK and Online Training Modules Drop-in Lab Sessions Quarterly Policy and Procedures Class

11. Assign and communicate roles in your organization: Admin Entry Coordinator? Determine Chair/Manager Approver Identify Back-ups for each role Submit information to the OPA Communicate change to Faculty Sign your staff’s certification and request authority before our Go Live date Next Steps for Department Managers

12. Questions? H&S OPA Staff: Tammy Wilson, Assistant Manager helpsu.stanford.edu