Voyage Digital
    Workflows· Operations & Project Management

    The Status Bridge

    A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.

    automatinganalyticalstructuring

    Description

    A weekly status report is rarely the problem, gathering the groundwork for it is: opening the project tool, working through tasks and deadlines, identifying overdue items, and turning all of it into a readable form. This workflow takes over exactly that groundwork. At a fixed time, for example every Friday, it pulls the active projects together with tasks, milestones, deadlines and owners from the project tool, then has a language model derive progress, risks and delays from that data.

    This analysis produces a structured report with an executive summary, progress figures, prioritized risks, a list of delayed tasks and the most important next steps. The report is saved to cloud storage with a date and project ID in the file name and sent by email to the stakeholder distribution list, optionally as a draft first.

    What gets automated is the data compilation and the wording, not the substantive judgment. Especially during the ramp-up phase, a human stays involved in filtering for active projects, maintaining the stakeholder list and approving dispatch, until the tone and risk criteria are properly calibrated. After that, the role shrinks to a brief review before sending.

    • Consistent status communication: Every weekly report follows the same layout, regardless of who is responsible for that week.
    • Risks visible early: Overdue tasks and stalled projects are flagged automatically, instead of surfacing only in the next meeting.
    • Less reporting effort: The project owner reviews a finished draft instead of writing the report from scratch.
    • Faster decisions: The executive summary and next steps are ready by Friday, instead of being pulled together only on Monday.

    Steps

    Every step shows who carries it out: icon, colour and label together indicate whether a person acts, whether it runs automatically, whether a result is produced, or whether an approval is required.

    01Person

    A fixed weekly time, by default Friday at 4pm, starts the workflow.

    02Automated

    03Automated

    04Automated

    05Automated

    06Result

    Key
    PersonAutomatedResultApproval

    Requirements and operations

    Requirements

    • PM tool Asana, Trello, Monday or similar, as the source for tasks, status, deadlines and owners.
    • Cloud storage Drive, Dropbox, OneDrive or Notion for storing the report.
    • Email tool Gmail, Outlook or similar for sending to the stakeholder distribution list.
    • LLM access An API key for OpenAI, Claude or Gemini.

    Testing

    • Test run Trigger the workflow manually, against a known active project.
    • Data retrieval Check whether all active projects load completely with tasks, status, deadlines and owners.
    • Analysis and report Verify that progress and risks are traceable and the report structure is complete.
    • Edge cases Check projects with no activity, missing owners and a distribution list covering several projects.

    Go-live

    • Approval to start Activate the workflow only once data retrieval, the report, storage and dispatch work cleanly together.
    • Draft mode Send the report to the project lead only, for two to three weeks, and adjust the template during that time.
    • Refinement Adjust tone, level of detail and risk criteria based on the feedback from this phase.
    • Expand Extend the workflow as needed with multi-project reports, a trend comparison to the previous week, or escalation alerts.

    Common issues

    • Filter on active projects missing The report fills up with stale data. Set a reliable filter on active projects.
    • LLM output not parseable Specify the format firmly in the prompt and build in validation before storage.
    • Stakeholder list outdated Review the distribution list quarterly.
    • File name collides Use the date and project ID in the file name.

    Builder Prompt

    Copy the prompt below in full into your automation tool or agent builder. As a file: status-bruecke.en.json

    GOAL
Build a workflow that pulls project data from the PM tool every week, analyzes progress, risks and delays, and files and sends a finished status report for stakeholders.

Adapt the structure to the concepts of your automation tool (for example nodes, steps, zaps or agent actions). While doing so, preserve the trigger logic, the sequence and the data flow.

TRIGGER
Type: scheduled, weekly, by default Friday at 4pm.

STEPS
1. Retrieve data: Active projects only, a filter on active projects is mandatory, otherwise the report fills up with stale data, with tasks, status, milestones, deadlines and owners.
2. Prepare data: Structure completed, in-progress and overdue tasks per project.
3. AI step: project analysis and report. Use the working prompt below exactly.
4. Storage: Save the report to the cloud folder, with the date and project ID in the file name, to avoid collisions.
5. Output: Send the report by email to the stakeholder distribution list. During the introduction phase, send it as a draft to the project lead for approval first, then optionally automatically.

PROMPT, COPY EXACTLY AND UNCHANGED
"""
You are an experienced project manager. Analyze the following project data and create a professional weekly status report.

Project data:
[PROJECT_DATA]

Analyze the following aspects:
1. Progress: Which tasks have been completed? How does overall progress compare to plan?
2. Risks: What potential risks or blockers are apparent?
3. Delays: Are there overdue tasks or projects that are behind schedule?
4. Next steps: What are the most important tasks for the coming week?

Create a report with the following structure:

# Project Status Report, [DATE]

## Executive Summary
[Brief summary of the project status in two to three sentences]

## Progress
- Completed tasks: [Number]
- In progress: [Number]
- Overall progress: [Percent]
- Highlights of the week: [Bullet list]

## Risks and Blockers
[List of identified risks with priority]

## Delays
[List of overdue or delayed tasks with owners]

## Next Steps
[Top 3 to 5 priorities for the coming week]

## Team Performance
[Optional: workload and performance notes]

Tone: [TONE]
Format: Professional, clear, with concrete recommendations for action
"""

DATA FLOW
Step 1 and 2 to step 3: prepared project data as [PROJECT_DATA].
System to step 3: current date as [DATE].
Step 3 to step 4 and 5: the finished report.

