How a workflow earns publication

Evidence labels

Observed means directly present in a supplied dashboard snapshot, the repository, a live response, an exported file, or a checked public source. Inference is a product decision drawn from those observations. Forecast is an assumption-based range and never a promise.

The 16 July 2026 release reused the supplied 21 June–12 July 2026 Google Search Console snapshot: 496 impressions, zero clicks, 0% CTR, and average position 74.6. No Bing baseline was available for this domain, and none is represented as zero. No Ahrefs data or credits were used.

Selection and canonical ownership

1. Use observed job queries and product evidence to identify a distinct operational outcome.
2. Assign one canonical URL to that job; tone and scenario variations stay inside the builder.
3. Retire formulaic or high-risk prototype routes. Redirect only when intent equivalence is real; otherwise return 410.
4. Require a complete field model, example boundary, source list, reviewer scope, safety notice, version, and fixed reviewed date.

Drafting method

The builders are deterministic. They assemble visible, job-specific sections from the values entered in the form; no hidden generative service is called. Blank draft fields remain explicit placeholders. A final file requires server-side validation. Example values are labelled and gated until the user explicitly adopts them as a draft.

Editorial review

The current reviewer label is TemplateNook editorial review. Its scope is operational clarity, conservative wording, field coverage, export parity, and regression testing. It is not a claim of legal, medical, accounting, security, standards-body, or regulatory expertise. Each workflow states the exact boundary next to the builder.

Review checklist

• One job and one canonical owner.
• Required fields match the final document’s real decisions and controls.
• System wording avoids unsupported promises, threats, fees, statutory claims, or compliance claims.
• Preview and exported files use one normalized document model.
• Visible version, reviewed date, change summary, sources, reviewer, and correction route.
• Every labelled action completes or reports a truthful failure.

Export integrity

DOCX and XLSX files are Office Open XML ZIP packages. PDFs use embedded Roboto fonts for selectable Unicode text and are marked as tagged with document language and metadata. XLSX user values are emitted as literal string or typed date cells, never formula objects; workbook tests inspect package parts and reject cell formula nodes.

PDF accessibility target for this release: readable contrast, selectable Unicode text, document title/language metadata, tagged output, logical source order, and clear headings/tables. Full PDF/UA conformance has not been independently certified and is not claimed.

Primary standards and guidance

• ECMA-376 Office Open XML
• Microsoft SpreadsheetML structure
• OWASP formula-injection guidance
• W3C Web Content Accessibility Guidelines 2.2
• Google structured-data policies
• ICO data-protection principles

Corrections and versioning

A correction report receives a reference in restricted deployment logs without collecting an email address. A material correction changes the workflow version, fixed review date, change summary, tests where relevant, and public version history. Cosmetic deploys do not rewrite review dates.