Getting Started

Tracking Order Progress with the Activity Timeline

Track order progress on Serpverse with the Activity Timeline — a per-order history of every milestone, visible to both buyer and publisher in real time.

Last updated June 8, 2026·7 min read

What the Activity Timeline Is

Every Serpverse order moves through a series of milestones — accepted, content submitted, published, approved — and the Activity Timeline records each one in order. It is the single place to track order progress without messaging the other party or guessing what happened last.

The timeline is a running history of an order's lifecycle events. Each entry is added automatically the moment something happens, so you never have to refresh a status field manually or ask "where are we now?" The most recent event sits at the top, and older events scroll back to the moment the order was placed.

Crucially, the timeline is shared. Both you and the other party — buyer and publisher — see the same history on the same order. There are no private events and no hidden steps. That shared view is what makes it the foundation of trust on the platform.

Where to Find It

Open any order from your Orders dashboard and look for the Activity tab on the order detail page. It sits alongside the order's other tabs, such as content and messages.

Buyers, publishers, and Serpverse support staff all see the timeline on the same order — each from their own dashboard, but reading the identical sequence of events. You do not need to enable anything; the timeline is built automatically from the order's history the moment the order is created.

How to Read Order Progress at a Glance

Each timeline entry has three parts that tell you what happened, who did it, and when:

• A label describing the event, such as "Content published" or "Revision requested"
• An actor — whether the buyer, the publisher, or the system performed the action
• A timestamp, grouped by day so a long order stays easy to scan

Entries are also colour-coded by tone. Completions and approvals read as positive, revision requests and warnings stand out as caution, and cancellations or chargebacks are flagged clearly. Some entries carry a little extra context underneath the label — for example, a publish event shows the live URL, and a deadline extension shows the new due date.

To understand the current state of an order, read the most recent entry at the top of the timeline. That entry reflects the latest milestone the order has reached. Everything below it is the path the order took to get there.

The Events You Will See

The timeline records the meaningful milestones in an order's life. You will not see noise like draft auto-saves or read receipts — only the moments that actually move the order forward. Here are the events, described in plain language.

Getting started

• Order placed — the buyer submitted the order. This is always the first entry.
• Order accepted — the publisher agreed to fulfil the order.
• Order rejected — the publisher declined the order; the buyer is refunded in full.
• Order auto-rejected (publisher non-response) — the publisher did not respond in time, so the system rejected the order automatically and refunded the buyer.

Content workflow

• Content submitted for review — the author (the publisher for Article orders, the buyer for Guest Posts) sent a draft for the other party to review.
• Content approved — the reviewer approved the draft, and work continues toward publishing.
• Revision requested — the reviewer asked for changes before approving. Reviewer notes appear with the entry.
• Content published — the publisher placed the content live and submitted the URL. The live link shows with the entry, and the buyer's review window begins.

Finishing the order

• Order approved — the buyer approved the published link and the order completed.
• Order auto-completed — the buyer's review window passed without a response, so the system completed the order automatically.

Deadlines and extensions

• Deadline extended — a buyer or publisher used a self-service extension to push a writing or content deadline forward. The new deadline appears with the entry.
• Deadline extended by admin — Serpverse support extended a deadline on the order.

Cancellations

• Cancelled by buyer — the buyer cancelled. Depending on the stage, a cancellation fee and the refunded amount may show with the entry.
• Cancelled by publisher — the publisher cancelled; the buyer is refunded in full.
• Cancelled by admin / Refunded by admin — Serpverse support cancelled or refunded the order, usually as part of resolving a dispute.

Auto-cancellations from missed deadlines

• Auto-cancelled (content not submitted) — a Guest Post buyer did not submit their content before the deadline.
• Auto-cancelled (revision deadline) — the at-fault party did not address a requested revision in time.
• Auto-cancelled (delivery deadline) — the publisher did not deliver by the due date.

Disputes and chargebacks

• Dispute opened / Dispute resolved — a buyer escalated the order to Serpverse support, and the timeline records when support resolved it.
• Order disputed (chargeback) / Order cancelled (chargeback) — the buyer's deposit was charged back through their bank, affecting this order.

If an order ever stalls between events, the timeline shows you exactly which milestone it is waiting on — a good first stop before reading the stuck-order troubleshooting guide.

Timeline vs Notifications vs Messages

Serpverse keeps three separate streams of information about an order. They look similar but serve different jobs, and confusing them leads to missed updates.

The distinction matters. Notifications are alerts — they tell you now that something changed, but they are tied to you as a recipient and are easy to clear or miss. The timeline is the durable record — it never disappears and is the same for both parties, so it is the source of truth when a notification has scrolled away. Direct messages are your conversation with the other party; they are not lifecycle events, so a chat message about, say, a tone preference does not appear on the timeline.

A simple way to remember it: notifications tell you to look, the timeline tells you what happened, and messages are where you talk it through.

Why the Timeline Helps

The timeline is the platform's transparency layer. Because both parties read the same history, there is no ambiguity about who did what or when. If a buyer requested a revision on Tuesday and the publisher published on Thursday, both events are timestamped on the same feed for everyone on the order to see.

That shared record is also your best evidence if a disagreement arises. When a buyer escalates an order to Serpverse support, the timeline gives the reviewing team an objective sequence of events to work from — no reconstructing the story from memory or scattered emails. Keeping your actions on the platform, rather than off-channel, means the timeline reflects the full picture.

For day-to-day use, the timeline simply saves time. Instead of opening a chat to ask for a status update, you open the Activity tab and read the top entry. That is the entire point: progress you can see at a glance, on a record you can trust.

Next Steps

Now that you can read an order's history, put it to work across the rest of the order flow:

• New to ordering? Start with placing your first order to see how the early timeline events are created.
• Need a change before approving? Learn how the revision events appear in requesting revisions.
• Choosing who to work with? A reliable publisher means a cleaner timeline — see how to find the right publishers.