Decide who the report is for
An owner wants to know how the business performed and what needs attention. A team lead needs the group's progress and blockers. An employee needs their own assignments and goals. Those audiences should not automatically receive the same scope or financial detail.
A useful report leads with a conclusion, traces numbers to records, and assigns a next action to each issue. Start with that reader need rather than compiling every available metric into a long message.
Use five sections in a consistent order
Begin with an overview, then highlights, team results, employee detail, and actions required. The overview orients the reader; highlights show what is working; the next two sections explain where results came from; the final section assigns work.
Cover sales, production, publication, attendance, and account issues only where records support them. Add profit and cost to the owner's version under the intended permissions. A complete structure does not require inventing a number for every field.
A template you can adapt to your team
Title: [Business date] daily report. Coverage: orders through [date/time, time zone]; production for [work date, time zone]. Overview: [order count], [GMV and currency], [selling accounts], [completed edits/target], [verified publications], and [attendance coverage]. Owner-only finance: [income], [cost], [profit], with the comparison period stated.
Highlights: [team, person, or account] and [verifiable result]. Team results: [team], [scope], [output], [orders], [assessment with reason]. Employee detail: [name], [assigned work], [completion], [publication verification], and relevant attendance information.
Actions: [issue], [evidence], [owner], [deadline], [status]. Use 'pending sync,' 'not configured,' or 'not available' where appropriate. These are placeholders for your records, not sample customer results.
Label US business dates and staff work dates separately
For a China-based team selling in the US, financial activity may use the selected US business date while attendance and editing use Beijing workdays. Name both. Publish the completed financial report after the chosen US window ends and data coverage is sufficient.
Do not compare a partial current day with a full prior day as though the difference were a decline. Missing orders, absent targets, and attendance not yet in use need status notes, not zeros. The order-date guide explains the cutoff and boundary checks.
Make the weekly report answer three more questions
A weekly report should explain what changed, which teams or accounts drove the change, and what will happen next week. Use matching completed periods and consistent scope. Seven pasted daily reports do not answer those questions by themselves.
Include recurring blockers, changes in account inventory, product concentration, and staffing changes where relevant. Carry unresolved actions into the next week with owners and dates. A short review meeting can then focus on decisions rather than reconstructing the report.
Separate the owner's view from the team lead's view
Owners may need company-wide profit and cost. Team leads generally need their own group's orders, workload, attendance, and exceptions. Apply the actual role and organization scope rather than sending the full report and hoping readers ignore restricted lines.
If you prepare reports manually, review the recipient scope before sharing. Once copied into a group conversation, financial detail cannot be made private by changing the original document. Keep employee-level information limited to a legitimate operational audience.
Generate a report from records already in Star Captain
Star Captain's team reports draw on existing order, cost, completion, attendance, publishing, and account records. The documented schedule follows completion of the US reporting day, around 3:30 p.m. Beijing during daylight time and 4:30 p.m. during standard time, with a weekly report on Monday.
The report can be copied as plain text. Owner and manager scope remain distinct, and incomplete periods carry context. The signed-in report interface currently uses Chinese. Verify feature access in team management and on the pricing page.
Use five writing habits that make reports readable
Put the main conclusion first. Emphasize a few decision-relevant numbers. Name the specific account or task behind a problem. Compare equivalent completed periods. Keep the overview short and place detailed staff records later.
Deliver the report at a predictable time and in a predictable place. A steady format helps readers spot changes. Avoid a positive or negative label without its reason: 'needs attention because three tasks await review' tells a manager what to do.
Turn the action section into follow-through
Assign account checks to account owners, approval backlogs to reviewers, and production blockers to the relevant team lead. At the next review, check whether the issue was resolved and what evidence shows completion.
Look back across several weeks for recurring patterns. Repeated late reviews may need a capacity change; persistent unknown order data may need an access investigation. Use the performance checklist to keep the financial definitions consistent while improving the process.
Frequently asked questions
What belongs in a TikTok Shop agency daily report?
Use overview, highlights, team results, employee detail, and actions required. Keep numbers traceable and tailor the scope to the reader.
When should a US-sales report be published by a China-based team?
After the chosen US business date ends and synchronization is sufficiently complete. State the cutoff and coverage instead of treating a scheduled publication time as proof of completeness.
Should every report include profit?
Include profit and cost only for the authorized audience. A team lead's report can focus on the group's sales, production, and issues without exposing company finances.
How is a weekly report different?
It explains changes, the teams or accounts driving them, and next week's actions. It also carries unresolved issues forward with owners and deadlines.
Can a Star Captain report be copied into a team message?
The report supports copying plain text. Review the recipient scope before sharing, especially when the owner's version contains financial detail.
Where do the report's numbers come from?
Existing system records: orders and operating calculations, completed-work counts and goals, attendance, publishing records, synced videos, and account status. Missing coverage should remain explicit.
Related guides
Put it into practice: Explore Team management →
