Skip to main content
Loading...
content

Legal Team Hub

The Legal Team Hub is a five-page intranet site that helps employees decide when to involve Legal, prepare a question, find approved guidance, and locate a contact. Clone it to give staff a clear starting point while keeping intake routes, materials, and coverage grounded in your confirmed processes.

Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Technology and software · Manufacturing · Financial services · Professional services

Overview

The Legal Team Hub is a five-page intranet site that gives employees an orientation path for working with an in-house Legal team. The landing page points to four tasks: understand when to involve Legal, prepare a request, find approved templates and guides, and look for a contact. A separate Contracts callout distinguishes contract work assigned to the Contracts app from other Legal questions without inventing an app link or intake workflow.

The supporting pages make the handoff more useful. “When to Involve Legal” offers prompts such as proposed commitments, unclear terms, formal notices, and questions about sensitive information, then asks employees to describe the issue, gather relevant material, and choose the verified route. “Request Help” helps employees state the pending decision, add relevant context, and use approved sharing methods. “Templates & Guides” explains that materials must be current and approved for the user's role, location, and purpose. “Contacts” uses a connected employee-directory block, with a clear warning that a listing alone does not establish responsibility for a matter.

Use this template when employees need a common starting point and the Legal team can confirm service scope, routes, coverage, and authoritative materials. Before launch, configure the directory source and replace the fictional Northstar example with verified organizational guidance. Do not use the sample as legal advice, a substitute for formal escalation procedures, a contract intake system, or a published policy before those details are confirmed. Keep each authoritative process or document in its designated system and link to it only when the destination is available.

Standards & compliance context

  • Treat the Northstar service descriptions and scenarios as fictional examples, and have the Legal team confirm scope and escalation rules before presenting them as organizational guidance.
  • Do not describe the hub as legal advice or as a replacement for approved procedures, formal notices handling, or applicable professional review.
  • Direct employees to organization-approved channels for confidential documents and confirm any records, privacy, or jurisdiction-specific requirements with the appropriate internal owners.
  • Use accessible page headings, descriptive link labels, and readable contrast consistent with WCAG 2.1 AA when configuring the site.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Legal Team

  • Legal Team Hub
    A starting point for Northstar employees who need to work with Legal, wherever they work. Use this hub to understand when to involve Legal, prepare a request, find shared guidance, and identify a contact. Northstar is a fictional example; confirm actual service scope and routes before publishing.
  • Choose your next step
    Go directly to the page that matches your task. When to Involve Legal Review situations where early Legal input may help. Request Help Prepare the context Legal may need to understand your question. Templates & Guides Learn how to use approved Legal materials. Contacts Look for Legal colleagues in the connected directory.
  • What Legal may help with
    Illustrative service areas only. Confirm the team’s actual scope and location coverage before publication. Contract questions Legal may help clarify review needs and contract-related questions. Use the Contracts app for contract work designated for that app. Check Contracts for the current workflow and status of contract work. Raise a question if the agreement, parties, or requested terms are unclear. Legal questions about work Questions involving legal obligations, proposed commitments, or a situation that may affect Northstar may need Legal input. The appropriate route depends on the issue and Northstar’s confirmed process. Share relevant facts and the decision or deadline you are working toward. Use the Request Help page to prepare information for your question.
  • Contract work happens in Contracts
    Use the Contracts app for the contract workflow Northstar has configured there. Contracts is the app name; this example does not supply an app URL. Open Contracts to start or continue contract work. Follow the app’s instructions for the applicable workflow and required details. If you are unsure whether your matter belongs in Contracts, review When to Involve Legal or use the verified Legal contact route.

When to Involve Legal

  • When a question may need Legal input
    Use these examples as prompts to check the right route, not as a complete statement of Northstar policy. Consider involving Legal when a work decision could create a legal commitment or when you are unsure how a legal obligation applies. Northstar’s actual escalation rules and coverage must be confirmed before using this example as policy. Before agreeing to terms: a customer, supplier, landlord, or other party asks Northstar to sign an agreement, accept new terms, or make a written commitment. When terms are unclear: a contract contains a clause, requested change, or obligation you do not understand. When a dispute or formal notice arrives: you receive a claim, demand, regulator communication, or other formal notice that may require a legal response. When handling sensitive information: a proposed sharing, use, or retention of information raises a legal question. For contract work designated for Contracts, use that app. If you are unsure whether an issue is covered there, use the verified route described on the Request Help or Contacts page.
  • Prepare a clear question
    A few concrete details help the right person understand what you need. Describe the issue State what happened or what decision is pending, who is involved by role or organization, and where the work applies. Gather relevant material Have the current agreement, notice, draft, or other relevant document available through Northstar-approved systems. Share only information needed for the question. Choose the route Use Contracts for contract work assigned to that app. For other Legal questions, follow Northstar’s verified request route or contact guidance.
  • Choose the right route
    Use the matching page or app for your next step. This page is general orientation, not legal advice or a substitute for Northstar’s approved procedures. For non-contract questions, start at Request Help and follow the verified Northstar route. For contract work, open the Contracts app and follow its current instructions.

