Educator Preparation Program Management Software: Placements, Dispositions and the Accreditation Evidence Nobody Can Find in March

March of the self study year, and the evidence is in four systems

Your accreditation report is due and you need three cycles of data on candidate performance at each checkpoint, disaggregated by programme, with evidence that your assessment instruments are used consistently. The observation scores are in one platform. The placement records are in a shared spreadsheet the field office maintains. Dispositions live in a folder of scanned forms because the concerning ones were handled by a committee that met in a conference room. Licensure recommendations are in the state's portal, which you cannot query.

So two people spend six weeks assembling it, and the number they produce is defensible but not reproducible: nobody could regenerate it next month and get the same figure. Then the cycle closes, everyone exhales, and the same exercise is scheduled for three years later.

The stakes justify the attention. Educator preparation programmes are the gateway to licensure, accredited by CAEP or a state equivalent, and losing approval closes the programme. States publish report cards on completer performance, and federal Title II reporting adds its own annual obligation. Meanwhile the day to day operation, placing hundreds of candidates in schools that owe you nothing, is a relationship business that runs on a coordinator's memory.

Placement is a matching problem with capacity limits and a clearance gate

Placing a candidate requires a district that is currently accepting placements, a school within reasonable travel distance, a cooperating teacher who holds the right certification and meets your experience criteria and has agreed to take someone this term, a university supervisor with capacity in that geographic cluster, and a grade and subject match for the licensure area.

Then the constraints tighten. Districts cap how many candidates they will take, sometimes per building and sometimes per principal's discretion. Partnership agreements specify their own requirements. Some districts require their own onboarding on top of yours. And a strong cooperating teacher is a scarce resource everyone wants, which is why placement coordinators guard their relationships like the assets they are.

The gate underneath all of it is clearance: background checks, fingerprinting, tuberculosis screening in some states, mandated reporter training, and required testing before a candidate may enter a classroom. Every one of these expires. A candidate cleared in September of the junior year is frequently not cleared for a spring placement eighteen months later, and the discovery happens on day one at the school, which costs your programme credibility with a partner you cannot afford to annoy.

A build turns this into a solvable assignment problem with hard gates: no placement confirmation without current clearances, no assignment to a cooperating teacher who has exceeded capacity, no supervisor assignment that breaks the travel radius you agreed to pay for. What it produces beyond the schedule is a partnership view: how many candidates each district took over five years, which schools produce strong outcomes, and which cooperating teachers your candidates consistently rate highly.

Assessment instruments are the accreditation evidence, and consistency is the claim

Your programme has checkpoints: admission to the programme, admission to clinical practice, mid clinical, exit, and sometimes a first year follow up. Each has instruments, usually a mix of observation rubrics, key assessments embedded in courses, a performance assessment such as edTPA where your state uses it, and required testing.

The accreditation question is not whether you have scores. It is whether the instrument measures what you claim, whether raters apply it consistently, and whether you act on the data. That means the system has to store item level scores rather than totals, so you can look at an individual rubric indicator across programmes and across raters. It means you need calibration records: which supervisors were trained on this instrument, when, and how their scoring compares with the group on the same evidence.

Programmes that can show rater agreement data have a materially easier accreditation conversation than programmes that show only means, and almost nobody has it because the underlying systems store the total.

Dispositions are the part that ends up with a lawyer

A candidate is chronically late to placement, dismissive with a cooperating teacher, or shows a pattern of judgement that concerns faculty. Dispositions exist to handle exactly this, and they are the most legally sensitive records a college of education keeps, because acting on them can end someone's career path before it begins.

Handled properly, a disposition concern is a dated record with a specific observed behaviour, an author, a notification to the candidate, a documented meeting, a written improvement plan with checkpoints, and a decision with an appeal path. Handled the usual way, it is an email chain plus a memory of a hallway conversation, which is exactly what does not survive contact with a grievance.

This is also where the system must be careful about visibility. A concern filed by one instructor should not be broadcast to every faculty member, and the design needs explicit role scoping with an audit trail on access. Build it as an append only record with amendments rather than edits, for the same reason as any other consequential file: the value is that it could not have been rewritten afterwards.

Licensure recommendation is a transaction, and it is the last mile

At the end, your programme certifies to the state that a completer is eligible for a licence. The mechanics vary by state, running through portals such as New York's TEACH system or the Illinois Educator Licensure Information System, and the recommendation typically requires programme completion, required testing, and clearances, all verified.

Most programmes do this by hand, which is fine at fifty completers and painful at six hundred. The build should assemble the eligibility packet automatically, flag exactly what is missing per candidate in April rather than in July, and keep the recommendation record for the years afterwards when a district or another state asks you to verify it. State portals rarely offer a usable interface for bulk submission, so plan for a prepared file or a supervised submission rather than a fully automated pipeline, and be sceptical of anyone who promises otherwise.

