MiddleGroundA daily dashboard
12Open4Due today3Waiting
Use a structured overview for status and ownership. Ask the assistant for a short briefing on what needs attention.
Illustrative numbersReporting · From sources to results
Your sources.
The result you need.
Bring together the sources your AI assistant can read and ask for the result you need: a report, email, table, presentation or structured file. A template guides its content, structure and appearance; the output format follows the task.
Gather the right information.
Ask your connected AI to work with the documents, records and project context it can read. Sources can have different formats and come from different parts of the shared workspace.
Describe the result with a template.
A template describes what to include, how to organize it and how it should look: sections, tone, tables, visual style or branding. Review and refine the result with your assistant.
Choose the output that fits.
The destination might be a document, an email, a spreadsheet or structured data. The principle is open-ended: the assistant and its connected tools need to be able to read the sources and create the chosen output.
The template describes the result, not necessarily a file format. Markdown to PDF is one useful route through a broader idea.
The service desk, seen through its results
One set of records.
Several useful answers.
The ticket workflow creates more than a queue of messages. It becomes a source for daily coordination, customer communication and learning from repeated issues.
Shared source in MiddleGroundTickets · Emails · Owners · Due dates · Actions · Outcomes
The same records support each output. You do not have to compile a separate set of facts for every audience.
A progress update
The assistant gathers relevant messages and actions into a clear update. Keep the prepared email or PDF with the ticket.
A period report
Bring together recurring issues, recorded outcomes and unresolved questions. Ask the assistant to propose improvements, with the underlying evidence in reach.
Repeat the structure, reuse the work
A familiar report.
Fresh information.
A template is a reusable set of instructions for content, form and appearance. It can describe the audience, required sections, evidence, tone, tables and visual style. MiddleGround keeps the template, source material and saved outputs with the work.
- 01Choose the scope
A project, customer or reporting period.
- 02Prepare the content
Extract facts, summarize activity and draft conclusions from the relevant sources.
- 03Review & refine
Check the supporting material and turn agreed improvements into follow-up actions.
- 04Create & keep
Create the chosen output and save it with the relevant work. Use the same instructions again as the sources change.
A renovation updateDecisions, work completed and outstanding questions.
A research briefReferenced extracts, synthesis and reviewed conclusions.
A business overviewProject records, costs, missing information and next steps.
Build from your actual information
The overview you need.
The data you already have.
In the web app, open Reports and choose Build overview. Compose a shared Report from tables, cards, lists, details and Thing counts, using your Environment’s existing Views and fields.
Choose the source.
Select a View containing the Things you want to inspect. Choose the fields, filters, sorting and formats that make the information useful.
Preview the real data.
See the result before saving. Click a Thing to explore its context while whole-View blocks retain the wider picture. Missing information remains missing.
Save a shared Report.
Save the definition for your Environment. People see the results they have permission to read. An assistant can help prepare the same Report definition.
Illustrative setup · use your own fields
A service overview: choose your work View, show a list of open items and a Thing-count block, then add a detail block for the selected job. Filter on your existing status field instead of maintaining another spreadsheet of the same records.
The builder supports defined blocks and sources. Counts are not sums, and this is not a general app builder. Drafts are temporary until saved or exported; editing an existing definition in the visual workspace saves a new shared Report.
Keep the steps behind the result
A meaningful version.
A traceable source.
Working documents change. Name the moments that matter and retain the earlier revisions behind them.
Name a point in the work.
Give an artifact revision a label and optional note, such as “For review” or “Agreed scope”. Named revisions stand out in its history; ordinary autosaves continue alongside them.
Labels are your own names, not an enforced approval process.
Look back or restore.
View historical Markdown or retrieve an earlier file. Restoring creates a new revision of the same artifact, keeping its history. A restore does not silently reset the current version label.
Keep the source of a generated file.
When a generation workflow records provenance, its output can link to the exact source artifact, historical revision and version label used. The generated file remains its own artifact.
See when the source has moved on.
Source details can show that the source is unchanged, has later edits or has moved to a new named version. A changed source is a reason to review the output; it does not automatically replace or invalidate the file.
Example · a renovation brief
Plan
“Agreed scope”
“Agreed scope”
PDF brief
Recorded source revision
Recorded source revision
Plan updated
Review source status
Review source status
An uploaded file does not acquire source history from its filename. The workflow must explicitly record that relationship.
More than a final PDF.
Ask your assistant for a summary, a set of extracts, a conclusion or an improvement list. The content can become a message, a document or input for another tool. Save the result with the relevant project and sources in MiddleGround, ready to review and build on.
See reporting in the use cases →One source, different destinations.
A dashboard or saved Report presents structured workspace information. An assistant can also use that information to prepare an email, a presentation, a table or a document. Reporting is the wider workflow of turning sources into something useful.
Explore reports in the guide →