Resources/Core concepts/Requests
Requests
Request: one handoff. One person needs something from another, and the record waits until the holder or a teammate delivers it. A request has a requester, a holder, a type, and the bond, certificate, or project it is about.
A request is one handoff. Someone needs something from someone else, and the record it belongs to waits until the holder or a teammate delivers it. A request has a requester, a holder, a type, and a context: the bond, certificate, or project it is about. When the holder fulfills it, we move the ball on.
A request is a handoff, not a conversation
The conversation about a record lives on its thread, where anyone seated on the record can post and reply. A request is narrower. It names one thing that is owed, by one holder, and it stays open until the holder or a teammate delivers that thing or declines the request. That is why a request shows up in the holder’s court and a thread post does not.
A request has a type
Send a document, ask a question, review and comment, approve or sign off, confirm receipt, something else, system notification, huddle tasks, huddle invitation, and idle huddle. The type sets what fulfilment looks like: an upload target, an answer, a decision, an acknowledgement, or a huddle move. The full table is on My Court.
You pass, transfer, decline, or fulfil
| Move | What it does | Who can do it |
|---|---|---|
| Fulfil | Deliver what was asked. The shape depends on type: upload, answer, approve, confirm. | The named holder. |
| Pass | Hand the request to someone inside your own company. | The holder. The list shows internal stakeholders only. |
| Transfer | Hand the request to an outside party seated on your account: a broker, surety, sub, or owner. | The holder. The list shows external stakeholders only. |
| Decline | Refuse the request. It closes, and the requester sees that you declined it. | The holder. |
Every move is explicit and recorded. There is no way to make a request quietly disappear, and no way to complete one you do not hold.
Kuhlman creates requests too
Most requests start with a person: the Start new request action, or a wizard step that asks someone for something. Some start with us. When you send a bond to your broker, we open the request the broker holds. When we read an email and propose a request to the broker, and you accept it, we create it. When a renewal is coming due, we can raise a request so the renewal doesn’t stall. Requests from Kuhlman carry the Kuhlman mark, never a person’s name.
A stalled request stays visible
A request you sent sits under Waiting on others until the holder or a teammate fulfills or declines it. The Requests page is the portfolio queue: filter by whose court, act on the row in front of you, and find finished work under Archived. Nothing falls out of the list because someone stopped answering email.
You work with requests on these screens
| Screen | What it shows |
|---|---|
| Requests | Every request on your account, filtered by court, with Archived for completed work. |
| Request detail | One request: what is asked, the related record, the thread, the activity, the documents, and the moves available to the holder. |
| Start new request | Available from the header actions on the Documents and Huddles pages, and from a record. |
| Home → My Court and Waiting on others | Previews of requests you hold and requests you sent. |
We use these terms
- Request
- One handoff with a requester, a holder, a type, and a context.
- Requester, holder
- Who asked, and who owes the answer right now.
- Pass, transfer
- Move the request inside your company, or to an outside party on your account.
- Decline
- Close a request with a reason instead of fulfilling it.
- Closed
- Requests the holder or a teammate fulfilled or declined.
Read next
Product pages that build on this concept: Submit and track requests · Ball in court