RFIs should start as drafts, not guesses

Construction teams do not need an agent that invents certainty. They need an assistant that captures the issue, connects it to the right drawing, and leaves the accountable people with a clear draft to review.

Breeks treats an RFI as a durable project record first. The agent can help assemble the draft from chat context, recent drawings, comments, and project metadata, but the record itself belongs to the Breeks system of record.

The workflow that matters

• Retrieve project context before acting.
• Draft the RFI with status draft.
• Search candidate drawings with metadata and semantic search.
• Link the likely document with a visible reason.
• Ask for confirmation when confidence is low.

This keeps the agent useful without turning it into a hidden source of truth. Every write has a tenant, project, actor, permission check, and audit event.

Why the draft state matters

RFIs carry commercial and contractual weight. A draft gives the site team speed while preserving review. The agent can remove the blank-page problem, but the project team still decides what gets issued.