One recent analysis found that the average school accessed nearly three thousand distinct edtech tools during a year, with the figure for the typical district even higher. Meanwhile, updated rules under the federal children's privacy law and ongoing attention to student records have made schools more careful about which vendors may collect and store information from minors. Student writing is some of the most personal data a school holds, because essays contain opinions, family stories, and sometimes details about health or home life.

Despite this, many teachers have adopted writing tools on their own, such as grammar checkers, drafting platforms, discussion boards, and feedback apps. Each tool may be reasonable by itself, but nobody has a complete picture of where student writing travels, who can access it, and how long it is kept. Without a map, a school cannot answer a parent who asks where a child's essay is stored or who has been able to read it.

An audit does not need to be a major project. A small team can map the tools that handle student writing in a few weeks, and the result gives the school a clear basis for deciding what to keep, what to replace, and what to explain to families. Starting with writing is sensible because it is the category where the most personal student information tends to appear, and a focused scope keeps the project from stalling.

Start by listing every tool that stores or processes writing

Ask each department to list the tools students use to draft, submit, or receive feedback on writing, including free browser extensions and tools that teachers use on their own accounts. Compare the list to the district's approved software inventory and to network logs, if available. The gaps between what is approved and what is actually used are usually the most revealing part of the exercise.

• List every tool that stores or processes student writing
• Ask what data each tool collects, stores, and shares
• Check whether vendors use student work to train models
• Sort tools into keep, change, and retire groups
• Publish a plain-language list of approved tools for families

Ask a consistent set of questions about each tool

For each tool, find out what student data it collects, where it is stored, who can access it, and how long it is kept. Check whether the vendor uses student work to train models, whether it shares data with third parties, and whether it can delete records on request. Record the answers in a simple table so that the team can compare tools side by side.

Confirm that the vendor has signed the district's data privacy agreement where one is required, and that parental consent is handled correctly for younger students. If the answers are unclear, treat that as a signal. A vendor who cannot explain its data practices in plain language is a risk for a school, and that uncertainty alone can be reason enough to pause a rollout until the questions are answered.

Decide what to keep, replace, or retire

Sort tools into three groups: approved and necessary, acceptable with changes, and not acceptable. Tools that duplicate each other can often be retired in favor of one well-vetted option. Fewer tools also reduce training burdens for teachers and make it easier to support students who need help, since every additional platform adds another login, another interface, and another set of settings to explain.

When replacing a tool, communicate early with teachers and offer a short training. Abruptly removing a tool that teachers rely on will push them toward unapproved alternatives. Pair the change with a clear explanation of the reasons, including what risk was found, what the replacement offers, and exactly when the old tool will stop working, so that no teacher is surprised halfway through a unit with essays already in progress.

Tell families what you found and what you decided

Publish a plain-language list of the writing tools the school uses, what each one does, and what data it handles. Families appreciate transparency, and it builds trust that the school takes student work seriously. Include a contact for questions and a process for opting out where the law allows, and update the page whenever a tool is added or removed so that it stays accurate.

Repeat the audit annually and whenever a new tool is proposed. Establish a simple request form so that teachers can ask for a tool to be reviewed before they begin using it. Where a school evaluates a rubric-based feedback product, the same checklist applies: ask where the writing goes, who sees it, and what the vendor does with it, and ask the same questions of every vendor so the comparison stays fair.