ChatGPT Dots for architects: project follow-ups
Learn how architects can use OpenAI's ChatGPT Dots to track consultant follow-ups, decisions, and deadlines, with a practical prompt and review steps.
Direct answer
Answer
Architects can give a ChatGPT dot an ongoing responsibility, such as tracking consultant responses and preparing meeting briefs from approved project sources. Define the register it should maintain, the changes that deserve attention, and the decisions you will review. Start with one project and check the first result before expanding its role.
Audience + setup
Before you start
- For
- Architects and project leads · Small architecture practices managing consultant coordination
- Software context
- ChatGPT Dots, with supported connected apps where needed. Official documentation checked on 30 September 2026.
- Prerequisites
- An account with access to Dots · Approved meeting notes and a project action list · Access to any connected sources the dot needs · A project lead to verify the register
- Outcome
- Set up a bounded pilot that produces a traceable follow-up register and draft meeting brief for project-lead review.
01
What are ChatGPT Dots?
OpenAI's update for the week of 28 September–2 October 2026 introduces Dots as agents that continue assigned work between conversations. They can use connected apps, produce files, and delegate work to ChatGPT Work or Codex. The rollout is gradual, so access can differ between accounts.
For an architecture practice, that suggests a useful pilot: keeping track of the small commitments that accumulate between coordination meetings. The project example below is an archiPrompt proposal for using the feature; its results still need evaluation on your own material.
02
Start with the next consultant meeting
Imagine a small housing project with a revised landscape plan, an unresolved service route, and a client decision on balcony finishes. The useful output is a short register showing what changed, who owes the next response, and which source supports each entry.
Give your dot the current meeting notes, the existing action list, and the agreed milestone dates. Define a pilot lasting two weeks. Ask it to identify new actions, preserve items that remain unresolved, and prepare the next meeting brief. Treat unclear ownership or conflicting dates as questions for the project lead.
- — Issue or decision, with a source link or document reference
- — Responsible person and due date, when the source names them
- — Status: open, waiting, proposed resolution, or confirmed closed
- — Next action and the person who needs to review it
03
Give it a responsibility it can check
In your dot's conversation, paste the prompt below after supplying the project sources. Replace the placeholders with the actual project, source locations, and pilot end date. A precise instruction makes the first result easier to compare with the meeting record.
Help me maintain the consultant follow-up register for [project] until [end date]. Use only [approved meeting notes, action list, and connected source locations]. For each action, record the source, owner, due date, status, and next step. Preserve unresolved items. Mark missing or conflicting information as needing confirmation. Prepare a brief before the next coordination meeting. Notify me in ChatGPT when a milestone is at risk or a decision needs my input. Draft any suggested follow-up messages for my review. Ask me before sending messages, closing an issue, or changing a project commitment. Show me the initial register so I can correct it.04
Confirm how follow-ups will happen
Dots can decide when to resume assigned work. A fixed recurring check needs a saved schedule, including timing, time zone, notification conditions, and destination. Ask your dot to confirm what was saved, then inspect a real run. If a connected service supports event monitoring, confirm which events it can actually watch.
For this pilot, a weekday check at 9 a.m. America/Toronto until the agreed end date is a reasonable starting point. Keep routine changes in the register and reserve notifications for overdue responses that affect the next milestone. Adjust that rule after the first week if it produces too many alerts.
05
Keep the source and the decision together
A late consultant response can contain both a proposed solution and a request for approval. Have the register preserve that distinction. An item should become confirmed closed only when the project record contains the evidence and the responsible reviewer accepts it.
Check several entries against the original notes: one new action, one overdue item, and one completed item. Confirm names, dates, revision references, and whether the summary changes anyone's commitment. A successful pilot reduces the time spent preparing the meeting without making the action list harder to trust.
06
Understand what stays available when you step away
A dot has its own cloud computer and browser. Cloud work can continue while your devices are off. Work that needs your connected personal computer requires that computer to stay online with the ChatGPT app open. Connecting a messaging channel, an app, and a computer are separate steps.
Choose the sources deliberately. A folder of approved minutes is a better first input than an entire project archive with mixed revisions. Tell the dot which documents govern the register and which material is background information. Review delegated results through Activity before relying on them.
07
Turn the pilot into an office method
At the end of two weeks, review the corrections you had to make. Did the dot miss owners, confuse proposed dates with confirmed dates, or carry superseded information forward? Use those observations to improve the source pack and instructions before assigning another project.
The related Project Lessons Learned Brief is an archiPrompt Template bundle for turning closeout interviews into a lessons brief and action register. Its structure can help record what the pilot taught your team. Check the listing's compatibility and setup separately when choosing a workflow.
REVIEW BEFORE USE
Known limitations
- Dots are rolling out gradually; eligible plans, regions, account controls, and connected tools affect availability.
- This is an illustrative architecture pilot. archiPrompt has not benchmarked Dots on a live project or verified a direct CAD or BIM integration.
- Project leads must verify commitments and issue status before the register informs an issued record or external communication.
PRIMARY SOURCES
References used for this guide
These guides support Prompt evaluation and do not replace project-specific advice, code interpretation, consultant coordination, or qualified professional review.
Reviewed by archiPrompt Studio · Editorial + product review