Future Vanguard GovernmentWhen the manuals disagree, it says so
Two provisions that give different values for the same case are shown side by side, each with its page and quoted passage. Nobody has to find out about the conflict three weeks into construction.
Working software, live nowOpen the demo (opens in a new tab)
Every answer from your manuals, with the page to check.
Spec Assistant gives your staff and your public a plain-language answer from the standards, procedures and drawings you already publish, and names the section and page behind it. Where the manuals do not say, it says so and points to a person.
- Section and page on every answer
- Your Azure tenant, US only
- Okta SAML for administrators
Spec AssistantReal demo output
What is the minimum cover over a water main?
Searching the manuals
The minimum cover over all water mains is 4½ feet below final grade. 12
Standards, section 5.04 (page 47)1
Standards, section 11.03 (page 80)2
Shown as the live demo returned it, on public Aurora Water manuals effective January 15, 2026.
What is the minimum clearance for a stormwater and sanitary crossing in ROW, with minimum pipe sizes?
Questions that span two manuals are a built-in sample prompt in the demo. Run it and read the answer and its sources yourself.
Run it in the live demo (opens in a new tab)What is the maximum ponding depth in a parking lot?
Conditions and exceptions is another built-in sample category. Run it live and check the cited page.
Run it in the live demo (opens in a new tab)The demo runs on public City of Aurora Water manuals to show what the software does. It is not a City of Aurora service, and Aurora is not our customer.
Product video, no sound needed
See it in 90 seconds
What Spec Assistant does and how it works: from your manuals to a cited answer, and what your team controls behind it.
Built and operated by Future Vanguard LLC
- Woman-owned
- U.S.-owned and operated
- Active in SAM.gov
- UEI HQ1GXJ6RXJ86
- CAGE 230T9
The public chat
A good answer you cannot check is a liability.
So the receipts come with it. Residents, contractors and staff ask in plain words and get the answer, the sources and the original page, in one view.
- 1
Ask the way you would ask a colleague
No codes to remember and no keyword guessing. Sample questions get a new visitor started.
- 2
Numbered citations, section and page
Each answer names where it came from, and the exact excerpt opens beside it with the passage highlighted.
- 3
One tap to say it helped, or did not
Feedback goes straight to an administrator's review queue. It is how the library gets better.
The live demo as it answered, on public Aurora Water manuals.
What it reads and what it does with it
Text, tables, drawings, and the places they disagree.
The same engine serves the counter, the field and the person who keeps the library current.
Reads the drawings, not just the text
Standard detail sheets are read as images, so a question about bedding, backfill or a manhole detail is answered from the sheet itself and cited by sheet and page.
Standard details and drawingsWhat bedding is required for reinforced concrete pipe?
One of the sample questions built into the live demo.
- Text
- Tables
- Detail sheets
- Cross-references
Compares across manuals
A question that spans two documents returns one answer with both sources.
Try it the live demo (opens in a new tab)Surfaces the exceptions
Conditions and limits that apply to a rule come with the rule, not three pages later.
Try it the live demo (opens in a new tab)Declines, then hands off
If the manuals are silent, it says so and points to the person who can help.
See who keeps it current
Administration
A new manual never goes live by accident.
Administrators upload to staging, read a validation report, and a second person approves before anything changes for the public. If something is wrong after launch, one action rolls it back.
- Uploaded
- Staged
- Validated
- Pending approval
- Approved
- Scheduled
- Active
- Retired
A validation report before approval
Document health, what changed from the live version, whether every citation still points at a real page, a regression run of replayed questions, and a scan for contradictions.
Two people, by design
The person who uploads cannot approve. Editor, approver, analyst and administrator roles are checked on every route.
One-action rollback
Return to the previous version immediately, with the reason recorded.
An audit log that shows edits
Every action is recorded in a chained log, so a change to history is visible, and exportable.
Analytics and the feedback loop
Learn what people ask, and fix what they could not find.
Every question that ends in a thumbs-down or a referral becomes a review item, not a lost visit.
A visitor flags an answer
Wrong citation, missing information, or no answer.
It lands in the review queue
An administrator sees the question, the answer given and the sources.
The fix is a visible change
An approved answer or a library update, never a silent change inside a model.
Reports show the effect
Most-asked questions, no-answer rate, satisfaction and cost per question, with CSV and JSON exports for Power BI.
Deployment
It runs in your tenant. Your data stays in the United States.
No shared multi-customer platform. We build it inside the Azure subscription you control, and you pay Azure consumption directly under your own agreement.
Your visitors
Your websiteThe chat sits in an iframe on any page you choose
Your staffSign in with Okta SAML to administer
Your Azure tenant, US regions only
Chat service
Search index
Database
Document storage
Key Vault
Private endpoints
East US 2 primary, Central US paired. Services reach each other over private endpoints with managed identity, and public access to them is turned off.
Your Azure tenant, US only
The subscription, the keys and the documents are yours. Data stays in the U.S. Data Zone, and no third-party analytics are loaded.
Okta SAML for administrators
Administrators sign in through your Okta. Roles are enforced again on the server for every request, and access ends when your directory says it does.
An iframe, and you are live
Embed the chat on your existing site with one snippet. Nothing to install on your side.
<iframe src="https://assistant.your-domain.gov/embed"
title="Ask the manuals" width="100%" height="720"></iframe>- Adapts to the frame width
- Light and dark themes
- No third-party scripts or analytics
- Keyboard and screen-reader tested
Security and compliance
Built on controls your security office already knows.
We build to the frameworks your reviewers use, on infrastructure they already trust, and we test what we claim.
Runs on FedRAMP High authorized Microsoft Azure infrastructure
Deployed in your own tenant, with controls aligned with NIST SP 800-53, the FedRAMP baseline.
- Controls aligned with SOC 2 Trust Services Criteria
- TLS 1.2 or higher in transit, AES-256 at rest
- Aligned with the NIST AI Risk Management Framework
- Aligned with ISO/IEC 27001 Annex A
- WCAG 2.2 AA tested
- OWASP Top 10 for LLM applications tested
Sessions are isolated
Each visitor gets a random session token. No endpoint lists sessions, and nothing carries across them.
Roles are enforced
Editor, approver, analyst and administrator roles are checked on every administrator route.
Uploads are vetted
Files with scripts, embedded files, encryption or malformed structure are refused with a readable reason.
Changes leave a trail
Two-person approval, one-action rollback and a chained audit log.
Limits on abuse and cost
Rate limits, a per-session question cap and a daily ceiling that falls back to search-only.
Citations come from the page
Citations are built by the program from the retrieved passages, never typed by the model.
Measured in our own testing
Counts, with the work behind them.
From our own test run on October 15, 2026, against the live demonstration build. The full test record is available on request.
of 280280 of 280
Authorization checks behaved as expected. Five kinds of caller tried 56 administrator routes.
of 195195 of 195
Session-isolation probes found no leak. Token guessing, token changes, parallel sessions and history were all tried.
of 77 of 7
Hostile PDF types refused at upload. Scripts, launch actions, embedded files, encrypted, malformed, wrong type and decompression bombs.
Implementation
From kickoff to a live public assistant in about twelve weeks.
A typical engagement. We confirm the dates with you at kickoff.
- Week 1
Kickoff
Scope, documents, named contacts and access requests. We agree what a good answer looks like using your own sample questions.
- Weeks 1 to 4
Tenant and identity
We build the landing zone in your Azure subscription, connect Okta SAML and set up staging and production.
- Weeks 3 to 8
Library and tuning
Manuals and drawings are ingested and validated. Your test set runs through the same checks an approver will see.
- Weeks 8 to 10
Staff pilot and training
Your staff use it for real. Administrators are trained on upload, approval, rollback and the review queue.
- Week 12
Public launch
The embed goes on your site. Support and monthly reporting continue after launch.
Our approach
Software that earns trust one citation at a time.
Cited, or silent
An answer without a source is not an answer. If the manuals do not support one, the assistant says so and points to a person.
People decide
Staff approve new documents and resolve flagged answers. The software does the reading; people keep the judgment.
Your documents answer your questions
We do not fine-tune models on your documents. Corrections are reviewable changes to the library.
Everyone can use it
Accessibility is tested screen by screen at desktop and phone width, with keyboard and high-contrast passes.
Our offer
Send us one of your public documents. We will show the assistant answering from it.
Pick a manual, standard or procedure you already publish. We load it, and show you the assistant answering your own questions from it, with the page cited. No cost, no commitment.
- 1
You send a public PDF
Anything already on your website.
- 2
We load it
Indexed page by page, drawings included.
- 3
You ask your own questions
And check every cited page yourself.
Your manuals already have the answers. Let’s make them easy to find.
Start with the live demo, then tell us about your documents.