Your first submission

Follow one team from first sign-in to final handoff.

Understand the destination before learning the buttons.

Think of the last answer your team struggled to trace.

Know why evidence and review matter as much as prose.

Use the example to follow the workflow, not as clinical advice.

Recognize which parts you will replace with your real project.

Check the selected organization before opening a project.

Know where the project and its documents belong.

Identify which source supports the field you need to answer.

Separate source evidence from your own explanation.

Describe the submission question in your team's own terms.

Understand what makes a source relevant to this question.

Read the field and its guidance together.

Know what a satisfactory answer needs to cover.

Keep template authoring and submission work distinct.

Know which document your edits will change.

Do not treat a visible suggestion as a saved answer.

Know exactly when the document changes.

Move forward only when the previous handoff makes sense.

See how each later chapter fits the bigger picture.

Choose the path that matches why you came to Dossier.

Avoid creating an unnecessary organization just to accept an invitation.

Begin with signup; inspect plans when you need more capacity.

Know which organization you are creating.

Choose Continue with Google and your intended account.

Return with the same identity you selected.

Finish email verification rather than stopping at account creation.

Reach the organization entry step with verified identity.

Confirm the organization's name before creating it.

See the intended organization selected after setup.

Read which email the invitation expects.

Avoid accepting with a convenient but wrong Google account.

Stay in the invitation path rather than independent team signup.

Reach the invitation decision without creating a separate organization.

Choose after checking the organization and invited identity.

Know whether you actually became a member.

Create your own organization only when you actually need one.

Keep one account with distinct memberships.

Check the organization name if expected projects are missing.

Find the original work without recreating it.

Assign responsibilities and the permissions needed to carry them out.

Do not assume the title Reviewer automatically enables comments.

Invite using the address the teammate will actually sign in with.

The invitation is addressed to the right person.

Check invitation status rather than assuming email delivery completed onboarding.

Distinguish pending invitations from active team members.

Check both when a teammate cannot do their assignment.

Understand why joining may not expose every project.

Grant only the access their work needs.

The teammate sees the correct project and available actions.

Give a commenting reviewer the required rights, not just a Reviewer label.

Know who can change the deliverable.

Use a group for a meaningful team, not to bypass permissions.

Understand how the group gives a person project access.

Consider everyone assigned before changing a role.

Expect access changes beyond the current settings screen.

Resolve the organization's capacity, then use the pending invitation.

Do not create duplicate accounts as a workaround.

Ask the teammate to open the project and locate their task.

Move on with a functioning team, not assumed access.

For our example, create a Canadian treatment project with CDA-AMC alignment.

Know why the project exists.

Check Canada and CDA-AMC for this example.

Avoid choosing a convenient but unrelated form.

Decide what evidence and form the project needs.

Do not mistake absence of sample content for lost data.

Use a title teammates can recognize in the Autofill selector.

Select the intended PICO later without guessing.

Use the project's actual research question, not invented clinical criteria.

A teammate can recognize a relevant study population.

Describe the comparison the submission needs.

Avoid retrieving relevant-sounding but mismatched evidence.

Specify the outcomes and time horizon your team needs.

Know what a useful source passage must address.

Read the PICO even when it says Complete.

Avoid looking for an extra Final button before Autofill.

Match the selected context to the field you are answering.

Do not assume the last PICO used is always the right one.

Coordinate edits to the same PICO section.

Continue with a saved, understood question.

Collect the real source files before starting AI work.

Recognize your source, not just its filename.

Upload the CSR and economic paper in our example.

Find them in the correct project's source list.

Check every selected file's classification before confirming.

Avoid a batch of differently typed documents labelled alike by accident.

Open the uploaded source and verify it is the intended report.

The document identity and visible content make sense.

Choose Prepare for AI when the source is useful for drafting.

Understand why an uploaded source may not yet be usable by Autofill.

Choose Start preparation or Not now after reading the quote.

Make an informed preparation decision.

Use the displayed stage, progress and details to understand what is happening.

Distinguish active work from a finished source.

Return to the same source rather than reuploading it to check progress.

Find its final Ready or reported problem state.

Inspect Usage & limits if a quote cannot start.

Do not confuse storage, preparation pages and drafting usage.

Verify Ready before the first Autofill run in this walkthrough.

Pass a usable, understood source to the drafting stage.

Choose the form that matches the submission.

Open a project-specific working document.

Check whether you are authoring a template or filling a submission.

Avoid changing the wrong document.

Mark meaningful fields and name them clearly.

The submitter can recognize each question.

Enter ordinary guidance beneath the field name.

A newcomer can explain what answer is expected.

Choose the editing surface that represents the content faithfully.

Formatting is preserved rather than silently flattened.

Preview the form after authoring important fields.

Check that the intended guidance can actually be understood.

Select the study-design field for the first worked answer.

Know which field the next action will affect.

Read the guidance before generating or typing an answer.

Stay oriented in the submission while understanding the question.

Respect the field's intended type.

Avoid forcing a paragraph into a date or checkbox.

Check all three before generating.

The team knows where the answer will go.

