The sectioned Details form on a deal

Your deal properties normally show up as one long list. Switch this on and they group into sections you name (Lead, Scoping, Details for contract, Pre Start admin tasks, Build), each one a heading you can fold away.

Along with the sections you get three things the plain list can't do: a Yes / No / N-A answer with a box to explain it, several documents attached to one field, and a line on every answer saying who filled it in and when.

Turning it on

Go to Settings → Deal properties (you need to be an owner) and tick Group the Details tab into sections.

It applies to your organisation only. Enable it before creating, importing or restoring Yes / No / N-A or multiple-document fields. Your existing values appear automatically.

Once it's on, the panel says so: Applies to every deal now. With an Open a deal link straight to one (a recent deal if there is one, otherwise the pipeline board) and a How to roll this out link to the rollout walkthrough.

Keep it on while you use those fields: the plain list cannot display their explanations and document lists. To switch back, deliberately archive any active fields that depend on the form first. Their saved answers and uploads are retained; enable the form again before restoring them. If an operator turns the feature off for the whole installation, the plain list explains which fields need it restored.

If you don't see that tick box, the form isn't switched on for this installation yet. Ask whoever runs your Summit Hub.

Setting this up over a list of fields you already have? Rolling the sectioned Details form onto deals you already have walks through it in order: sections, retiring what you don't want, ordering, and the lead-capture autofill.

Giving a field a section

Edit any deal property (or add a new one) and fill in Section. Anything you type there becomes a heading; every field sharing that heading appears under it.

• Start typing and it will suggest the sections you already use, so a typo doesn't quietly create a second heading with one field under it.
• Leave it blank and the field sits in an Other details group at the bottom. Nothing ever disappears just because you haven't sectioned it yet.
• Sections appear in the order of the fields inside them, so a field near the top of your list pulls its section to the top. Settings → Deal properties is where you arrange both. See Putting them in order.

The field types

Everything you could pick before still works the same way. Two are new:

| Type | What you get on the deal | |---|---| | Yes / No / N-A (with explanation) | Three buttons, plus a box underneath for the detail: *Architect chosen?* → Yes, "Hansen Architects". You can also attach documents to the answer. | | File uploads (several) | A list of documents on one field, rather than one. Good for "Signed contract" where there are two to keep. |

N/A counts as answered. A checklist that can never reach the end because two items don't apply is a checklist people stop trusting.

If deals already hold something under that name, you can't give it either of those two types. You'll be told which values are in the way. Neither type has anywhere to show a note somebody typed into the old Details editor, so the first Save on that deal would quietly replace it. Clear those values from the deals first, or give the new field a different name.

Use Clear answer to return a question to unanswered. Its explanation and documents stay in place.

Attaching documents

Fields of type File upload and File uploads (several) always show a file picker. Yes / No / N-A properties show one too, unless you switch it off (see below). Uploaded documents are listed with a link, and staff can open them from the deal.

Choosing which properties take documents

Edit a Yes / No / N-A or Tick box property in Settings → Deal properties and you will find three settings under the type:

• Allow document uploads. On by default for Yes / No / N-A, so nothing changes for the properties you already have. Switch it off where a document makes no sense. Tick boxes start off; switch it on where a task needs a document, such as a signed form. Other types (text, dates, dropdowns and so on) never take documents, and the file types always do.
• When to show the upload box. *Always*, or *Only when the answer is Yes* (for a tick box, *Only when ticked*). With the second choice the upload box appears once the answer is Yes, and until then the card says Answer Yes to attach a document. It is only about what you see: you can still add a document before answering, and Summit does not reject one because of the current answer.
• Upload prompt. Your own words on the upload box, such as *Upload signed agreement*, instead of *Attach a document*. File properties can have one too.

Turning uploads off never hides anything. Documents already attached stay on the card, and you can still remove them. You just can't add more.

These three settings are not part of the export and import file. An import leaves them as they are on fields you already have, and new fields start with the defaults above.

Each file can be up to 20 MB, with up to 20 documents per field for multiple-document fields and Yes / No / N-A answers. Remove one to make room when you reach the limit. Save and document removal wait until an upload finishes. If an upload fails, choose Retry upload or select another file.

Remove takes the document off the field. It does not delete the file: a mis-click should never destroy the only copy of a signed contract.

A single-document field shows whatever the deal record currently holds, even when that document was attached from somewhere other than this form, so a change made elsewhere is never hidden behind a stale copy here, and saving the form does not undo it. If the record holds something on such a field that is not a document at all, the field says so and refuses to save until you attach one; that stops a Save from quietly replacing a reference somebody meant to keep.

An automation cannot fill a File uploads (several) field: documents are attached here, on the deal. Pick one in a workflow's *Set property* step and it says so rather than offering a box to type into.

Collapsed sections

Every section starts collapsed, showing just its heading and progress count. Click a heading to open it. Summit remembers which sections you opened or closed, in that browser, and keeps them that way on every deal.

One property per row, each in its own box

Every section looks the same: one property per row, at every screen width, and each property sits in its own box. A section that mixes dates, text, dropdowns and Yes / No / N-A questions no longer leaves half-empty rows. Properties do not fold away on their own. Only sections fold.

Section status

Each section heading shows Complete, Partial or Incomplete, with a green, amber or red dot beside the word. It is Complete when every property in the section is answered, Incomplete when none are, and Partial in between.

