Guides

Guides in the order to read them

New users can find the guide for their job and work in order. Each guide lists the steps to follow, the check that shows you have finished, and a plain note on the record you keep for review.

Getting started

Work through these guides in order to go from sign in to a first weekly change set that is ready to publish.

  1. Start your first publication

    Create a publication, add a chapter from a template, invite an editor and a reviewer, and prepare a first paragraph for review.

    Read the guide

  2. Write a typed paragraph

    Choose a type, write the text, add geography and chart numbers, and save a draft with a reason.

    Read the guide

  3. Send a paragraph for review

    Select paragraphs, assign reviewers, set a due date and a message, and send the review.

    Read the guide

  4. Approve a paragraph

    Read the paragraph in context, resolve comments, accept or reject suggestions, and record an approval with a reason.

    Read the guide

  5. Build a weekly change set

    Collect approved paragraphs, run checks, compare the set with the last edition, and lock the set.

    Read the guide

  6. Publish an edition

    Choose PDF, web pages or JSON, run the checklist, preview the output, publish, and confirm the files produced.

    Read the guide

  7. Report a change and check the status

    Send a report as a mariner or field unit, keep the reference code, and check the status with that code and a contact detail.

    Read the guide and check a report status

Guides by role

Pick the guide that matches your role. Each person sees only the work assigned to them and only the actions their role allows.

Nautical editor

Write typed paragraphs, add geography and chart numbers, save with a reason, and send work for review. Start with Write a paragraph and Send a paragraph for review.

Reviewer

Open an assignment in context, leave a comment or suggest replacement text, and mark the review done. A reviewer comments only and cannot change the live paragraph.

Approver

Read the final text and history, accept or reject each suggestion, and approve or return the paragraph with a reason. No paragraph publishes without that record.

Publication manager

Plan editions, collect approved paragraphs into a weekly change set, run checks, lock the set, and publish PDF, web pages and JSON. Start with Start your first publication and Build a weekly change set.

Field unit

Send a change report tied to a paragraph or an area, add location and chart detail, and check the status of your own reports in plain words.

Mariner reporter

Report a change without an account, keep the reference code you receive, and check the status with that code and the contact detail from the form.

Glossary

Plain definitions for the words used in the guides and in the app.

Typed paragraph

A single nautical statement stored once with a type, geography and chart numbers. The type can be aid to navigation, hazard, anchorage, bridge and cable, regulation, general, caution or note.

Chapter

A named part of a publication that holds an ordered list of paragraphs. A chapter keeps a stable identity when paragraphs are reordered.

Edition

A named release of a publication that freezes the exact versions of approved paragraphs it contains. A published edition is locked.

Weekly change set

A smaller release that gathers the approved paragraph changes for the week and publishes them as one unit. A correction to a published set creates a new set.

Change request

A report from a mariner or field unit that links to the paragraphs it changes. The sender can check its status with a reference code.

Approval and snapshot

An approval records an approver, a decision, a reason and a date. A snapshot records the exact paragraph versions used for one output so it can be reproduced.

Questions reviewers and auditors ask

Short answers that link to the guide where the step is explained.

What must happen before a paragraph can publish

The paragraph needs a type, geography and chart numbers before it can move to in review. A reviewer must check it and an approver must record an approval. The edition or weekly set that contains it must then pass checks. See Approve a paragraph and Build a weekly change set.

Who can change what

Editors can edit paragraph text. Reviewers can comment and suggest. Approvers can record a decision. Publication managers can plan editions and publish. A person cannot approve their own edit in the normal flow. Roles are set in People and access and each person signs in with their MAJIC account.

What record is kept

Every save records who saved it, when and why. Every approval records the approver and date. Every edition records the exact paragraph versions it contains, and every publish records the snapshot used. Activity shows who created, changed, approved or published an item and when.

What the public can see

The public reader portal shows only approved paragraphs in a published edition. Draft, in review and returned text is not reachable by public link, search or download. See Features and Accessibility.

Start with a sample chapter

Ask for a walkthrough and bring a sample chapter so the team can show editing, review, approval and review on your own work.

Request a demo