ERROR HANDLING
Filter on active projects missing or not working: fix it as mandatory, otherwise the report fills up with stale data.
Project with no activity in the week: explicitly mark it in the report as "no movement" instead of leaving it out.
Owners missing: mark the affected task in the report as having no owner.
AI output incomplete or unstructured: the structure is specified in the prompt. Validate the output before storage and retry the call once if it fails.
Stakeholder distribution list outdated: maintain it as a configuration item and review it quarterly.
File name collides: use the date and project ID in the file name.

PLACEHOLDER CONVENTION
All placeholders in square brackets in the input section are variables: [PROJECT_DATA] and [DATE] are mapped dynamically, as described in the data flow. [TONE] is not dynamic: set this value manually before activation. The square brackets inside the report structure are formatting instructions to the language model and remain unchanged. List all placeholders that require manual configuration separately at the end.

SELF CHECK BEFORE COMPLETION
Check, before you report the workflow as finished:
1. Are all steps connected correctly, and does the filter on active projects work reliably?
2. Is the working prompt inserted completely and unchanged, and are [PROJECT_DATA] and [DATE] mapped?
3. Do storage, with the date and project ID in the file name, and dispatch to the distribution list work?
4. Are all points listed that require manual configuration: PM tool access and the active filter, the cloud folder, the stakeholder distribution list, the rule for draft or automatic dispatch, [TONE], and the LLM access?

    Working prompts

    Prompt for project analysis and the report

    Use this prompt in step 3 of the workflow, for the AI analysis and report creation.

    You are an experienced project manager. Analyze the following project data and create a professional weekly status report.

Project data:
[PROJECT_DATA]

Analyze the following aspects:
1. Progress: Which tasks have been completed? How does overall progress compare to plan?
2. Risks: What potential risks or blockers are apparent?
3. Delays: Are there overdue tasks or projects that are behind schedule?
4. Next steps: What are the most important tasks for the coming week?

Create a report with the following structure:

# Project Status Report, [DATE]

## Executive Summary
[Brief summary of the project status in two to three sentences]

## Progress
- Completed tasks: [Number]
- In progress: [Number]
- Overall progress: [Percent]
- Highlights of the week: [Bullet list]

## Risks and Blockers
[List of identified risks with priority]

## Delays
[List of overdue or delayed tasks with owners]

## Next Steps
[Top 3 to 5 priorities for the coming week]

## Team Performance
[Optional: workload and performance notes]

Tone: [TONE]
Format: Professional, clear, with concrete recommendations for action

    JSON export

    Setup

    Two routes lead to the same result. Pick the one that fits your setup.

    Suitable when you want to build the workflow in your own automation tool.

    1. Open your workflow tool, for example n8n, Make, Zapier or Langdock.
    2. Create a new workflow and give it a name.
    3. Choose the AI-assisted build option if your tool offers one.
    4. Paste the builder prompt from above in full.
    5. Check the result against the step sequence in this document, then add your access credentials and channels.

    Suitable when you want to take the workflow over unchanged.

    1. Download the JSON file from the JSON export section.
    2. Open the workflow area of your tool and create a new workflow.
    3. Give it a name and confirm.
    4. Open the menu on the workflow name and choose to import a JSON file.
    5. Upload the file, then add your own access credentials.
    6. Run a test before you activate the workflow.

    Last reviewed:

    In the workshop this becomes your method.

    A single prompt becomes a repeatable method. We show that in the workshop From Prompt to Method.

    View workshops

    Related resources

    Browse all resources
    Workflows

    The Inbox Router

    A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.

    Learn more
    Skills

    The Task Grid

    Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.

    Learn more
    Workflows

    The Team Digest Loop

    A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.

    Learn more
    Assistants

    The Risk Matrix Reviewer

    Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.

    Learn more
    Assistants

    The Gap Analyst

    Systematically compares the current state with the desired target, quantifies the gap between them, and derives initial prioritized actions.

    Learn more
    Google Drive
    Tools

    Google Drive

    Google's cloud file storage for documents, spreadsheets and presentations, with real-time collaboration, granular sharing and automation through the Drive API.

    Learn more
    Skills

    The Kickoff Briefing

    The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.

    Learn more
    Skills

    The PDF Workbench

    The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.

    Learn more
    Skills

    The Inbox Rulebook

    Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.

    Learn more
    Skills

    The Retro Rulebook

    The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.

    Learn more
    Skills

    The Shutdown Protocol

    The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.

    Learn more
    Skills

    The Handover Package

    Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.

    Learn more
    Workflows

    The Onboarding Pipeline

    Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.

    Learn more
    Workflows

    The Appointment Bridge

    A workflow that reads incoming appointment requests, checks calendar availability, and drops a ready reply draft with three time proposals into the inbox for review before sending.

    Learn more
    Assistants

    The OKR Strategist

    Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.

    Learn more
    Assistants

    The Project Sparring Partner

    Guides you through every phase of a project with systematic risk analysis, prioritized courses of action for acute problems, and structured lessons learned after completion.

    Learn more
    Assistants

    The Process Documenter

    Captures undocumented business processes through a structured interview and turns them into clear, visual process documentation with steps, decision points and responsibilities.

    Learn more
    Assistants

    The Status Report Curator

    Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.

    Learn more
    Assistants

    The Negotiation Strategist

    Analyzes a supplier quote along with its market context and develops a concrete, ready-to-use negotiation strategy with goals, levers, arguments and fallback positions.

    Learn more
    Assistants

    The Workflow Planner

    Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.

    Learn more

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call