1. Open the tool
   Download a fresh copy of the school care plan generator file from SharePoint each time, then double-click it. Downloading it fresh means you are always on the current version, not an old copy left in Downloads. It opens in your browser and runs offline; nothing is sent anywhere and the child’s data never leaves your device.
2. Start the plan
   Click Start New Plan for a new child. To update an existing plan (for example at the annual review), first download that child’s saved working file (.json) from their SharePoint folder, then click Open Existing Plan and choose it.
3. Complete it, top to bottom, and sign
   Fill the sections in order: child and centre details; the three build choices, diabetes type, then therapy, then glucose device (incompatible devices grey out on their own); the ICR and correction factor on MDI plans; the three hypo carbohydrate sources; any additional information. Last, enter your name and the date in the sign-off at the bottom.
4. Build plan
   Click Build plan and read the finished plan through.
5. Remove any sections the child does not need
   Each section that is not clinical-core shows a red × Remove button at the top right of its heading. Click it to drop any section that does not apply to this child; click it again to bring the section back. Do this before you save, because removed sections carry through to the school copy, so the school sees only what applies. The core sections (the child’s details, the contacts, the diabetes overview, hypoglycaemia, hyperglycaemia and the sign-off) have no button and cannot be removed; a diet-only child has no hypoglycaemia section automatically.
6. Save the editable working file (the patient file)
   Click Save editable file (.json, reopen here). This is the editable working file that holds the patient details and reopens in the tool. It lands in your Downloads; upload it into the child’s SharePoint folder so next year’s review starts from it.
7. Save the school copy, both formats, and send both
   Click Save school copy (.html, hand to school), then click Save school copy as PDF (signed, reliable export). Always save and send both to every school: the .html gives them the live carbohydrate calculator, and the PDF is a fixed, reliable copy that opens correctly even when a school’s own browser or printer struggles with the .html. Upload both into the child’s SharePoint folder, then send both to the school securely.

The three copies, in one line. The .json reopens in the tool and is fully editable (keep it in the patient record). The .html is the school’s live copy, with the clinical content locked and the carb calculator working. The .pdf is a fixed, reliable copy for schools whose own setup cannot render the .html properly; send it alongside the .html every time, never instead of it. All three are named with the child’s surname, first name and date.

Three save buttons on the built plan. Left to right: Save editable file (.json, reopen here), Save school copy (.html, hand to school), then Save school copy as PDF (signed, reliable export). The .json stays in the patient record; the .html and the PDF both go to the school, every time, not one or the other.

Where the files live: SharePoint. The tool cannot reach SharePoint itself; it only reads and writes files on your own device. So the pattern is always the same three moves: download from SharePoint, work in the tool, then upload the results back to SharePoint.

• To upload: open the child’s folder in SharePoint in your browser and use its Upload button to add the new .json working file and the new school .html and PDF.
• Same file name? If a file with that name is already in the folder, SharePoint asks whether to Replace it or Keep both. Choose Replace: it saves your file as the latest version and keeps the earlier ones in the file’s version history. This is normal SharePoint behaviour and needs no special technique.
• Optional shortcut, only if it is already set up for you: if the child’s SharePoint folder is synced to your PC (it shows up in File Explorer under OneDrive), you can save straight into that folder and skip the manual upload. Most staff do not have this, so treat download-then-upload as the normal way.

Sign as you fill it in, before you build. Saving is locked until the plan is both signed and built. Save all three for every child: the .json for next year’s review, the .html and the PDF for the school today.