What Watermark Tk20, Anthology Chalk and Wire and LiveText do, and where they stop

These are the established products in this category, and the market has consolidated: Watermark now carries both Tk20 and LiveText, and Chalk and Wire sits under Anthology. They are genuinely strong at assessment collection, rubric based scoring, portfolio management, and accreditation reporting aligned to standards frameworks. If your central problem is aggregating key assessment data against CAEP standards, they were built for that job.

Where they stop is the operational half. Placement as a capacity constrained matching problem, with district partnership limits, cooperating teacher eligibility and capacity, supervisor travel clusters, and clearance expiry gating, is thin across the category, which is why almost every field office in the country runs a parallel spreadsheet. Cooperating teacher relationship history, including stipends and district agreements, generally is not modelled. Disposition workflow with formal notification, improvement plans, appeal paths, and access auditing tends to be lighter than the legal exposure warrants. And integration with the university student information system, the learning management system (LMS), and state licensure portals is where the seams show. Products give you the assessment warehouse. The field office is where the work happens, and it is usually unautomated.

What a custom build has to include

• Placement as a constrained assignment problem, covering district and school capacity, cooperating teacher eligibility and load, supervisor travel clusters, and licensure area matching
• Clearance tracking with expiry driven gating, so a placement cannot be confirmed with lapsed requirements
• Cooperating teacher and supervisor records with certification, training, capacity, stipend history, and candidate feedback over time
• Checkpoint assessment capture at item level, from mobile devices in school buildings with poor connectivity
• Rater calibration and agreement analysis across supervisors and instruments
• Disposition workflow with dated observations, notification, improvement plans, appeal path, role scoped visibility, and access auditing
• Evidence aggregation mapped to accreditation standards, reproducible on demand rather than assembled per cycle
• Licensure recommendation packets with automated eligibility checking and retained records
• Title II and state report card data preparation from the same underlying records
• Integration with the student information system, the learning management system, and any performance assessment vendor your state requires

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape. A first release covering placement with clearance gating, checkpoint assessment capture, and standards aligned evidence aggregation runs $65,000 to $140,000 and ships in 12 to 18 weeks. We build placement first because it is where staff time is burning today and because it produces the partnership data nobody currently has.

A full platform adding disposition workflow, cooperating teacher management with stipends, licensure recommendation, and Title II preparation runs $180,000 to $420,000 over 7 to 13 months. Cost rises with the number of licensure areas, since each carries its own checkpoints, instruments, and state requirements. It rises for programmes operating across state lines, where clearance requirements, testing requirements, and recommendation processes all differ. It rises with integration count, particularly if your student information system is an older on premise installation without usable interfaces. It falls if you accept the existing assessment platform as the warehouse for now and build the field office layer around it, which is a reasonable staged approach and often the fastest path to relief.

Build versus buy, stated plainly

Buy if you place fewer than about 150 candidates a year in one or two licensure areas within a single state, with a stable set of partner districts. Tk20 or Chalk and Wire will carry the accreditation reporting, and a coordinator with a good spreadsheet will carry placements without drama.

Build when two or more of these are true. You place more than roughly 400 candidates a year, at which point placement becomes a genuine optimisation problem rather than a scheduling task. You operate across more than one state, so clearance, testing, and recommendation rules differ per candidate. You run many licensure areas with materially different checkpoint structures. Your last accreditation cycle required weeks of manual evidence assembly that nobody could reproduce. You have had a disposition decision challenged and found the record thin. Or you are a large system or consortium of preparation programmes where per campus rules and central reporting have to coexist.

How to choose a developer for educator preparation software

Ask them to model a placement in front of you. Cooperating teacher capacity, district level caps, supervisor travel radius, and clearance expiry should all appear as constraints without prompting. If they draw a candidate table joined to a school table, they will build you a directory and the field office spreadsheet will survive the project.

Ask how the system handles a clearance that expires between confirmation and the start of the placement, which happens constantly. The answer must include proactive alerting on a horizon you choose and a block at the point of start, not a report someone reads later.

Ask how a disposition record is protected. Role scoped visibility, access auditing, append only storage with amendments rather than edits, and a defined retention period are the minimum. A developer who treats it as a form with a comments field has not understood what this record is for.

Ask specifically what they will do about state licensure portals. The honest answer usually involves prepared files and supervised submission rather than a clean interface, and a developer who claims full automation without having seen your state's system is guessing.

Ask who owns the code, the data, and the cloud accounts, in writing, before kickoff. Candidate assessment and licensure records must remain producible for many years, including when another state asks you to verify a recommendation from a decade ago. At Digital Heroes the institution owns the repository and the data from the first commit.