How it could look

An evening with Attendit

This is how it could feel when the interface re-composes itself at every step: from fixed blocks, fitted to your question and your company. Every block carries a source.

1. 20:15 Tension

   Here is the tender.

   Read. Two things matter today.

   • Question deadline in 9 days 26 Feb 2027, 12:00 · page 2
   • Extract too old Allowed: at most 3 months · page 8

2. 20:20 Orientation

   Is it worth it?

   Bid or not?

   • Bid deadline 12 Mar 2027, 10:00 · page 14
   • Award Price 70 %, construction time 20 %, team 10 % · page 15
   • Documents 6, of which 2 open

3. 20:30 Decision

   What am I missing?

   Match with your documents:

   • Signature on file
   • Trade licence too old
   • Form 3 missing

4. 20:45 Action

   Write a question to the authority about the submission.

   Draft, reference: bid rules, page 14.

   • “Please confirm that the upload in the procurement portal is possible until 12 Mar 2027, 10:00.“

   Review and send

5. 21:00 Calm

   Thanks. Remind me.

   Done. I will remind you on 11 Mar 2027.

   • Open Renew the extract, form 3
   • Reminder 11 Mar 2027, 09:00

Tension, orientation, decision, action, calm.

Concept, not available. Invented example.

Feasible in parts: the pipeline delivers deadlines, documents, weights and quotes today. The draft of the question would come from a language model, the source from the findings, and you review before sending. The match with your documents is more effort.

In a chat (MCP app)

The summary appears as a card in a conversation with an assistant, for example in Claude or ChatGPT. The card is a small HTML page that the chat shows in a sandboxed frame.

Feasible with today's data: yes. An MCP server over the pipeline's findings would have to be built. The deadlines carry ISO dates, so the calendar file can be derived.

By role

The same data, four views. The person chooses the view. There is no hidden profiling.

Concept, not available. Invented example.

Feasible: yes. The roles are only different arrangements of the same findings.

By tender: only what it contains

Which blocks appear depends on what the tender contains. The model only chooses from a fixed catalogue.

Concept, not available. Invented example.

Feasible: yes. The kind of findings (eligibility, award, deadline) decides which blocks appear.

One description, many surfaces

The summary is stored as a description: blocks from a fixed catalogue, every item with a source. Each surface shows it in its own way. This is a sketch in the style of A2UI, not the real standard.

{
  "surface": "kurzfassung",
  "catalog": "attendit-basic (draft)",
  "components": [
    {
      "id": "doc-d2",
      "component": "RequirementRow",
      "title": "Prove the trade licence",
      "quote": "Der Bieter hat die erforderliche Gewerbeberechtigung durch einen Auszug aus dem Gewerberegister nachzuweisen. Der Auszug darf nicht älter als drei Monate sein.",
      "source": {
        "section": "Suitability",
        "page": 8
      }
    },
    {
      "id": "dl-f2",
      "component": "DeadlineRow",
      "title": "Bid deadline",
      "when": "2027-03-12T10:00",
      "source": {
        "section": "Bid rules",
        "page": 14
      }
    }
  ]
}

Rule: every block with content carries a source (section and page).

Feasible: yes. The findings are already typed and carry source, page and section. The format shown is a draft.