Capability template for operations and process improvement
Academic calendar check
While year, term and session dates are being assembled, your registrar gets a draft calendar with every registration window tied to its term, and every conflicting, missing or out-of-bounds date listed as a question. Nothing is published or changed.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
The calendar reaches the registrar as one draft instead of a pile of proposals. Each year, term and session is listed with its dates, the term it belongs to and its registration window, so anyone can see at a glance what sits inside what.
The problems that normally surface after the dates are public are on the page before: two offices proposing different withdrawal deadlines, a grade deadline nobody supplied, a session that runs past its term, an add and drop date that falls after the withdrawal date, a deadline on a weekend or a closed day. Each arrives as a question for the registrar with the facts beside it.
Two sessions that overlap are listed too. The capability cannot know whether the overlap is planned, so it asks; the registrar says.
Your registrar still owns the calendar. The AI assistant picks no date between competing versions, invents none that is missing, and updates no student system, notice or web page.
Who starts the work, and when
The registrar, or the person in the registrar's office who assembles the calendar, starts it when the proposed dates for a year are collected, and again each time an office sends a changed date. The registrar reads the draft and decides every finding before any record or notice is updated.
What they supply
- The structure. Each year, term and session, and which unit it belongs to.
- The date proposals. Each proposed date or window: the unit, what kind of date it is, the dates, the version and who proposed it.
- The closed days. The days the institution is shut, such as recesses.
- A few settings. Today's date, the non-working weekdays and, if you want a different list, the dates each kind of unit must have.
What comes out
One draft calendar, in date order, with each term followed by its sessions. Under it, the numbered findings in a fixed order: structure problems, conflicting versions, missing dates, dates outside their term, dates in the wrong order, overlaps to confirm, and dates on non-working days. A group with nothing in it says so.
Every date shows the proposal it came from, so each line can be checked against the file the offices sent. A conflicting date shows all its versions and no chosen one.
An invented example
Illustrative example with invented data. The college, the offices, the units and every date below are invented. The college is an invented small community college, called the College here, whose registrar is assembling the calendar for the 2027-28 year. The registrar asks for the check on Tuesday 10 November 2026. Offices are named by role. First come the inputs the registrar supplied, in full, then the draft the capability returned.
The inputs
1. Settings (typed by the registrar)
Institution: the College
Academic year: 2027-28
Today: 2026-11-10
Non-working weekdays: Saturday, Sunday
Required dates: use the defaults
Rules: use the defaults
Confirms dates and overlaps: the Registrar
2. Structure
unit_id,unit_name,unit_type,parent_id
Y28,Academic year 2027-28,year,
A28,Autumn term 2027,term,Y28
S28,Spring term 2028,term,Y28
A28-1,Autumn first session,session,A28
A28-2,Autumn second session,session,A28
WI28,Winter intensive session,session,
3. Date proposals
proposal_id,unit_id,item_type,start_date,end_date,version,proposed_by,note
P01,Y28,unit_span,2027-08-30,2028-05-05,1,Academic senate,
P02,A28,unit_span,2027-08-30,2027-12-17,1,Academic senate,
P03,A28,registration,2027-04-12,2027-08-27,1,Registrar's office,
P04,A28,add_drop,2027-09-10,,1,Registrar's office,
P05,A28,withdrawal,2027-11-05,,1,Registrar's office,
P06,A28,exams,2027-12-13,2027-12-17,1,Academic senate,
P07,A28,grades_due,2027-12-24,,1,Registrar's office,
P08,A28-1,unit_span,2027-08-30,2027-10-22,1,Academic senate,
P09,A28-1,add_drop,2027-09-03,,1,Registrar's office,
P10,A28-1,withdrawal,2027-10-01,,1,Registrar's office,
P11,A28-1,grades_due,2027-10-27,,1,Registrar's office,
P12,A28-2,unit_span,2027-10-18,2027-12-20,1,Academic senate,
P13,A28-2,add_drop,2027-11-30,,1,Registrar's office,
P14,A28-2,withdrawal,2027-11-24,,1,Registrar's office,
P15,A28-2,grades_due,2027-12-22,,1,Registrar's office,
P16,S28,unit_span,2028-01-10,2028-05-05,1,Academic senate,
P17,S28,registration,2027-11-01,2028-01-07,1,Registrar's office,
P18,S28,add_drop,2028-01-22,,1,Registrar's office,
P19,S28,withdrawal,2028-03-17,,1,Registrar's office,
P20,S28,withdrawal,2028-03-31,,2,Academic senate,senate asks for two more weeks
P21,S28,exams,2028-05-01,2028-05-09,1,Academic senate,
P22,WI28,unit_span,2028-01-03,2028-01-14,1,Academic senate,
P23,WI28,add_drop,2028-01-04,,1,Registrar's office,
P24,WI28,withdrawal,2028-01-10,,1,Registrar's office,
P25,SU28,unit_span,2028-06-05,2028-07-28,1,Academic senate,summer term not yet in the structure
4. Closed days
closed_id,closed_name,start_date,end_date
CL1,Harvest recess,2027-11-25,2027-11-26
CL2,Winter closure,2027-12-24,2028-01-02
CL3,Spring recess,2028-03-20,2028-03-24
The draft
ACADEMIC CALENDAR CHECK: the College, academic year 2027-28
For: the Registrar. Prepared: Tue 2026-11-10, from the structure (6 units), the date proposals (25 rows), the closed days (3 rows) and the settings.
Column check: all headers matched.
Proposals placed on the calendar: 24. Proposals for units not in the structure: 1. Findings: 11.
DRAFT CALENDAR
Y28 Academic year 2027-28 (year): Mon 2027-08-30 to Fri 2028-05-05 (P01).
Parent: none (a year has none).
Registration window: not required for a year.
Add/drop deadline: not required for a year.
Withdrawal deadline: not required for a year.
Exam period: not required for a year.
Grades due: not required for a year.
A28 Autumn term 2027 (term): Mon 2027-08-30 to Fri 2027-12-17 (P02).
Parent: Y28 Academic year 2027-28, Mon 2027-08-30 to Fri 2028-05-05. Within the parent.
Registration window: Mon 2027-04-12 to Fri 2027-08-27 (P03).
Add/drop deadline: Fri 2027-09-10 (P04).
Withdrawal deadline: Fri 2027-11-05 (P05).
Exam period: Mon 2027-12-13 to Fri 2027-12-17 (P06).
Grades due: Fri 2027-12-24 (P07). See F10.
A28-1 Autumn first session (session): Mon 2027-08-30 to Fri 2027-10-22 (P08). See F9.
Parent: A28 Autumn term 2027, Mon 2027-08-30 to Fri 2027-12-17. Within the parent.
Registration window: not required for a session.
Add/drop deadline: Fri 2027-09-03 (P09).
Withdrawal deadline: Fri 2027-10-01 (P10).
Exam period: not required for a session.
Grades due: Wed 2027-10-27 (P11).
A28-2 Autumn second session (session): Mon 2027-10-18 to Mon 2027-12-20 (P12). See F6, F9.
Parent: A28 Autumn term 2027, Mon 2027-08-30 to Fri 2027-12-17. OUTSIDE the parent, see F6.
Registration window: not required for a session.
Add/drop deadline: Tue 2027-11-30 (P13). See F8.
Withdrawal deadline: Wed 2027-11-24 (P14). See F8.
Exam period: not required for a session.
Grades due: Wed 2027-12-22 (P15).
S28 Spring term 2028 (term): Mon 2028-01-10 to Fri 2028-05-05 (P16).
Parent: Y28 Academic year 2027-28, Mon 2027-08-30 to Fri 2028-05-05. Within the parent.
Registration window: Mon 2027-11-01 to Fri 2028-01-07 (P17).
Add/drop deadline: Sat 2028-01-22 (P18). See F11.
Withdrawal deadline: CONFLICT, no date chosen: Fri 2028-03-17 (P19, version 1, Registrar's office) against Fri 2028-03-31 (P20, version 2, Academic senate). See F3. Not checked against the term, the order or non-working days.
Exam period: Mon 2028-05-01 to Tue 2028-05-09 (P21). See F7.
Grades due: not supplied, see F4.
Units with no parent in the structure
WI28 Winter intensive session (session): Mon 2028-01-03 to Fri 2028-01-14 (P22). See F1.
Parent: none in the structure. Not checked against a parent.
Registration window: not required for a session.
Add/drop deadline: Tue 2028-01-04 (P23).
Withdrawal deadline: Mon 2028-01-10 (P24).
Exam period: not required for a session.
Grades due: not supplied, see F5.
Proposals for units not in the structure
P25 SU28: unit_span, Mon 2028-06-05 to Fri 2028-07-28, version 1, Academic senate. Not placed on the calendar. See F2.
FINDINGS FOR THE REGISTRAR
Structure
F1. WI28 Winter intensive session has no parent in the structure, so it is not placed under a year or term and its dates are not checked against one. Which term or year does it belong to?
F2. Proposal P25 names the unit SU28, which is not in the structure ("summer term not yet in the structure"). Its dates are shown and not placed. Is SU28 a unit to add to the structure, and under which year or term?
Conflicting versions
F3. S28 Spring term 2028, withdrawal deadline: P19 (version 1, Registrar's office) says Fri 2028-03-17 and P20 (version 2, Academic senate) says Fri 2028-03-31, with the note "senate asks for two more weeks". Which date stands?
Missing dates
F4. S28 Spring term 2028: grades due not supplied. Which office supplies it, and what is the date?
F5. WI28 Winter intensive session: grades due not supplied. Which office supplies it, and what is the date?
Outside the parent or the unit
F6. A28-2 Autumn second session ends Mon 2027-12-20, 3 days after its parent A28 Autumn term 2027 ends on Fri 2027-12-17. Which dates stand?
F7. S28 Spring term 2028: the exam period ends Tue 2028-05-09, 4 days after the term ends on Fri 2028-05-05. Which dates stand?
Wrong order
F8. A28-2 Autumn second session: the add/drop deadline, Tue 2027-11-30, is 6 days after the withdrawal deadline, Wed 2027-11-24. Which dates stand?
Overlaps to confirm
F9. A28-1 Autumn first session (to Fri 2027-10-22) and A28-2 Autumn second session (from Mon 2027-10-18) share 5 days, Mon 2027-10-18 to Fri 2027-10-22, both under A28 Autumn term 2027. Is the overlap intended?
Non-working days
F10. A28 Autumn term 2027: grades due on Fri 2027-12-24, which falls in CL2 Winter closure (Fri 2027-12-24 to Sun 2028-01-02). Which date stands?
F11. S28 Spring term 2028: the add/drop deadline falls on Sat 2028-01-22, a non-working weekday. Which date stands?
Also noted
No repeated identical rows. No proposal is dated before today. Closed days that no checked date falls on: CL1 Harvest recess, CL3 Spring recess.
Draft for the Registrar's confirmation. No date has been chosen, and no record, notice or page has been changed, sent or published.
Where it fits
- Operations and process improvement, where a dated calendar is a process that needs a check before it goes out.
- Project and delivery, where dated windows that depend on one another are tracked to a fixed outcome.
- Education, where the registrar publishes the year, term and session dates that students, departments and communications rely on.
- Government, where public schools and colleges publish a calendar that others plan around.
- Established businesses, for a company that runs its own school or training academy and assembles the dates from several offices.
What has to change for your company
Name your own units: year, term, session, or whatever your institution calls them. Decide which dates each kind of unit must have; the defaults are a start. Decide the order rules you accept: for example, whether registration may stay open after classes begin, and whether add and drop must come before withdrawal. Supply your closed days and non-working weekdays. Say who confirms intentional overlaps, such as staggered sessions. It runs in ChatGPT, Claude, Copilot or Gemini, from files you supply; it needs no connection to your student system.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example, on an earlier wording of the instructions, in Claude on 10 November 2026, and the record is published with it; that run saw the example's header counts early, which the record says. It has not been tested in a client environment or as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past year the registrar knows well, plus cases written in advance with the expected result: a withdrawal date proposed twice, a term with no grade deadline, a session that ends after its term, a deadline on a closed day. The registrar checks every date against the files before anyone relies on the draft. Spreadsheet check before sharing covers the same habit for any file that others will rely on.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: