Service

Legal advice portal development

For the directors and service managers of advice charities, legal networks, trade union legal services and membership helplines who need questions triaged, matched to the right adviser and answered within a controlled, private workflow.

The problem

What goes wrong today

Where it usually starts

An advice service usually starts with an email address and a rota.

  • Questions arrive in a shared inbox, a coordinator reads each one, guesses the category and forwards it to whichever adviser seems free.
  • Urgent questions, such as an eviction notice with a hearing next week, sit behind routine ones because the inbox is sorted by arrival.
  • Two advisers sometimes answer the same question; others go unanswered because the forwarded email was buried.

Where it gets harder

Advisers keep their own notes and attachments on their own machines, so when one leaves, the history of a member's question goes with them.

  • Guidance documents live in a folder with no record of which jurisdiction they cover or when they were last reviewed, and advisers paste from out-of-date versions.
  • Members who pay a subscription cannot see what they have asked before or what was answered.
  • When a funder asks how many questions were answered in each category, and by whom, the coordinator spends a week counting emails.

Scope of the service

What the build covers

A custom advice portal build normally covers:

  • Question submission with category and urgency triage With the urgency rules set by the service
  • An adviser pool With specialism matching and workload limits so nobody holds more open questions than the service allows
  • Private question threads between asker and adviser With controls on what attachments are permitted
  • A guidance library With jurisdiction and review-date metadata so an adviser is warned when a document is past review
  • A public anonymised archive Where answers can be published after moderation and redaction
  • Credit or subscription access for askers
  • An escalation path from a written answer to a booked consultation
  • Tracking of how long each question waits at each stage Reported per adviser and per category

We begin by watching a week of questions arrive and following five of them to their answer: who read them first, how urgency was judged, who answered, and what guidance they used. Those become named stages: ask, triage, assignment, answer, optional consultation, archive.

Deliberately out of scope

  • The legal content of the answers, which stays with the advisers
  • Case management for matters that go beyond a question, which belongs in a practice system
  • Automated answering

When the scope grows

Scoping scenario

A membership organisation with an in-house team of four advisers and an external panel of thirty volunteers needs questions in employment and housing to go to in-house staff first, overflow to the panel after a set time, panel answers reviewed by staff before release, and member credits deducted only when an answer is released. The two-tier pool with review-before-release is what makes it a custom build.

Deliverables

What you receive

  • Discovery notes from following a week of questions through the current process
  • A scope document naming each question stage, the triage and assignment rules and what is out of scope
  • Design of the asker's question form, the adviser's queue and the moderation screen on mobile and desktop
  • The build, deployed to your hosting or ours, with private threads and role permissions from the first release
  • Migration of guidance documents, adviser profiles and member accounts, where relevant
  • Training for coordinators, advisers and moderators, with a written guide per role
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to the current inbox, guidance folder, adviser rota and membership list, with a coordinator as the named contact.

    Project stage: Onboarding
  2. Planning

    Sessions with the service manager, a coordinator and two advisers to define categories, urgency rules, pool tiers and review steps; scope document agreed.

    Project stage: Planning
  3. Design

    Clickable designs of the question form, the adviser queue, the thread and the moderation screen, tested with a volunteer adviser.

    Project stage: Design
  4. Development

    Built in stages: categories and triage first, then the adviser pool and threads, then the guidance library and archive, then credits and consultation escalation.

    Project stage: Development
  5. Client review

    The service runs a fortnight of real questions in parallel with the inbox and compares assignment, waiting times and answer quality.

    Project stage: Client review
  6. Revisions

    Changes to triage rules, workload limits and moderation steps from the review are made and re-checked against the scope document.

    Project stage: Revisions
  7. Ready for launch

    Guidance library loaded with review dates, member accounts migrated, archive moderation tested, launch checklist signed off.

    Project stage: Ready for launch
  8. Delivered

    New questions arrive through the portal only; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Membership databases so member status and entitlements drive access
  • Card payment and subscription billing providers for credits and plans
  • Booking and video platforms for escalated consultations
  • Email and SMS providers for notifications that never include the question content
  • Single sign-on for organisations whose members already have accounts elsewhere
  • Reporting tools funders or boards already use, fed by anonymised exports

How we would approach it

Worked example

Concept demo

A membership helpline with in-house advisers and a volunteer panel

The situation

A membership organisation with four in-house advisers and thirty volunteer panel members wanted employment and housing questions answered in-house first, passed to the panel after a time the service sets, and panel answers reviewed by staff before members saw them.

Why it is a custom build

The reason this needs a custom build is the overflow and review logic; a generic ticketing tool assigns to a queue and stops there, which leaves the service managing the panel by hand.

The scope we would propose

  • A two-tier adviser pool with per-tier workload limits
  • An overflow rule per category
  • A review step that holds panel answers until a staff member releases them, credits deducted at release rather than at submission
  • A dashboard showing waiting time at each stage per tier

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of advisers, whether they are in-house, external or both, and tiering between them
  • Categories and urgency rules, and whether triage is manual, rule-based or mixed
  • Access model: free, credits, subscription or membership-linked
  • Review-before-release and moderation requirements
  • Size and condition of the guidance library to migrate with jurisdiction and review dates
  • Public anonymised archive and the redaction workflow it needs
  • Consultation escalation and the booking and video platforms involved
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

When is a custom build the right choice?

When your adviser pool, access model or review steps go beyond what the legal advice portal package handles with configuration. During discovery we lay your week of questions against the package and tell you plainly whether tiers, overflow rules or funder reporting need custom work.

Does the portal give legal advice itself?

No. Every answer is written by a human adviser. The system triages, assigns, holds the thread, warns about out-of-date guidance and records what happened; it never generates advice.

How is the asker's privacy protected?

Threads are private between the asker and the assigned adviser, with moderators able to see what the service decides they should. Notifications carry no question content. Publishing to the archive requires moderation and redaction, and the asker can be given the choice to opt out.

Can waiting times be reported per adviser?

Yes. The system records when a question entered each stage and who held it, so the service can see waiting time per adviser, per tier and per category. What target the service sets for itself is its own decision; the build reports against it rather than promising a figure.

Who owns the system afterwards?

The organisation does. Source code and data are handed over at delivery; hosting and maintenance are optional, separately agreed and movable to another provider.

Get a project quote for legal advice portal software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote