Your format, not ours.
The draft lands in your .docx or .xlsx with styles, tables, and branding untouched.
Your template.
Your playbook.
Drafted for you.
Upload the Word or Excel template your firm already uses and teach the agent how your team fills it in. Specset drafts the safety plan, QC plan, proposal section, or closeout form from the project record, with the formatting intact and every value cited.
MERIDIAN MARINE CONTRACTORSSafety Management System · SMS-DIV-04
REV 0Site-Specific Dive Safety Plan
Ridgeview Center Marine Terminal · Contract C-22141 · Project Description
Diving operations support fender pile replacement at Pier 4, Berths 12–14, performed from a spud barge within the active vessel traffic envelope.
2 · Site Conditions and Hazards
Tidal currents to 2.1 knots; maximum planned depth –42 ft MLLW at the fender line. All dives surface-supplied per 01 35 33 §3.2.
3 · Dive Team
RoleAssignmentCert
Dive supervisorR. AlvarezADCI
Diver 1M. OkaforADCI
Emergency musterNeeds your input—
D7fx=COUNTIF(E3:E6,"NCR")
1QUARTERLY QC REPORT · Q3 2026 · RIDGEVIEW CENTER
2DateFeature of workSpec §ResultNCR
307-08Fender pile driving, Berth 1231 62 00PASS—
407-15CIP concrete, pile caps03 30 00PASS—
507-22Coating DFT, splash zone09 97 13FAILNCR-012
608-02Cathodic protection anodes26 42 13PASS—
723 inspections22 pass1 NCR
Every value has a source.
Content is pulled from the conformed project record and keeps its citation.
A draft, not an autopilot.
Ungroundable fields are flagged for a person. Your team edits and signs.
Trusted by the teams delivering public work
“The safety plan that took two days now takes an hour, and it cites the spec better than we did.”
2.6M+Pages read into project records
50+Organizations running Specset on public work
01 · How a draft is built
Template in, playbook once, drafts forever.
Specset separates what never changes, the format and the playbook, from what changes every project, the record. That is why the second project takes minutes.
01 · Your templateQuarterly QC Report.docxParsed
field Project name, contract no., reporting period
table Inspection log · repeating rows
field Narrative summary · multi-paragraph
Upload the .docx or .xlsx your firm already submits. Specset reads its fields, tables, and repeating sections without changing the format.
02 · Your playbook
Saved as a skill
“Pull inspection results from the daily reports. Summarize non-conformances by section. Keep the narrative under one page.”
Teach the agent how your team fills it in, once, in plain language. The playbook becomes a skill anyone can run with a slash command.
03 · Drafted from the record
14 fields drafted · cited
Inspection log · 23 rows
2 items need your input
Every value is pulled from the specifications, drawings, submittals, and logs, with the citation kept. Anything the record cannot ground is flagged, never invented.
02 · What teams draft
One skill per deliverable your firm repeats.
If your team produces it on every project from the same template, it is a candidate. These are the ones running today.
Site-specific safety plans
Dive safety plans, fall protection plans, and activity hazard analyses drafted from the contract requirements and site conditions.
Safety template + record→Pre-con submittal
Bid proposal sections
Approach narratives, past-performance writeups, and compliance matrices assembled against the instructions to bidders.
Proposal shell + RFP→Draft sections
Quality control plans
Definable features of work, inspection schedules, and testing requirements pulled from every governing section.
QC template + specs→Project QC plan
Closeout & warranty forms
O&M transmittals, warranty letters, and turnover certificates filled from the approved record as the job closes.
Owner forms + record→Closeout package
Progress & QC workbooks
Excel templates with repeating rows filled from logs and schedules. Formulas and formatting survive the draft.
.xlsx template + logs→Filled workbook
Agency & permit forms
Recurring owner and agency paperwork drafted from the same record, in whatever format the agency mandates.
Agency form + record→Draft for signature
03 · Where it runs
A slash command, wherever your team works.
Skills run inside Specset, and the same tools are reachable from the systems your project already lives in.
/quarterly-qc-reportAnyone on the project runs the skill from the agent thread. The draft lands with citations and open items.
Procore · Autodesk CCThe record stays synced with the platforms of record, so drafts pull from live project data.
MCP · Specset CLIThe same skills and tools are callable from MCP clients and the command line for scripted workflows.
Common questions
What teams ask about document generation.
01What file formats can it draft into?
Word documents and Excel workbooks. Specset parses the fields, tables, and repeating sections in your .docx or .xlsx and drafts into them directly, so styles, headers, logos, and formulas come through untouched.
02Where does the content come from?
The project record: specifications, drawings, submittals, RFIs, schedules, and logs, conformed into one governing set. Every drafted value keeps its citation, and anything the record cannot ground is flagged for your input instead of invented.
03How does the agent learn how we fill in a document?
You describe it once in plain language: what to pull, how to summarize, what to leave for a person. That playbook is saved as a skill alongside the template, so the next project runs the same deliverable with a slash command.
04Can it handle documents we produce on every project?
That is the point. A skill pairs one template with one playbook and runs against whichever project record you point it at, so recurring deliverables like QC plans, safety plans, and closeout forms stop being retyped from the last job.
05Who reviews the draft?
Your team, always. The output is a draft with citations and open items, not a finished submission. Reviewers edit in the document they already know, resolve the flagged fields, and sign as they do today.
06Is our template or playbook shared with anyone else?
No. Templates and skills belong to your organization, and customer data never trains models. Skills can be shared across your own projects and teams as broadly or narrowly as you choose.
Start with one deliverable
Bring the template you dread retyping.
Send a recent project and the document your team produces every job. We'll set up the skill and return the draft, cited and in your format.