100 Questions to Ask Before Accepting a Collaboration

No.	Item	Definition
1.	Are expenses covered?	Asks about reimbursements.
2.	Are indemnity terms included?	Checks legal risk transfer.
3.	Are meetings required?	Checks meeting expectations.
4.	Are there blackout dates?	Identifies unavailable periods.
5.	Are there compliance needs?	Checks regulatory requirements.
6.	Are there confidentiality terms?	Asks about secrecy obligations.
7.	Are there hidden costs?	Checks unexpected expenses.
8.	Are there legal issues?	Checks legal concerns.
9.	Are there security requirements?	Asks about security standards.
10.	Can deadlines move?	Checks schedule flexibility.
11.	Can I bring in a partner?	Checks co-creator permission.
12.	Can I review the contract?	Allows legal review time.
13.	Can I show it in my portfolio?	Checks portfolio permission.
14.	Can I speak to past partners?	Checks references.
15.	Can I use the work later?	Checks future usage rights.
16.	Can I work remotely?	Checks location flexibility.
17.	Can the terms be revised?	Asks about changes.
18.	Do I need to sign an NDA?	Checks for nondisclosure agreement.
19.	Do we need outside help?	Checks for external support.
20.	Does this align with my values?	Checks personal fit.
21.	Does this fit my brand?	Checks reputation fit.
22.	Does this fit my goals?	Checks strategic fit.
23.	Does this fit my schedule?	Checks availability.
24.	Have you done this before?	Checks prior experience.
25.	How fast is feedback?	Sets feedback timing.
26.	How is data handled?	Checks data practices.
27.	How many revisions are included?	Sets revision limits.
28.	How much time will this take?	Estimates workload.
29.	How often will we check in?	Sets meeting frequency.
30.	How will conflicts be handled?	Plans dispute resolution.
31.	How will I be credited?	Specifies credit format.
32.	How will I be paid?	Clarifies payment method.
33.	How will success be measured?	Defines evaluation metrics.
34.	How will we communicate?	Sets communication channels.
35.	Is exclusivity required?	Asks about exclusive commitment.
36.	Is ongoing support expected?	Checks continued involvement.
37.	Is overtime expected?	Asks about extra hours.
38.	Is the compensation fair?	Assesses fairness.
39.	Is there a contract?	Checks for a formal agreement.
40.	Is there a kill fee?	Checks cancellation compensation.
41.	Is there room to negotiate?	Checks flexibility on terms.
42.	Is this worth my time?	Evaluates value.
43.	Is this worth the pay?	Compares effort and pay.
44.	Is travel involved?	Checks travel needs.
45.	What access do I need?	Identifies needed permissions.
46.	What are the brand guidelines?	Asks about style rules.
47.	What are the constraints?	Defines limits.
48.	What are the deliverables?	Lists expected outputs.
49.	What are the dependencies?	Reveals outside requirements.
50.	What are the goals?	Clarifies the collaboration’s purpose.
51.	What are the milestones?	Breaks work into stages.
52.	What are the must-haves?	Lists essential elements.
53.	What are the nice-to-haves?	Lists optional extras.
54.	What are the risks?	Identifies possible problems.
55.	What assumptions are we making?	Surfaces hidden expectations.
56.	What counts as a revision?	Defines revision scope.
57.	What does success look like?	Establishes success criteria.
58.	What exactly is expected?	Clarifies required deliverables.
59.	What examples do you like?	Reveals preferences.
60.	What failed before?	Learns from past issues.
61.	What file types are required?	Clarifies technical deliverables.
62.	What format is needed?	Specifies output format.
63.	What happens if plans change?	Prepares for changes.
64.	What happens if scope grows?	Addresses scope creep.
65.	What if I need more time?	Checks flexibility.
66.	What if we disagree?	Tests conflict process.
67.	What if you need changes late?	Addresses late requests.
68.	What is my role?	Defines your responsibilities.
69.	What is the approval process?	Explains review steps.
70.	What is the budget?	States available funding.
71.	What is the deadline?	Confirms the final due date.
72.	What is the end date?	Confirms project ending.
73.	What is the payment rate?	States compensation amount.
74.	What is the review timeline?	Schedules review stages.
75.	What is the scope?	Sets the project’s boundaries.
76.	What is the start date?	Confirms project beginning.
77.	What is the timeline?	Shows the project schedule.
78.	What is your track record?	Assesses experience.
79.	What message matters most?	Prioritizes key point.
80.	What problem are we solving?	Defines the core challenge.
81.	What quality standard applies?	Sets expected quality.
82.	What resources are provided?	Lists support and materials.
83.	What should be avoided?	Identifies no-go areas.
84.	What time zone are we using?	Aligns scheduling.
85.	What tone do you want?	Clarifies desired voice.
86.	What tools will we use?	Names required platforms.
87.	What worked last time?	Finds proven approaches.
88.	When will I be paid?	Confirms payment timing.
89.	Who approves the work?	Identifies approver.
90.	Who decides what?	Defines decision-making authority.
91.	Who gives feedback?	Identifies reviewers.
92.	Who is involved?	Identifies all key participants.
93.	Who is the audience?	Defines intended recipients.
94.	Who is the main contact?	Identifies primary communicator.
95.	Who owns the copyright?	Defines copyright control.
96.	Who owns the work?	Clarifies ownership rights.
97.	Why me?	Shows why you were chosen.
98.	Why this collaboration?	Reveals the reason for partnering.
99.	Will I get credit?	Confirms attribution.
100.	Will sensitive data be shared?	Flags privacy concerns.