Correspondence
Correspondence Overview
Construction projects generate formal communication every day — contract notices, instructions, claims, responses. These need to be traceable, immutable, and defensible. Correspondence in Pasco Cloud ("Corro" in the sidebar) is a purpose-built formal communication system designed for contract administration.
![[Screenshot: Correspondence inbox showing a list of received items with subject lines, sender names, dates, read/unread indicators, and entity tags linking to contracts and projects]](/images/placeholder.png)
What Is Correspondence?
Correspondence is Pasco Cloud's formal communication channel. It is not email — it is an in-platform system where sent items become immutable contractual records. Every piece of correspondence has a sender, recipients, subject, body, and optional attachments. Once sent, none of these can be changed.
This is fundamentally different from two other communication channels:
- Newsfeed — Pasco Cloud's informal channel for team updates and collaboration. Posts can be deleted. No delivery tracking. No immutability. See Newsfeed Overview.
- External email — fragmented across inboxes, no audit trail within the platform, no entity tagging, no guarantee of delivery tracking.
Correspondence sits between these — more formal and traceable than the newsfeed, more integrated and auditable than email.

ℹ️ Did you know?
Correspondence in Pasco Cloud uses the term "Corro" in the sidebar — this is standard shorthand on AU/NZ construction sites. You will see both terms used throughout the platform and documentation.
Key Features
- Email-style interface — inbox, sent, drafts, archive, and trash folders. Familiar layout with a folder sidebar and message list.
- Rich text body — formatted text with bold, italic, underline, bullet lists, ordered lists, blockquotes, and links. Not plain text.
- File attachments — upload files via presigned S3 URLs. Attach documents, photos, and PDFs.
- Recipients — direct (To) and copied (CC) recipients. You can send to individuals or expand a group to include all its members.
- Entity tagging — link correspondence to contracts, projects, issues, reports, and tasks. Tags are searchable and create cross-references.
- Threading — replies and forwards maintain conversation context. View the full thread from any message.
- Immutability — once sent, the subject, body, recipients, and attachments cannot be changed. This is by design for contractual defensibility.
- Delivery tracking — see when each recipient received and read the correspondence. Important for contract administration where proof of receipt matters.
- Recipient scoping — you can only send to your connections and members of your shared groups. This prevents unsolicited correspondence and keeps communication within your project network.
Correspondence Lifecycle
Correspondence items move through a simple lifecycle:
- Draft — compose your correspondence, add recipients, write the body, attach files. Save and come back later if needed. Drafts are editable.
- Sent — once you click Send, the correspondence becomes immutable. Recipients see it in their inbox. Delivery tracking begins. The item moves to your Sent folder.
There is no recall or unsend. If you need to correct something, send a new correspondence referencing the original.
Formal vs Informal Communication
Pasco Cloud provides two communication channels. Understanding when to use each is important:
| Correspondence | Newsfeed | |
|---|---|---|
| Purpose | Formal contractual communication | Informal team updates |
| Immutability | Yes — cannot be altered once sent | No — posts can be deleted |
| Delivery tracking | Yes — read receipts per recipient | No |
| Threading | Yes — reply, reply all, forward | Comments on posts |
| Entity tagging | Yes — link to contracts, projects, issues | Visibility-based sharing |
| Typical use | Contract notices, formal instructions, claims | Site updates, photos, team collaboration |
Use correspondence when the communication needs to be a permanent, unalterable record. Use the newsfeed for day-to-day team communication.
Integration with Notices
Notices are formal documents created from notice-category templates — contract notices, extension of time claims, variation requests, and similar. Once a notice has been approved, it can be transmitted via correspondence using the "Send via Correspondence" action.
This action opens the compose page with the notice PDF auto-attached and the report pre-tagged. You add recipients, optionally write a cover message, and send. The correspondence record links back to the source notice, creating a complete audit trail from document creation through formal transmittal.
This is the primary mechanism for formal document transmittal in Pasco Cloud.
Mobile Support
Correspondence is fully available on the mobile app. You can compose and send correspondence, browse your inbox, read items, and reply — all from the field. The mobile interface mirrors the web experience with the same folder structure and threading.

💡 Tip
Need to send a contract notice from site? Approve the notice on your phone, then use "Send via Correspondence" to formally transmit it — without returning to the office.
What's Next?
- Ready to send correspondence? Learn how in Composing & Sending.
- Need to manage your inbox? Read Managing Correspondence.
- Want to understand notices? See the Notices Overview.