From a conversation to a project record
Your business administrator
Your business administrator manages projects, rosters, categories, and the Review Queue for your organization. This role is for people inside your organization, not clients or external collaborators.
Blue Data Works is the platform operator: we handle hosting, infrastructure provisioning, releases, and fleet monitoring. Those tasks are separate from using Provenience to manage your work.
1. Give the work a home
Create a project for a bounded piece of work: a remodel, a client engagement, or a campaign. Add its staff, customers, and collaborators to the roster with the phone numbers they use.
The people registered on a text arrange its context before extraction begins. With a customer on it, the customers' one shared active project decides, whoever else is on it; several shared active projects or none wait for an administrator. Without a customer, every registered participant must share the job: one shared active project files there, several go to the Review Queue, and none is company-level.
2. Bring messages in
Send texts to the Site contact and keep each project's people current in its roster. Qualifying images and short PDFs can be considered with their message, and every attachment is preserved and cataloged as a file. Other files remain preserved records rather than an assurance that their contents were interpreted.
See capture for how Provenience preserves messages and records.
3. Make the useful parts findable
Extraction turns communication into discrete records: decisions, selections, expectations, and outcomes. Categories come from a vocabulary you control at the tenant or project level.
A tentative budget stays tentative. An original message remains separate from what was extracted from it. Records carry their project context and source citation, so a useful answer can also be checked.
4. Review what needs judgment
A business administrator uses one Review Queue to resolve unknown senders, unclear categories, and extraction failures. The system queues ambiguity rather than quietly accepting a guess. Records with open queue items remain unqueryable until those items are resolved.
Add categories when your work calls for them. Apply them to new messages, or deliberately reprocess an active project. You do not need a product deploy to change the vocabulary. See structure and review.
5. Ask from the tools you use
An authorized business administrator can connect an AI assistant that supports a remote MCP server and ask questions such as:
- What tile did we choose for the bathroom, and where was it discussed?
- Which budget expectations have been stated on this project?
- What did the client say about the launch date?
MCP supplies structured, cited records to your assistant. Citations let a business administrator check the original source; they do not turn an AI-generated answer into a confirmed business decision. Read access and MCP.
6. Keep the record current
When your categories change, reprocess an active project's earlier messages and review the proposed records before confirming them. Your current records remain in place until you confirm; you can also discard the rerun. See Reprocessing a project.
Plan your first project
Choose work with a clear beginning and end, a manageable roster, and conversations whose participants you can keep current in that roster. Decide who reviews ambiguous records. Then explore what you could build, or run the current substrate locally.