[{"data":1,"prerenderedAt":203},["ShallowReactive",2],{"marketing-site-en":3,"articles-en":4},null,[5,88,144],{"id":6,"title":7,"author":3,"body":8,"category":72,"cover":3,"coverAlt":73,"description":74,"draft":75,"extension":76,"featured":77,"locale":78,"meta":79,"navigation":77,"path":80,"publishedAt":81,"seo":82,"slug":85,"stem":86,"translationKey":85,"updatedAt":81,"__hash__":87},"article\u002Farticles\u002Fen\u002Fconnected-student-record.md","Why a connected student record changes daily school operations",{"type":9,"value":10,"toc":65},"minimark",[11,15,18,23,26,29,33,36,55,58,62],[12,13,14],"p",{},"A student's information usually enters a school through admissions, but it rarely stays inside the admissions office. Academic teams need class placement and prior records. Finance needs the correct fee structure. Transport may need a route. Teachers need an accurate class list, while guardians expect attendance, results, and notices to refer to the same child.",[12,16,17],{},"When each department keeps a separate version, staff spend time reconciling names, identifiers, classes, and balances. The cost is not only administrative. A correction made in one sheet may never reach another team, and families lose confidence when two departments provide different answers.",[19,20,22],"h2",{"id":21},"start-with-ownership-not-software","Start with ownership, not software",[12,24,25],{},"A connected record works only when the school defines who may create, verify, update, and view each kind of information. Admissions may own the initial identity and application evidence. Academic staff own placement and progression. Finance owns charges and receipts. Those responsibilities should be reflected in permissions rather than handled through shared administrator accounts.",[12,27,28],{},"The system should preserve a clear school and campus context around every action. A connected platform does not mean unrestricted access; it means governed handoffs.",[19,30,32],{"id":31},"design-the-handoff","Design the handoff",[12,34,35],{},"Map the important transitions before migration:",[37,38,39,43,46,49,52],"ul",{},[40,41,42],"li",{},"inquiry to submitted application;",[40,44,45],{},"verified application to active student;",[40,47,48],{},"class placement to assigned fee structure;",[40,50,51],{},"attendance or result publication to guardian visibility;",[40,53,54],{},"withdrawal to finance, library, and transport clearance.",[12,56,57],{},"For each transition, record the trigger, responsible role, required evidence, and expected next state. This creates a testable implementation plan and prevents the new platform from reproducing old ambiguity.",[19,59,61],{"id":60},"measure-the-practical-result","Measure the practical result",[12,63,64],{},"Useful measures are operational: fewer duplicate records, fewer unresolved mismatches, shorter admission processing, and fewer manual corrections after class or branch changes. Review exceptions with the teams doing the work. A connected student record succeeds when staff can explain where the information came from, who changed it, and which workflow uses it next.",{"title":66,"searchDepth":67,"depth":67,"links":68},"",2,[69,70,71],{"id":21,"depth":67,"text":22},{"id":31,"depth":67,"text":32},{"id":60,"depth":67,"text":61},"Operations","Connected school departments around one student record","A practical look at the handoffs between admissions, academics, finance, and family communication.",false,"md",true,"en",{},"\u002Farticles\u002Fen\u002Fconnected-student-record","2026-08-02",{"title":83,"description":84},"Connected student records for school operations","How one governed student record reduces repeated entry and broken handoffs.","connected-student-record","articles\u002Fen\u002Fconnected-student-record","TKMOdgcWkWYeE7fcpJ7U8OzN0v8imUUONLkIG_QU4zU",{"id":89,"title":90,"author":3,"body":91,"category":133,"cover":3,"coverAlt":134,"description":135,"draft":75,"extension":76,"featured":75,"locale":78,"meta":136,"navigation":77,"path":137,"publishedAt":138,"seo":139,"slug":140,"stem":141,"translationKey":140,"updatedAt":142,"__hash__":143},"article\u002Farticles\u002Fen\u002Ffee-reconciliation-checklist.md","A school fee reconciliation checklist that teams can actually use",{"type":9,"value":92,"toc":127},[93,96,100,103,107,110,114,117,120,124],[12,94,95],{},"Day closing should answer a simple question: can the school explain every amount collected, the method used, the student balance affected, and any reversal or adjustment? A single total cannot provide that evidence.",[19,97,99],{"id":98},"before-collection-begins","Before collection begins",[12,101,102],{},"Confirm that cashiers have individual accounts, the correct campus scope, and only the permissions required for collection. Review active fee structures and payment methods. If discounts or reversals require approval, test that workflow before a busy period begins.",[19,104,106],{"id":105},"during-the-day","During the day",[12,108,109],{},"Receipts should be issued from the system and tied to the student and assigned charge. Avoid temporary identifiers and shared cashier accounts. Record the payment method at the time of collection. An exception should remain visible until a responsible role resolves it; it should not disappear through an informal edit.",[19,111,113],{"id":112},"at-closing","At closing",[12,115,116],{},"Compare the system total by payment method with the evidence for that method. Review cash, bank transfers, cards, and other configured channels separately. Inspect reversed receipts, partial payments, discounts, and manual adjustments. A difference should produce an assigned follow-up item with an explanation, not merely a changed total.",[12,118,119],{},"Keep student fee collection separate from the school's software subscription billing. They involve different payers, obligations, approval paths, and records.",[19,121,123],{"id":122},"after-closing","After closing",[12,125,126],{},"Lock or clearly mark the closed period according to policy. Produce a concise report showing totals, exceptions, approvers, and unresolved items. The goal is not more paperwork. It is the ability to reconstruct what happened without relying on one person's memory.",{"title":66,"searchDepth":67,"depth":67,"links":128},[129,130,131,132],{"id":98,"depth":67,"text":99},{"id":105,"depth":67,"text":106},{"id":112,"depth":67,"text":113},{"id":122,"depth":67,"text":123},"Finance","Finance team reviewing school fee receipts and reconciliation","Turn day closing from a last-minute total into a controlled review of receipts, methods, and exceptions.",{},"\u002Farticles\u002Fen\u002Ffee-reconciliation-checklist","2026-07-24",{"title":90,"description":135},"fee-reconciliation-checklist","articles\u002Fen\u002Ffee-reconciliation-checklist","2026-07-30","-wTTFGlx0t96nOp_2YLrMKIlf3L_0Vp3lqnlAAN8U1M",{"id":145,"title":146,"author":3,"body":147,"category":192,"cover":3,"coverAlt":193,"description":194,"draft":75,"extension":76,"featured":75,"locale":78,"meta":195,"navigation":77,"path":196,"publishedAt":197,"seo":198,"slug":199,"stem":200,"translationKey":199,"updatedAt":201,"__hash__":202},"article\u002Farticles\u002Fen\u002Fsaas-isolation-questions.md","Questions to ask about isolation in a school SaaS platform",{"type":9,"value":148,"toc":186},[149,152,156,159,163,166,169,173,176,180,183],[12,150,151],{},"\"Multi-tenant\" describes a business model, not a sufficient security control. A school evaluating a SaaS platform should ask how the system identifies the school, selects data connections, scopes storage and cache, enforces authorization, and controls operational access.",[19,153,155],{"id":154},"what-happens-before-sign-in","What happens before sign-in?",[12,157,158],{},"The platform should determine the intended school from an exact, verified host before tenant authentication begins. Ask what happens when a host is unknown, malformed, or belongs to the control plane. Fail-closed behavior matters because a fallback to the wrong school is more dangerous than a clear not-found response.",[19,160,162],{"id":161},"where-do-models-connect","Where do models connect?",[12,164,165],{},"Ask whether school records rely on a shared default connection or whether the request selects a dedicated school database connection. Control-plane models should remain explicit about their landlord connection even while tenant requests change the default used by the original ERP models.",[12,167,168],{},"The same question applies to background jobs. A web request may resolve the correct school while a queued task later runs without that context unless the job carries and restores it safely.",[19,170,172],{"id":171},"what-else-is-scoped","What else is scoped?",[12,174,175],{},"Database separation is only one boundary. Review storage roots, cache keys, sessions, generated URLs, and uploaded files. Check whether each component changes and reverts when the active school changes, especially in long-running workers.",[19,177,179],{"id":178},"how-does-support-work","How does support work?",[12,181,182],{},"Operators should not receive implicit access to school data. A support session should be justified, approved where policy requires, limited in time and scope, visibly identified, and recorded for review.",[12,184,185],{},"Finally, ask about suspension, cancellation, export, recovery, and deletion. Good isolation includes lifecycle behavior: one school's status change must not affect another, and payment failure should not silently destroy educational records.",{"title":66,"searchDepth":67,"depth":67,"links":187},[188,189,190,191],{"id":154,"depth":67,"text":155},{"id":161,"depth":67,"text":162},{"id":171,"depth":67,"text":172},{"id":178,"depth":67,"text":179},"Security","Separate school databases connected through controlled tenant resolution","A practical review guide for host resolution, databases, storage, authorization, support access, and lifecycle controls.",{},"\u002Farticles\u002Fen\u002Fsaas-isolation-questions","2026-07-12",{"title":146,"description":194},"saas-isolation-questions","articles\u002Fen\u002Fsaas-isolation-questions","2026-07-28","yJ5Xh_O2NKb9OJwddDLGuaQ3MBXu7D3hOd_Z6eXJyjk",1786509989896]