TypezoAppendix A
The run and the limits.
This is the part a proposal manager asks about after the walkthrough: how a run moves from upload to export, and what the tool will not do. The security rider and data handling are on the security page.
One requirement
through the files.
A requirement can cite one file, or two. The line runs from the sentence through every file it uses, and the answer names the page.
Sample path, shown complete. Some requirements cite two files.
Offerors must show an active SAM.gov registration, a CAGE code, and three relevant contracts from the past five years.
Offerors must hold commercial general liability insurance.
Name the project manager and provide a current ISO/IEC 27001 certificate.
Our SAM.gov registration is active and our CAGE code is 8QK41.
SAM-Registration-2026.pdf, p. 1
We completed three federal facilities contracts since 2022.
Past-Performance-Summary.pdf, p. 4
Commercial general liability is $2,000,000 per occurrence, valid through 30 June 2027.
Insurance-Certificate.pdf, p. 2
The project manager reports to the Director of Operations.
Org-Chart.pdf, p. 1
ISO/IEC 27001, acquired 12 March 2024, valid.
ISO-Certificate.pdf, p. 1
Upload
The solicitation and the company files are parsed once.
Extract
Every requirement stays in document order.
Check
A quote must be on the cited page, or the row is a gap.
Export
A clean matrix and draft leave only when the check passes.
A run, from upload
to export.
The pipeline is deliberately unromantic. Parse once. Extract in document order. Draft only against stored spans. Then let a deterministic verifier decide whether the result may leave.
Upload once. The parser sets the pages.
PDF, DOCX and XLSX are parsed into pages and stored spans at upload. Page numbers and character offsets come from the parser, never from a model. Scanned pages are marked as OCR with lower confidence. A run never re-parses.
one parse · page-anchored spans · OCR marked · no model coordinates
Extract every requirement, in document order.
Each obligation is pulled out with its section and page, then typed mandatory or optional. The matrix follows the solicitation’s order, always. Classification is fail-safe: a clause the extractor cannot place stays in the result for review; it is not dropped to make the run look cleaner.
document order · mandatory | optional · no reordering · review stays review
The verifier decides, not the model.
A deterministic Go verifier runs after the draft and before anything is visible. It re-checks every quote against stored page text, every page against the parser, and every number, date and dollar figure against a cited quote. The model never grades its own work.
quote substring · page match · numeric grounding · verdict pass | fail | not_run
Two files. No clean export if it failed.
A clean run exports the compliance matrix (XLSX) and the requirement-by-requirement draft (DOCX). A failed run becomes needs_review and its export is watermarked. There is no clean export of an unverified run.
XLSX matrix · DOCX draft · assembled on demand · watermark on fail
What the verifier refuses.
- A citation page does not match the parser’s page.
- A quote is not a verbatim substring of the stored page text.
- An answered requirement has no citation.
- A missing requirement has no gap row.
- A number, date, percentage or dollar figure has no supporting quote.
- A citation points at a document that failed or was deleted.
What it will
not do.
Typezo does one part of a bid, the part where an answer has to stand on a document, and refuses the parts that would turn it into a proposal mill.
Write the narrative.
Executive summaries, win themes and past-performance volumes are not generated. Answers are drafted requirement by requirement; the narrative stays with your team.
Guess.
If a requirement has no supporting span, it stays missing and the matrix gets a gap row. Nothing is invented to make coverage look better.
Claim FedRAMP, CMMC or SOC 2.
Typezo does not hold any of them. If your questionnaire requires one today, this is not the right vendor, and this page will not imply otherwise.
Run on your servers.
There is no self-hosted install. Each customer runs on a dedicated instance that we operate, under one key per tenant.
Invent a help desk answer.
If no published article supports the question, there is no answer and no summary of something close enough. The question opens a ticket in the tenant-wide queue instead.
What it
does.
The narrow job, done with page references you can open. If a bid needs a narrative or a certification we do not hold, that work stays outside this tool.
Read the solicitation.
Every requirement is extracted with its section and page, in document order, from a parse that happens once at upload.
Draft with a citation.
Every sentence in an answer points to a stored span, or the requirement is explicitly marked missing with a gap row.
Verify before export.
A deterministic verifier re-checks quotes, pages and numeric claims after the model finishes. The model never grades its own work.
Export the working documents.
A compliance matrix (XLSX) and a requirement-by-requirement draft (DOCX). No narrative sections, no submission to a procurement portal.
Keep the document on its own instance.
One dedicated instance, one per-tenant KMS key, and no training on customer documents, by us or by a provider.
Answer from the same knowledge base.
The tenant-wide help desk retrieves published article spans and drafts a cited answer. A tender selects a subset of collections; a daily question uses every published collection.
Hand the question to a person.
No verified evidence means a ticket, with the requester and the originating workspace as context. Members see their own tickets, agents see the queue, admins manage the knowledge base.