Communication & vendor follow-up

Keep the conversation with the work it belongs to.

A Req is more useful when the decisions, delays, labor, vendor coordination, approvals, and supporting files remain connected to it. REQQER uses Activity as the running operational history so staff can see not only what the request was—but what happened next.

REQ 18427Elevator service follow-upOpen · Internal Assignee: Maintenance Director · External Vendor: Elevator Contractor
1
ActivityIntermittent door fault documented.
2
Question sentRequest service date and quotation.
3
Email replyVendor response returns to the Req.
4
Document attachedProposal.pdf

Activity + Work Duration

Build the history as the work happens.

Activity is the running record of meaningful work, communication, decisions, and delays. Work Duration records the actual labor time associated with that work.

  • Document work performed and troubleshooting findings
  • Record parts ordered, delays, temporary actions, approvals, or next steps
  • Capture contact with an External Vendor
  • Enter actual Work Duration rather than elapsed calendar time
  • Add Activity after meaningful steps on multi-day work instead of reconstructing the history at closure
Req ActivityIllustrative timeline
Inspection

Confirmed intermittent failure; unit remains operational.

Work Duration · 25 min
Vendor contact

Requested service availability and proposal.

Follow-up

Proposal received and attached; approval requested.

Document · Proposal.pdf

Need Additional Information

Ask the question from the Req—and keep the answer there too.

When work depends on a photograph, quotation, approval, report, part detail, or other response, REQQER can send the request while saving the question as Activity.

Req Activity“Please confirm delivery date.”
Email requestUser · manager · vendor · follower
ReplyText + attachments
Same ReqReply becomes Activity; files become documents
The Req stays accountable while you wait.

Sending a request for information does not automatically close the Req. Staff decide whether it should remain Open or be placed On Hold while awaiting the response.

Internal

Internal Assignee

The staff member responsible for managing the Req and making sure the work is handled appropriately.

  • Coordinate staff or contractor
  • Follow up on delays
  • Confirm documentation is received
  • Ensure appropriate completion
+
External

External Vendor

An outside company or specialist involved in the work, such as an elevator contractor, sprinkler company, electrician, plumber, or supplier.

  • Perform specialized work
  • Provide proposals or reports
  • Supply certifications or invoices
  • Respond to questions and requests

Internal accountability + external expertise

A vendor can do the work without making internal follow-up disappear.

A Req can identify both an Internal Assignee and an External Vendor. When outside work is involved, the internal person can remain responsible for communication, documentation, delays, and follow-through.

Assignment and Department serve different purposes: Department helps organize the work; assignment identifies responsibility for the individual Req.

Reply by email

Useful communication can come back into REQQER without retyping it.

Supported REQQER-generated emails can be answered directly. Reply text becomes Activity on the existing Req, while attached files are added to its documents.

Reply becomes Activity

The response is added to the existing Req rather than creating another Work Order.

Attachments stay with the Req

Photographs, proposals, invoices, inspection reports, and approval documents can return with the reply.

Duration can travel with assignment replies

Assignment-notification replies can include Work Duration so the labor record and communication stay together.

Vendor quotations and approvals

The same communication pattern can support purchasing decisions.

For organizations using REQQER to coordinate purchase requests, the Req can preserve vendors contacted, quotations, negotiations, approvals, final decisions, delivery information, and supporting documents in one history.

  • Request pricing, availability, delivery terms, specifications, warranty, or alternatives
  • Receive vendor replies and attachments back into the Req
  • Document approvals, denials, selections, final price, or back-order information
  • Notify the requester and close the Req when the workflow is resolved

REQQER can support this practical workflow, but it is not positioned as a dedicated purchasing or accounting system.

Vendor A$4,850Proposal attached · 3-week lead time
Vendor B$5,120Proposal attached · 1-week lead time
Decision preserved with the ReqApproval · vendor selected · final price · delivery status

Related capabilities

Communication is part of the Req lifecycle—not a separate system.

See REQQER in action

See how communication, vendor follow-up, and documentation stay connected to the work.

A demonstration can follow a Req from assignment through Activity, outside-vendor communication, documents, and resolution.