AutoNexit Training 3 min readAT-03

Write project notes your team can find and use

Share

A useful note answers a question that someone will ask later. Instead of writing Meeting notes, try Why we moved the sensor. Give the reader the decision and the reason without making them reconstruct a chat conversation.

A short example

For a sensor relocation, record the old position, the obstruction found on site, the agreed new position and who will check it. Attach a marked-up photo if it helps. If there is work to do, create a task rather than leaving the action buried in the paragraph.

Choose the right place

  • Open the intended project’s Notebook. Keep routine technical notes separate from restricted commercial notes.
  • Create a folder when several pages share one subject. A single isolated note does not need an extra folder.
  • Decide whether the page needs restricted access before attaching confidential material.
A specific title makes a decision easier to find later.
Notebook page and editor

A specific title makes a decision easier to find later.

Create and organize the page

  1. 01

    Choose New page. To place it inside a folder, use that folder’s add-page action.

  2. 02

    Enter a specific title, then write what happened, why it matters and the next action. Use a small table only when the information is easier to compare in rows.

  3. 03

    Add a relevant image or supporting file and wait for the upload and save indicators to finish.

  4. 04

    Use the three-dot menu to rename or manage access. In access settings, leave checked the members who may see the note; project managers retain access.

  5. 05

    Search for a distinctive word from the title and reopen the page to check the saved result.

Keep the next action in a task instead of burying it in prose.
Tasks beside project notes

Keep the next action in a task instead of burying it in prose.

Read it as if you were new to the job

Could another engineer explain the decision after reading the page once? Add the missing reason, date or reference if needed. You do not need to repeat the project’s entire history in each note.

Keep work and access clear

  • If simultaneous edits create a conflict, compare the versions before saving; do not discard a colleague’s text blindly.
  • For files with a formal revision history, use Revision control. An attachment in a note is supporting material.
  • A restricted note and its descendants are excluded from the Project Passport. Check access deliberately rather than relying on a vague title to hide information.

Frequently asked questions

Will moving a page into a restricted folder affect access?

Parent-folder restrictions also apply to the page. Review the destination before moving shared material.

Can I correct a typo in the title later?

Yes. Renaming changes the page’s label; it does not require a second copy of the note.

Can an absent page mean it was deleted?

Not necessarily. Search filters, the archive or your permissions can also explain why you cannot see it.

Should I put passwords in a note?

No. Use your organization’s approved secret-management process instead of project text or attachments.

Related articles