Request Help

  • Prepare a useful Legal request
    Use Northstar’s verified intake route for non-contract questions. Do not send confidential material through an unapproved channel. Before contacting Legal, write a short description of the question and the decision you need to make. Include the relevant location or work group, the parties involved, key dates, and any deadline that has been communicated to you. Attach or identify the current document or notice using Northstar-approved sharing methods. Separate confirmed facts from assumptions or open questions. Say what action has already been taken and who is waiting for the next decision. For contract work assigned to Contracts, use that app’s workflow rather than treating this page as a separate contract intake process. This example does not promise a response time or outcome.
  • Before you send a question
    Use this short check to make the handoff easier to understand. State the decision Write what needs a decision or clarification and what action is waiting. Add the context Include the relevant location, parties, dates, and approved source documents; distinguish facts from assumptions. Use the verified route Use Contracts for contract tasks assigned to that app. For other matters, follow Northstar’s approved Legal intake route once confirmed and published.
  • Find a Legal contact
    Check the Contacts page for configured directory information and verified contact guidance. Northstar must verify and publish any intake or escalation route. This example does not assume a Legal request form is available. Look for a Legal colleague in Northstar’s connected employee directory on the Contacts page. If the directory does not identify the right route, follow Northstar’s confirmed internal escalation guidance.

Templates & Guides

  • Use current, approved materials
    A template is a starting point, not confirmation that a document or approach fits every situation. Use only materials Northstar has approved for your role, location, and purpose. Check each item’s instructions, intended audience, and stated limits before relying on it. If a material is missing, appears out of date, or does not fit the situation, ask through Northstar’s verified Legal route rather than adapting it as if it were approved. For contract work, use the Contracts app and its current workflow. This page does not replace contract records or instructions in that app. Setup for this fictional example: authoritative templates and guides have not been supplied. Add approved files only after confirming their audience, owner, and review trigger.
  • Start contract work in Contracts
    Use the app configured for Northstar’s contract workflow. Do not rely on an unverified copy of a template. Open Contracts for contract work and follow the instructions available there. Use this page for approved guidance only after Northstar has connected the authoritative materials.

Contacts

  • Find the right Legal contact
    Coverage can differ by issue, location, and employee group; confirm Northstar’s contact guidance before relying on it. Use the connected directory below to look for Legal colleagues by name or job title. A directory listing can help identify a person, but it does not by itself establish responsibility for a particular issue or location. If you cannot determine the right contact, follow Northstar’s verified internal escalation guidance. Publish a shared contact route and coverage information only after confirming them with the Legal team.
  • Search Northstar’s employee directory
  • If you are unsure who owns the question
    Use verified Northstar guidance rather than guessing a contact or escalation route. Setup needed: configure the directory source, confirm which Legal colleagues should appear, and publish verified general contact and escalation guidance. For contract work, use Contracts and follow the workflow shown in the app. For other Legal questions, use the intake or escalation route Northstar has confirmed and published.

How to use this template

  1. Clone the site and replace the fictional Northstar name and sample language with organization-specific details confirmed by the Legal team.
  2. Confirm which matters belong in the Contracts app, establish the verified route for other Legal questions, and publish escalation guidance for cases employees cannot route themselves.
  3. Add only authoritative templates and guides after confirming each item's audience, owner, approved location, and review trigger.
  4. Configure the employee-directory source and verify which Legal colleagues should appear, while explaining that directory results do not determine matter ownership.
  5. Review every page link, app reference, scope statement, and sharing instruction with the relevant owners before making the site visible to employees.
  6. Assign a content owner to check the hub when routes, materials, directory coverage, or team responsibilities change, and correct stale guidance promptly.

Best practices

  • Keep the landing page focused on the four employee tasks and preserve the distinction between Contracts work and other Legal questions.
  • State the audience, location coverage, and limits of Legal services only when the team has confirmed those facts.
  • Tell employees to separate confirmed facts from assumptions and identify the decision or deadline waiting for action.
  • Direct employees to share documents through approved systems and avoid asking them to include more sensitive information than the question requires.
  • Publish only approved, current materials and show each item's intended audience and review trigger where available.
  • Treat directory search as a way to find colleagues, not as proof that a person owns a particular issue or location.
  • Give each process and authoritative document one maintained home, linking to it from relevant pages rather than copying competing instructions.
  • Check the site after changes to intake routes, Contracts instructions, directory configuration, or team coverage, and remove links that no longer work.

