The reporting file — where your work exists
Anything not in the reporting file did not happen. Learn it before you have anything to report.
Two sheets
Talent flow holds the rules and the creator terms. Reporting holds one block per cohort, 30 rows each.
Columns and who fills them
Link to profile — you. Shopable content — you (Shopable / Mix / No shopable). Approved status — Trendweave (Waiting approve / Approved / Declined). Connected status — you (Connected and answered / Connected but no answer / Not connected). Registration status — you (Registered / Not registered). Contract status — you (Contracted / Not contracted). 1st, 2nd, 3rd calendar month and "4th and more" — you, verified by Trendweave (Did all / Did partially / Didn't / No data).
How milestones are read from the file
Approved = rows marked Approved. Contacted = Connected and answered + Connected but no answer. Registrations = Registered. Contracts = Contracted. A contract month = Did all.
Rhythm and proof
Fill the file as you go, not on Sunday night. Trendweave reviews on Monday and confirms the week's payout. On the 1st Trendweave verifies the closed month for every contracted creator and confirms the bonus or revenue share. Trendweave verifies from the profile link, your screenshots and the platform record — keep screenshots of every conversation in your shared folder.
Key takeaway: What is not in the reporting file did not happen and is not paid. Fill it daily; Trendweave verifies on Monday and on the 1st.
Next step: Fill row 1 now. Then Lesson 7 — the last one before the exam.
- Learning outcome
- You know every column of the reporting file, who fills it, and how each milestone is counted from it.
- Action in product
- Fill row 1 of Cohort 1 with a real candidate: profile link and Shopable / Mix / No shopable.
- Success metric
- Row 1 filled correctly.
- Unlock / Reward
- Lesson 7 — Red lines.
- Format
- Guide.