DCRFI coordination

One record from issue to site instruction

Each item stays linked to what caused it, who answered it and the drawing it refers to.

What you can track

  • Issues

    Log blockers by discipline, package and zone, with owners and due dates.

  • RFIs

    Raise questions from issues, attach evidence, and send them for a formal answer.

  • Decisions

    Keep each answer in a decision log, along with the documents behind it.

  • Submittals

    Track review records with linked source evidence.

  • Changes

    Record what changed, and why, against the issue that caused it.

  • Site instructions

    Issue instructions that stay linked to the decision behind them.

  • Programme

    See schedule activities alongside the coordination items affecting them.

  • Meetings

    Capture actions and generate packs from live project data.

  • Documents

    Register drawings and versions. Older revisions are flagged when replaced.

How it keeps work moving

  • One trail from issue to site

    Every RFI, decision, change and site instruction stays linked to the issue that caused it and the drawing it refers to.

  • My work, reminders and escalation

    Everyone sees what is overdue and due this week across projects. A daily digest chases owners, and stuck items escalate to the project lead.

  • Consultants answer with one link

    Send the architect or engineer a private link. They answer without an account, and the answer lands in your decision log.

  • Superseded drawing warnings

    Anyone about to reference an out-of-date revision is stopped and asked why, before it reaches site.

  • Meeting packs

    Agendas are built from overdue RFIs, decisions needed and open actions. Export the pack as PDF, CSV or JSON.

  • AI-drafted RFIs

    Turn an issue and its drawing reference into a clear RFI draft. You always review it before it is sent.

Try it on a sample project

Free for your first project. No card needed.

Start free