What this template typically catches

Issues teams running this template most often surface in practice:

Employees may mistake an illustrative service area for a complete promise of Legal coverage.
A generic or missing intake route can leave employees unable to act after preparing a question.
Contract work may be submitted through an informal channel instead of the Contracts app designated for that work.
An unverified template or copied guide may be used beyond its approved audience, location, or purpose.
A directory result may be mistaken for confirmation that the listed colleague owns the employee's issue.
Confidential documents may be sent through an unapproved channel when sharing instructions are unclear.
Outdated scope, app instructions, or directory entries can undermine otherwise useful navigation.
Long explanations can bury the immediate next step if the page's task links and route guidance are not kept prominent.

Common use cases

Procurement manager preparing supplier terms
A procurement manager can use the hub to distinguish contract work assigned to Contracts from a question about unclear terms, then gather the current agreement and pending decision. The template directs the manager to follow the configured workflow rather than implying that the hub itself submits a request.
People operations lead handling a formal notice
A People operations lead can recognize a formal notice as a situation that may need Legal input and prepare the relevant facts, dates, and document through approved sharing methods. The organization's verified escalation route must be published before this guidance is relied on.
Regional operations employee checking sensitive information use
An operations employee can use the prompts to identify a question about sharing, using, or retaining information and note the relevant location and decision. The hub does not determine local legal requirements, so coverage and routing must be confirmed by the Legal team.
Legal operations owner publishing approved guidance
A Legal operations owner can use Templates & Guides as the entry point for authoritative materials, adding them only after confirming audience, ownership, and review triggers. The page warns employees not to treat an unverified copy as approved.

Frequently asked questions

Who is this Legal Team Hub for, and what questions does it cover?

It is an employee-facing orientation site for people who need to work with an in-house Legal team. Its pages explain situations that may need Legal input, how to prepare a question, where approved materials belong, and how to look for a contact. The examples are not a complete statement of any organization's service scope or policy.

Does the template provide legal advice or determine whether Legal must be involved?

No. It gives employees practical prompts for recognizing questions that may need Legal input, but it does not decide whether a matter requires review. Replace the fictional Northstar guidance with confirmed internal policy and escalation rules. Employees should use their organization's approved procedures for urgent or formal notices.

How often should the Legal Team Hub be reviewed?

Review it whenever the Legal intake route, Contracts workflow, approved materials, directory source, or team coverage changes. Set a regular review cadence that matches your organization's content governance, and assign an owner to check the linked destinations and page copy. The template does not prescribe a review interval or claim that its sample content has been verified.

Who should own and run this hub?

A Legal team content owner should confirm service scope, escalation guidance, approved materials, and contact coverage before publication. An intranet or site administrator can configure navigation and the employee-directory connection. The Legal owner should coordinate corrections with the people responsible for Contracts and directory data.

What regulatory or compliance requirements does this template satisfy?

The template is an orientation structure, not a legal compliance certification or substitute for approved procedures. Its sample copy cautions users to share confidential material only through approved channels and to use current, role- and location-appropriate guidance. Have the appropriate internal reviewers confirm any regulatory, jurisdictional, records, or confidentiality requirements before publishing.

What should we customize before employees use the site?

Replace the fictional Northstar references with confirmed organization-specific scope, locations, routes, and escalation guidance. Add only approved templates and guides, identifying their audience, owner, and review trigger. Confirm the Contracts app instructions, configure the directory source and included Legal roles, and remove or revise any example that does not match actual practice.

What integrations or live content does the template include?

The Contacts page contains an employee-directory block that requires a configured directory source and confirmation of which Legal colleagues should appear. The site refers to Contracts by name but does not include a Contracts app URL or establish a technical integration. Quick links connect the site's own pages; do not treat them as links to systems that have not been configured.

How is this different from sending employees to a general Legal inbox or asking them to contact someone they know?

The hub gives employees a shared starting point, separates contract work from other questions, and explains what context to prepare before using a verified route. It also provides a designated home for approved guidance and contact lookup. It does not replace an inbox, intake system, or escalation procedure; publish those routes only after they are confirmed.

What is the main rollout pitfall to avoid?

Do not publish the fictional examples as if they were verified policy or assume that the directory identifies the right owner for every issue. Confirm each route, scope statement, and linked resource with the responsible Legal owners before launch. Also test the directory block and page navigation so employees are not directed to empty or unavailable destinations.

Go deeper on the topic

Related concepts
  • A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Legal Team Hub ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.