What counts as answered:

• Yes / No / N-A: any of the three. N/A counts as answered.
• Tick box: only when ticked. An unticked box is not answered.
• File upload and File uploads (several): at least one document attached.
• Everything else: anything other than a blank.

Checklists

Section headings distinguish completed tasks from answered questions. Tick boxes count once ticked, for example 3 / 8 completed. Yes/No/N-A questions count any answer, including No and N/A, for example 5 / 8 answered. Mixed sections show both counts separately: answering No does not mean a task is complete.

Saving your work

The save bar stays within reach and shows Unsaved changes after you edit an answer or change its documents. Press Save to keep them together; an uploaded document appearing in the list does not mean the field has been saved yet. Leaving through an app link, or with your browser's Back or Forward button, asks first while changes or uploads are pending: Stay here keeps your edits, Leave page discards them and carries on to where you were going. Reloading or closing the tab still shows your browser's own warning. If the form cannot load, use Retry. A failed save keeps your edits so you can try again.

Who filled it in

Every answer you change records your name and the date, shown under the field. Each section heading also shows the most recent one: *Last filled by Roshean O'Connor on 1/9/2026*.

Pressing Save on a card where you changed nothing doesn't touch any of those lines: the date means "when this was last actually dealt with", not "when someone last had this screen open". Save only sends the fields you actually edited, so answering one question can't overwrite what a colleague saved in a different one while you had the deal open.

If somebody answers the same field while you have the deal open, Save stops and tells you: *Sam answered "Preliminary payment received?" while you had this form open — it now reads "No".* Nothing is saved, and nothing you typed is lost. The form quietly picks up everything else that changed in the meantime and shows their name and date under that field, so you can see whose answer you are about to replace. Press Save again and yours goes in.

Filled from a signed agreement

A project agreement can be set to file its signed copy on one of these fields once the client signs it (see *Filing the signed copy on the deal's Details form* in the customer agreements guide). When that happens the field is answered Yes (or, for a file field, given the signed PDF), the signed PDF is added beside any documents already on it, and any note is kept. Automations watching the field run as usual.

Instead of a person's name, the field says *Filled from signed agreement Pre-start agreement v2 on 8/10/2026*. The agreement's name links to its signed copy. The section heading credits it the same way. Once someone on your team changes that answer, the line goes back to *Filled by* their name.

If the agreement is later voided and nobody has touched the field, the signed copy and the Yes come back off. If it's replaced, the new version's signed copy takes the old one's place once the client signs it. The customer agreements guide has the details.

Using answers in automations

Automations can read more than a field's answer. For every field on the form, a Check a deal property step and the Insert field menu also offer:

• … — explanation: the note typed beside a Yes / No / N/A answer.
• … — attached documents: the file names, separated by commas.
• … — number of documents: how many attached documents can still be opened. A document field nobody has touched counts as 0.

These two are offered on the fields that take documents: file fields, a Yes / No / N/A question unless Allow document uploads is switched off for it, and a tick box only when Allow document uploads is switched on.

• … — last answered on: the date under the field. A branch can ask *is more than 14 days ago* of it. Both the date and "today" follow the timezone in Region & tax settings, so an answer given at 9am your time is dated that day, not the day before.
• … — last answered by: the name under the field.

So "the signed contract has been uploaded" is a branch on *Signed contract — number of documents* is greater than 0, and an email can quote the explanation someone gave. The date and name only move when the answer changes, as described above, so "last answered on" means when someone last dealt with it.

These details can only be read. The Set a property step doesn't offer them, because they come from the form and change when someone fills it in.

Moving a whole set of fields in or out

At the bottom of Settings → Deal properties:

• Export deal properties downloads your whole list as a file. Keep it as a backup, or use it to set the same fields up in another organisation you run.
• Import deal properties takes a file like that and shows you what it would do before anything happens: how many fields it would create, how many it would update, how many are already right, and a field-by-field list of changes with their old and new values, including any type conversions. Nothing is applied until you press Apply import.

An import never deletes anything, and it only ever changes an existing field's *type* in a direction that keeps every answer already saved, the same two widenings Edit offers, described in full under deal properties: Single-line text into Multi-line text, and text, a tick box or a dropdown into Yes / No / N-A. For that second one it checks your deals first: if even one of them holds something other than Yes, No or N/A in that field, it stops rather than widen it, and so does a lead capture form that still asks for the field. Any other type that disagrees with a field you already have stops the import too, and nothing is written. Everything else in the file (the label, the description, the section, the order, a dropdown's list of choices, the value new deals start the field with, and whether new deals start with the field at all) is applied to a field you already have, and shows up as an update in the preview rather than "already right". A starting value has to be one the field itself would accept, so a file field can't have one: each deal's document is uploaded on the deal.

A field the exporting organisation had archived comes back archived, so restoring a backup never quietly re-offers staff something you retired. Archiving and restoring an existing field stays a deliberate choice you make in Settings: an import can't do either.

Clearing out fields you no longer want

Tick the box beside any fields in the list and press Archive selected. There's also Select all unsectioned, which picks every field you haven't given a section, handy after an import, when what's left unsectioned is exactly what you meant to retire.

Archiving never deletes answers. The field stops being offered, everything already saved on a deal stays put, and Restore brings it back.