{"id":55062,"date":"2026-08-18T01:08:57","date_gmt":"2026-08-18T01:08:57","guid":{"rendered":"https:\/\/sitemate.com\/?p=55062"},"modified":"2026-08-26T05:15:29","modified_gmt":"2026-08-26T05:15:29","slug":"claude-for-weekly-progress-reports","status":"publish","type":"post","link":"https:\/\/sitemate.com\/au\/answers\/how-to-use-claude-for-weekly-construction-progress-reports\/","title":{"rendered":"Claude for Weekly Progress Reports"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":15,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","rank_math_title":"","rank_math_description":"Connect your project to Claude and it drafts the weekly progress report from the records you already have. You check it against the week, then send it.","rank_math_canonical_url":"","rank_math_focus_keyword":""},"categories":[1],"tags":[],"industry":[],"product":[],"region":[145],"system":[86],"content_type":[170,173],"topic":[],"class_list":["post-55062","post","type-post","status-publish","format-standard","hentry","category-uncategorized","region-global","system-field-reporting","content_type-ai-landing-page","content_type-llm-use-case-page"],"acf":{"ai_lp_breadcrumb":"Topics<\/a>\/<\/span>Field Reporting<\/a>\/<\/span>How to Use Claude for Weekly Construction Progress Reports<\/span>","ai_lp_h1":"Writing your weekly progress report with Claude","ai_lp_intro":"Everything a weekly progress report needs is already recorded somewhere: the daily reports, the inspections, the photos, the delays. The work isn't finding out what happened, it's assembling it into something a client will read. Connect your project to Claude, write the prompt once, and the report comes back every week for you to check, correct and send.","ai_lp_hero_media":"
\"Claude\"Claude<\/div>
Draft the weekly progress report for Northgate Stage 2, week ending 15 August.<\/div>
<\/span>Read 14 records from Northgate Stage 2<\/div>

Northgate Stage 2, week ending 15 August.<\/p>

  • Level 3 slab poured Tuesday, stripped Friday<\/li>
  • Facade install reached grid line 8, two days behind program<\/li>
  • One weather delay Wednesday, six hours lost to rain<\/li><\/ul>

    Two items need your input before this goes to the client.<\/p><\/div><\/div>","ai_lp_body":"

    \n

    The short answer<\/p>\n

    Connect your Dashpivot project to Claude, name the week, and it drafts the progress report from the daily reports, inspections and photos already recorded. Write that prompt properly once and it becomes the weekly one, where only the dates change. You read the draft against the week you had, correct what is thin, and send it.<\/p>\n<\/div>\n\n

    \n

    How to connect Claude to your project<\/h2>\n

    Connecting takes a few minutes and happens once. Your own Dashpivot permissions carry across, so you see what you can already see and nothing more.<\/p>\n<\/div>\n\n

    \n
      \n
    1. \n

      Step 1<\/p>\n

      Turn on MCP access<\/h3>\n

      An Org Controller enables MCP Access in Dashpivot, under Settings then Security. Nobody in the workspace can connect until that is on, so start here rather than in Claude.<\/p>\n <\/li>\n

    2. \n

      Step 2<\/p>\n

      Find the Sitemate connector<\/h3>\n

      Go to Settings, then Connectors, then Add, then Browse connectors. Search for \"Sitemate\" and pick the connector tagged Community.<\/p>\n <\/li>\n

    3. \n

      Step 3<\/p>\n

      Connect and approve<\/h3>\n

      Click Connect, sign in with your Sitemate credentials, and approve the permissions. The connector then appears under Connected.<\/p>\n <\/li>\n

    4. \n

      Step 4<\/p>\n

      Pick it in a chat<\/h3>\n

      Start a new chat, click the + button, choose Connectors, and select Sitemate MCP.<\/p>\n <\/li>\n<\/ol>\n<\/div>\n\n

      \n

      The prompt worth keeping<\/h2>\n

      The prompt is the thing worth building, not the conversation around it. Get it right once and it becomes your weekly report prompt, where the only thing that changes is the dates. One rule matters more than the rest: it queries one form template at a time, so name the exact template, the project and the dates.<\/p>\n

        \n
      • "What workspaces do I have access to? List the projects and teams."<\/li>\n
      • "What form templates are available in [team name]?"<\/li>\n
      • "Pull the [exact daily report template name] forms for [project] between [date] and [date]. Put each one in a table with the date, area and progress."<\/li>\n
      • "From those, draft the weekly progress report for [project] using these sections: [list them]. Write it so I can send it to the client."<\/li>\n
      • "Same prompt, new dates: [project], [start] to [end]. Tell me if any days have no report at all."<\/li>\n<\/ul>\n<\/div>\n\n
        \n

        What goes into a weekly progress report<\/h2>\n

        A weekly progress report tells the client and head office what moved this week, what didn't, and what is about to become a problem. Most formats cover the same ground:<\/p>\n

          \n
        • What moved this week, by area or work package<\/li>\n
        • What didn't, and why<\/li>\n
        • Delays, variations and anything about to become a problem<\/li>\n
        • Progress against program, with the photos that show it<\/li>\n
        • What's planned for next week<\/li>\n<\/ul>\n<\/div>\n\n
          \n

          The report is only as good as the week's records<\/h3>\n

          This is worth being blunt about. Claude reading your project cannot describe work that was never written down, and it won't pretend otherwise. Teams who already keep their daily reports current get a draft that's nearly right. Teams who don't get a short report that accurately reflects a thin week of records, which is its own useful signal.<\/p>\n<\/div>\n\n

          \n

          If the draft comes back thin<\/h2>\n

          The records are the source, so a thin draft is usually a thin week rather than a bad prompt. These are the fixes, in the order worth trying.<\/p>\n

            \n
          • Nothing connects at all:<\/strong> MCP Access is probably still off, and only an Org Controller can turn it on<\/li>\n
          • Sitemate does not appear in the connector list:<\/strong> search "Sitemate" exactly, and look for the Community tag<\/li>\n
          • The connector does not show in a chat:<\/strong> start a new chat, click +, and pick it under Connectors<\/li>\n
          • The draft misses whole days:<\/strong> those days have no daily report. Fill the gap before asking again<\/li>\n
          • Progress cannot be counted:<\/strong> it is written in comments rather than fields<\/li>\n
          • Results look short:<\/strong> it queries one template at a time, so ask for the daily reports and the variations separately<\/li>\n<\/ul>\n<\/div>\n\n
            \n

            Why it takes an afternoon to write<\/h2>\n

            None of that's unknown on Friday. It's all recorded somewhere: in the daily reports, the inspections, the dockets, the photos taken on the walk. The report isn't an act of finding out what happened, it's an act of assembly.<\/p>\n

            That assembly is what takes the time. Site supervisors and project managers compile progress from scattered notes, photos and verbal updates. Things get missed, percentages become guesswork, and the report goes out late or thin. The client sees a gap in visibility. The site sees an afternoon gone.<\/p>\n<\/div>\n\n

            \n

            It's four o'clock on Friday, the report is due to the client Monday, and every fact in it's already sitting in the system somewhere.<\/p>\n<\/div>\n\n

            \n

            What it can and cannot do<\/h2>\n

            The failure mode isn't a badly written report. It's a confident one that nobody checked, sent to a client who will hold you to it. So it is worth being plain about where the line sits.<\/p>\n<\/div>\n\n

            \n

            What it can do today<\/h3>\n

            Connected to your workspace, this is what it can actually reach.<\/p>\n

              \n
            • Read the projects, forms and records you already have access to<\/li>\n
            • Resolve names, roles and register values instead of guessing them<\/li>\n
            • Pull one week from one project, rather than a general summary<\/li>\n
            • Work inside your own permissions, so connecting it widens nobody's access<\/li>\n<\/ul>\n<\/div>\n\n
              \n

              What it cannot do<\/h3>\n

              These limits are the point. A report that reads well and is wrong is worse than a thin one that is right.<\/p>\n

                \n
              • Describe work that was never written down<\/li>\n
              • See anything you cannot see yourself<\/li>\n
              • Change your records. It reads them, it doesn't write to them<\/li>\n
              • Send the report. You check it, and you send it<\/li>\n<\/ul>\n<\/div>\n\n
                \n

                How the record gets there<\/h2>\n

                A report is only as good as the records behind it, so the question worth answering is how they got there in the first place.<\/p>\n<\/div>\n\n

                \n
                  \n
                1. \n

                  Storm captures it on site<\/h3>\n

                  The daily reports, inspections and photos a weekly report is assembled from get captured while the work happens, by voice and photo, rather than typed up later.<\/p>\n <\/li>\n

                2. \n

                  Dashpivot holds it as the record<\/h3>\n

                  Each one lands against its project as a structured record rather than a file, which is what makes a week of them readable rather than a folder to dig through.<\/p>\n <\/li>\n

                3. \n

                  Sitemate MCP reads it back<\/h3>\n

                  Connecting Claude to Dashpivot is what lets it answer from your own records instead of the internet. Your own permissions still apply.<\/p>\n <\/li>\n<\/ol>\n<\/div>","ai_lp_comparison":"","ai_lp_band_heading":"Connect Claude to your Dashpivot data","ai_lp_band_intro":"Sitemate MCP is the access layer between your AI assistant and Dashpivot. It connects ChatGPT, Claude and Microsoft Copilot to your workspaces, projects and forms, so answers come from your own project records instead of a general model's best guess.","ai_lp_capabilities":"

                  \n
                  \n
                  \n
                  \"\"<\/div>\n
                  \n

                  Sitemate MCP<\/h3>\n

                  Connect ChatGPT, Claude or Microsoft Copilot to Dashpivot. Your assistant reads your workspaces, projects, forms and records directly, so the answers come from your own site data instead of a general model's guess. You stop leaving your AI tool to go and look something up.<\/p>\n <\/div>\n <\/div>\n

                  \n
                  \"Sitemate<\/div>\n <\/div>\n <\/div>\n<\/div>\n\n
                  \n
                  \n
                  \"\"<\/div>\n <\/div>\n
                  \n

                  Reads your workspace<\/h3>\n

                  Projects, folders, templates and the forms inside them. Your assistant knows how your work is actually organised, so you can ask about a specific project rather than describing it first.<\/p>\n <\/div>\n<\/div>\n\n

                  \n
                  \n
                  \"\"<\/div>\n <\/div>\n
                  \n

                  Knows your team<\/h3>\n

                  Users and register lists come through as well, so names, roles and list values resolve to the right people and the right options instead of being guessed at.<\/p>\n <\/div>\n<\/div>\n\n

                  \n
                  \n
                  \"\"<\/div>\n <\/div>\n
                  \n

                  Your permissions still apply<\/h3>\n

                  Your assistant only ever sees what you can already see. Every request is checked against your own workspace permissions, so connecting an AI tool does not widen anyone's access.<\/p>\n <\/div>\n<\/div>","ai_lp_faq_heading":"Frequently Asked Questions","ai_lp_faq":[{"question":"Can Claude actually see my project data?","content":"

                  Once your Dashpivot workspace is connected, yes. Claude reads your projects, folders, forms and the records inside them directly, rather than working from whatever you remember to paste into the chat.<\/p>"},{"question":"Do I have to paste records into the chat?","content":"

                  No. That is the difference between this and using Claude without the connection. Pasting is where the errors come from: you paste what you remember, so the report reflects your memory rather than the record.<\/p>"},{"question":"What can it see, exactly?","content":"

                  Your workspaces and projects, the folders and templates inside them, the forms and their records, and your users and register lists. It reads what is there. It doesn't invent progress that was never recorded.<\/p>"},{"question":"Does this work with ChatGPT and Microsoft Copilot as well?","content":"

                  Yes. The same connection supports Claude, ChatGPT and Microsoft Copilot, so this method holds whichever assistant your team already uses.<\/p>"},{"question":"Can it see data it shouldn't?","content":"

                  No. Every request is checked against your own workspace permissions, so Claude only ever sees what you can already see. Connecting Claude doesn't widen anyone's access.<\/p>"},{"question":"What if the report needs records from another project?","content":"

                  Keep each report to one project. Reading across separate projects isn't something to rely on today, and a report assembled from the wrong project is worse than one that took longer to write.<\/p>"}],"ai_lp_version_history":"","ai_lp_closing_heading":"Stop rebuilding the weekly report from memory","ai_lp_closing_body":""},"custom_permalink":"answers\/how-to-use-claude-for-weekly-construction-progress-reports","_links":{"self":[{"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/posts\/55062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/comments?post=55062"}],"version-history":[{"count":1,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/posts\/55062\/revisions"}],"predecessor-version":[{"id":55063,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/posts\/55062\/revisions\/55063"}],"wp:attachment":[{"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/media?parent=55062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/categories?post=55062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/tags?post=55062"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/industry?post=55062"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/product?post=55062"},{"taxonomy":"region","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/region?post=55062"},{"taxonomy":"system","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/system?post=55062"},{"taxonomy":"content_type","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/content_type?post=55062"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/sitemate.com\/au\/wp-json\/wp\/v2\/topic?post=55062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}