One Request, One Route: Reducing Duplicate Work Across School Teams
When facilities, vendor, and policy requests arrive through separate channels, teams can end up asking for the same information or acting on the same issue twice. A shared intake and explicit routing rules give school leaders a practical way to make ownership visible and work easier to follow.
Start by finding where requests split
Duplicate work often begins before anyone starts the task. A staff member emails a principal about a broken door, submits a facilities form, and mentions it in a team meeting. Each route may be reasonable on its own, but together they can create multiple records, repeated follow-up, or uncertainty about who is responsible.
For one week, note the kinds of requests that cross team boundaries. Look at facilities issues, vendor questions, and requests to review or clarify a policy. Record where each request arrived, what information was missing, who responded, and whether another team was already handling it. Do not start by trying to measure every minute spent. First identify the handoffs that cause confusion.
For example, a request to replace a classroom lock may involve a school office, facilities staff, and a vendor. The useful question is not simply, “Where should people submit this?” It is, “What information does the first recipient need, and who owns the next decision?”
Define one front door without forcing every task into one team
A shared intake process gives staff a predictable starting point. It does not mean every request should be handled by the same person. Choose a primary route for incoming work, then identify the team that should own each type of request after initial review.
Keep the intake questions short and useful. For a facilities request, ask for the location, a plain-language description, urgency, and a contact person. For a vendor matter, capture the vendor, the school or department involved, the request, and any relevant deadline. For a policy question, ask which policy is involved, what decision or clarification is needed, and who is affected.
Avoid asking staff to choose from a long list of specialist categories they may not understand. If people are unsure whether a matter is a facilities issue or a vendor issue, let them describe it in ordinary language and have the intake owner route it. A shared process should reduce guesswork, not move it to the person submitting the request.
When considering OnwardSync, treat it as a workspace for school operations planning and coordination. Map the intake questions and handoffs your team needs, then confirm how your intended process should be represented in your actual setup. For a broader look at the product context, visit school operations software.
Make routing rules visible and specific
A routing rule should name a first owner, a next step, and a fallback. “Send vendor questions to operations” is too vague if no one knows who reviews them or what happens when that person is away. “The operations lead reviews new vendor requests, assigns a department contact, and identifies an alternate reviewer when unavailable” is more actionable.
Write rules for the work that most often crosses boundaries:
• **Facilities:** Who reviews the request, and how are urgent safety concerns surfaced through the school’s established process? • **Vendor work:** Who confirms the internal sponsor, tracks the open question, and coordinates follow-up with the vendor? • **Policy work:** Who determines whether a question needs interpretation, a policy review, or simply a link to existing guidance?
Keep ownership separate from consultation. A facilities lead may own a repair request while a school administrator provides context. A policy lead may coordinate a review while affected teams contribute. Naming one accountable owner prevents several people from assuming someone else will close the loop.
Use a short checklist at handoff
A consistent handoff helps the receiving team act without restarting the conversation. Before routing a request, check that it has:
• A clear description of the work or decision needed. • A school, department, location, or vendor identified where relevant. • A named first owner and a stated next step. • A priority or requested-by date when one has been provided. • A place to note who needs an update and when to follow up.
For instance, instead of forwarding “Can someone look at this?” with an old email chain, send a concise handoff: “Facilities request: north entrance door does not latch; submitted by the main office; facilities lead to review; office manager needs an update after assessment.” The point is not a particular software format. It is a record that makes the next action clear.
If your school tracks compliance work alongside operations, establish how policy-related requests connect to the relevant deadline and owner. See compliance and deadline tracking for related planning context; do not assume a general intake process replaces your established compliance procedures.
Review the process, then take one next action
A shared intake route is a working agreement, not a one-time announcement. After a few weeks, ask staff and request owners where submissions still get lost, which questions are unnecessary, and whether requests are reaching the right team. Adjust the routing rules when responsibilities change, and tell staff what changed so old habits do not quietly return.
Start with one request type that regularly crosses team boundaries, such as vendor work connected to a facilities issue. Name the intake owner, write the route and fallback in plain language, and agree on what counts as a complete handoff. Then test that process with real incoming work before expanding it to policy requests or other categories.
Your next action: bring the people who receive these requests together for a 30-minute mapping session. Choose one recurring request, trace its current path from first message to close, and leave with a single front door, a named owner, and a clear next step. You can explore more operational ideas in the Onward blog.
Common questions
Does shared intake mean every request goes to the same team? No. It means staff have a predictable way to submit work. Routing rules can send different requests to the appropriate facilities, vendor, or policy owner after intake.
What should a school do first to reduce duplicate requests? Choose one recurring request type, map how it currently arrives and moves between teams, then agree on a first owner, a fallback, and the information needed for a useful handoff.