The Gold Standard of Anthropology | Mandate Changes, Role Renegotiation and Consent to a Narrower Return

1. Compare the old mandate with the work that now exists

Back to contents

Begin with two short descriptions: what the panel was originally asked to do and what decisions now remain. List changes in purpose, deliverables, audience, data access, timetable, governance and risk. A label such as advisory member can hide a large shift from commenting on interview questions to approving a public data release. Separate decisions already closed from decisions still open. If the project has moved beyond the stage where the returning person could exercise the promised influence, say so plainly. The aim is not to make the revised mandate sound attractive. It is to give the person an accurate basis for deciding whether any present role still fits.

2. Treat a narrower return as a legitimate form of participation

Back to contents

A returning partner may be willing to review two documents but not resume monthly meetings, represent a whole community or handle identifiable records. That is a scope decision, not evidence of weak commitment. Offer components that can stand on their own: agenda review, language checking, interpretation of findings, governance voting or public communication. State which combinations are feasible and which would create unsafe gaps. Do not attach full-member obligations to a small task after acceptance. A narrower role should have a clear start, endpoint and route to decline further work. The person can later expand the role through another explicit conversation; silence or good performance does not enlarge it automatically.

3. Explain why the mandate changed and who authorised it

Back to contents

Mandates can change because funding is reduced, methods fail, new evidence appears, community priorities shift or a regulator requires a different pathway. Record the reason and the authority behind it. A project team should not present its own convenience as an unavoidable external rule, and a funder request should not erase community governance. Identify whether the change was discussed with current partners, whether objections were recorded and whether any collective approval is still required. This history matters because a returning member is deciding not only about tasks but about the legitimacy of the process that produced them.

4. Build a role card that can be accepted or refused

Back to contents

A role card turns a vague invitation into a testable offer. It should name the purpose, tasks, estimated time, meeting pattern, information access, decision rights, privacy conditions, payment, acknowledgement, support, term and exit route. It should also state what is outside the role. Use ordinary language and allow edits before agreement. The card is not a substitute for conversation, but it prevents later claims that an undefined expectation was always implied. If several roles exist, show them side by side rather than steering the person toward the broadest one. Keep a dated copy so future scope changes can be compared with what was actually accepted.

5. Renegotiate authority, access, compensation and credit together

Back to contents

A smaller workload does not always mean less decision authority. A member who reviews only youth-facing materials may still need veto power over identifiable quotations. Match access to the task, but do not withhold the information required to exercise a promised right. Recalculate payment for preparation, meetings, care or travel burdens and specialist knowledge; do not use the word volunteer to bypass an earlier compensation standard. Clarify authorship, acknowledgement and the right to remain unnamed. These terms interact. A person cannot make a meaningful decision without relevant information, and credit cannot compensate for authority or pay that was removed without agreement.

6. Worked example: a youth panel after a project pivot

Back to contents

A youth advisory panel originally helped design school interviews. During one member’s six-month absence, the project pivots to a public toolkit and a restricted archive. Staff first invite her to return as a full panel member, which would include archive-governance meetings she does not want. They then prepare three role cards. She chooses a four-week role reviewing the toolkit’s youth-facing language, with access to the draft and meeting notes, payment for six hours, the right to reject her earlier quotation and no duty to represent other students. Archive decisions remain with the continuing governance group. The narrower return succeeds because the boundaries, rights and endpoint are explicit; it is not disguised full membership.

7. Prevent scope creep after the return begins

Back to contents

Scope often expands through small requests: one extra meeting, a quick introduction, an urgent review or permission to reuse a comment elsewhere. Use a change rule. Any new task should identify the added time, information, authority, risk and payment, then ask for a separate yes or no. Make declining easy and do not treat prior helpfulness as consent. A short check-in after the first task can ask whether the role matched the card, whether access was sufficient and whether any pressure was felt. Repeated informal additions are evidence that the mandate was never genuinely narrowed.

8. Changed-context transfer check: an Indigenous digital archive

Back to contents

An Indigenous archive project changes from local cataloguing to training an automated search system. A former adviser offers to return only to review public descriptions. The transferable method is to compare mandates, define the bounded task and secure a fresh decision. The changed context adds collective authority: one person’s consent cannot authorise model training on community-controlled material or override cultural access rules. The role card must distinguish review of public labels from governance of restricted records, and the archive may need a community decision before either activity proceeds. A narrower individual return does not narrow the project’s obligations to the community.

9. Know the limits and common misconceptions

Back to contents

Role renegotiation does not repair every breach, and a signed role card does not prove that the choice was free. A person may accept limited work because of financial pressure, loyalty or fear of losing future opportunities. Narrow participation should not be used to display diversity while excluding the person from decisions that affect the contributed knowledge. Nor should a project promise authority over matters that are already legally, contractually or collectively fixed. Human-subject regulations may not apply to every advisory relationship, but clear information, voluntariness and freedom from penalty remain useful ethical checks. Local governance, employment and research requirements still need specific review.

10. Audit the mandate-to-role pathway

Back to contents

Retain the former and current mandate, reasons for change, approval route, outstanding decisions, invitation, role options, questions, selected boundaries, compensation, access, credit and later amendments. Record refusals without demanding personal explanations. Compare actual requests and meetings with the accepted role card. Note whether optional work became routine, whether promised information arrived before decisions and whether the person could leave or narrow the role again. Keep private reasons and conflict details under restricted access. An independent reviewer should be able to see that the narrower return was real without learning information the partner did not authorise for circulation.

11. Frequently asked questions

Back to contents

Can a returning member resume only one task? Yes, when that task can be bounded honestly and supported with the required rights. Must the old mandate be formally cancelled? Record what ended, what continues and who authorised the change. Does a smaller role require lower pay? Pay should follow time, burden and expertise rather than status alone. Can the role expand later? Yes, through another explicit agreement. What if the project needs full participation? Say so before acceptance and allow the person to decline. Does attendance mean agreement with the new mandate? No. Attendance, access, voting, quotation use and future work are separate choices.

12. The gold standard lets commitment become specific

Back to contents

A project earns trust when it can describe what changed without recruiting the person into repairing the project’s own uncertainty. The gold standard compares old and new mandates, offers bounded roles, joins workload to practical authority and records every later change. It makes a narrower return visible as a legitimate choice, not a temporary step toward obligations the person already refused. Participation remains meaningful because the partner can see the work, influence the promised decisions, receive fair recognition and stop again without penalty.