Give your team an operating manual that answers back.
The right procedure is buried in documents and chat.
Est. deploy 2–4 weeksSee the walkthrough
Knowledge & Internal Tools · Education
Find the current school policy with a citation.
Staff share outdated handbook copies.
For: School administrators and the team responsible for knowledge & internal tools in education.
01 · The outcome
What good looks like.
The team has a cited administrative answer for staff verification, with source evidence and an explicit approval before any external action. Track policy answers backed by current sources against a baseline; do not assume automation improves it.
A connected workflow that uses current approved handbook, revision history, and access rules to retrieve the relevant clause and flag conflicts between school and program policies. It produces a cited administrative answer for staff verification.
Where AI helps, and where a person decides.
AI can retrieve the relevant clause and flag conflicts between school and program policies. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The school administrator verifies the source facts and approves the final action.
School administrator is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- School administrator: Capture the source and scope
- School administrator: Review the proposed outcome
- School administrator: Release only the approved version
- School administrator: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A staff member asks a handbook question. Connect only current approved handbook, revision history, and access rules. The school administrator confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to retrieve the relevant clause and flag conflicts between school and program policies. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a cited administrative answer for staff verification against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: School administrator has recorded approval or a reason to hold the item.
After explicit approval, save a cited administrative answer for staff verification in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review policy answers backed by current sources each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=education-policy-finder
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- EDUCATION-POLICY-FINDER-DEMO-001
- Trigger
- A staff member asks a handbook question.
- Owner
- School administrator
- Prepared output
- a cited administrative answer for staff verification
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Policy answers backed by current sources
Start with your tools.
Connect Student information system, Google Workspace, Admissions CRM through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
- Follow applicable student-record privacy rules, including FERPA where relevant. Verify guardian authority, minimize student data, and leave eligibility and safeguarding decisions to qualified staff.
Try this week / no DAVID required
A useful first step.
This week, have your school administrator time five examples of this work. Use redacted copies of current approved handbook, revision history, and access rules to make a cited administrative answer for staff verification manually, then list which fields required judgment.
What to measure.
- Policy answers backed by current sources
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Find the current policy with its source.
Staff rely on outdated policy attachments.
Est. deploy 4–6 weeksSee the walkthrough
Find approved menu answers during service.
Staff guess when menu details change.
Est. deploy 2–4 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.