Turn one thing you observed into bite-sized feedback your direct report can act on this week.
Free edition · School Registrar · Core Job Functions
The Operations Feedback Generator turns one thing you observed into a piece of written coaching feedback. It produces four parts: what you observed, why it matters, what your direct report should do next, and what you will look for on your next visit. You choose one indicator, enter the observation, or the details of the observation, and edit the draft the generator returns.
This is the free edition. It covers the five Core Job Functions indicators for the School Registrar. The full Operations Feedback Generator inside the Charter School Operations System covers all twenty-one Registrar indicators across five domains, and the system itself covers twelve operations roles.
Nothing you type leaves this page. There is no account and no sign in, and nothing you write is stored or transmitted.
This tool is for the manager who oversees an operations role in a school. That is usually the director of operations, the school leader, the business manager, or an operations manager at a network office. It is written for the manager who gathers the evidence and writes the feedback, not for the direct report being evaluated. You do not need to have been trained on a rubric to use it, because the wording you need is already written into each entry.
Use it within a day or two of observing something, while the details are still specific enough to write down. One entry covers one indicator and one occasion. Though some managers save feedback for the end of a cycle, at Growth MindED we believe it should be written the same week, because a direct report can only act on something that is still fresh. The entries you write serve as written feedback that is used across the year as the objective record of data and trends you bring to the mid-year and end-of-year evaluation.
Feedback to operations staff is often given in passing, in a hallway, and it disappears before anyone acts on it. The purpose is to support the growth and development of the person you manage, by making feedback specific enough to act on, written enough to return to, and short enough to give every week. The purpose is not to document a concern for a personnel file, and it is not a substitute for the mid-year or end-of-year evaluation.
When feedback stays verbal and general, the direct report cannot tell what to change, and the manager arrives at the end-of-year evaluation conversation with subjective feedback rather than an objective record of data and trends shared over time.
The first entry takes about ten minutes. After that, most take about five.
Written from a blank page, one piece of feedback takes close to twenty minutes, and much of that time goes to finding words for why the thing matters and what you will check next. The generator supplies the why and the look-fors, so your time goes to the one part only you can write, which is what you actually saw or found.
Accuracy comes from the same place. The wording of each indicator is taken from the rubric the direct report is scored on, so the feedback you give in October is written in the same language as the score you give in June. A direct report who reads the two side by side sees one standard rather than two.
That is also what makes accountability data driven rather than subjective. The direct report leaves with a written action step and a stated list of what you will look for, so the next visit is clear, with previously aligned look-fors.
| Word | What it means here |
|---|---|
| Indicator | One named expectation in the rubric for a role, such as Student Records Accuracy and Integrity. |
| Domain | A group of related indicators. This free edition covers one domain, Core Job Functions. |
| Bite-sized feedback | One piece of written feedback about one indicator, short enough to give weekly and specific enough to act on within a week. |
| Evidence | What you actually saw, heard, or counted, written with a date and without interpretation. |
| Action step | The one thing you are asking the direct report to do before your next visit. |
| Look-for | Something you will be able to see on your next visit that tells you whether the action step happened. |
Domain: Core Job Functions
One indicator per entry. Stay on the same indicator until the practice is consistent.
Strong evidence carries a date, a quantity, or a quotation, and describes one moment rather than a pattern.
Edit anything. The Why, How, and look-fors start from the bank and should be adjusted to your school's own systems and names.
If it is vague, it is not bite-sized. A person should be able to do this tomorrow without asking a follow-up question.
This generator gets better because people who use it say what was off. If an entry did not fit what you saw, or the action step would not work in a real front office, say so.
The Charter School Operations System carries a performance rubric for each of twelve operations roles, a written standard for how to write bite-sized feedback, a feedback bank with one written entry for every indicator, an annual calendar, walkthrough tools, a scoring guide, and manager training. This generator is one piece of it, scoped to one domain of one role so that you can try the method this week.
If it works, the full set is at growthmindedconsulting.com. If it does not, Step 5 above is where you tell me why.