Choose Autofill for this selected field.

Know what you will compare the result against.

Choose the Ready CSR for our study-design example.

Do not expect evidence from unselected sources.

Confirm both selectors before generating.

The offer will be based on the request you intended.

Generate only after those inputs agree.

Understand why two different fields may produce different results from one source.

Observe the generation state instead of repeatedly starting it.

Wait for a result or an explicit reported problem.

Read the full suggestion in the Autofill panel.

Distinguish proposed content from accepted document content.

Inspect the cited passage and relevant original context.

Confirm figures, population and study attribution.

Determine which case you have before taking the next action.

Do not force the CSR to invent a missing fact.

Use the action matching what you want to stop or decline.

Know what will remain in Word.

Inspect offers and any fields without support.

Do not treat generation completion as a finished submission.

Compare the suggestion with guidance and source evidence.

Know what you would keep and change.

Edit the visible suggestion before applying it.

The proposed answer reflects your intended wording.

Use full Word review for richer formatting or native citation work.

Know that you are editing a draft, not yet the parent answer.

Read the discard or close message in its actual context.

Know whether the answer was ever applied.

Use the apply action and wait for Saved.

See the answer in the actual field.

Choose placement, or Cancel if uncertain.

Avoid replacing useful prior work by habit.

Read the replacement choice before confirming.

You genuinely intended to remove the earlier answer.

Choose Add after existing answer when you intend to preserve both.

Build a combined answer through explicit reviewed applications.

Use the built-in apply action when retaining evidence association matters.

Do not promise provenance from a plain text paste.

Read the final save state before leaving or exporting.

A teammate can reopen the intended answer.

Select a filled prose field you actually want to refine.

Know what content will be summarized.

Choose a writable, filled prose field.

Understand why Summarize may be unavailable elsewhere.

Prefer applying supported suggestions through the normal workflow.

Do not expect unreferenced text to gain invented support.

Choose Summarize field and wait for its result.

Keep the original answer until you choose to replace it.

Read the original and draft with those three checks.

Know whether the draft preserves what matters.

Check a flagged number or term in context.

Do not blindly accept or blindly dismiss a warning.

Choose the result that best serves the field.

Remember that declining is not a failed workflow.

Use the review result, not the old warnings from before your edits.

Accept only the version you have actually reviewed.

Choose Replace field text deliberately and confirm Saved.

Do not expect both full original and summary in the answer.

Review the accepted answer as part of the whole document.

Continue with a clearer, defensible draft.

Check all three, not just a visible citation number.

A reader can follow the evidence trail.

Use the Zotero setup and its personal API-key instructions.

Your library is available to your signed-in account.

Add the source to Zotero if you want to select it manually there.

Do not assume upload imported bibliographic metadata into Zotero.

Check the caret, then choose Add Citation.

The citation belongs to the intended claim.

Inspect the item rather than selecting the first plausible result.

Avoid citing the wrong article about a similar treatment.

Use the style required for this deliverable.

Do not confuse changed formatting with changed evidence.

Use the action matching the document's state.

Confirm there is one intended generated list.

Correct the record rather than treating the rendered list as permanent prose.

The next refresh still gives the intended reference.

Use the PICO toolbar rather than expecting Word's ribbon inside it.

Reopen the PICO and recognize the citation.

Check leftover examples, missing metadata and source mismatches.

A reviewer can trace the important claims.

Share the existing deliverable with the intended team.

Everyone knows which document is authoritative for the work.

Use the right presence surface for the question you are asking.

Do not assume Online means reading your current field.

Comment on the actual claim rather than posting an unlocated complaint.

The writer knows which content the feedback concerns.

Read the revision before resolving its discussion.

The concern is addressed, not merely hidden.

Use the correct surface for reading history versus editing comments.

Avoid expecting the Activity projection to be a second Word editor.

Assign the review or drafting responsibility to a real person.

Someone knows they own the next action.

Open the notice and check the destination.

Continue the relevant work rather than only clearing a badge.

Divide section ownership or communicate before overlapping edits.

Do not assume every text surface merges like Word.

Read the actual status before leaving or exporting.

Know which work is confirmed saved.

Discuss unresolved concerns explicitly.

The team knows whether it is a draft or approved for release.

Review the form against the actual submission requirements.

Know what still needs human completion.

Review examples and placeholders in the actual document.

Do not mistake sample reference entries for your generated bibliography.

Refresh where needed, then inspect the result.

No unresolved citation issue is hidden by a green save indicator.

Inspect review state and any information inappropriate for handoff.

The file represents the version your team intends to share.

Do not export around an unresolved save problem.

Know the latest intended changes are stored.

Use More document actions → Export DOCX or Export PDF.

Choose the required output format.

Wait for completion and download; you can return to exports later.

Have an actual downloaded file, not just an export request.

Open the DOCX/PDF and check important pages.

Catch problems before handing over the file.

Use your team's approval and submission process.

Know who approved which version.

Begin your real project—or revisit any chapter where the handoff is unclear.

Remember: Uploaded ≠ Ready. Suggested ≠ Applied. Filled ≠ Approved.